Inbound
There is one inbound surface: attach a workflow to a phone number, and that number answers calls as they arrive rather than placing them. It is the answering counterpart to Campaigns — a workflow either answers, or a campaign dials it.
Attaching a workflow to a number
Carrier wiring — pointing the number at Woise so an incoming call actually routes in — is handled from the same place the workflow is attached, since the two have to agree with each other for a call to connect at all. A number with no workflow attached cannot answer; a workflow with no number attached can only be reached through an in-browser test call.
What happens on an inbound call
When a call reaches an attached number, Woise answers it and starts the attached workflow from its start node, the same graph you built for an outbound or test call. On a managed number, the call may open with a recording or AI disclosure utterance before the workflow's own greeting — see Recordings for when that applies. From there the call proceeds exactly as it would in a test call: the workflow's nodes drive the conversation, and the run is recorded under Reports and Recordings once it completes.
When a call does not reach the agent
If an incoming call does not reach the agent, check two things in order: that the number is attached to a workflow at all, and that the carrier wiring for that number still points at Woise. A number can be correctly attached in Woise and still fail to route if the number itself was repointed at a different destination outside Woise.
Common questions
What is Woise?
Woise is a managed platform for voice AI agents. You design an agent in a drag-and-drop workflow editor, connect a phone number, and it handles real inbound and outbound calls over the phone network or in the browser. The infrastructure, carrier setup and scaling are run for you.
Do I need a phone number to start?
You bring a number you already own and import it — that is the primary path today, and it means you keep your carrier relationship and your existing number. Agents can also take and place calls in the browser over WebRTC with no number at all.
How does billing work?
You are billed for the call minutes your agents actually use, metered as credits against your account. There is no seat licence and no per-agent fee, so an agent that takes no calls costs nothing to keep.
Can an agent connect to my CRM or calendar?
Yes. Agents can read from and write to your CRM, calendar and support tools through the integrations marketplace — you authorise each connection once with OAuth, and no credentials are stored in your workflow.
Do I need engineers to build an agent?
The workflow editor is visual, so building and changing an agent needs no code. There is also a REST API, a Python SDK and a TypeScript SDK if you would rather drive the platform programmatically, and an MCP server so coding agents can build workflows for you.
What happens to call recordings and transcripts?
Recordings and transcripts belong to your workspace and are available through the dashboard and the API. Raw transcripts, recordings and phone numbers are never handed to third-party analytics or error tracking without redaction.
What infrastructure do I have to run?
None. Woise runs the speech models, the language model turn, the call recording pipeline and the telephony legs for you, and scales them with your call volume. There is nothing to provision, patch or keep running.
Still stuck? Talk to our team.