duplex.gg
Dashboard
Use case · agent teams and realtime communities

Give every agent team a voice receptionist.

Duplex turns an agent stack into a live voice front desk: talk to a receptionist in Discord, route to the right specialist, capture the transcript, and hand work back to the agent system.

Try receptionist demo Connect Discord
Agent Ops
agent receptionist live
User: “Why did the workflow fail after approval?”
Receptionist: “Routing to Ops. Context: workflow failed after approval; inspect service state, gateway logs, and policy gates.”
Ops joins with onyx voice · transcript capture enabled · high-risk actions gated
7
agents
6
routes
100%
transcribed
Market map

Use cases beyond agent teams.

The wedge is receptionist/router infrastructure, but the same pattern sells into Discord communities, e-commerce, DevOps, creators, and service businesses.

Use-case selector
Primary wedge

Voice receptionist for autonomous agent workspaces.

Users speak once, Duplex identifies intent, routes to the right named agent, carries context, and lets any agent transfer back to the receptionist or another specialist.

Front door
Discord voice, Telegram voice note, Slack huddle, browser WebRTC
Buyer
AI operators, agent framework users, founders running multi-agent workflows
Integrations
agent profiles · workflow agents · MCP servers · skills · memory · cron/webhooks
Market read
A generic agent registry models the route graph, voice assignments, handoff summaries, and safety contract.
Example routes
ReceptionistOpsResearchPlanningAnalyticsBuilderReviewer

Profiles and agent identity

Map each specialist agent to a voice route, voice, permissions, and role description.

Messaging gateways

Use Discord/Slack/Telegram as the operator surface for approvals, summaries, escalations, and session links.

Tool calling

Let routed agents inspect systems, create tickets, search docs, schedule calls, or run workflows after voice confirmation.

MCP servers

Expose CRMs, Linear, GitHub, Shopify, calendars, docs, and internal systems behind a standard tool interface.

Memory and session history

Carry caller context and route history across transfers without making users repeat themselves.

Skills / playbooks

Package domain workflows like support triage, e-commerce returns, incident intake, and research routing.

Cron and webhooks

Trigger follow-ups, daily summaries, SLA alerts, missed-call recovery, and async agent work.

Approvals and safety

Gate high-risk actions with explicit spoken or operator approval before deploys, payments, orders, or sensitive access.

Routing UX

Users can switch agents by voice without losing context.

Receptionist is the home base. Any specialist can route back to Receptionist or transfer to another specialist with a compact handoff summary.

Interactive route switcher

Show the handoff loop, not just a static bot.

The product should make it obvious that users can say “I want Ops,” “send me back to the receptionist,” or “switch me to Builder,” and Duplex carries context across the transfer.

Receptionist
Speaking with
Receptionist
front desk router · alloy voice
live
I can connect you with Ops, Research, Planning, Analytics, Builder, or Reviewer.
Handoff summary
Session started with Duplex Receptionist. User can request a named specialist or describe the task.
High-risk actions require explicit confirmation before tools run.
Why this sells

Agent operators already have specialists. They need a voice front door.

The blueprint is simple: an agent voice registry, a routing contract, OpenAI Realtime sessions, Discord-first testing, and PSTN later.

Caller speaks naturally

Discord voice, browser WebRTC, or eventually PSTN via Twilio/Telnyx.

Receptionist routes intent

One short clarification pass, then a compact context handoff to the right agent.

Specialist agent answers

Each specialist agent gets its own voice, style, and routing contract.

Transcript becomes work

Call summary, approvals, blockers, and next actions are written back to the agent channel.

Voice registry

Receptionist
front desk router · identifies intent and hands off
alloy
Ops
lead operator · service health, deployments, incidents
onyx
Research
research briefs · markets, vendors, opportunity scans
shimmer
Planning
workflow specs · hypotheses, risk models, acceptance criteria
echo
Analytics
experiments · metrics, benchmarks, and caveats
fable
Builder
implementation · code, tests, change prep, debug loops
nova
Reviewer
review gate · regression, safety, release review
ash

Receptionist routing

“Why did the workflow fail after approval?”
routes to Opsoperations diagnosis
“Research free alternatives to Twilio.”
routes to Researchexternal research
“Design the onboarding route for VIP members.”
routes to Planningworkflow specification
“Compare provider latency across the last test run.”
routes to Analyticsbenchmark review
“Build the voice gateway endpoint.”
routes to Builderimplementation
“Review whether this is safe to deploy.”
routes to Reviewerindependent review

Voice safety gates

Transcript required for every call
Post-call task summary required
Explicit confirmation before deploys, credential changes, payments, or third-party calls
No sensitive external actions by voice alone

Deployment path

Phase 1: Discord/WebRTC with OpenAI Realtime proves the receptionist, specialist voices, routing, and transcript handoff without buying a phone number.

Phase 2: Add Twilio Voice Media Streams or another PSTN bridge for inbound calls.

Phase 3: Turn post-call summaries into tasks, tickets, PRs, or agent session resumes.

This is the killer wedge: Duplex is not only “AI in voice.” It is a receptionist layer for existing autonomous agent teams.

Build the voice front desk for your agent stack.

Start in Discord, prove routing and transcripts, then add a public phone number when the workflow is worth paying for.

Try demo Open playground