IER-0
Home
Product

Voice support

Hosted phone numbers route callers into project-scoped voice intake with call history, transcript context, approval boundaries, and voice-minute billing.

Numbers
Hosted

Workspace owners can choose and assign LiveKit phone numbers.

Routing
Project

Calls connect to the right project voice agent.

Billing
Minutes

Voice uses a separate hard-capped minute meter.

1.0

Voice intake is available

Workspace owners can provision hosted phone numbers from the voice surface and route calls into the right project context.

  • Hosted number search
  • Project assignment
  • Agent dispatch
2.0

Calls follow the same control model

Phone conversations create operational records instead of bypassing the governed support loop. Operators can review call history, transcripts, routing state, and voice-minute usage beside the rest of the workspace.

  • Call history
  • Transcript context
  • Voice-minute meter
3.0

Outbound remains bounded

Phone support is for support workflows. Bulk calling, cold outbound campaigns, and unreviewed high-risk actions are outside the product boundary.

  • No bulk campaigns
  • No cold outbound
  • Human-owned outcomes
Operations

What this means in production.

These pages describe the product contract behind the UI, not a decorative brochure. Each surface should connect back to the same governed support loop.

Control boundary

Hosted numbers are assigned to project voice intake.

Operator workflow

Support moves through secure ingest, AI preparation, human approval, outbound execution, and audit evidence.

Configuration impact

Provider setup, project policies, knowledge trust, retention, and billing limits decide how this behaves for a real workspace.

Proof points

Designed for governed support, not hidden autonomy.

Hosted numbers are assigned to project voice intake.
Call events are recorded for review.
Voice usage is metered with voice minutes.
Next

Keep exploring the operating model.