Concepts
A handful of terms recur through the rest of these docs. This page defines each one the way the product actually uses it.
Organization
Your account and billing boundary. Phone numbers, workflows, integrations, tools, and teammates all belong to exactly one organization. Your business country is set once per organization at signup.
Workflow
A versioned graph of nodes and edges, designed in the builder. A workflow is a definition, not a call — saving it does not place or answer anything. A workflow can be in draft or published form; only the published version runs for real callers, while a draft lets you keep editing without disturbing production. See Versions & forks.
Node and edge
A node is one step in the conversation — greeting the caller, running a language-model exchange, collecting keypad digits, firing an integration. An edge connects two nodes and decides which one runs next, based on how the previous node resolved. The full catalogue of node kinds is in Nodes.
Workflow run
One execution of a workflow against one caller or WebRTC peer. A run is what actually carries a transcript, a recording, a cost, and a disposition — the workflow definition itself carries none of those. Every placed or received call, and every browser test call, produces exactly one run.
Campaign
A batch of outbound runs driven from an uploaded list of phone numbers, all using the same workflow and the same telephony configuration.
Inbound
The path by which an external caller reaches a workflow, as opposed to a workflow placing an outbound call. A number and a workflow are wired together for inbound the same way they are for outbound — through a telephony configuration.
Telephony configuration
The record that ties a workflow to a phone number and a telephony provider so it can actually place or receive calls. Without one attached, a workflow can only be reached through an in-browser test call.
Integration tool
A tool an agent node can call mid-call, or that runs after a call completes, backed by an external system you've connected — a calendar, a CRM, a spreadsheet. Integration tools are created and configured on the same Tools page as any other tool. See Integrations.
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.