CallsAround

The proof page

Anatomy of a 2 AM call.

A burst supply line on a Saturday night, from first ring to a crew commitment in under four minutes — with every piece of machinery that made it happen shown in the margin. This is what “rings until a human answers” actually means.

A representative walkthrough built on the real mechanics — 25-second hops, voicemail detection, whisper-and-accept transfers — exactly as they run in production. Want the unscripted version? The live demo line is at the bottom of this page.

Saturday, 2:04 AM. The phone rings.

2:04:11 AMHomeowner calls — burst supply line, water spreading across the first floor.

Second call of the night for them; first company that answered with a plan wins.

2:04:13 AMAI answers on the second ring with the company's own greeting and starts loss intake.

No hold queue exists to be stuck in — the agent picks up instantly, every time, in the voice and greeting the owner configured.

2:04:50 AMAddress, loss type, insurance status, and affected areas captured. Call flagged EMERGENCY.

The restoration template's triage rules decide what qualifies — the owner sets them, the agent applies them the same way at 2 AM as at 2 PM.

2:05:02 AMDispatch begins: on-call tech #1 rings. The caller is kept company, not on hold-music.

The escalation chain starts walking while the caller is still on the line — 25 seconds per contact before moving on.

2:05:27 AMTech #1 doesn't pick up. SMS alert sent; chain moves to the next contact.

Every hop is journaled and alerted — nobody wakes up Monday wondering why they never heard about Saturday.

2:05:31 AMTech #2's voicemail answers. Detected as voicemail — skipped, not counted as a human.

Voicemail detection is the difference between dispatch and theater: a greeting recording never bought anyone a truck.

2:06:02 AMOwner answers. Before the bridge: “Water loss at 41 Maple, first floor flooding, insurance filed.” Owner presses 1 — connected.

The whisper means the human accepts with context — no cold handoff, no groggy “...who is this?” with a customer listening.

2:07:30 AMOwner commits a crew for 3:15 AM. The caller never dialed a competitor.

Total time from first ring to a live human with the address: under two minutes — through two failed contacts.

2:08 AMRecording, transcript, and the full hop-by-hop journal are in the dashboard; the message is already in the job platform.

Native pushes to Jobber, PSA (Canam), or ServiceMonster; Zapier or the API for everything else. The 2 AM call is a job before the crew rolls.

And if the night had gone worse?

If nobody on the chain answers — after every contact is tried with retries and timeouts, the caller forwards to the fallback number and the entire team gets an SMS with the caller's number and an explicit this call went uncovered alert. A missed emergency is loud, never silent.

If CallsAround itself is having a bad night — a canary holds real conversations with the line around the clock, and on repeated failures the number flips to plain carrier call forwarding at the phone network, below our servers. Callers ring the backup phone instead of dead air, and the AI takes the line back when probes pass again. The full architecture is on the reliability page.

If it wasn't an emergency — a Tuesday-afternoon quote call never wakes anyone. It's qualified, captured, and filed as a structured message in the dashboard and your job platform. Judgment about what interrupts you is the product; the dispatch chain is reserved for the calls you defined as worth a 2 AM phone.

Don't take a timeline's word for it.

The agent in this story is not a mockup — it's answering a public line right now. Call it, describe an emergency, and try to trip it up.

Skeptical? Call the AI right now.

(410) 673-3601

You'll reach our demo company's line — the same agent your customers would get. Ask it anything. Try to trip it up.

Your next 2 AM call is coming either way.

Build your own version of this timeline in an afternoon: intake rules, on-call order, whisper transfers, failover — then sleep through the calls that don't need you.

Put a dispatcher on the night shift

Dispatch from $229/mo · month to month · live the same afternoon