Billing
Understand what your organization is charged for, and where the numbers behind it come from.
This page describes the model — what is metered and how it is counted. It does not state a price, a rate, or a plan name.
Three terms carry the model:
- Run — one execution of a workflow against one caller. Every call produces exactly one.
- Duration — how long that run's call lasted, stored in seconds on the run itself.
- Rate — your organization's agreed price for a minute of call time, set when your account is set up.
What is metered
Call time, per run. Each run records its own duration when the call ends, and that duration is what an amount is calculated from. Usage is the same per-run record, listed and filterable — nothing on the billing side is computed from a different source than what you can already see there.
How duration becomes an amount
Duration is billed per minute, rounded up to the whole minute. A call that runs a few seconds past a minute boundary counts as the next full minute; a very short call still counts as one.
Why this matters
Rounding is applied per run, not to the period total. Two hundred short calls therefore cost noticeably more than the same total talk time gathered into a handful of long ones, which is worth knowing before you design a workflow that hangs up and calls back.
When your rate is fixed
The rate for a run is captured when the call starts, not when it ends and not when it is invoiced. A rate change part-way through a call does not apply to that call, and a run's recorded amount does not move afterwards.
Payments
Payments and payment methods are handled through Stripe. A failed payment is reported by Stripe and resolved the same way you would update any payment method on file; the purchase it was for stays unfinished until the payment clears.
Rates are agreed for your organization rather than published in these docs. This page describes how billing works, not what it costs.
For the consumption an amount is based on, start at Usage — it is the same per-run record, not a separate estimate.
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.