Voice out-of-scope: connect the call, or take the message?

Proposed — pending Fede review · 2026-08-15

The question. When a phone caller asks for something Clara can't do herself (the misdelivered-package call is the canonical case), what happens by default: Clara takes a message that lands in the team's inbox — today's behavior — or she says "Let me connect you with someone on the team" and forwards the live call to the office?

What's already settled (no decision needed)

What the decision actually changes

Only the calls where the caller did not ask for a person and there's no urgency: general questions past Clara's scope, notices to pass along, a stranger's package, "just a quick question," wrong numbers, and solicitors. Today those become a structured message (what they wanted, urgency, who they are, category) delivered to the team's inbox. The change would ring the office live instead.

Side effects to weigh

1 · The office phone starts ringing more, including for junk

Today the unknown-caller line quietly absorbs solicitors and wrong numbers as low-urgency notes. Forward-by-default sends those to the office too, unless we carve them out — and a carve-out means Clara deciding live who "deserves" a human, which is its own failure mode.

2 · After hours, the caller's outcome gets worse, not better

You ruled no-answer → office voicemail. But today's after-hours caller gets a structured note in the team inbox with urgency and callback number attached; a voicemail is unstructured, easier to miss, and the note never gets created. The caller also sits through ringing before learning nobody's there.

3 · It trades away part of what Clara is for

The pitch to the property team is that Clara absorbs interruptions so humans work uninterrupted. Forward-by-default moves calls back onto the office line — the metric moves in the direction the product exists to prevent. Worth doing only if the caller-experience win clearly outweighs it.

4 · We don't know the volume yet

No number exists today for how many calls per week this default would redirect (the count of messages taken where the caller never asked for a person). That's measurable from the last 30 days of unknown-caller notes and transfer outcomes before committing.

The measurement (done 2026-08-15 — option A executed)

All voice calls from the last 30 days were pulled from the call platform: 588 total, of which 150 were real-property calls (Camellia + Yale 25) — the rest were our own test robots and bench agents. Classing office hours as Mon–Fri 9–5 Denver (assumption — exact posted hours may differ slightly):

Every figure above traces to the pulled call records; nothing is estimated except the office-hours boundary, which is labeled.

Your options

A · Measure first — done, see the section above

Fede picked this on 2026-08-15; the numbers are in. The remaining choice is B, C, or D below.

B · Forward by default on the unknown-caller line only RECOMMENDED, NOW DATA-BACKED

The measured volume is small (~1–2 redirected calls per week, mostly reaching an open office), so the office-phone load is negligible and the caller-experience win is real. The five specialist lines keep current behavior — the data shows they already transfer everyone who asks.

C · Forward by default on all six lines

Consistent everywhere; largest shift of live calls to the office. Not recommended without the measurement.

D · Keep today's behavior, ship only the wording ruling

Messages stay the default; the already-settled improvements (handoff-first openings, transfer-on-request, "let me connect you" copy when transferring) still land. Zero new load on the office.

Context: the 2026-08-14 misdelivered-package call. Clara's old reply opened with "I'm not able to look up packages or coordinate retrieval from here…" — fixed the same day so the handoff leads. In the second half of that call, the caller asked for a person, the transfer connected, and the team member resolved it — the transfer path already works; this page is about when it should be the default.

PropFlow Docs