Skip to content
Guides7 min read

Run One AI Agent on iMessage, WhatsApp, Slack, Telegram and Email

Connect five channels to one agent, keep the same tools and instructions, and learn where channel features, identity and memory differ.

Cracked, grainy painting of an arm raising a gold crown tipped with blue stars against a deep blue sky, white clouds and orange foliage

Keiki runs one AI agent on iMessage, WhatsApp, Slack, Telegram and email. You keep the same instructions and tools, then connect each channel to that agent.

For customer reply times, conversation depth and handoffs by channel, read what we learned from 66,000 messages.

For example, a bike shop can let customers ask about a repair by text, send a photo on WhatsApp, or email a receipt. Staff can ask the same agent for a repair update in Slack. The repair system stays the source of truth; the channel is where someone asks.

This is a setup guide, not a promise that every channel works identically. A phone number, a Slack app, a Telegram bot and an email inbox are separate identities. Connecting them does not automatically merge private conversations. It's part of our guide to customer-facing AI agents.

What stays the same, and what changes?

The agent's instructions, tools and memory system sit above the channel layer. You don't need five copies of your repair-status tool. The connection and presentation change.

ChannelWhat you connectWhat the person getsWhat to watch
iMessageA dedicated line, or a shared number with a join codeMessages, with tapbacks and voice notes on supported linesFeatures depend on line type; shared numbers only reply to people who text the code
WhatsAppA business number through guided signup, or your existing setupText, photos, voice notes and native cardsReplies outside Meta's service window are restricted
SlackAn app created from Keiki's manifestThreaded answers and native cardsInvite the app to channels it should read
TelegramA bot token from @BotFatherA bot with files and voice notesGroups need their own reply-mode and privacy decisions
EmailAn inbox, optionally on your domainReplies in the same thread, with attachmentsCustom domains need DNS verification; email has no tapbacks

See the channel reference for capabilities and limits, and pricing for current costs.

Step 1: Give one agent one useful job

Create an agent in the dashboard. Connect the system it needs through tools or an MCP server.

For the bike shop, the instructions could be:

Help customers check repair progress. Look up the repair before answering. Don't invent a completion time. If the customer disputes a charge, get a person involved.

This is an illustrative configuration, not a deployed customer story. Start with a read-only lookup. Decide which actions need approval before adding writes.

Adding a channel doesn't create permissions in your system. Decide how someone proves that a repair is theirs before a tool returns private details.

Step 2: Connect iMessage and WhatsApp

Open the agent's Channels tab. For iMessage, buy a dedicated line or use the shared number and its join link. On a shared number, the contact sends the join code first; this isn't a dedicated identity for your business.

Connect WhatsApp through guided signup: log in with Facebook, choose the business and verify the number. Existing setups have their own connection options in the channel reference.

These are separate connections. Don't assume buying an iMessage line also gives you a WhatsApp account on that number. Connecting non-iMessage channels requires an active plan.

Send a real message on both channels. Ask the same repair question and check that both answers use the repair tool rather than guessing from the instructions.

Step 3: Add Slack, Telegram and email

Connect these identities to the same agent, not to three new agents.

  • Slack: create the app from Keiki's manifest, install it and invite it to the channel where you want answers. Follow the Slack setup guide.
  • Telegram: create a bot through @BotFather and paste its token into the connection dialog. Keiki sets the webhook.
  • Email: create an inbox. On your own domain, add the DNS records shown and wait for verification.

Repeat the repair lookup from a Slack thread, a private Telegram chat and an email. Check the email reply lands in the original thread. In Slack, check the app only sees channels it was invited to.

Don't test private customer records in a public channel. Staff and customer tools need explicit access boundaries; separate agents may be the right choice when their permissions differ.

Remember customers without mixing them up

One agent is not one public memory bucket. Keiki has a common memory system, but conversation memory is scoped to the agent and conversation identity. Slack DM threads use the same DM memory; that is not a blanket merge across every channel.

A Telegram user ID, a phone number and an email address don't prove they belong to the same person. Don't promise that someone can switch from email to Telegram and automatically resume a private conversation.

For the bike shop, keep the repair record in your own system. Verify the customer's account, then let an authorized tool fetch that record on each channel. Continuity comes from the record, not the model guessing that two names match.

Identity and permissions describes the principal and tool-scope contract, its rollout limits and the partner-deployment configuration path. It isn't a switch that merges conversation memory. Groups need extra care: members share the group's conversation.

Keep the answer useful on each channel

Share the job, not the exact message layout. A repair photo and a short status answer work in a text thread; a receipt belongs naturally in an email attachment.

Keiki uses channel-neutral tools such as reply and send_file. Native cards render on supported channels, including Slack and WhatsApp. Unsupported channel features return unsupported rather than silently sending something else.

For example, ask the agent to explain the repair status in text even when it also sends a card. Don't make the answer depend on an iMessage-only effect or an email reaction that doesn't exist.

A successful "hello" proves routing, not that your product is ready. Use a test repair record:

TestExpected result
Same question on all five channelsThe same repair tool returns the same underlying status
No matching repairIt says it cannot find the record, without inventing one
Lookup service failsIt says it couldn't check, without claiming the repair is ready
Another customer's repairThe tool refuses access; a matching display name isn't enough
Switch from email to TelegramIt requires verification rather than revealing the email conversation
An action needing approvalIt waits for the configured approval before running
A feature the channel lacksIt can still answer in text without claiming it sent an unsupported feature

Use real channel messages for this pass. Synthetic Live Test conversations don't read or write conversation memory, so they cannot prove returning-customer behavior.

Start with one channel, then add the others when their checks pass. See testing an agent before customers for a broader checklist.

FAQ

Do I have to build five agents? No. One Keiki agent can connect to all five channels. You still configure and authorize each connection separately.

Is it the same phone number everywhere? No. Slack uses an app, Telegram a bot and email an inbox. iMessage and WhatsApp each need their own setup; this guide doesn't promise one number for both.

Does one agent mean automatic cross-channel memory? No. Shared infrastructure isn't automatic identity linking. Use verified customer identity and your own records for continuity across unrelated channel identities.

Where should I start? Create an agent, connect one channel and test a real lookup. Add the next channel to that agent when the first works.

Sources

Product behavior checked against Keiki's documentation and implementation for this November 17, 2026 guide:

The bike shop and test messages are illustrative, not customer results or a live integration benchmark.

Published · Guides