Skip to content

Tickets overview

Tickets turn a conversation into a piece of work your team can assign, prioritize and resolve — without losing the chat it came from.

Tickets can be switched off for a whole workspace. If you don’t see Tickets in the sidebar, the owner has disabled Enable tickets for the workspace in privacy settings.


Four entry points:

FromHow
The Tickets pageNew
A chatCreate Ticket in the chat panel’s Tickets tab
A single messageCreate ticket in the message’s action menu
An AI agentOver MCP

Creating from a message stores it as the ticket’s Source Message (marked Incoming or Outgoing), so whoever picks the ticket up sees exactly what triggered it.

FieldNotes
TitleRequired, minimum 2 characters
DescriptionFree text
Linked ChatsOne or more chats — the conversation context
Source MessageAuto-filled when created from a message
PriorityLow, Medium, High
Assign ToA workspace member, or Unassigned
DateDue date
FilesAttachments, subject to a per-file size limit and a max count per ticket
Custom ColumnsYour own ticket fields
CommentsYou can queue comments while creating — they save with the ticket

Save with Submit as {status} — the split button lets you choose which status the ticket starts in.


Default statuses: New, Open, Pending, In Progress, Blocked, Solved, Completed, Closed. Priorities: Low, Medium, High.

Both are option lists you can edit — rename them, recolour them, add your own. Changes are recorded in the activity log (Ticket status option updated, Ticket priority option created, and so on).

A closed ticket shows a Closed badge and “This ticket is closed and read-only.” Use Reopen to edit it again.


SectionContents
Ticket IDStable reference
Title / DescriptionEditable
Status / Priority / SLAInline editors, with an SLA badge
Assign ToMember picker
Created By / Created At, Closed By / Closed AtAudit fields
Last Updated
Linked ChatsAdd or remove chats; each links back to the conversation
FilesAdd file and download
Custom ColumnsYour ticket fields
CommentsThreaded team discussion

Comments support emoji and are attributable to a member. Alongside them, Entergram records every change as activity you can read back in plain English:

  • set Status to In Progress
  • changed Priority from Low to High
  • cleared Due date
  • added VIP to Segment

The same events feed Log history and Ticket analytics.


Three separate workspace toggles govern members (owners and admins always have full access):

  • Members can create tickets
  • Members can edit tickets — status, priority, fields and linked chats
  • Members can delete tickets — permanent deletion

A member without permission sees “You do not have permission to create tickets.”