Ticket View
The Ticket View is where agents act on tickets. For the concepts behind a ticket — what one is, the statuses it moves through, and how it transitions — see Ticket Lifecycle.
Two Ways to View Tickets
The information in the Inbox and in the Ticket View overlaps, but they exist for two different audiences (see Getting Started):
- The Inbox lists customers and their conversations — for agents who talk to customers.
- The Ticket View lists tickets with deep detail — for agents (often backend agents) who investigate and add input without messaging the customer.
The Ticket List
The Tickets page shows a list of tickets with filters and saved views to focus the queue, such as:
- All tickets
- My tickets — tickets assigned to you
- Snoozed by Me — tickets you snoozed that haven't woken up yet
- Unassigned tickets
- Blocked tickets
- Monitoring — child tickets waiting for order data before their team can act (see Monitoring)
In the table view, an amber dot next to an open ticket's status means it needs action: the customer wrote, or the ticket came back to the queue, and no agent has replied since. Hover over the dot to see this.
In the split-pane Ticket View, the search box finds tickets by order number, ticket name, customer email, or phone. Type at least 3 letters or numbers and press Enter; a shorter search is not run.
The date range applies to the date field picked beside it: Created, Assigned, Resolved, or Active. Active shows every ticket that was open at any point in the range: tickets created in the range, tickets created earlier that are still open, and tickets created earlier that were resolved during or after the range. Use it to see all the work your team carried in a period, not only the tickets that arrived in it.
The date range picker also sets a time. If you only pick days, the range starts at 00:00 on the first day and ends at 23:59 on the last. To narrow it to part of a day, set the start and end times in the picker and click OK, for example 10:00 to 14:00 today. Saved views keep the times you set.
Copy the list as an API call
To fetch the same tickets from your own system, filter the Tickets table and click Actions → Copy API. Flowcall copies a curl call to the List Tickets API with your current filters and date range in the request body. Replace <your_access_token> with a token from Settings → Integrations before running it. The date range is copied as fixed dates, so edit startDate and endDate to fetch a different period. The Actions menu is shown to admins and to roles that can bulk-assign tickets.
In the table or split-pane Ticket View, use Add filter → Resolved By (the filter icon in the split-pane view). Select Webhook re-evaluation, Manual re-evaluation (including bulk), or Any order re-evaluation to find root tickets resolved after an order refresh. You can save the selection as a view. Existing webhook closures are included; older manual closures may lack trigger information. For closures in a period, choose Resolved At as the date field. Exports include Resolution Trigger beside Resolved By, showing Webhook order re-evaluation or Manual order re-evaluation when the current closure can be identified. Other resolutions and unclassified historical closures leave this column blank. Resolution continues to show the completion reason. For export options, what each time column measures, and why a value such as First Response Time or Resolution Time is blank, see Ticket Export.
Use Add filter → Reopened → Yes to find tickets with a Reopen Count greater than zero: tickets that returned to the queue after a customer reply during resolution confirmation, including email replies while waiting for automatic resolution. The filter includes tickets that have since been resolved again. It does not count manual reopens or returns from ordinary awaiting response. You can save the filter in a view; exports and Insights use the same selection. The selected date range still applies to the date field you choose.
To see every ticket in one customer journey, even tickets that ended in a flow other journeys share, use Add filter → Use Case. A use-case export adds each ticket's flow route and an objective column for every flow on it. See Use Cases.
To find child tickets for one piece of work, use Add filter → Child ticket objective and pick one or more objective names, for example pickup_reason. The list shows child tickets whose objective has that name. This includes child tickets agents created manually from the Data Library and child tickets the workflow created. A child ticket with several objectives, such as one created from an objective collection, is listed under its first objective. The options are the objective names on your account's child tickets. Objectives that a Replace current child took over from the ticket it replaced don't count; only the child's own objective does. You can save the filter in a view, and exports use the same selection.
To see tickets people created by hand, use Add filter → Created By → Manual (any user). It includes tickets anyone on your team created from New Ticket and child tickets they added manually from the Data Library. It leaves out tickets created by the AI, the API, and integrations such as ClickPost or custom webhooks. Pick Me or a teammate instead to see only the tickets one person created. You can save the filter in a view, and exports use the same selection.
To see tickets that aren't routed to any team, use Add filter → Team → No team. You can pick it together with teams to see their tickets and the ones with no team. You can save the filter in a view, and exports use the same selection.
In the split-pane Ticket View, the filter icon also offers Status if your role can open the Tickets table page. Pick one or more statuses (for example Queued or Resolved by AI) to narrow the current view to them. Status replaces the view's own status rule, so All Open filtered to Resolved by Agent shows resolved tickets. Roles without the Tickets table page don't see this filter.
Select a ticket to open the ticket panel — a single workspace with everything needed to investigate, respond, and resolve. The same panel appears whenever you open an active ticket, whether from the Ticket View or the Inbox. The sections below walk through what it offers.
Working an Open Ticket
The actions you can perform depend on your account role's Action access, as well as the ticket's state, assignment, and ownership. Viewing a ticket does not automatically grant permission to change it.
Summary and Context
The top of the panel orients you on the ticket at a glance:
- Conversation summary — an AI-generated recap of what's happened so far, so you don't have to read the whole thread.
- Highlights — the key facts the AI pulled out of the conversation, surfaced for quick scanning.
- Info fields — the ticket fields captured for this ticket, shown with their values.
- Tags — apply or change ticket tags from your configured tag set.
Alongside the panel you can also see customer detail (who they are, past and recent orders), the linked order detail, the full conversation (across every channel the customer used), and the customer history the AI has gathered.
Assignment
- Assignment — assign or reassign the ticket to an agent, route it to a team, or unassign it. Agents are filtered to those who can handle the ticket's channel; permission to assign, reassign, or unassign agents and teams is configured separately in Teams → Roles → Action access.
See Agent Assignment & Teams for how routing decides who is eligible and who gets a ticket.
Ownership
Set a long-term owner (and owner team) separately from the current assignee. The panel records who set the owner. An owner controls who may create child tickets and resolve the parent, while child and interaction tickets remain delegated to their own assignees.
See Ticket Ownership for the complete permission model, child hand-back behavior, automation safeguards, and owner changes.
Child Tickets (Backend Work)
A ticket can branch into child tickets — discrete pieces of backend work routed to a specific team or agent (see Child & Interaction Tickets). The active child ticket shows an objective: a question or parameter the agent needs to answer, with an optional hint and either free-text or selectable options.
- Submit the response, optionally add a resolution, and choose whether to share the resolution with the customer (it appears to them as a note, reframed by the AI into your customer-facing voice).
- Finish with Submit, or use the dropdown to choose Awaiting information — which keeps the child open instead of resolving it — or Snooze.
- Child tickets can be assigned to their own agent or team independently of the parent.
- When several are lined up, the panel shows a queue count ("X more in queue") and lists the queued child tickets.
- You can add a child ticket manually from the objective library, optionally replacing or blocking the current one. If the parent has an owner, only that owner can add one. You can also pick an objective collection; the form then asks for the collection's fields first (see Adding a child ticket from a collection).
- Clear a backlog in one pass with Export Child Tickets / Import Resolutions — see Resolving many child tickets at once.
Interaction Tickets
Interaction tickets are lightweight tickets that handle a customer who reaches out while a backend ticket of theirs is open (see Child & Interaction Tickets). Assign one to an agent and resolve it with an optional note; resolved interaction tickets stay listed for reference.
Awaiting Response and Snooze
When you're waiting on the customer, mark the ticket as awaiting response in one of two modes:
- Auto-resolve with CSAT — if the customer doesn't reply, the ticket resolves and a satisfaction survey is sent.
- Auto-close — same idea, but closes without a CSAT survey.
The panel shows when the wait started and who set it, and lets you remove the awaiting status. Snooze pauses the ticket for a set number of hours: it moves to the Snoozed status, comes back to the queue when the snooze ends, and comes back early if the customer replies. Snoozing takes the ticket off your assignment, so it leaves My tickets until it wakes up. To find the tickets you snoozed, open the Snoozed by Me view in the split-pane Ticket View. It lists them by the time they wake up. Filter the ticket list by Snoozed to see all the paused tickets you can access. Starting awaiting response, removing awaiting status, and snoozing have separate action permissions. Existing ticket and assignment restrictions still apply.
When you start a New Ticket for a customer who already has open tickets, you can add a note to one of those tickets instead. If that ticket is awaiting response (or snoozed), a Remove awaiting response checkbox appears under the note. It's checked by default, so saving the note also puts the ticket back in the queue. Clear it to add the note and keep the ticket waiting. The checkbox only shows if you have permission to remove awaiting status.
Resolution and Execution
The panel's tabs cover the two ways a ticket gets closed out:
- Resolution — fill the disposition form (your ticket fields), enter a resolution, and resolve. Resolution is blocked — with the reason shown — while the ticket is still in progress (AI working), awaiting a response, has a pending child ticket, or you do not have permission. An unowned ticket can be resolved by its assignee or an admin; an owned parent can be resolved only by its owner.
- Execution — run the actions configured on the ticket's workflow manually, and see who executed them.
Objectives, Notes, and Reference Panels
- Objectives form — capture structured objective responses, optionally guided by a copilot suggestion.
- Order — set or change the ticket's order. Only an order your order system returns is accepted, or
ECOMMERCE/OFFLINEwhen the purchase has no order ID. Anything else (for examplena) is rejected with a message, and if the order system doesn't respond you're asked to try again. Accounts with no order system connected can enter any value. - Mark complete — queues this ticket for an agent on the channel it came from, without opening a new ticket.
- Notes — add internal notes, attach images, and optionally share a note with the customer.
- Collapsible panels keep supporting detail one click away: Timeline (full ticket activity log), Order (order details, loaded on demand), Call Records (voice calls with direction, status, and duration), Email Threads (linked Gmail threads), and Details (raw payload fields).
Replying and Outreach
From the bottom of the panel you can reach the customer directly:
- Send Response — insert a canned response into the chat input.
- Send Email — compose an email and link it to the ticket, available even for non-email tickets.
- Send Template — pick one of the approved WhatsApp templates allowed in WhatsApp Templates, fill in its variables, and send it to the customer's phone number. Shown only when at least one template is allowed.
- Call — start a voice call when calling is enabled, prompting for a number if none is on file.
Users with Mark stale / spam action access can mark a parent ticket as stale to close out work that's no longer relevant. Admins and Team Leads have this permission by default; the account can change access for non-admin roles. The same action is available through the Ticket API using the parent's ticket ID or ticket number. Eligible unresolved children are marked stale and open interaction tickets are closed as part of the parent's cleanup.
Insights
Click Insights next to the page title on the Tickets page to open the Insights strip above the list. It counts the tickets the list shows, with the same filters and date range, and has two views: Breakdown and Funnel. Insights needs a date range. The strip's view is kept in the page link, and saving a view saves it too.
Breakdown
Pick a field in Group by to count the tickets by Status, Source, Team, Task, Mood, Child ticket objective, or one of your task objectives. In the organization view you can also group by Account. Each row shows how many tickets have that value and their share of all the tickets counted. The 10 most common values show first; click Show more to see up to 30.
Pick a second field in Split by to turn the rows into a table. For example, group by Team and split by Mood to see which teams get the most frustrated customers. The table shows the six most common values of the second field, and Other holds the rest. The Total column and the Total row count all the tickets of each row and column, and cells are shaded by size so the largest stand out. With the Count measure, use Show as to see each cell as a count or as its share of the row, the column, or all tickets; hover over a cell to see all three. Click the swap button next to Split by to switch the rows and the columns.
Click a row to filter the list to that value, and click it again to remove it. Click a number in the table to filter by both values. Values the list is filtered to are highlighted. The strip doesn't apply the filter on the field it groups by, so you can keep picking more of its values; the strip says so above the rows. Tickets with no source or no child ticket objective can't be picked, because there's no filter for them.
The line above the rows says what the strip counted:
- Status, Source, Team, Task, and Account count every ticket the list shows, including child and interaction tickets. Tickets without a team or task appear as No team or No task.
- Child ticket objective counts child tickets, one row per objective they were created for, for example
pickup_reason. Child tickets created without an objective appear as No objective. For example, group by Child ticket objective and split by Status to see which pieces of backend work are still open. If you filtered the list by Ticket Type, it counts those tickets instead, and parent tickets appear as No objective. It takes priority over Mood and objectives: group by Child ticket objective and split by Mood, and the strip counts child tickets. - Mood and objectives count conversations (parent tickets), because child tickets repeat their conversation's mood and answers. If you filtered the list by Ticket Type or Child ticket objective, they count those tickets instead. A conversation can have no mood or several, so the strip says how many have a value, and the rows can add up to more than the total. A split by mood or an objective works the same way and has no Other column.
Measures
The strip counts tickets unless you pick another Measure, which shows a rate or a time for each row and cell instead:
- % resolved: the share resolved or closed, whether by AI, by an agent, or by going stale.
- % resolved by AI: the share with the status Resolved by AI.
- % with an agent: the share an agent worked on.
- Voice FCR: of the voice tickets checked for first contact resolution, the share resolved on the first call.
- Median time to resolve: the median time from creation to resolution, over resolved or closed tickets.
- Median first agent response: the median time from creation to an agent's first response, over tickets that have one.
For example, group by Team, split by Source, and pick Median time to resolve to compare how fast each team resolves WhatsApp, voice, and email tickets.
Hover over a value to see what it covers, for example 120 of 212 tickets resolved or closed, or a median over 180 resolved tickets. A dash means there was nothing to measure, such as a median time to resolve for a team with no resolved tickets. Totals measure all their tickets together instead of adding up the rows, so the Total of a median is the median over every ticket in that row or column.
Objective answers
To see the most common answers to a task objective, for example how many customers gave each NPS score, pick the objective under Objectives in Group by. Objective columns you added to the table are listed first. When an objective holds a list, each item counts as an answer.
Click an answer to filter the list to tickets with that answer. The filter appears as Objective value: name in the filter bar, where you can add or remove values. Values of one objective match any of them; filters on different objectives must all match. You can save the filter in a view, and exports use the same selection.
Task Funnel
Switch the strip to Funnel and pick a task to see how conversations moved through it and the tasks it routes to. If you filtered the list to one task, the funnel starts with that task.
The funnel counts parent tickets, one per conversation, that went through the task in the selected date range. It applies your other filters, such as status, channel, or team. Task, Ticket Type, and Child ticket objective filters don't apply, because the funnel follows each conversation's route instead of the task it ended on. The funnel needs a date range.
The funnel opens as a flow chart. Each band is drawn as wide as the number of conversations that took it, so you can see at a glance where most conversations went. Bands too thin to label are listed under the chart with their counts, and you can hover a band or a task to see its count. Routes no one took aren't drawn, and a conversation that took two routes appears in both bands. A task that doesn't route to other tasks shows the list instead.
Switch to List for the exact numbers. Each row is a task and shows:
- how many conversations reached it, and their share of the row above;
- for each objective of the task, the share of those conversations that have a value. For a yes/no objective, one whose answers in the funnel are all yes, no, true, or false, it shows the share that answered yes instead, for example
isOrderRTO yes 23%; - Agent involved: the share where an agent worked the ticket or one of its child tickets.
Hover over a share to see the counts behind it, for example how many conversations answered yes, answered no, or have no answer.
Under a task that routes to others, Didn't continue counts conversations that reached none of its routes, for example because they ended there or moved to an unrelated task. The funnel shows routes up to three steps below the task you picked, and a route back to a task already on the path isn't shown again.
The funnel relies on the route each conversation took. Conversations that started before routes were recorded aren't counted; the funnel shows how many such conversations are on its tasks.
For example, an NPS task that routes to detractor, passive, and promoter tasks shows how many customers fell into each group, how many detractors gave a reason, and how many passives an agent picked up.
Tickets Copilot
Click Copilot next to the page title on the Tickets page to open a Copilot chat beside the ticket list. Copilot sees the filters, columns, and Insights view the page shows. It reads tickets with your own access, so it only counts tickets you can see.
Ask it about your tickets, for example:
"How many of these tickets went to an agent, by team?" "Which teams get the most frustrated customers?" "What are the most common cancellation reasons this month?" "Show the NPS funnel for the last 30 days." "What's the median time to resolve by team this week?" "Why is First Response Time blank for this ticket in the export?"
It can also change what the list shows:
"Show only open detractor tickets, with the reason as a column." "Filter to WhatsApp tickets where the customer was frustrated."
When Copilot changes the list, it applies the new filters, objective columns, or Insights view right away and shows a card in the chat. When it answers with numbers, it can also open the Insights strip on the breakdown or funnel they come from, so you see the same counts. Its counts match the strip's, except that the strip leaves out the filter on the field it groups by. Click Undo on the card to put the list back the way it was, or Apply to use a view from an earlier message again. Copilot only changes what the page shows; save it as a view to keep it. Configuration changes, such as editing a task, still come as cards for you to review.
The chat uses the same conversations, permissions, and usage limits as the main Copilot; Open in Copilot continues the conversation there. Copilot and Insights can be open at the same time. If you don't see Copilot, your role doesn't have Copilot access.
Related
- Ticket Lifecycle — what a ticket is and the statuses it moves through.
- Ticket Ownership — parent control, delegated children, and owner hand-back.
- Child & Interaction Tickets — backend sub-tasks and handling customers mid-flight.
- Ticket Fields & Disposition — the fields shown and captured on a ticket.
- Ticket Export — the CSV export's columns and why a value can be blank.
- Agent Assignment & Teams — how tickets are routed to the right people.
- Inbox — the customer-centric view of the same conversations.
- Insights → Tickets — analyze ticket volume, resolution, and trends.