Skip to main content

Setup

Settings → Contact Center → Tickets, then Ticket Types or Ticket Statuses. Day-to-day work is the Tickets app in the main sidebar.
New workspaces receive five system statuses automatically. If the list is empty, contact developers@oration.ai. Do not try to recreate the system slugs by hand unless support asks you to.
No. System statuses cannot be archived or cloned. You can rename labels and change colors. For extra states, create a custom status.

Types and categories

Category is the behavior family: customer, back-office, or tracker. Type is a named use case inside that family, such as Refund (customer) or Fraud review (back-office). See Ticket categories.
Create a new type in the other category. Existing tickets keep the category they were created with. Cloning copies the original category.
Either it is a tracker (never shared), or it is back-office and the type has sharing off, or sharing is on at the type but the ticket’s own shared switch is still off. Assign and share explains the two levels.

Creating and working tickets

Attach at least one in progress status on the type and mark it default. New types get this automatically from system statuses; it is missing if those attachments were removed. See Statuses on a type.
Custom statuses are workspace-wide. You still have to attach them to the type. Also check the status is not archived.
A conditional attribute hid it when the controlling list changed, and the stored value was cleared on purpose. Fill it again after you pick the matching product.
No. Waiting on customer returns to in progress on customer reply. Resolved stays resolved until a teammate moves it.
No. A ticket has one current disposition. Changing it replaces the previous code and logs from → to. See Dispositions.

Clone and archive

No. Clone copies configuration only: settings, attributes, options, conditions, status attachments, and the disposition set pointer. Tickets stay on the original type.
No. The copy is a new catalog row. Attach it where you need it. System statuses cannot be cloned.
They keep the archived type or status. You just cannot pick that type on create, or that status on a move, until you unarchive (and, for statuses, keep the type attachment).

Conversations and grouping

No. A conversation is the live call or chat. A ticket is follow-up work. You can link them.
The parent must be a tracker and the member must be a customer ticket. Back-office tickets cannot be members. A ticket cannot group itself. See Tracker groups.

Still stuck?

Read Tickets overview or email developers@oration.ai.