Settings
Organization settings cover the configuration that applies across every workflow and number in your organization, rather than any one workflow's own configuration.
Compliance settings
Compliance settings govern outbound calling for your organization: disclosure text, calling-hours restrictions, state allowlists, do-not-call handling, brand identity shown to callees, and the audit trail those decisions leave behind. Each of these is its own subsection:
- Disclosure — the recording and AI disclosure text spoken to callees; see Recordings for when disclosure actually fires.
- Calling hours — the windows outbound calls are permitted to go out in.
- State allowlist — which destinations your organization is cleared to call.
- Do-not-call — numbers your organization has opted out of calling.
- Brand — the identity presented to a callee, such as caller-ID branding.
- Audit — a record of changes made to the settings above, so compliance decisions are traceable after the fact.
These settings differ in what's required, and in some cases what's even configurable, by region — see Regions & compliance rather than treating one region's requirements as universal.
What lives outside settings
Per-workflow configuration — a workflow's own prompt, nodes, and connected number — is set on the workflow itself, not here. Settings is for the configuration that spans every workflow at once.
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.