Skip to the prototype
Book a call

Voice reception · Arden · capability prototype

The caller hears a voice. The operation sees a state.

Every reply has an intent, a safe state and a business action beside it. Scroll through one call, then drive the scenarios yourself.

No call is placed No microphone is used Authored synthetic fixtures

01 · One call, end to end

After hours.
Still answered.

  1. The phone rings at 21:47

    The team is offline. Arden answers inside approved coverage: known questions, prepared availability, structured capture. Everything else waits for a person, and says so.

  2. An approved answer, not an improvised one

    The question is classified before it is answered. Arden replies only from approved knowledge, so it cannot invent a price, a promise or a policy at midnight.

  3. A booking is prepared, not assumed

    Two real slots are offered and a hold is prepared. Nothing lands on the calendar until the caller explicitly confirms, because a wrong booking costs more than no booking.

  4. A person is one sentence away

    The moment the caller asks, automation stops. The handoff carries the reason, the context and the contact preference, so nobody repeats themselves tomorrow.

Prepared dialogue · no live model
Arden · reception line 01 01 / 04
Connected · after hours 00:06
A Arden · Bluerook reception Simulated caller · no real call
Intent—
Safe stateAnswering after hours
Business actionCall recorded

02 · Drive it yourself

Six scenarios.
Different obligations.

Choose what the caller wants. The conversation, the safe operational state and the business action update together, and a finished call can leave as a report you keep. These are authored fixtures, not a live language model or a production telephone system.

Local state only · report generated in-browser
Scenario console · six prepared paths

The call

Line 01 Ready · no real call
A Arden Prepared synthetic dialogue

What the operation sees

IntentApproved information
Safe stateKnowledge answer available
Business actionAnswered and logged
CalendarNo calendar change
OutcomeNo outcome recorded

Human boundary

Only approved information is used; uncertainty routes to a person.

03 · When Arden stops

The handoff lands
somewhere visible.

A handoff is not a transferred call ringing into the void. The bot goes quiet on that one thread, the conversation joins a queue a person actually watches, and the bot resumes only when the person is done. Take a thread over yourself.

Synthetic queue · anonymized implementation shape
Handoff queue · 2 waiting
Conversation auditLive counts · synthetic
Agent replies0
Resolved by agent0
Flagged to verify0
Billing question · caller asked for a person Waiting 6 min · bot muted on this thread · context attached
Complaint · tone flagged by the audit Waiting 14 min · flagged before anyone had to ask

Every reply the agent sends is auditable. Flags become corrections, and a person approves each correction before it changes live behaviour.

Control before automation

A useful voice system knows where it must stop.

Approved scope Routine, reversible actions only Approved answers · prepared availability · structured capture
Immediate handoff Relationship and exception work belongs to people Human requests · complaints · payment · uncertainty
Completion A call ends in an owned next state Outcome · responsible owner · next action, all visible
Privacy This page places no call and uses no microphone Authored fixtures · nothing recorded or transmitted

Voice becomes useful when the operation stays legible.

Try the live channel Discuss voice operations

The live speed-to-lead channel on the work page places a real call to your number, with consent and a one-call-per-day limit. This page stays entirely synthetic.