CARRIER-GRADE TELEPHONY NETWORK
TELECOM SALES & DEMO: 1 (417) 835-0402
KaiCalls
Help Center

Phone work, handled with Kai

Ask Kai to make the call. Come back for the answer.

Connect your KaiCalls account to your AI assistant to request a supported call, check its progress, and read the result when it is available. You choose who Kai calls and what to ask. Account access and calling permissions still apply.

Kai working at a desk alongside an AI assistant

One business

Account access

Each connection is tied to the KaiCalls business you choose.

Secure sign-in

No shared password

Compatible assistants send you to KaiCalls to sign in and approve access.

Action by action

You stay in control

Reading, placing calls, and changing settings do not share one blanket permission.

Your first task

What do you need the call to find out?

Use an existing KaiCalls agent configured for the kind of outbound call you need. For an agent set up to check order status, give the business number and what you need to find out, then confirm the details before the call.

  1. 1

    Connect, then return to your request

    Sign in and approve access to the intended KaiCalls account. Return to the same conversation. If your assistant has lost the request, repeat the number and what you need to find out.
  2. 2

    Confirm the agent and the call

    Ask your assistant to use the agent configured for this task. Check the destination, the question, and any limits on what Kai may say or agree to. KaiCalls checks whether the call can be placed. India and Pakistan are not supported.
  3. 3

    Keep the call reference

    An accepted request is not an answer. Keep the call reference in the conversation so you can ask for progress without placing the call again.
  4. 4

    Ask for the result

    Ask “What happened on that call?” Review the summary or transcript when available. If the call did not produce an answer, decide what to do next; another call needs your instruction.
You can return to the conversation to check the result. Do not assume the assistant will notify you automatically or retry a call while you are away.

Set it up

Connect the assistant to the business you want to manage.

You need a KaiCalls login with access to that business. Your assistant must support a remote MCP connector, which is the secure link that lets it use approved KaiCalls actions. Some assistants limit this feature by plan or workspace role.

10-second picker

Which assistant is right for your setup?

ChatGPTZero setup

Easiest on phone & web

  • Official published app in the OpenAI Directory
  • Works on ChatGPT Free, Plus, and Team
  • Sign in once with your KaiCalls account
Open in ChatGPT
ClaudePaste 1 URL

Best for transcripts & analysis

  • Granular toggle for each of 39 actions
  • Deep reasoning on transcripts & voicemails
  • Direct link into Claude Connector Settings
Open Claude Settings
Meta Muse (Facebook)Paste 1 URL

Mac & mobile AI agent

  • Personal AI agent by Facebook / Meta
  • Works on Mac, iOS, Android, and WhatsApp
  • Built-in Sentinel safety confirmation
See Muse Setup
CursorOne click deep link

Builders & engineering teams

  • 1-click deep link prefills server config
  • Automate accounts across customer rosters
  • Git-backed prompt versions & CI eval testing
Launch Cursor Link

Remote MCP Connector URL

https://www.kaicalls.com/api/mcp

Paste into Claude, Meta Muse, Cursor, Grok, Gemini, Copilot, or any MCP client.

  1. 1

    Open your assistant’s connector settings

    Use its app directory or add the remote connector URL: https://www.kaicalls.com/api/mcp.
  2. 2

    Sign in to KaiCalls

    Complete the KaiCalls authorization screen using the account that can access the intended business.
  3. 3

    Choose one business

    If your login belongs to more than one business, select the one this connection may reach.
  4. 4

    Review and approve access

    Allow only the reading or account actions you want the assistant to perform.
  5. 5

    Run a real read

    Ask “Did I miss anything overnight?” and confirm the response reflects that business.
KaiCalls authorization screen showing business selection dropdown and requested permissions
The KaiCalls consent screen: pick which business this AI assistant connects to and review the approved permission scopes before clicking Allow access.

Watch the video tutorial

Adding the KaiCalls custom connector in Claude connector settings with https://www.kaicalls.com/api/mcp
Add KaiCalls as a custom connector in your AI assistant (e.g. Claude Settings → Connectors → Add custom connector) using https://www.kaicalls.com/api/mcp.

Pick your client

The installation effort depends on the assistant.

Filter by your preferred client to get direct shortcut links, commands, or setup steps.

ChatGPT

One click

Open the KaiCalls app and press Connect, then sign in. Nothing to paste.

Open ChatGPT

Cursor

One click

Opens Cursor with the connector already filled in. Approve it and sign in.

Open Cursor

Claude Code

One command

Run the command, then authenticate with /mcp inside Claude Code.

claude mcp add --transport http kaicalls https://www.kaicalls.com/api/mcp

Claude

Paste a URL

Opens Claude’s connector settings. Press “Add custom connector”, paste the KaiCalls URL, and sign in.

Note: On a Team or Enterprise plan, only a workspace owner can add a connector. If you do not see the option, ask whoever owns your Claude workspace to add it.
Open Claude settings

Gemini

Paste a URL

In Settings & help → Connected Apps, paste the KaiCalls URL under “Add a custom app link”, then sign in.

Note: Gemini offers custom connectors first in Gemini Spark, on personal Google accounts, and on the web. A Workspace account may not show the option.

Grok

Paste a URL

In grok.com/connectors, add a Custom connector and paste the KaiCalls URL.

Meta Muse (Facebook)

Paste a URL

In Muse for Mac or the mobile app → Settings → Connectors / MCP, choose “Add Server”, paste the KaiCalls URL, and sign in.

Note: Requires Meta Muse (Facebook / Meta) for Mac (macOS 15+) or Muse Code. Approve access when Muse Sentinel requests permission.

Codex

Edit a config file

Add KaiCalls to ~/.codex/config.toml, then let it sign in on first use.

Note: Support for remote connectors varies by Codex version; older builds need the mcp-remote bridge shown in the setup guide.

Manus

Edit a config file

In Settings → Integrations → Custom MCP Servers, add the KaiCalls URL with an API key as the bearer token.

Note: Manus needs a KaiCalls API key rather than a normal sign-in, so create one in Settings → API Keys first. If you’d rather not manage a key, use one of the sign-in options above.

VS Code & GitHub Copilot

Edit a config file

Add KaiCalls to .vscode/mcp.json, then approve the sign-in on first use.

KaiCalls in the official ChatGPT App Directory with Try Now button
KaiCalls in the OpenAI ChatGPT App Directory: click “Try now” to connect immediately on phone or desktop with zero manual URL configuration.

Confirm it works

A saved connection shows setup. A correct answer shows access is working.

  • The assistant completes KaiCalls sign-in without an authorization error.
  • The response to “Did I miss anything overnight?” contains data from the selected business, or clearly says there was no matching activity.
  • An approved change returns its own success or approval result. Reading account data does not prove the assistant can make changes.
  • A placed test call proves the assistant can start that call. It does not prove an inbound number or call route works from start to finish.

What you can ask

Ask naturally. KaiCalls uses the actions you approved.

Click Copy on any prompt to paste it straight into your assistant conversation.

Catch up on what you missed

The morning question, without opening the dashboard or listening to anything.

  • “Did I miss anything overnight?”
    Reads back last night’s calls, voicemails, and texts in one answer.
  • “Summarize the calls Kai handled this week and how many turned into leads.”
    Totals for the week, with the calls that produced a lead called out.

Fix how Kai talks

When a caller got the wrong answer and you want it never to happen again.

  • “Kai keeps flubbing the pricing question. Pull a recent call and fix it.”
    Finds the call, reads the transcript, and updates the agent so it answers right.
  • “We’re closed Sundays now.”
    Updates your hours so Kai stops offering Sunday appointments.
  • “Add our $149 drain-cleaning special so Kai quotes it correctly.”
    Adds the offer to what Kai knows, so it can quote the price on a call.

Chase leads and follow up

Have Kai place the calls and send the texts you would otherwise do yourself.

  • “Call the three leads from yesterday who never booked.”
    Kai places the calls and reports back how each one went.
  • “Text the customer from the 2pm call our address and a booking link.”
    Sends the text from your business number.

Test before you trust it

Run your saved voice tests against your own line whenever you ask.

  • “Test that the after-hours flow still works before I go to bed.”
    Runs your saved call scenarios and tells you which ones passed.
  • “I just changed the greeting. Run the tests again and tell me if I broke anything.”
    Re-runs the scenarios against the current setup and reports failures.

See what changed, and undo it

Every change is recorded, so "put it back how it was" is a real instruction.

  • “What changed on my agent last week, and who changed it?”
    Lists the changes with timestamps and where each one came from.
  • “Undo whatever changed the greeting last Tuesday.”
    Rolls that change back and confirms what the greeting says now.

Check usage and billing

Answer "am I about to get a surprise?" without a support ticket.

  • “Am I going to blow past my plan this month?”
    Reports the usage on record for this billing period, plus any plan change already recommended for the account.
  • “Why did my bill change?”
    Walks through the plan and add-on changes on your account.

Check nothing is quietly broken

Catch a dead calendar or CRM connection before a customer finds it for you.

  • “Is anything broken today?”
    Surfaces failed bookings, sync errors, and tool timeouts from your calls.
  • “Is my number actually answering right now?”
    Confirms which numbers are live and attached to which agent.

You stay in control

The assistant only gets the business and actions you approve.

Read account activity

The assistant can read calls, leads, messages, voicemails, and reports only when you approve that access.

Take an action

Calling a lead and other actions need separate permission and return their own result.

Sensitive changes

Agent activation, prompts, phone configuration, and other sensitive operations can require explicit confirmation or dashboard approval.

One business at a time

One connection reaches one selected business. Connect again and choose another business to work in a different account.
The assistant cannot skip phone company requirements, KaiCalls permissions, or approval steps. A preview or assistant response does not prove that an inbound call route, transfer, or phone number works on the live phone network.
KaiCalls tool permissions list in Claude showing granular access for read-only tools and actions
Tool permissions in Claude: review all 39 KaiCalls actions and control whether each is allowed automatically, requires confirmation, or is disabled.

Failure and recovery

Reconnect only after identifying where setup stopped.

The connector option is missing

Check the client path above. Claude Team and Enterprise may require a workspace owner; some clients or versions do not support remote connectors.

Sign-in or authorization failed

Remove the incomplete connector, sign in with the correct KaiCalls account, and authorize the intended business again.

The wrong business appears

Revoke the connection and reconnect, selecting the correct business during authorization.

It can read but cannot make a change

Review the connection permissions and any approval request. Changes use separate access, and important settings may need dashboard approval.
You can revoke the connection at any time. Revoking access stops future tool calls; reconnecting creates a fresh authorization.