EntitiesCore
Support Ticket
Customer support ticket entity
Customer support ticket entity
Represents support requests from members.
Fields
Field Registry (from workspace/sources/entity-registry.csv)
| Field | Input Type | Required | Notes |
|---|---|---|---|
| Support Ticket ID | Number | Required | Automatically generated by the system and locked |
| Support Ticket Subject | Text | Required | - |
| Support Ticket Description | WYSIWYG (Textarea) | Required | - |
| Support Ticket Files | File | Not Required | - |
| Support Ticket Status | Select | Required | Open, Awaiting Response, Closed |
| Support Ticket Member ID | Number | Required | Automatically pulls through based on the member who created the ticket |
| CRM ID | Number | Required | Automatically pulls into a CRM note or ticket ID based on if a CRM is connected |
| Support Ticket Type | Select | Required | Pulls through a list of different support ticket types defined in the settings |
| Support Ticket Staff ID | Number | Required | Automatically pulls through based on who gets assigned |
| Support Ticket Response | WYSIWYG (Textarea) | Required | Have a toggle 'public / non public' |
| Support Ticket Response Files | File | Required | - |
| Survey ID | Number | Required | Ref google forms |
| Survey Title | Text | Required | - |
| Survey Question Type | Select | Required | Options are: Rating, Multiple Choice |
| Survey Question | Text | Required | - |
| Survey Answer | Select | Required | Repeater field to allow for multiple choice if chosen |
| Survey List | - | Required | Datatable displaying all the members to allow the admin to select which member to send the survery to |
| Survey Close Date | Date | Not Required | - |
| Survey Status | Select | Required | Options are: Draft, Puiblished, Close - this means you need a "saft draft" option. Once it goes to published it cannot go back to draft |
Relationships
| Relation | Type | Target Entity |
|---|---|---|
| user | ManyToOne | Member |
| assignee | ManyToOne | User (admin) |
| responses | OneToMany | TicketResponse |
Features
Support Ticket
Acceptance Criteria
Frontend
- Admin/client UI can view and manage
Support Ticketrecords where applicable.
Backend / API
- CRUD operations exist for
Support Ticket(create, read, update, delete/archive).
Permissions
- Access is restricted to appropriate roles (tenant-scoped).
Business Rules
- Fields and relationships documented on this page are enforced for
Support Ticket.
Error Handling
- Invalid payloads return field-level validation errors.