CASE STUDY

Case study: 24/7 urgent-ticket triage that calls a human until one answers

August 2026 · 5 min read · client name under NDA, numbers real

The business problem

An industrial services company receives maintenance requests around the clock. At 2 AM, a burning smell in a compressor room and a routine filter change look identical in the inbox: two unread emails. The dispatcher slept, the SLA did not.

The architecture

Watchers on the inbox read every incoming request the moment it arrives.
The triage decision runs on the iSol API: urgency, reason, escalation channels and an SLA, returned as JSON that the dispatch system consumes directly.
Escalation ladder: critical tickets fire SMS, WhatsApp and phone calls in sequence until a human confirms. The loop only stops on confirmation, never on delivery.
Everything is wired to the client's field-service system, so the ticket carries its triage with it.

The decision, live

The exact pattern, run today against the live gateway, with a night-shift message that must not wait for morning:

Real triage decision: critical, escalate via phone and SMS, SLA 15 minutes — Real call, captured 2026-08-19. Burning smell plus tripped breakers plus stopped line: the model flags critical, proposes phone-first escalation and a 15-minute SLA.

Real triage run: the overnight ticket comes in and leaves classified as critical, with escalation channels and SLA. 7.3s measured.

Results in production

Urgent tickets stopped waiting for a human to wake up: the human is woken by the ticket, by phone if needed.
Routine requests flow to the normal queue without interrupting anyone at night.
Every triage decision is logged with its reasoning, so dispatch reviews are arguments about facts, not memory.

What made it work

JSON out, not prose. The dispatch system consumes fields, not paragraphs. Constrain the output shape in the system prompt.
Escalate until confirmed. Delivery is not acknowledgement. The ladder stops when a person replies, not when a message sends.
Sovereign endpoint. Maintenance messages describe client sites and incidents; they stay on infrastructure under contract, with one audit log.

Replicate the pattern

The WhatsApp leg of the ladder is the WhatsApp guide, the inbox side fits Power Automate or n8n, and the triage prompt above is reusable as-is.

Ready to try it? Your key lives in the customer portal, isollm.ai/account → API keys. The endpoint is https://tokens.4clouders.com/v1. Prefer the outcome delivered instead of building it: that is exactly what iSol Squad is.

See plans →