Reference
·
Updated Mar 27, 2026
Workflow — Complete Queue Journey (Walk-Up)
1 min read
1,798 views
Workflow — Complete Queue Journey (Walk-Up)
Trigger: Visitor navigates to /queue/join
Step-by-Step
| Step | System Action | Ticket Status |
|---|---|---|
| Visitor selects service and submits | IssueTicket action creates Ticket |
waiting |
| — | TicketIssued event broadcast to display |
— |
| — | SendTicketNotification job dispatched (type=issued) |
— |
| Counter calls next | CallNextTicket action |
calling |
| — | TicketCalled event broadcast (TTS triggered on display) |
— |
| — | SendTicketNotification job dispatched (type=called) |
— |
| Visitor arrives at counter | StartServing action |
serving |
| Staff completes service | CompleteTicket action |
completed |
| — | TicketCompleted event broadcast |
— |
| — | SendTicketNotification job dispatched (type=completed, includes feedback URL) |
— |
State Transition Diagram
waiting → calling → serving → completed
↘ transferred (creates new TicketStage in target office)
↓ (no-show)
missed
↓ (recalled within 15 min)
recalled → calling → ...
↓ (expired after 15 min)
expired
Priority Ordering
When CallNextTicket selects the next ticket, it uses: ORDER BY priority_score DESC, issued_at ASC
| Priority Type | Score |
|---|---|
| Normal | 0 |
| Scholarship | 5 |
| PWD / Senior / Pregnant | 10 |
| VIP | 15 |
Was this article helpful?
Let us know so we can improve our documentation.
Thanks for your feedback!
Glad we could help.
Sorry to hear that
How can we improve this?
Thanks for your feedback!
We'll use your feedback to improve.
Related articles