United States
Telephony path: bring your own number
For US organizations, bringing your own number is the supported path. You add your own carrier credentials under Telephony configurations, then import a number you already hold — Woise dials through your carrier account, not a shared Woise-owned one. Managed number purchasing is not available in the US today — this is a scope statement about where the product is today, not an apology, and it is not on the near-term roadmap.
Because a BYO number carries the compliance posture you already hold with your own carrier, there is no KYC step layered on top of it for US organizations.
TCPA consent controls
Under Workflow → Settings → Compliance, you configure what your agent says on every call it handles — recording disclosure and AI disclosure, each with custom wording and a "speak within N seconds" requirement. Under Settings → Compliance, you maintain an organization-wide do-not-call list and a compliance audit trail recording every change to these settings.
These are controls you configure, not a guarantee Woise enforces for you. Bring-your-own calls route through your own carrier and your own dialing decisions; Woise's own outbound preflight does not currently block a BYO dial for calling-hours, do-not-call, or brand-registration reasons — those checks exist and are configurable today, with runtime enforcement for BYO traffic still ahead of us. The one thing Woise blocks unconditionally, on every US call regardless of source, is a dial to an emergency number.
These are controls, not legal advice. You remain responsible for having consent to call each number you dial.
Recording and AI disclosure
The recording-disclosure utterance is spoken automatically to a callee in a two-party-consent state, and the AI-disclosure utterance identifies your agent as an AI assistant for your business. Both are editable per workflow, under Workflow → Settings → Compliance, and both fire on inbound, outbound, and web calls when configured — not only on a managed number. We do not cite a specific statute section here beyond what our own settings pages already reference; treat these as the mechanism, and confirm the legal requirement for your own states with your own counsel.
The FCC know-your-customer duty
US carriers operate as resellers under an FCC know-your-customer obligation that flows down the chain: Woise vets the customers it carries traffic for, and a BYO customer is responsible for their own relationship and standing with their own carrier. In practice, this means Woise may ask you for basic business information when you connect a carrier account — this is a duty we and your carrier share, not a promise of any particular approval outcome.
Currency
Billing for US organizations is in USD.
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.