How to delegate emergencies when you're the decision-maker.
The hardest delegation problem in a solo business: handing off urgent calls to people who don't have your judgment, your relationships, or your context. You can't hire a clone. But you can build a system that handles 80% of emergencies without you — and surfaces only the 20% that genuinely need a decision.
Quick answer
Most "emergencies" aren't decisions — they're routings. Pipe burst? Plumber. Roof leak? Roofer. Locked-out tenant? Locksmith. The actual decision was made when you picked the vendor. Delegation works when you separate routing (which can run automatically) from judgment calls (which still need you, but rarely). Build the routing first; the judgment calls naturally narrow.
→ The routing layer
OutOfOfficePro is the system this playbook describes.
Primary + backup vendor per category, two-sided dispatch closure, you cc'd or invisible. 14 days free.
Walk through a week of after-hours inbounds and sort them into two buckets:
Routing. The action is obvious; the only question is who. Most plumbing, HVAC, electrical, lockout, roofing, and pest issues fall here.
Judgment. Genuinely requires your decision. A dispute that could end a tenancy. A settlement offer. A client threatening to leave. These are real but they're rare — usually 1–3 per month.
The trap most owners fall into: treating everything as judgment because they handle everything personally, so it all feels equally weighty. Make the split honest and you discover delegation is mostly a routing problem.
The four levels of emergency delegation
Level 0: Nothing delegated
Every inbound hits you. You decide, dispatch, follow up, close. Most solo businesses start here. Sustainable for ~6–18 months before burnout.
Level 1: Manual forwarding
You receive the call, then you forward it. Slightly better — at least the work happens. But you're still in the loop and still on the hook for response time. This is most owners' "delegated" reality.
Level 2: Automatic routing with single coverage
Caller hits a routing URL or auto-attendant. The system picks the handler. You're cc'd. Big improvement — but if the single handler doesn't answer, the inbound stalls and you get pulled back in.
Where you want to be. Each category has primary + backup. The system tries primary; if no answer or vendor declines, backup auto-fires. Both handler and tenant can confirm closure. You see the result in a digest.
This is what OutOfOfficePro implements out of the box, and it's the structural shift that turns "delegated in theory" into "delegated in practice."
How to choose primary + backup pairs
Primary criteria
Speed. Picks up most of the time. (≥80% in your experience.)
Quality. You'd recommend them if a friend asked.
Billing. Invoices you cleanly without a separate scope conversation.
Backup criteria
Different availability profile. If the primary works 9–5, the backup should work nights/weekends (or vice versa). Two same-availability vendors aren't real backup.
Equivalent quality. Don't downgrade for the backup — same standard.
Geographic backup. If primary is across town, backup should be in-town. Or vice-versa.
The "what if they don't answer" problem
Most delegation systems fail at the silence point. The primary doesn't pick up; nothing happens; the inbound dies; the tenant calls you anyway. The system needs an explicit answer for silence.
Three options:
Time-based escalation. Auto-escalate to backup after X minutes of no response. Simple but slow.
Tenant-driven escalation. Tenant taps "they didn't answer, try next." Fast but requires tenant action.
Vendor-driven decline. Primary clicks "I can't take this" in the dispatch email; backup is auto-dispatched. Even faster than tenant escalation.
The best systems combine all three. Tenant gets a "try next" button. Vendor gets accept/decline buttons. After-hours timer fires if neither responds. (This is how OutOfOfficePro handles it.)
The "but they don't have my judgment" objection
Three responses, in order of effectiveness:
Most "judgment" is pattern recognition. A plumber who's worked with you for two years knows what you'd authorize. The judgment isn't being lost; it's being delegated to someone who's seen the patterns.
Set explicit thresholds. "Anything over $500, call me. Under, just bill me." That single sentence turns 90% of judgment calls into routing calls.
Accept that 5% of dispatches will be slightly suboptimal. The cost is way less than the cost of you handling 100% personally. Suboptimal-but-handled beats optimal-but-you-burn-out.
What to brief handlers on
One short conversation per handler. Cover:
What the dispatch email/SMS will look like. So they recognize it as legitimate.
What's in scope. Categories you've routed to them. Not other categories.
Authorization thresholds. "Under $X, just handle. Over $X, text me."
How to close the loop. Click the "I've got it" button; reply with photos when done; bill as usual.
What's "wake the owner." Genuine emergency requiring an owner-level decision. Define it tightly so it doesn't get abused.
The "still cc me on everything" stage
Most owners new to routing want to be cc'd on every dispatch — and that's fine, for the first 30 days. After that, the cc'ing becomes an anxiety habit, not a useful signal. Migrate to digest mode (one summary email per day) once you trust the system.
// The mechanical layer
The whole playbook, built in.
OutOfOfficePro implements primary + backup routing, vendor accept/decline links in dispatch emails, tenant try-next buttons, and a "summary / verbose / quiet" notification toggle. 14 days free.