Skip to main content

Ticket Lifecycle

This section holds the statuses, messages, and timing rules that decide how tickets move through your workspace — how they're numbered, which channel an active ticket lives on, when Flowcall nudges a quiet customer, when a ticket is treated as stale, and how resolution is confirmed. For the statuses themselves and how a ticket transitions between them, see Ticket Lifecycle.

All sections appear in one continuous page with clear headings. Use the sticky On this page links to jump to a section. Each link adds a section fragment to the URL, so you can copy or bookmark the link and open that section directly. Save changes applies edits across the whole page; Discard restores the saved values. Changes are not saved automatically.

SectionWhat you configure
Ticket basicsNumbering, tags, manual sources, and support staff wording
Ticket creationInteraction tickets and requirements for manual and child tickets
Routing & assignmentCross-channel handling, assignment tracking, and login assignment
Waiting & follow-upsQueue messages, awaiting-response rules, reminders, and stale timeouts
Resolution & outreachResolution confirmations, customer outreach, and CSAT requirements

Use the link icon beside a setting name to share that specific setting: click it and copy the browser address, or right-click and choose Copy link address. See sharing settings links for details.

Ticket basics​

Ticket numbering​

  • Ticket numbering — every new root ticket automatically receives an incrementing number scoped to its account. Child and interaction ticket names are derived from the root number.
  • Ticket name prefix — optional text prepended to each new ticket name, for example FC-BrandName-. Only letters, numbers, and hyphens are allowed; spaces and special characters are stripped as you type, and the field is capped at 40 characters (a counter warns you as you approach the limit).

Ticket tags​

  • Ticket Tags — define the tags agents can apply to tickets. Type a tag and press enter (or separate with commas). Duplicate and blank tags are removed automatically. These are the values that appear in the tag picker on a ticket.

Manual ticket sources​

Add labels such as Store or POS for manually created tickets.

Support staff term​

Customize the words used in automated messages instead of "agent" / "agents" — useful if your brand calls them "specialists," "advisors," or similar.

  • Singular — the singular term (e.g. agent). Defaults to "agent" if left blank while a plural is set.
  • Plural — the plural term (e.g. agents). Defaults to "agents" if left blank while a singular is set.

Leave both blank to use the default wording.

Ticket creation​

Interaction ticket​

Turn on Interaction Ticket to create a follow-up ticket when a customer messages on a blocked ticket that has a backend child ticket in progress. This keeps the customer's new message from being lost while backend work is still open. For the full picture of how a ticket branches into child work and why the AI pauses, see Child & Interaction Tickets.

Configure:

  • Delay from Child Ticket Creation (minutes) — how long after the child ticket is created before interaction tickets may be created, so an immediate follow-up doesn't spawn a duplicate.
  • Assigned Team — the team every interaction ticket is routed to.

Turn on Link other contacts to attach a different customer who reaches out about the same order as an open ticket to that ticket, instead of opening a new one. These linked contacts are routed to the same Assigned Team, so a team must be selected before you can turn this on. It works independently of the Interaction Ticket switch.

Choose how the customer is told:

  • Link straight away — tell them their message has been added to the open request.
  • Ask first — tell them about the open request and ask whether they want to be connected; they are linked unless they say no.

See Linked Contacts.

Manual and child ticket requirements​

  • Mandatory Note on Manual Tickets — require a note before an agent creates a manual ticket.
  • Mandatory Task on Manual Tickets — require a task selection before creation. On the New Ticket form, agents can find the task by typing the customer's issue in their own words, such as "fan not working" or "wants a refund": the list matches tasks by what they handle, not only by name. Once a task is picked, the order lookup stays on the form only if the task reads the customer's order, and each question hides any "[Note to AI: …]" text meant only for the AI.
  • Allow Pending Manual Tickets — offer creation before all task objectives are complete; see Asking the customer for missing details.
  • Require Note for Manual Child Tickets — require note text or at least one image. These notes are internal.
  • Mandatory Disposition on Child Tickets — require agents to save required disposition fields before creating a child ticket or submitting a child response.
  • Default Child Ticket Action — choose whether Block current or Replace current is initially selected when adding a child ticket.

Values the New Ticket form doesn't accept​

When an agent fills a task objective on the New Ticket form and a required condition rejects the value, the field turns red and shows why. The reason is the condition's failure message, or one generated from the condition if none was written. Underneath, the form shows the check and the value entered, so the agent can correct it before creating the ticket. Pressing Enter in an answer saves it, like Save & Continue.

Asking the customer for missing details​

When an agent creates a ticket from the New Ticket form and the task still has pending objectives the customer must answer, the agent can tick Ask customer for missing details. The AI takes over the ticket: it asks the customer on WhatsApp and email and continues the ticket in the chat or email thread where the customer replies, as if the conversation had started there. Photos, videos and documents the customer sends there fill the matching objectives. When every question still on the form will go to the customer, the agent can answer what they know and click Save & Continue, or click Create Ticket and leave the rest to the AI. When only files the customer must send are left, the form hides Save & Continue and tells the agent to click Create Ticket.

An objective that collects a file through the attachmentUrls data point (for example an invoice that may come as a PDF or a photo) shows a Select PDF or Image upload on the New Ticket form instead of a text box. Only an uploaded file fills it. If you don't have the file, leave it empty and keep Ask customer for missing details ticked: the AI asks the customer for it after the ticket is created.

Whether the option is offered depends on Allow Pending Manual Tickets:

Allow Pending Manual TicketsCustomer reachableNew Ticket form
OnYesAsk customer for missing details is shown and ticked by default.
OnNoAllow creating pending ticket creates the ticket and queues it for agents.
OffYesCreation stays blocked unless the only missing details are photos, videos or documents; then the AI can ask.
OffNoCreation stays blocked until the objectives are filled.

The follow-up uses the reply timeout from Customer Outreach and the Info request template from WhatsApp Templates. The template is sent without variables and only when the 24-hour WhatsApp window is closed. While the AI waits, the ticket stays in progress with a Waiting for customer (AI follow-up) card, from which an agent can stop it. If the customer doesn't reply in time, or the message can't be sent, the ticket goes to the queue and its SLA starts then.

Routing & assignment​

Cross-channel ticket handling​

Turn on Cross-channel Ticket Handling to keep one active ticket when the same customer reaches you on more than one channel. Flowcall uses the fixed order Chat → Email → Voice Call. Chat groups WhatsApp, Instagram, and Live Chat.

The order is not editable. The numbered rows in this card describe the fixed policy; they are not drag-and-drop controls.

How it works. The behavior depends on the ticket's status:

  • Tickets that are queued, assigned, or blocked stay on the highest-priority segment. Chat beats Email, and Email beats Voice Call.
  • A ticket already on WhatsApp, Instagram, or Live Chat stays on its existing chat channel when the customer uses another chat channel.
  • A Voice Call ticket moves to Email or Chat when the customer contacts either. An existing Email or Chat ticket does not move to Voice Call.
  • Tickets marked awaiting response ignore the fixed order and move to the channel where the customer actually replies, because that reply is now the live customer channel.
  • A manually created ticket uses the first supported customer channel that contacts it.

The toggle controls fixed segment routing for queued, assigned, and blocked tickets. Awaiting-response reactivation and manual-ticket channel claiming still apply when the toggle is off.

See the cross-channel ticketing recipe for worked examples.

Track agent assignments​

  • Track Agent Assignments — records every ticket-to-agent assignment attempt for auditing and staffing analysis. It increases database writes, so turn it on when you need the assignment history and off if you don't.

Agent login assignment​

Controls whether tickets get assigned to an agent simply because they logged in.

  • Restrict assignment on agent login — when checked, login-triggered assignment is limited to business hours plus a configurable pre-opening buffer, so agents signing in early don't sweep up queued work before you're open.
  • Pre-opening buffer (minutes) (shown when restriction is on) — how far before business-hours open (0–1440 minutes) a login is still allowed to assign queued tickets.

Waiting & follow-ups​

Ticket in queue message​

  • Ticket In Queue Message — turn on to message customers while their ticket is waiting in the queue, so they know they've been received and are in line.
  • Message Prompt (shown when on) — the wording sent to the customer. This is a prompt the AI uses to compose the message, not a fixed string.

Auto mark awaiting response​

Turn on Auto Mark Awaiting Response to move older queued WhatsApp, Instagram, and Live Chat tickets to awaiting customer response when agents come online. Eligible customers receive a reminder that agents are available, inviting them to reply to continue the conversation.

  • Delay (minutes) — how long to wait before marking the ticket as awaiting (default 1410 minutes). The timer measures time since the last relevant activity.
  • Message Prompt — the instruction the AI uses to write the availability reminder. Leave it blank to use the default message asking whether the customer is available to chat.

Message batching​

  • Message Batching — controls whether availability reminders are staggered. When off, all eligible reminders are sent together as soon as working hours allow; any saved time slots are ignored. When on, reminders use the slots below. With no slots configured, all eligible reminders are sent together.
  • Time slots — add one or more slots to control when nudges go out and how many per slot, so you don't blast every waiting customer at once:
    • Time — the time of day the batch is released.
    • Batch Size — how many messages to send in that slot.
    • Unlimited — when on, that slot sends to all remaining waiting tickets (Batch Size is ignored).
    • Use Add Time Slot to add slots and the delete button to remove them.

Availability reminders wait until your next business opening if they become due outside working hours. For example, with a 9:30 AM opening and batching off, eligible reminders are queued immediately when agents come online at 9:30 AM.

This is the mechanism behind the shift-start stale-chat cleanup recipe — schedule nudges for the start of a shift so agents open to a clean live queue and customers hear from you only when someone is available to help.

There is also an Auto Mark Awaiting on Expired Chat card: turn it on to automatically mark tickets awaiting response when the WhatsApp chat window expires, and pick the Template to send in that case (only approved templates can be delivered outside the 24-hour window).

Stale ticket timeouts​

Treat long-silent tickets as stale and close them. Timeouts are in minutes; each field notes how blank and zero values behave.

  • WhatsApp (minutes) — mark WhatsApp, Instagram and Live Chat tickets stale after this much time with no reply. New accounts start at 1380 (23 hours). Leave blank to disable.
  • Email (minutes) — mark Gmail or Outlook tickets stale after this much time with no reply. New accounts start at 2880 (48 hours). Leave blank to disable.
  • Live Chat (minutes) — mark inactive Live Chat tickets still being processed by AI as stale.
  • AI In-Progress (minutes) — mark non-email, non-Live Chat tickets still being processed by AI as stale after this much inactivity. Leave blank to inherit the WhatsApp timeout, or set 0 to disable.
  • Live Chat AI In-Progress (minutes) — use a separate timeout for Live Chat tickets still being processed by AI. Leave blank to inherit the Live Chat timeout, or set 0 to disable.
  • Stale Ticket Closing Instruction — an optional message sent when auto-closing a stale ticket, used for both WhatsApp and email closures. Leave blank to use the default closing message.

Email replies and follow-ups​

The Email follow-ups before closing card can start an awaiting-response sequence automatically after an outbound reply. Turn on Start after reply to enable this behavior. It is enabled by default for newly created businesses. Existing businesses keep their saved value and are not enabled automatically by this change.

When enabled:

  • A successful agent email reply moves an eligible queued, assigned, blocked, or in-progress ticket to Awaiting response (by agent).
  • A successful, substantive AI email reply moves an eligible queued, assigned, blocked, or in-progress ticket to Awaiting response (by system).
  • The ticket is unassigned, its previous agent is retained as the preferred agent, and a new awaiting-response timer starts from the successful reply.
  • Automated acknowledgements, follow-up reminders, CSAT messages, and stale-ticket closing emails do not restart the timer.
  • If the customer replies, the ticket returns to the queue and all remaining follow-ups for that waiting cycle are cancelled.

If Start after reply is off, sending an agent reply does not automatically change the ticket's status or assignment, and an AI reply does not automatically start this sequence.

Use Add follow-up to configure up to ten reminders. Each row contains:

  • Send after (minutes) — an absolute offset from when the ticket entered awaiting response, not a delay from the preceding reminder.
  • Message prompt — instructions the AI uses to compose that reminder.

Each delay must be unique and earlier than the Email (minutes) stale timeout. Flowcall records each successful delivery so a reminder is sent only once during the same waiting cycle. If multiple reminders are overdue, the worker sends at most one per ticket on a run. The stale-ticket worker runs hourly, so a reminder or closure is processed on the first run after its deadline rather than at an exact minute.

For example, to remind after 24 and 48 hours and then close after three days:

ActionMinutes
First follow-up1440
Second follow-up2880
Mark stale4320

At the stale deadline, no further reminder is sent. The ticket is marked stale if the waiting cycle was started by an agent, or stale (automatic) if it was started by the AI. Flowcall then sends the configured stale closing instruction by email.

Resolution & outreach​

Resolve confirmation​

Turn on Resolve Confirmation to ask the customer to confirm a resolution before an agent-resolved ticket is closed. It also applies when the AI is about to resolve an unowned parent after all of that parent's objective child tickets have finished.

Internal-only tickets are exempt and resolve immediately without sending a confirmation prompt.

How it works. For WhatsApp, Instagram, and Live Chat tickets, clicking Resolve does not immediately close the ticket. Instead it moves the ticket to awaiting response to resolve and sends the customer a confirmation message with Yes / No buttons:

  • If the customer taps Yes, the ticket closes.
  • If they tap No, the ticket reopens to the queue so an agent can keep helping.

For an objective-ticket family, the parent does not need a temporary agent assignment. The last child first returns the parent to the workflow. If that workflow completes with auto-resolution, Flowcall parks the root parent in awaiting response to resolve instead of closing it immediately. Parents with another unresolved child remain blocked and are never sent for confirmation.

Configure:

  • Auto-resolve Timeout (minutes) — if the customer doesn't respond within this window, Flowcall auto-resolves the ticket anyway (1–1440 minutes; default 1440 / 24 hours).
  • Max Reopen Count — how many times the customer can answer No before Flowcall auto-resolves the ticket regardless (default 3). This stops a ticket from bouncing back into the queue forever.
  • Confirmation Message — the message shown with the Yes/No buttons. Leave blank to use the default ("Is your query resolved?").

Customer Outreach (WhatsApp & Email)​

Manual and call tickets don't start in a chat, so Flowcall needs a way to reach the customer when it has something to tell or ask them. Customer Outreach sets this up. It sends a message on WhatsApp and by email, and the conversation continues on whichever channel the customer replies.

It is used in two places:

  • Send resolutions to the customer (switch): when a child ticket of a manual or call ticket is resolved, the resolution goes to the customer and the ticket waits for their reply.
  • AI follow-ups for missing details, from the New Ticket form or after a call. These are turned on by their own settings; the switch above doesn't affect them.
SettingWhat it does
Reply timeout (hours)How long to wait for the customer's reply (1–720). After a resolution, the ticket is then auto-resolved. After an AI follow-up, it goes to an agent.

The WhatsApp templates used when the 24-hour window is closed, the Info request template and the Resolution update template, are chosen in WhatsApp Templates. Without them, only email is used in that case.

Allow skipping CSAT on resolve​

Show a Don't send CSAT survey checkbox when agents resolve a ticket. It starts unchecked. Selecting it suppresses the survey and records the suppression against the agent. Configure the survey itself in CSAT Surveys.