Customer support ticket BPMN diagram example
A support ticket process shows off two BPMN strengths: escalation across teams and SLA timers. It's a realistic example of routing and time-based handling.
Take this diagram with you. The BPMN 2.0 XML below is the exact source behind the diagram above — open it in Camunda Modeler, Flowable, Activiti, bpmn.io, or any BPMN 2.0 tool.
↓ Download Support ticket handling .bpmnOpen in BPMN Studio
Free, no sign-up, no attribution required.
The process in plain English
A customer raises a ticket. Support triages it and either resolves it at first line or escalates to a specialist. Throughout, an SLA clock runs; if it's about to breach, the ticket is escalated automatically. Once resolved, the customer confirms and the ticket closes.
Steps and their BPMN elements
| Step | BPMN element | Lane |
|---|---|---|
| Ticket raised | Message start event | Customer |
| Triage & categorise | User task | First-line support |
| Resolvable at first line? | Exclusive gateway | First-line support |
| Resolve ticket | User task | First-line support |
| Escalate to specialist | User task | Specialist |
| SLA about to breach | Timer boundary event | — |
| Notify customer of resolution | Send (message) task | Support |
| Customer confirms fixed? | Exclusive gateway | Customer |
| Ticket closed | End event | — |
| Reopen / continue | Loop back | — |
Key modelling points
- The timer boundary event models the SLA — a headline reason to use BPMN over a flowchart.
- Escalation crosses lanes (first-line → specialist).
- The customer-confirms gateway can loop back if the fix isn't accepted.
Generate your own support workflow
Describe your triage rules, tiers and SLAs to BPMN Studio for an instant, editable BPMN 2.0 diagram. More templates · events explained.
Frequently asked questions
How do you model a support ticket process in BPMN?
Begin with a message start event (ticket raised), triage with a user task, then an exclusive gateway on priority or complexity. First-line resolves simple tickets; complex ones escalate to specialists via a second lane. An SLA timer boundary event handles breaches, and the process ends when the ticket is resolved and confirmed.