Receptionist routing is the killer demo for voice agents
A voice agent should not just answer. It should route. The Duplex demo starts with a receptionist, transfers to specialists, returns home, and carries context across every handoff.
The clearest Duplex wedge is a voice receptionist for Discord-native communities and autonomous agent teams.
Voice becomes useful when it moves work
A standalone talking bot is easy to copy. A receptionist that routes voice into existing agents, channels, tools, and approval flows is much harder to replace.
The core interaction is simple: start at Receptionist, ask for a named agent, transfer with context, return to Receptionist, and continue without losing the thread.
The market wedge
Traditional AI receptionist tools focus on phone calls, missed leads, and appointment booking. Discord and agent-workspace users have a different problem: people do not know which channel, bot, moderator, specialist, or tool should handle the request.
Duplex can become the front desk for that environment.
The technical wedge
Agent teams already run specialized agents. Duplex should expose those agents as voice routes, then use transcripts, memory, MCP, skills, and approval gates to turn spoken requests into auditable work.
That is the difference between “AI voice bot” and “voice control plane for agent teams.”
See the realtime voice stack results.
Review the public Duplex scorecard for PersonaPlex, OpenAI Realtime, Gemini Live, Pipecat, and other SOTA candidates.