never_say lists and hard gates - and a policy layer is in
build.
You build these workers with SuperDialog, the
open-source agent framework, and a
playbook is the instruction set a worker
runs against. SuperDialog’s defining rule -
the wire carries text, not audio - is what lets
the same playbook drive a phone call, a chat thread, or a browser session.
The primitives
On the spine
A worker reads context and the entity it was dispatched for, then acts: each task produces an interaction on the entity’s conversation, and each interaction closes with a structured outcome. Task dispatch, tool calls, handoffs and completion all emit events. Workers never write to the spine directly outside their task - what a worker learned reaches the Context Engine through the outcome, not through a side channel.What stays hidden
Model-provider orchestration internals stay hidden: which LLM served a given turn, provider failover, prompt assembly, and inference routing. You declare the playbook and the tools; the workforce decides how to run them. A provider outage is Unpod’s problem, not a change to your agent.Status
Production. Voice agents carry production traffic today, spun up per task, with human handoff. Actions run today as tools inside voice agents. Browser agents are in build. Chat runs through the same workers via the Chat API.Go deeper
SuperDialog
The open-source framework you build workers with.
What is a playbook
The instruction set a worker runs against.
Build an agent
From a blank playbook to a running worker.
Task API
Dispatch a task - calling runs this way today.
Flows & Journeys
The workflows that dispatch tasks to the workforce.