Emergency, urgent, same-day, routine: four tiers and who defines them
In short
An emergency service call is one meeting a condition the operator has written down and can observe over the phone: damage in progress, no heat or cooling with a vulnerable occupant, no water, or a safety risk. None of that is standard across the trade — the tier is business policy, so it has to exist as data before anyone can apply it the same way twice.
Key takeaways
- The tier is the operator's policy, not an industry standard. Two shops in one town define it differently.
- Define each tier by an observable condition a caller can confirm, never by how alarmed they sound.
- The response commitment is the definition. A tier with no promised window is a label, not a priority.
- Capacity never changes the tier. A full board changes who you call, not what the job is.
- Name who may override, because an override with no owner becomes everyone's discretion.
An emergency call is one meeting a condition the operator has written down and an intake agent can confirm over the phone: water or gas escaping, damage happening now, no heat or cooling where an occupant is vulnerable, no water in the building, or an electrical safety risk. There is no trade-wide definition — two shops on the same street will draw the line differently, and both can be right.
That has a consequence for anyone building intake. If the tier is business policy rather than a fact about the world, no model infers it from the caller's tone. It has to be encoded — conditions, commitments, overrides — then applied.
A four-tier table you can actually encode
4 tiers is the practical maximum. Beyond that, dispatchers stop distinguishing them and everything collapses into 'today' or 'not today'.
| Tier | Qualifying condition, observable on the call | Response commitment | Who may override |
|---|---|---|---|
| Emergency | Damage in progress, no water, safety risk, or no heating or cooling with a vulnerable occupant | Dispatch now, including after hours; a 4-hour arrival target stated on the call | Nobody downgrades without the on-call lead |
| Urgent | No conditioning but no vulnerable occupant, partial water loss, a failure that becomes an emergency within 24 hours | Same day against capacity, otherwise the first slot next day | Dispatcher, with the reason recorded |
| Same-day | Customer needs it today for their own reasons — a let, a sale, a landlord deadline | Offered only against genuinely free capacity | Office, freely |
| Routine | Maintenance, quotes, non-failing equipment, anything the customer will schedule | Next slot inside the standard 10-day booking horizon | Anyone |
The conditions are trade-specific, and that is the point
A single generic tier table applied across trades is what produces mis-tiered calls. Each trade has its own observable separating 'now' from 'tomorrow', and intake has to be able to establish it.
| Trade | Typically emergency | Usually urgent, not emergency |
|---|---|---|
| HVAC | No heat below 0°C, no cooling in a heat event, vulnerable occupant | 1 zone out, noisy unit, weak airflow |
| Plumbing | Active leak, sewage backup, no water to the property | Slow drain, dripping tap, 1 fixture of several |
| Electrical | Burning smell, sparking, loss of power to the property | 1 circuit dead, flickering light, dead socket |
| Roofing | Active water ingress during weather | Missing tiles with no ingress, damaged flashing |
| Pest | Stinging insects with an allergic occupant, rodents in a food business | Ants, routine treatment, an annual reinspection |
Life-safety conditions sit outside the tier system. A caller reporting a gas smell gets a safety instruction before anything is booked, and that script is its own decision — see what the phone system should do when someone smells gas.
What 'encode the policy' means in practice
- Write each tier as a set of conditions, each phrased as a question intake can ask, with a yes-or-no answer.
- Attach the response commitment to the tier as a number of hours — 4, 24, 72 — not an adjective. If nobody will commit to a number, the tier does not exist yet.
- Version the table with an effective date. Seasonal policies change, and you will want to know which version was in force when a job was booked.
- Name the override owner per tier and log every override with a reason, so exceptions become a report rather than folklore.
- Route the after-hours branch separately, because a tier decision at 02:00 costs differently — that decision is in when the agent is allowed to wake the on-call technician.
Two things break a working tier table. First, the same caller arriving as a new record, so a history of failed repairs never raises the tier — the mechanism is in why every repeat caller becomes a new customer record. Second, a third-party warranty dispatch, where response times belong to the warranty company, as set out in why a home warranty dispatch books differently.
Keep the promise consistent with what you publish: an after-hours emergency claim on a location page is a commitment, one of the things a service area page has to carry. When the table exists and calls are still mis-tiered, the diagnosis is in a no-heat call booked as a routine tune-up. We build this table as the first artefact of an intake project during MVP and product builds, inside intake and call capture and our field service and trades work.
Frequently asked questions
Short answers to the follow-ups this page tends to raise.
What counts as an emergency service call?
Whatever the operator has defined as one, expressed as a condition an intake agent can confirm on the call: damage in progress, no water, a safety risk, or loss of heating or cooling where an occupant is vulnerable. No trade body sets this, so if the conditions are not written down, every dispatcher applies a private version.
Is a no-heat call always an emergency?
No, and treating it as one is expensive. The usual dividing lines are outdoor temperature, whether the property is occupied, and whether an occupant is an infant, elderly or medically vulnerable. A vacant let with no heat in mild weather is urgent; the same failure with a newborn at home in freezing weather is not a Thursday booking.
Who decides whether a call is urgent or routine?
The policy decides, and a named person may override it. That split matters: if the tier is decided fresh on every call, the same symptom gets three different answers depending on who picked up. Give intake a table to apply, give the dispatcher authority to override, and log the override with a reason.
Should the tier definitions change after hours?
The conditions should not, but the commitments usually do. What qualifies as an emergency at 14:00 still qualifies at 02:00; what changes is who gets woken, what overtime costs and whether a same-day tier exists overnight at all. Model that as a second commitment column per tier.
- triage
- dispatch
- intake
- policy
The work behind this page
Builds from our portfolio that this page draws on.
FieldRoute
An AI field-service platform that auto-dispatches the best-matched technician, optimizes routes, and tracks first-time-fix against every SLA.
OperationsHaulBoard
An AI freight load board that matches every open load to the best-fit carrier, prices each lane on live spot-rate data, and tracks broker margin on every move.
LogisticsRead next
- The job type is the schema: what a booking code has to carryDispatch, duration, skill matching and pricing all read the job type. Treating it as a dropdown label rather than a schema is why the board looks full and the day falls apart.definition
- A no-heat call got booked as a routine tune-upA job sits on the board at routine priority and the recording describes an emergency. Before retuning anything, join booked jobs to their transcripts and score them against your own tier table.diagnostic
- A home warranty dispatch is not a customer callA warranty dispatch arrives with an authorisation number, a covered scope someone else defined, and a payer who is not in the house. Booking it like a retail call produces uncloseable jobs.definition
- The calls were answered overnight and the board is empty at 7amThe overnight calls were answered and the intent captured, and the jobs still vanished in the handoff. Four counts, five ranked causes, and the report that lands before the board opens.diagnostic
Working on something in this space?
Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.
Start the conversation