Emergency Dispatch (FSE View)
Skeleton — content TBD, we'll build this line by line.
Purpose of this page: walk an FSE through an emergency callout from the moment dispatch pings them to closeout. Differs from the normal daily workflow in time pressure, parts availability, and the covered-vs-billable distinction.
When You'll Get Called
(how emergency assignments reach you — activity in inbox, Slack, phone call)
The 30-Second Context Check
(what you need to know before rolling — customer, system, is-it-covered, what's broken)
Accepting the Assignment
(move task from Open to Confirmed with Client, set dates, grab the service request details)
Before You Leave
(parts check, tool check, confirm the site address, any special access instructions)
On-Site
(same flow as Your Daily Workflow — log time, log parts, fill checklist, mark complete — with callouts for what's different on a callout)
Covered vs Billable — What It Means for You
(you mostly don't care; dispatcher handles the branching. One line on why it matters for analytic account picking.)
Closeout
(resolution code on the service request; specific codes that matter for callout reporting)
What Happens After You Close
(dispatcher closes, accounting posts, any callout-specific metrics)
Related
- Your Daily Workflow — the base flow this extends
- Service Requests — resolution codes
- Logging Parts & Materials — parts + analytic