Cross-channel AI memory for iMessage, WhatsApp and email
Link verified identities to one customer record and give your Keiki agent the right context when a customer switches between iMessage, WhatsApp and email.
How can my AI agent remember customers across iMessage, WhatsApp and email?
Use Keiki to run the same agent on iMessage, WhatsApp and email, and give it a tool that looks up customer context by your verified account ID. Keep each thread separate: the agent can recall the same order, case or preference after a customer switches channels without merging transcripts or guessing who is texting.
Key takeaways
- Connect iMessage, WhatsApp and email to the same Keiki agent, so its instructions and tools are shared.
- Link each verified channel identity to a stable customer ID in your own backend. A display name or matching contact detail is not proof of identity.
- Give the agent a read tool backed by your API or MCP server. Look up relevant facts and current case status, not a dump of every conversation.
- Let customers continue a task on another channel only after you verify their identity there. Keep the actual transcripts separate.
- Use Keiki's team inbox for exceptions, and keep permissions and approvals in force when someone asks the agent to take action.
Does one AI agent automatically share customer history across channels?
No. Connecting iMessage, WhatsApp and email to one Keiki agent shares its configuration, not a customer's verified identity or conversation history. Keiki's hosted agent guide explains how channels share tools and memory settings. To carry account context across channels, have your product link the verified identities and give the agent access to a shared customer record.
How do I link an iMessage sender to the same customer on WhatsApp or email?
Use your own stable account ID and bind each channel identity only after the customer proves control of their account and of the identity they are linking. On eligible Keiki-bought iMessage lines, the conversation authentication guide describes receiving provider-verified sender evidence in a direct conversation and completing a linking challenge from the original sender. Verify WhatsApp and email identities through the account-linking flow your product controls. If there's no verified binding, ask the customer to link the account or send the conversation to a person instead of revealing account details.
What should an AI agent remember when a customer switches channels?
Give the agent a narrow API or MCP lookup for useful facts such as a support case, an order status or a saved preference. For instance, if a customer who opened a return over iMessage asks about it from a linked email address, query the returns system for the verified customer ID. The agent can report the current status without copying the original conversation into email. Use the live system for facts that change, as in this order status example.
How do I keep cross-channel memory from leaking customer information?
Authorize each lookup in your backend using the verified identity and check that the requested record belongs to that account. Don't accept an account ID typed in a message or picked by the model. Keep private account data out of shared notes and group chats. Test that an unlinked sender, a revoked account and a second customer cannot retrieve the first customer's record.
Account linking is not permission to act. For a sensitive write, still check whether the action is allowed and ask for approval where needed. On eligible iMessage lines, Keiki Vault can require Face ID for configured approvals, and Vault Pay can take Apple Pay in the thread when Payments is configured. If the request needs judgment, use Keiki's team inbox to handle it without asking the customer to start over. See how iMessage support handles exceptions.
Can I host my cross-channel agent on Keiki or bring my own model?
Build and run the agent on Keiki and attach your account lookup as a tool. If you manage the agent in code, the SDK can define the hosted configuration. If your app already manages the model loop and customer memory, use Keiki's external harness or AI SDK handler. Your app can keep its existing lookup and permission rules while Keiki handles turn delivery across the connected channels.
Quick start for AI coding agents
Read setup.md and connect to the Keiki MCP server at https://onkeiki.com/mcp. For an existing app, use npx @onkeiki/cli login and then npx @onkeiki/cli init in the app directory. Connect iMessage first and test a verified, read-only customer lookup before adding WhatsApp or email. Confirm that the linked identity gets the right record and a different sender doesn't.
FAQ
Does Keiki automatically merge iMessage, WhatsApp and email conversations? No. Use the same agent across channels and connect a shared customer lookup in your backend. Keep each channel's transcript separate.
Can I use my existing CRM as the agent's customer memory? Yes. Expose a narrowly scoped CRM lookup through an API or MCP tool, and have the backend authorize the lookup against your verified customer ID.
Can I link accounts just because the phone numbers match? No. Verify control of the account and each channel identity before linking them.
What should the agent do when the customer's identity is unknown? Ask them to link their account before giving a private answer, or route them to a teammate. A public question doesn't need private customer context.