Phone calls, Face ID approvals, and payments
What changed from October 10 to 29: more ways to reach your agent, approve its work, take payments, and bring a person into the conversation.
Short answer: Keiki added phone-call availability, Face ID approvals in Messages, payment tools, Auto model selection, and a queue for human handoffs. Developers also get a fetch-only cloud client, Code Mode MCP, shared Slack apps, and more native channel actions for externally run agents.
This update covers October 10–29, following our October 9 Changelog. First, the changes you can use from the dashboard. Then, the tools for developers building on Keiki.
What's new
Let your agent answer phone calls
Phone calls are out of early access. Give your agent a number and it can answer callers using the prompt, tools, and rules you already set up. Choose an area code and a voice, and connect more than one line to an agent.
Open an agent's Channels → Phone calls → Buy line. The monthly line cost is shown before you buy. Read about phone calls.
Approve actions with Face ID in Messages
Keiki Vault brings approval requests into your iMessage conversation. When an action needs permission, you can approve or decline it with Face ID instead of leaving the chat. Afterward, the card shows the result.
The recipient needs the Keiki Vault iPhone app. Cards work in one-to-one chats on a dedicated iMessage line bought through Keiki; other lines and channels don't receive them. Builders choose which actions require approval. Set up Keiki Vault.
Take payments through your agent
The Payments ability lets an agent sign up a business, send its customers payment links, and check whether they've paid. The business owner approves payment limits and refund requests. Each business receives money through its own Stripe connected account; Keiki doesn't hold the funds.
An owner or admin connects the organization in Settings → Payments, completes identity verification, and switches the account to live once enabled. Then turn on Payments in the agent's abilities. Setup and verification are required before the agent can take payments. Payments are in US dollars.
Choose Auto instead of a model
Select Auto in the model picker and Keiki chooses how to handle each message. Quick questions can stay in the conversation; longer work can run in the background. You can send follow-ups while that work is running.
Auto is available on Pro, Max, and Enterprise, not Starter. You can still choose a specific model yourself.
See which conversations need a person
The Handoffs queue in Conversations brings escalations into one place. See what's waiting, what someone has taken, and what's resolved. Reply to take over, hand the conversation back with a note, or resolve it. An agent-opened handoff stays with the person until they hand it back or resolve it.
If you've configured Slack escalations, a teammate can reply in the escalation thread to take over and answer the customer. There's no separate takeover button. Older Slack installations may need to be reinstalled for owner and admin matching. Read the handoff guide.
Find the replies that need attention
The Quality tab now shows Signals: praise, frustration, corrections, and other patterns in customer conversations. Follow a signal or a drop in mood back to the exchange behind it, rather than reading every thread.
Signals score turns containing a human message, not scheduled runs or internal notes. History is kept for 90 days. Read about Signals.
Connect more lines and request an Apple business channel
One agent can now have several iMessage lines. Add or move lines from the dashboard; replies stay on the number the customer texted. Each line belongs to one agent.
Apple Messages for Business is available by request, not self-serve. Open Channels → Apple Messages for Business → Request access. Keiki reviews the request and assigns the channel. Customers must start the conversation. Compare Apple Messages for Business and iMessage.
For developers
Use hosted agents from a fetch-only client
The new @onkeiki/agents/cloud entry point lets your backend or Worker provision deployments, stream completions, and verify callbacks without importing the local Bun runtime. Keep the API key on your backend; your app still authenticates users and binds their conversations.
Compose Keiki API calls with Code Mode MCP
Connect your MCP client to https://onkeiki.com/mcp/codemode with OAuth. Its two tools, search and execute, let you find operations and combine them in JavaScript without loading every API schema into the client. The existing /mcp endpoint remains available.
Programs can call Keiki operations, not arbitrary network endpoints. Normal permissions and billing still apply. Read the Code Mode guide.
Give external agents native channel actions
Agents running in your own app can now send targeted replies, react, edit, delete, and send files through the turn API where the channel supports the action. The AI SDK adapter also supports incoming reactions through onReaction in push and inbox modes, without starting another model turn.
Read the turn API and AI SDK guide.
Connect one Slack app to many customer workspaces
Use one Slack app across customer workspaces, with each workspace routed to its own agent. Create install links, then bind or rebind workspaces from the dashboard. Enabling this routing starts with the developer API; install links and binding require an active plan.
Set up customer Slack workspaces.
Pick a sending line for new conversations
If an agent has several iMessage lines, name the line when starting a new conversation. There is no default sending line; omitting it returns sender_line_required. Replies to incoming messages continue on the line the customer used.
The cloud deployment client also accepts imessageLines as a minimum line count. Lowering the count doesn't release existing lines, and additional lines are recurring add-ons. Read the deployment guide.
New setup guides and help in the docs
Use Ask the docs on any documentation page to ask a question and follow up. The new BYOK guide explains supported services, setup, and billing; BYOK requires Pro or above. The Vercel guide walks through running your own agent on Vercel with Keiki channels—it's a setup guide, not a promise of a public one-click connector.
For local callbacks, npx @onkeiki/cli dev --port 8787 creates a public tunnel to an app you've already started. It requires cloudflared, or separately configured ngrok, and exposes that port; keep your app's authentication enabled. Read the tunnel guide.
Open the dashboard to try these changes. Plan details and line costs are on the pricing page.