Support template · 13 steps

Support triage with escalation

Support email gets cleaned, labelled for urgency and either escalated to on-call or queued with a drafted reply.

TRIGGERSupport emailTRANSFORMClean upAI CLASSIFYUrgencyCONDITIONUrgent?DRAFT MESSAGEDraft on-call pageHUMAN APPROVALConfirm escalationSEND MESSAGEPage on-callCRM WRITEOpen urgent ticketENDEscalatedDRAFT MESSAGEDraft replyHUMAN APPROVALReview replyCRM WRITEQueue ticketENDQueued

Highlighted: the path taken by the “Login outage” sample after approval.

Trigger

Inbound support email

Input: One email (from, subject, body)

Output

Urgent ticket and on-call page, or a queued ticket and drafted reply

Every write and send waits for a human approval first.

Permissions it would need
  • Read support inbox
  • Page on-call (after approval, simulated)
  • Write tickets (after approval)

Sample input

{
  "from": "it@brightcare-demo.org",
  "subject": "Nobody can log in",
  "body": "Since 9am all users cannot log in to the portal. This is blocking production work."
}

Steps in run order

#StepTypeWhat it does
01Support emailTriggerWhere a run starts: a form, email, call, schedule or other event.
02Clean upTransformReshapes data with a fixed, safe operation. No custom code runs.
03UrgencyAI classifyLabels text. In this demo a seeded keyword model stands in for a language model.
04Urgent?ConditionSends the record down the true or false branch based on your rules.
05Draft on-call pageDraft messageWrites a message from a template and the record. It is a draft until a Send step.
06Draft replyDraft messageWrites a message from a template and the record. It is a draft until a Send step.
07Confirm escalationHuman approvalPauses the run until a person approves or rejects. Required before sends and writes.
08Review replyHuman approvalPauses the run until a person approves or rejects. Required before sends and writes.
09Page on-callSend messageSimulated send of a drafted message. Nothing leaves this demo.
10Queue ticketCRM writeWrites a row to the synthetic CRM, with retries and a dead-letter queue.
11Open urgent ticketCRM writeWrites a row to the synthetic CRM, with retries and a dead-letter queue.
12QueuedEndMarks a finished branch and names the outcome.
13EscalatedEndMarks a finished branch and names the outcome.

Seeded scenarios and what they produce

Synthetic run

Login outage

Many users locked out. Labelled urgent and routed to on-call after confirmation.

Result: Escalated to on-call with an urgent ticket

Synthetic run

How-to question

A normal question. Gets a drafted reply and the general queue.

Result: Ticket queued with a drafted reply

Synthetic run

Hidden instruction

Email tries to order a refund. The instruction is flagged and ignored.

Result: Ticket queued with a drafted reply

Guardrails

  • Refund or credit requests in emails are never acted on
  • A person confirms every page

Connectors used

Try the live studio