Platform architecture

Conversations become controlled business operations.

VoxDesk separates conversational intelligence, provider infrastructure, and business authority. The model can request an action; the server decides whether it is permitted and records the result.

Core principle

Customer interactionverified contextauthorized actiondurable CRM state

System map

One operational conversation layer.

Channels are adapters. Customer identity, authority, business actions, and outcomes converge in the same domain.

01

Channel gateway

Normalizes every interaction before business logic runs.

Web voice
Web chat
PSTN / SIP
Approved campaigns
02

Conversation intelligence

Maintains turns, language, intent, context, and requested outcome.

ElevenLabs realtime voice
Conversation state
Intent and risk
Context assembly
03

VoxDesk orchestration

Establishes tenant, policy, authority, and the workflow allowed to proceed.

Tenant context
Policy evaluation
Tool authorization
Specialist routing
04

Operations domain

Turns an authorized request into durable business state.

Contacts and leads
Appointments
Tasks and follow-ups
Human handoffs
05

Quality and control

Makes outcomes visible and keeps production changes supervised.

Audit trail
Analytics
Evaluation
Human-approved improvement

Voice provider boundaries

Each system owns one clear responsibility.

Conversational voice intelligence

ElevenLabs

Owns
Speech, turn-taking, interruptions, realtime agent sessions, and provider conversation history.
Does not own
Tenant authority, CRM writes, business policy, or campaign permission.

PSTN and SIP infrastructure

Telnyx

Owns
Phone numbers, inbound/outbound transport, caller ID, call-control events, and transfer primitives.
Does not own
Conversation reasoning, CRM state, or customer-operation decisions.

Customer operations control plane

VoxDesk

Owns
Identity, tenant scope, policy, tools, CRM state, campaigns, audit, analytics, and human review.
Does not own
Carrier infrastructure or the realtime speech engine.

Web voice

Configuration dependent
Customer browserElevenLabsVoxDesk toolsCRM

Production telephone

Activation required
Customer phoneTelnyxElevenLabsVoxDesk

Authorized execution

The model cannot directly write to the CRM.

Every consequential request crosses validation, tenant authorization, policy, session-aware risk evaluation, idempotency, and an audited domain service.

  1. 01Tool proposalThe voice or text agent proposes a typed business action.
  2. 02Signed contextVoxDesk binds the request to its conversation and tenant.
  3. 03Policy decisionAllow, deny, or escalate for human approval.
  4. 04Execution integrityIdempotency prevents duplicate consequential writes.
  5. 05Domain resultCRM, calendar, task, opportunity, or handoff state is persisted.
  6. 06Audit and responseThe decision and safe result return to the conversation.
Architecture implemented

See the customer-service operating model in action.

The public demo distinguishes persisted simulation, Web Voice, and carrier activation. No simulated interaction is represented as a real PSTN call.

Voice
Chat
Policy
CRM
Scheduling
Human handoff
Providers
Customer operations