Everything below is fictional. When this gets built for a real business, the office queue is what dispatch or CSR staff use to log and track every promised visit, the manager queue mirrors the same data filtered to what actually needs attention, and the customer reference code is whatever the office already hands out (a work order number, an account number), not a new system to adopt.
Log a new commitment
Open queue, escalated and overdue first
Manager escalation queue
A commitment lands here automatically once it has been cancelled or rescheduled by the company twice, or once it has sat more than 24 hours past its scheduled time with no reschedule logged, whichever comes first. Nobody has to notice it and flag it by hand.
Check the status of a commitment
Try SCT-1001, SCT-1002, SCT-1003, SCT-1004 or SCT-1005 from the office view's sample queue.
How this gets built for real
The escalation thresholds are adjustable. A real build sets the cancellation count and overdue-hours trigger to match the business's own service-level target, not this demo's defaults.
This tracks the promise, not the technician's calendar. It sits alongside whatever tool already books the appointment (a contact form, a dispatch board) and only tracks whether the promised visit actually happens.
The reference code is whatever the office already uses. A real build reads from an existing work-order or plan account number instead of inventing a new one for the customer to remember.
The customer view shows only customer-safe wording. Internal notes and manager escalation reasons stay in the office and manager views; nothing typed there is exposed on the lookup page.
See it built for a real business: Premier Heating and Air, A Clean Pool USA, or Gray's Tree Service.