Account
Composer
Composer is the assistant built into the Voxa console. Chat with it to build, debug, analyse and test your voice agents. It does the work for you with the same tools and permissions you have.
Open it from Composer at the top of the sidebar, from the command palette (⌘K), or with the Composer button on an agent’s page. The button starts a thread about that agent.
You can ask things like:
- “Walk me through building an agent for my dental clinic that books check-ups.”
- “Diagnose recent call failures.”
- “Review call analytics for the week.”
- “Make the reminder agent greet in Hindi and attach the FAQ knowledge base.”
- “Call +91 98123 45678 with the reminder agent.”
What it can do
Composer works through the Voxa API as you, in the workspace you have open, with your role. If your role can’t do something (a viewer can’t edit agents, for example), Composer can’t either. Every change it makes shows up in the audit log under your name with “via Composer”, and agent changes are saved as new versions like any other edit.
| Resource | Read | Create | Update | Delete | Run | Publish |
|---|---|---|---|---|---|---|
| Agents | list, get, versions | create, duplicate | edit, restore a version | delete | put live or pause | |
| API tools | send a test request | |||||
| Phone numbers | list | connect to an agent | ||||
| Calls | list, details, timeline | cancel or hang up | place a call | |||
| Batches (campaigns) | list, details | create from contacts | pause | cancel | resume | |
| Knowledge bases | list, details, search | create | add text or a web page | delete | ||
| Webhooks | endpoints, deliveries | add an endpoint | edit | delete | send a test ping | |
| Analytics | stats, CSV export | test post-call analytics |
It can’t talk to your agent for you. For a voice test it links you to the agent, where you press Test in browser. It never sees webhook signing secrets.
Threads
Each conversation is a thread. Threads belong to you: other members of the workspace don’t see yours. The first message names the thread, and you can rename or delete it from the thread list. Deleting a thread removes the conversation only. Changes Composer made stay.
Each message runs at most 8 steps (model calls). If Composer stops at the limit, say “continue”.
Approvals
Reading never needs approval. For everything else, the approvals menu under the message box sets what Composer may do on its own in the current thread:
| Mode | What happens |
|---|---|
| Ask for approval (default) | Composer asks before it creates, updates, deletes, runs or publishes anything. |
| Skip some approvals | Creating runs without asking. Updates, deletes, runs and publishing still ask. |
| Skip all approvals | Every action runs without asking. |
| Custom · By resource | Choose Ask or Allow for each resource and action (the table above). Anything you leave out asks. |
When an action needs approval, Composer pauses and shows a card with exactly what it will send. Approve runs it, and Composer carries on. Reject tells Composer you declined, and it continues without that action. You can’t send a new message while an action is waiting.
Pricing
Composer is billed from your workspace’s prepaid credits, per model call, at a price per million input and output tokens set by the platform. Each answer shows what it cost and how many tokens it used. Every charge is a ledger row of kind composer in Billing.
If the balance is zero or below, Composer refuses new messages with 402 and asks you to add credits. If credits run out partway through an answer, it stops after the current step.
Actions Composer takes cost what they always cost. A phone call it places is billed per minute like any other call.
Turning Composer off
Composer is on for every workspace by default. The Voxa team can turn it off for a workspace. It then disappears from the sidebar and the command palette, and its API answers 403 with composer is turned off for this workspace.
Composer is a console feature. API keys and connected MCP apps can’t use it. To drive Voxa from your own assistant, use the MCP server.