Tickets & Disposition
Disposition is how a resolved conversation gets classified — the structured record of what the ticket was about and how it ended. That record drives your reporting, routing, and any downstream sync to another system. The Copilot configures the form agents fill, what runs when a ticket closes, and how flows pre-fill the form automatically.
Why disposition matters
Every closed ticket carries a set of field values — category, reason, outcome, and any custom fields you define. Getting this right means your Insights reflect reality, tickets route to the right place, and closures can trigger the correct follow-up action. The Copilot helps you shape the form, keep it consistent, and reduce how much agents have to fill in by hand.
Global disposition form
The shared set of disposition fields every ticket uses — the schema, how fields autofill from the conversation, and the on-closure actions that run when a ticket is resolved.
"Add a refund reason dropdown to the disposition form." "Make the root cause field autofill from the conversation." "Run an execute action to sync the ticket to Freshdesk on closure." "Add a required resolution type field with options resolved, escalated, and duplicate." "Route premium-tier customers to the VIP team."
Autofill lets the AI populate a field from what happened in the conversation, so agents confirm rather than type. On-closure actions let a resolved ticket trigger real work — syncing to a CRM, firing a webhook, creating a downstream record. Team routing assigns new tickets to a specific team based on a category field's autofilled value (for example a customer-tier data point) instead of the account's default team — and if the target team doesn't exist yet, saving the draft creates it.
For setup steps, mapping examples, routing priority, and when the data must be available, see Route tickets to a team from a data point.
Flow disposition presets
The field values that get set automatically when a specific flow runs. Presets are how you keep classification consistent without relying on agents to remember — when the cancellation flow handles a ticket, its category is already correct.
"When the cancellation flow runs, preset the category to Order → Cancel." "For the warranty flow, preset the issue type to Warranty claim and mark it for the returns team."
Presets fit into a flow's completion behavior, so they apply as the flow resolves the ticket. If you're building the flow itself, you can ask for its presets in the same request.
Customer request objectives
Objectives agents can pick from Request from customer on a ticket — the AI asks the customer on WhatsApp or email, reads the reply, and returns the ticket to the queue with the answer. See Request information from the customer.
"Let technicians ask the customer for a new visit date when a job needs rescheduling." "Make the delivery address requestable from tickets, using the info_request template." "Change the reschedule date request to time out after 48 hours and close the ticket."
The Copilot picks the answer type (a visit day becomes a date, which must be in the future), writes how to ask, and fills the template variables in order. Updating an existing objective keeps everything else on it.
The WhatsApp template is suggested, not required. When your account has WhatsApp connected, setting up a new request is a two-step plan: first a generic utility template called customer_info_request (Hi {{1}}, to continue with your request {{2}}, we need a quick detail from you: {{3}}), then the requestable objective that uses it, with the variables mapped to the customer's name, the ticket reference and the question. One template serves every requestable objective. Review and submit the template when its card appears; the objective step runs after it.
- To use a template you already have, name it ("…using the info_request template") and the template step is skipped.
- To go without one, skip the template card or say so ("…without a WhatsApp template"). If the template step fails, the objective is still set up.
- If your account has no WhatsApp number connected, the Copilot doesn't suggest a template and sets the request up for email only.
- A newly submitted template waits for Meta approval. Until it's approved, WhatsApp requests only reach customers who wrote in the last 24 hours; email works straight away.
Call follow-up
Flowcall can ask customers for details a phone call missed, over WhatsApp and email. The feature itself is a setting you turn on under Settings → Channels → Voice calls → Voice Call Processing (how it works); the Copilot can't change that setting, but it can draft the WhatsApp template the follow-up uses.
"Set up call follow-up for missing details." "Create the template for asking customers for details after a call."
When your account has WhatsApp connected, the Copilot suggests a utility template called call_followup_request with two variables: the customer's name and the ticket reference (Hi {{1}}, thanks for calling us. To continue with your request {{2}}, we need a few more details from you. Please reply to this message.). It deliberately leaves the question out: the customer's reply opens the chat, and the AI asks the questions there. After submitting it, enter call_followup_request as the setting's WhatsApp template, with the variables {{customerName}} and {{ticketName}}.
The template is optional. Skip it if your customers don't use WhatsApp; without a WhatsApp number connected, the Copilot only explains the setting, and follow-ups go by email.
Ask about your tickets
On the Tickets page, the Copilot panel answers questions about the tickets in the list and changes what the list shows: filters, objective columns, and the Insights strip, which shows a breakdown or a task's funnel. See Tickets Copilot.
"What are the most common cancellation reasons this month?" "Which teams get the most frustrated customers?" "Show only open detractor tickets, with the reason as a column."
It also explains the ticket CSV export, such as what a column means or why Resolution Time or First Response Time is blank for a ticket. See Ticket Export.
"Why is Resolution Time not available for this ticket?"
Getting it right
- Define the field before you preset it. A preset sets a value on an existing disposition field, so add the field to the global form first (or ask for both together).
- Say whether a field is required and whether it autofills — that changes how much agents have to do at closure.
- Name the exact flow a preset should apply to, and the exact option value it should set.
Related
- Ticket Fields & Disposition — the disposition form the Copilot configures.
- Flows — where per-flow presets fit into a flow's completion behavior.
- Insights — the reporting that disposition data feeds.
- Copilot overview