Use the platform from Claude Desktop

Claude Desktop can create an agent, edit a call flow, test it in chat, buy and connect a number, or review recent calls — by chatting. This uses a desktop MCP extension. It is separate from the in-app AI assistant.

Before you start

You need:

• Claude Desktop on Mac, Windows, or Linux.
• The Claude Desktop extension (.mcpb).
• Permission to create API keys. If Settings → API Keys is locked, ask a workspace owner or admin to create the key.

A key created here can act in the workspace. There is no read-only key. Treat it like a password.

1 Create your API key

1. In the platform, open Settings.
2. Under Developer, click API Keys.
3. Set Product to Portal. The description should read “API keys for the main platform.” Do not use Anti Bot.
4. Click Generate New Key.
5. Enter a memorable name, such as Claude Desktop, then click Generate Key.
6. Copy the key from the Key column. Use the eye icon to reveal it, then the copy icon to copy it.

Click to enlarge

Click to enlarge

More detail: Find or create your API key.

2 Copy your workspace ID

1. In Settings, click Workspace Details.
2. Click the copy icon beside Workspace ID.

You can also copy the small ID below the workspace name in the sidebar.

Click to enlarge

More detail: Find your workspace ID.

3 Install and configure the extension

1. Download the install file. Double-click it, drag it onto Claude Desktop, or in Claude Desktop open Settings → Extensions → Advanced settings → Install Extension.
2. Paste your API key into the API key field.
3. Paste your workspace ID into Workspace ID. This is Claude’s default workspace.
4. Ensure the Enabled toggle is on, then save.

Click to enlarge

Click to enlarge

You can review Tool permissions in the same screen. Claude still asks before destructive actions, even when a tool is allowed.

Click to enlarge

4 Check the connection

Start a new Claude chat and ask:

List the agents in my workspace.

Claude should return your agents, including their names, voices, and linked call flows. If it answers without using the extension, open the extension settings, confirm it is enabled, and start a new chat.

Asking Claude to create an agent is a stronger check: it should search available tools, confirm the connector is ready, and ask follow-up questions before creating anything.

Click to enlarge

Test an agent in chat

Ask Claude to hold a text conversation with the agent — the same as the Test panel in text mode:

Test my Front Desk agent — pretend you're an angry customer asking for a refund.

Claude starts a session, takes turns as the caller, then ends it. This works on ordinary prompt flows and on advanced (node) flows. Advanced flows run the real router and variable extraction, not a mocked preview.

This is a real call. It writes a call record and transcript, uses a small amount of credits, and bookings, webhooks, and transfers actually run. Tell Claude if those should hit test systems first. It does not check voice quality, speech recognition, interruption, keypad menus, or answering-machine detection.

What you can ask Claude to do

Agents and voices

• “Create a voice agent called Front Desk with a calm female voice.”
• “Find me a British male voice on ElevenLabs.”
• “Change the voice on my Front Desk agent.”

Call flows and prompts

• “Show me the prompt for the Front Desk call flow.”
• “Rewrite the prompt so the agent asks for the caller’s suburb before booking.”
• “Set the welcome message to ‘Thanks for calling Acme, how can I help?’”
• “Set transfers so billing questions go to +61…, warm transfer.”
• “Set office hours Monday to Friday, 9 to 5.”
• “Make the agent respond faster and be harder to interrupt.”
• “Add a post-call field that records whether the caller wanted a quote.”
• “Duplicate this call flow, then archive the old one.”
• “Create an advanced call flow from the receptionist template, validate it, then publish it.”

Do not write a greeting line in the prompt. The welcome message already plays it; a scripted opening makes the agent greet twice.

Tools during a call

• “Add an API tool that looks up the caller in our CRM.”
• “Add a code action that formats the booking reference.”

Store third-party keys as workspace secrets and tell Claude to use them. For a strict API, keep extra call metadata off the request.

Knowledge bases and workflows

• “Create a knowledge base called Pricing and add this text to it.”
• “Upload this PDF to the Pricing knowledge base and attach it to my call flow.”
• “Build a workflow that texts the caller after every missed call.”
• “Test it, then activate it.”
• “Why did the last run of this workflow fail?”

Phone numbers and calls

• “Search for available Melbourne numbers.”
• “Buy this number and bind it to my Front Desk agent.”
• “Register this Twilio number and bind it to Front Desk.”
• “Turn on call recording for this number.”
• “Call this number with the Front Desk agent.”
• “Show me yesterday’s calls.”
• “Give me the transcript and summary of the last call.”
• “Review this week’s Front Desk calls and tell me what went wrong.”
• “How many calls did we take this week, and what was the completion rate?”

Account information

• “Store this API key as a secret called crm-key.”
• “What’s my wallet balance?”
• “Show my recent charges.”

When Claude asks for confirmation

Claude asks before deleting agents, call flows, knowledge bases, or workflows; buying or registering a number; running a workflow for real; and placing an outbound call. Real workflow runs and outbound calls can send messages, contact people, and use credits.

For a safe rehearsal, ask Claude for a test run of the workflow. Texts, emails, calls, and webhooks are simulated as previews.

A text test call in chat does not ask for that confirmation. Treat it like pressing Test in the dashboard: side effects still run.

Important behaviour

• Do not write a greeting in the prompt. The welcome message already plays it.
• Editor drafts override live settings for test calls. If changes seem missing, ask Claude: “Check for drafts on this call flow and deactivate them.”
• Publishing a draft or advanced call flow changes live calls immediately.
• Transfers, in-call API tools, post-call fields, and attached knowledge bases are replaced as complete lists. Say “keep the existing ones and add this one.”
• Advanced call flows save without validation. Ask Claude to read the node-flow reference, then validate before publishing. Live calls use the published version.

Working across workspaces

Claude uses the workspace ID entered during setup. To work in another workspace, give Claude that workspace ID. The workspace must be attached to the same account that created the API key.

Troubleshooting

Current limits

The current release does not cover batch calling, message flows, agency features such as sub-workspaces, invoices, domains, team members or roles, adding funds, or connecting native integrations. Use the platform app for those tasks.

If you use Claude Code rather than Claude Desktop, install the matching plugin from the same project and run its setup command. The tools are the same; the extra slash-commands are Claude Code only.

Related: Find or create your API key, Find your workspace ID, Build an advanced call flow with nodes, Place a single outbound call, Create a custom API action for a conversation.