Introduction
Build voice agents that make and answer real phone calls, and learn where everything that shapes them lives.
You assemble an agent on a canvas, connect a phone number, and it holds a conversation — listening, deciding what to say, and acting on what it hears. The speech recognition, the language model, the speech synthesis and the turn-taking are wired together for you. What you supply is the conversation.
What runs on a call
Four things happen between a caller speaking and the agent replying. Every quality question lands on one of them, so they are worth knowing by name.
- Speech to text: turns the caller's audio into words as they speak, not after they finish.
- A language model: reads those words against the current node's prompt, then decides what to say and what to do.
- Text to speech: turns the reply back into audio, in the voice you chose.
- Turn-taking: decides the moment the agent starts talking — whether a pause means your turn or I am still thinking.
The first three are configurable per organization. The fourth is tuned rather than chosen, through the interruption settings on individual nodes.
Core components
- Workflow: a graph of nodes joined by edges. The graph is the agent — nothing sits behind it, and what you see on the canvas is what runs on the call.
- Node: one step in a conversation. A thing to say, a question to ask, a decision to make, a system to call.
- Edge: the rule for moving on — the model judging a caller's goal met, a keypad digit, or a condition on something already collected.
- Run: one execution of that graph against one caller. It carries the transcript, the recording, the cost and the outcome, and it is what every report is built from.
A workflow decides what happens. A number gives it somewhere to be reached. And a region, fixed when you sign up, decides which telephony path is open to you, which compliance rules apply, and which currency you are billed in. Everything else — voices, tools, knowledge, integrations — changes what the agent can do during a call, not whether the call can happen.
Design and configure
Everything that shapes what the agent does while someone is on the line.
| Goal | Guide | What it covers |
|---|---|---|
| Learn the vocabulary | Concepts | Workflow, run, node, edge, region — the words the rest of these pages assume |
| Place a first call | First call | New account to a real transcript, in five steps |
| Assemble a conversation | Builder | Adding nodes, drawing edges, testing without a phone number |
| Choose the right step | Nodes | All ten node types, what each holds, and when to reach for it |
| Decide what it says | Prompts | Per-node prompts, the global prompt, and why one big prompt fails |
| Pick how it sounds | Voices | Auditioning voices, saving a profile, and pointing a workflow at it |
| Act during a call | Tools | Calling out to your systems while the caller waits |
| Ground its answers | Knowledge | Documents the agent can consult instead of guessing |
| Change a live agent safely | Versions | Editing and publishing while calls are live |
Connect and deploy
Getting an agent onto the phone network and into your other systems.
| Goal | Guide | What it covers |
|---|---|---|
| Attach a phone number | Numbers | Connecting a number and choosing which workflow answers it |
| Reach your other systems | Integrations | The catalogue, and how authentication is handled for you |
| Answer incoming calls | Inbound | Routing an incoming number to a workflow |
| Call out to a list | Campaigns | Outbound batches, sources, and pacing |
Monitor and operate
What every call leaves behind, and how it is paid for.
| Goal | Guide | What it covers |
|---|---|---|
| Hear and read a call | Recordings | Where a finished run's audio and transcript live |
| See how agents perform | Reports | Outcomes across runs, built from what your agents extract |
| Track consumption | Usage | What is metered, and how to see it before the invoice |
| Understand the bill | Billing | How usage becomes an amount, and in which currency |
| Configure the organization | Settings | Org-level settings, including compliance configuration |
| Automate from your own code | API keys | Programmatic access and how keys are scoped |
Regions
Your region is fixed at signup. It is not a display preference — it decides which telephony path is open to you, which compliance rules you are subject to, and which currency you are billed in.
| Region | Guide | What it covers |
|---|---|---|
| All regions | Overview | What the choice affects, and what it cannot be changed to later |
| United States | United States | Connecting a number and the US compliance posture |
| India | India | Managed +91 numbers and the KYC requirement |
Start here
New to Woise? Read what Woise is for the shape of the product, then work through your first call, which takes an empty account to a real recorded conversation.
Common questions
What is Woise?
Woise lets you build AI agents that answer and make phone calls and chat on your website. You lay out the conversation on a visual canvas, try it in your browser, then connect it to a phone number.
Do I need a phone number to start?
No. You can build and test an agent in the browser without one. When you are ready, connect a phone number and choose which agent answers it.
How does billing work?
You pay for the minutes your agents use, from your credit balance. There are no seat fees and no per-agent fees, so an agent that is not taking calls costs nothing.
Which languages can an agent speak?
Agents can listen and speak in more than 40 languages, including English, Spanish, Hindi, Tamil and Arabic. You pick the language and the voice for each agent.
Can an agent connect to my CRM or calendar?
Yes. An agent can look things up and make changes in 26 apps, such as Salesforce, HubSpot, Google Calendar, Slack and WhatsApp, while the caller is still on the line. You connect each app once.
Do I need engineers to build an agent?
No. Everything is built in a visual editor, so you can create and change an agent without writing code. If your team prefers code, there is also a REST API and an MCP server.
What happens to call recordings and transcripts?
Every call keeps a transcript and its outcome, and audio is only recorded if you turn it on. Only people in your account can see your calls, and your account lives in the region you chose when you signed up.
What do I have to set up or run?
None. We run the speech, the language models, the recordings and the phone connections, and scale them with your call volume. There is nothing for you to set up or keep running.
How do I reach the team?
Email contact@woise.ai, call or WhatsApp +91 83412 34080, or use the form on our contact page. A person reads every message.
Still stuck? Talk to our team.