Space Docs
Domain Model

Support Ticket

Fields

FieldTypeRequiredDefaultDescription
idstring.uuidYes—Id
createdAtstring.date-timeYes—Created at
updatedAtstring.date-timeYes—Updated at
workspaceIdstringYes—ID of the associated workspace
numberintegerYes—Number
subjectstringYes—Subject
statusenum(new, open, pending, on_hold, solved, closed)Yes—Status
priorityenum(low, medium, high, critical)Yes—Priority
typeenum(question, incident, problem, task, billing)Yes—Type
channelenum(portal, email, sms, chat, phone, api, internal)Yes—Channel
queueIdstringYes—ID of the associated queue
assigneeUserIdunknownYes—ID of the associated assignee user
requesterContactIdstringYes—ID of the associated requester contact
customerIdstringYes—ID of the associated customer
siteIdunknownYes—ID of the associated site
relatedSystemIdunknownYes—ID of the associated related system
relatedAssetIdunknownYes—ID of the associated related asset
escalatedTicketIdunknownYes—ID of the associated escalated ticket
mergedIntoTicketIdunknownYes—ID of the associated merged into ticket
splitFromTicketIdunknownYes—ID of the associated split from ticket
inboundEmailTokenstring,nullYes—Inbound email token
slaPolicyIdunknownYes—ID of the associated sla policy
firstResponseDueAtunknownYes—First response due at
nextResponseDueAtunknownYes—Next response due at
resolutionDueAtunknownYes—Resolution due at
firstResponseAtunknownYes—First response at
solvedAtunknownYes—Solved at
closedAtunknownYes—Closed at
firstResponseBreachedAtunknownYes—First response breached at
resolutionBreachedAtunknownYes—Resolution breached at
slaPausedAtunknownYes—Sla paused at
slaPausedMsintegerYes—Sla paused ms
lastCustomerMessageAtunknownYes—Last customer message at
lastAgentMessageAtunknownYes—Last agent message at
reopenCountintegerYes—Reopen count
aiAutonomyModeunknownYes—Ai autonomy mode
aiTokenBudgetunknownYes—Ai token budget
aiHandoffReasonstring,nullYes—Ai handoff reason
csatScoreunknownYes—Csat score
visibilityModeunknownYes—Visibility mode
sourceMetadataunknownYes—Source metadata

Create Schema

Fields accepted when creating a new record:

FieldTypeRequiredDefaultDescription
subjectstringYes—Subject
typeenum(question, incident, problem, task, billing)Yes"question"Type
channelenum(portal, email, sms, chat, phone, api, internal)Yes—Channel
priorityenum(low, medium, high, critical)Yes"medium"Priority
queueIdstringNo—ID of the associated queue
assigneeUserIdunknownNo—ID of the associated assignee user
requesterContactIdstringYes—ID of the associated requester contact
siteIdunknownNo—ID of the associated site
relatedSystemIdunknownNo—ID of the associated related system
relatedAssetIdunknownNo—ID of the associated related asset
visibilityModeunknownNo—Visibility mode
bodyMarkdownstringYes—Body markdown

Update Schema

All fields are optional when updating:

FieldTypeRequiredDefaultDescription
subjectstringNo—Subject
typeenum(question, incident, problem, task, billing)No—Type
priorityenum(low, medium, high, critical)No—Priority
queueIdstringNo—ID of the associated queue
assigneeUserIdunknownNo—ID of the associated assignee user
siteIdunknownNo—ID of the associated site
relatedSystemIdunknownNo—ID of the associated related system
relatedAssetIdunknownNo—ID of the associated related asset
visibilityModeunknownNo—Visibility mode
statusenum(new, open, pending, on_hold, solved, closed)No—Status
fromStatusenum(new, open, pending, on_hold, solved, closed)No—From status
slaPolicyIdunknownNo—ID of the associated sla policy

On this page