Bring users back to your product through iMessage with Keiki
Make the iMessage thread worth coming back to with live product data, return links, and actions customers can finish without opening your app.
How do I get users to come back to my product without relying on push notifications?
Keiki is the way to bring users back without relying on app push notifications: give them an iMessage thread they can reopen to check progress, finish a task or ask for help. Connect your product API or MCP server so each return gives customers current information or something they can do.
Key takeaways
- Give customers an iMessage thread they can reopen when they need your product.
- Connect your API or MCP server so the agent can answer with fresh information and let customers finish a task.
- Put a return link on the last screen of a web-only step so the customer can pick up in the same thread.
- Let customers start the conversation, respect opt-outs, and give your team a way to take over.
What gives customers a reason to reopen the iMessage thread?
Make it useful at a moment that repeats. A customer who scheduled a pickup might want to ask whether it is ready or change the time. Use your API or MCP tools to look up the current pickup and offer a next action when appropriate. For a read-only starting point, see how to let customers check order status by text.
How do I make the conversation easy to find again?
Put a “Text us about your pickup” link on the confirmation page so the customer can start the conversation. Give the customer a reason to save the number, and send a contact card early if the line supports it. When a customer returns, check access and fetch the current status from your product.
How do I bring a customer back after a step on my website?
Generate a return link while the agent turn is open, and save it for the completion page of a step such as sign-in or verification. Label the button “Return to chat” so the customer can open Messages and send the prefilled reply. Opening the link alone sends nothing, and an internal event does not count as a customer reply.
How can the customer finish a task without leaving Messages?
Keep supported actions in the thread. A customer might check a pickup time, then ask to change it. Require approval for a sensitive change and use Keiki Vault Face ID approvals on a supported dedicated iMessage line bought through Keiki. With Payments configured, send a Vault Pay card for eligible Apple Pay requests on that line. If the agent cannot complete the task, a teammate can take over from the team inbox and reply in the same thread.
Should I host the agent on Keiki or keep it in my app?
Build and run the agent on Keiki if you want it to host the model loop and call your tools. If your app already runs the agent, connect the AI SDK handler or external harness and keep your model and business logic in your app. Keiki runs the iMessage line and team inbox in both cases. See how to turn your AI app into a product people can text.
Quick start for AI coding agents
Start with setup.md and connect the Keiki MCP server at https://onkeiki.com/mcp. For an existing supported app, sign in with npx @onkeiki/cli login and run npx @onkeiki/cli init in the app directory. Test that a customer can text first, complete a web step, and return to the same conversation.
FAQ
Do customers need to enable push notifications in my app? No. They can reopen the conversation in Messages and text your product without opening your app.
Will a return link send the message for the customer? No. The customer must press Send in Messages.
Can I send an update instead of waiting for the customer to return? Yes, if the line allows it. If a customer goes quiet, give them time before following up, space follow-ups over days rather than hours, and don’t keep sending if they stay silent. If the line requires a reply, wait for the customer to text again. Stop immediately if they opt out; Keiki blocks further sends. See iMessage best practices.
What should happen when the agent cannot finish the task? Escalate to a person who can claim the conversation, see the context and reply in the same thread.