Conversations / Support ticketsAll pages
Conversations

Support tickets

One ticket per request, however many calls and messages it takes. A ticket keeps the linked calls with their recordings and AI summaries, the message threads, the team that owns it, who is on it, and the discussion between colleagues.

Statuses
open · pending · resolved · closed
Priorities
low · normal · high · urgent
Links
Calls and conversations
Events
created · updated · resolved

What a ticket is

A customer rarely gets everything done in one call. They call, are put through to the wrong desk, send a photo on WhatsApp, and call again two days later. A ticket ties those pieces together under one number, so whoever picks it up next sees the whole story instead of asking the customer to repeat it.

linklinkowned byeventsCallsRecording · summaryConversationsWhatsApp · bridgeTicket #42Status · priorityTeamIT, Billing …DiscussionNotes between staffYour systemsticket.* webhooks
Calls and threads are linked, not copied: the ticket always shows their current recording, summary and messages.

The life of a ticket

Here a bank customer calls about a blocked card. The agent who answers opens a ticket from the call, Billing takes it over, the customer sends a receipt on WhatsApp, and Billing resolves it. Each step is one click in the dashboard and one webhook event for your other systems.

CustomerCustomerAgentAgentDashboardDashboardBilling teamBilling teamYour systemsYour systemsCall: card blockedrecorded, analysed1Add to ticket → Createcustomer number from the call2#42 opens with status open, priority normal, the default teamticket.created4Team → Billing, priority high5ticket.updated6WhatsApp: photo of receiptnew conversation7Link to ticket #42from the thread header8ticket.updatedchange: linked9Status → resolved10resolved_at stampedticket.resolved12
From the first call to resolved: every change is saved, audited and announced to your webhooks.

Creating tickets

Tickets are created where the work starts. Every entry point uses the same box: type a ticket number or words from its title to find an existing ticket (open and pending ones first), or press Create ticket “…” to start a new one with what you typed as its title.

FromHowWhat is linked
One callOpen the call's details on Calls and use Add to ticket.The call; the customer number is filled in from it when it is an outside number.
Several callsSelect rows on Calls and press Add N to ticket.Every selected call.
A conversationLink to ticket in the thread header.The thread; the sender's number is filled in.
By handNew ticket on the Tickets page.Nothing yet. Link calls from the ticket with Link a call.

The new ticket form

Titletextrequired
What the customer needs, in a few words. 3 to 160 characters.Example: Card activation failed after OTP
Teamteam
The team that owns it. Left empty, the organization's default team is used. Type a new name to create a team on the spot.
Prioritylow | normal | high | urgent
Defaults to normal.
Customer numbertext
The caller's number, up to 40 characters. Filled in from the call or thread; free text otherwise.Example: +92 300 1234567
Detailstext
What the customer needs and what was already tried.

Tickets are numbered per organization, starting at #1; the number is assigned inside a database transaction, so two people creating tickets at the same moment never get the same one. The ticket records who created it (their sign-in email) and when.

Fields and lifecycle

FieldValuesNotes
Statusopen · pending · resolved · closedNew tickets are open. Any status can be chosen at any time.
Prioritylow · normal · high · urgentShown as a badge in the list and on the ticket.
TeamOne of the organization's teamsFilled with the default team when none is chosen.
Assigned toAnyone in the organization, or UnassignedOnly people of your own organization can be chosen.
CustomerThe caller's numberSearchable from the Tickets page.
Title, DetailsFree textEdited in place on the ticket; saved when you leave the field.
LinksCalls and conversationsOne call or thread can be on several tickets; linking the same item twice has no effect.

Statuses

StatusMeaningCounts as
openSomeone needs to act.Active
pendingWaiting, usually for the customer or another department.Active
resolvedDone. Stamps the resolved time.Resolved
closedDone and filed. Also stamps the resolved time if it was not set yet.Resolved

The resolved time is set the first time a ticket moves to resolved or closed and kept when it moves between the two. Reopening it (back to open or pending) clears it, so the next resolution is timed again.

Teams

Every organization starts with IT, Product, Billing, Operations and Customer care; IT is the default for new tickets. The teams are created the first time anyone in the organization opens a ticket form or the Tickets page.

  • Custom teams: type a new name in any team box and choose Create team “…”. Anyone in the organization can do this; the name must be 2 to 60 characters and unique in the organization. Creating a team is written to the audit trail.
  • Filter by team: the Tickets page has an Every team menu next to the views.
  • Teams are per organization: another organization on the same installation never sees yours.

Linking calls and conversations

A ticket can hold as many calls and threads as the request needs. Linked items show up on the ticket in the order they were added.

Calls on a ticket

Each linked call shows the caller and the number called, the date, the talk time (or the outcome: no answer, busy, failed), a Recording button when the call was recorded, and the AI summary once the call has been analysed. The Recording button opens the recording on the Calls page.

  1. Open the ticket and press Link a call

    The dialog lists recent calls. Type a number or a name to narrow it down.

  2. Pick one or several calls

    Calls already on the ticket are greyed out. Up to 50 items can be linked in one go.

  3. Unlink if needed

    The × on a linked call or thread removes it from this ticket only. The call or conversation itself is not changed.

Conversations on a ticket

Threads are linked from inside the conversation with Link to ticket. On the ticket they are listed under Conversations and open the thread with a click. A ticket chip also appears in the conversation header, so people working the thread see that a ticket exists.

Working the queue

The Tickets page lists the newest activity first. Linking, a new comment or any change moves a ticket to the top.

ViewShows
Activeopen and pending tickets (the count is shown on the tab)
MineTickets assigned to you (the count on the tab is the active ones)
Resolvedresolved and closed tickets
AllEverything

Combine a view with the team menu and the search box, which matches the ticket number (42 or #42), words in the title, or the customer number. The home page shows how many active tickets are yours and how many are active in the organization.

Discussion

The Discussion section is for notes between the people working on the ticket: what was tried, who was called, what is next. Each note shows the author's name and time, keeps its line breaks, and can be up to 4,000 characters. Notes are internal: they are never sent to the customer.

Who can see what

RoleTickets
AdminEvery ticket of the organization; create, edit, link, comment, create teams. Can see the audit trail of ticket changes.
SupervisorEvery ticket of the organization, with the same actions. The Link a call dialog lists everyone's calls.
UserEvery ticket of the organization, with the same actions. The Link a call dialog lists only the user's own calls.
Other organizationsNothing. Every ticket query is limited to the signed-in person's organization.

Creating a ticket, editing it (with the names of the changed fields), linking items and creating a team are written to the organization's audit trail. Discussion notes and unlinking are not.

Ticket webhooks

Three events let a CRM, a help desk or a chat channel follow tickets. They are signed and retried like every other webhook. Subscribe to them under Integrations → Webhooks.

EventFires whenExtra fields in data
ticket.createdA ticket is created, from anywhere.created_by, links
ticket.updatedStatus, priority, team, assignee, title, details or customer changed; or calls or threads were linked.changed and by for edits; change: "linked" and links for links
ticket.resolvedThe status changed to resolved or closed from a different status. Sent instead of ticket.updated for that save.changed, by

Every ticket event carries the same ticket fields: id (internal), number (the # people see), title, team (its name), status, priority, assignee (an extension, or null) and customer.

ticket.createdJSON
1{2  "id": "evt_9a41c07e5b2d3f8812c4e6a0",3  "type": "ticket.created",4  "created_at": "2026-11-15T09:41:07.112Z",5  "organization": "acme-bank",6  "data": {7    "id": 318,8    "number": 42,9    "title": "Card blocked after travel",10    "team": "IT",11    "status": "open",12    "priority": "normal",13    "assignee": null,14    "customer": "+923001234567",15    "created_by": "sara@acme-bank.example",16    "links": [{ "kind": "call", "ref": "1794698412.231" }]17  }18}
ticket.updated (a conversation was linked)JSON
1{2  "id": "evt_0c7d2e9f41a3b5c6d7e8f901",3  "type": "ticket.updated",4  "created_at": "2026-11-15T10:06:30.904Z",5  "organization": "acme-bank",6  "data": {7    "id": 318, "number": 42, "title": "Card blocked after travel", "team": "Billing",8    "status": "open", "priority": "high", "assignee": "1004", "customer": "+923001234567",9    "change": "linked",10    "links": [{ "kind": "conversation", "ref": "12" }]11  }12}
ticket.resolvedJSON
1{2  "id": "evt_5e6f7a8b9c0d1e2f3a4b5c6d",3  "type": "ticket.resolved",4  "created_at": "2026-11-15T15:22:48.017Z",5  "organization": "acme-bank",6  "data": {7    "id": 318, "number": 42, "title": "Card blocked after travel", "team": "Billing",8    "status": "resolved", "priority": "high", "assignee": "1004", "customer": "+923001234567",9    "changed": ["status"],10    "by": "omar@acme-bank.example"11  }12}

Discussion notes and unlinking do not send an event.

Next steps