Bound the knowledge
The proposal identifies its source record so the team can inspect what informed the prepared response.
Voice Agent · Pro+
Prepare calls for a human handoff.
Use approved knowledge, bounded actions, confirmation states, and a visible owner when Voice Agent is ready.
RunBright Inbox
SMS · Connected for demo
Ava BrooksTaylor Morgan
Connected work#1048 · BK-1048OwnerTaylor Morgan
Preview only — no customer will be contacted
Require confirmation
Customer-facing actions remain paused for human review instead of implying autonomous execution.
Keep takeover available
The Inbox keeps a human owner and connected work visible when the conversation changes hands.
Ava Brooks · illustrative record
Move from prepared answer to owner.
- 1Capture the state
Use approved knowledge tied to Ava Brooks's source record.
- 2Check the boundary
Pause the customer-facing action when confirmation is required.
- 3Prepare the action
Keep success, failure, and awaiting-approval states inspectable in logs.
- 4Return to the record
Hand the conversation to Taylor Morgan with connected work still visible.
Labeled product and process proof
Product evidence, not human equivalence.
Voice Agent begins on Pro and requires provider availability, setup, approved knowledge, and explicit fallback rules.
Phone channels and Voice Agent depend on provider readiness.Voice Agent begins on Pro; provider availability and setup are required.
rB + automation logsControlled intelligence
Requires reviewrB
rB prepared
Prepare a reply from Ava's source record
Source recordAva Brooks · Website formdemo-customer-ava-brooks
Confirmation requiredA human must review customer-facing text
Preview state: Awaiting confirmation · no external execution
Automation logs
Human owner stays visibleRunStatusOwner
awaitingPaused · Awaiting approvalTaylor Morgan
succeededSucceededTaylor Morgan
failedFailedTaylor Morgan
Human takeover availableRequired confirmation and human ownership must be visible.
Readiness questions
Check the boundary before launch.
What does this product evidence show?
Voice Agent begins on Pro and requires provider availability, setup, approved knowledge, and explicit fallback rules.
What must be ready first?
Phone channels and Voice Agent depend on provider readiness. Voice Agent begins on Pro; provider availability and setup are required.
Guided beta onboarding
Move from prepared answer to owner.
Use approved knowledge, bounded actions, confirmation states, and a visible owner when Voice Agent is ready.