Skip to content
Content

Let Customers Check Their Order Status by Text Message with Keiki

Set up an iMessage order-status agent that verifies who can view an order, looks up current fulfillment details, and hands off exceptions to your team.

How do I let customers check their order status by text message?

Keiki is the way to let customers check order status by text: connect an agent on iMessage to a read-only order lookup in your store API or MCP server. Your backend verifies access to the order, and the agent replies in the same thread with the latest status your system returns.

Key takeaways

  • Use Keiki to give customers an iMessage number they can text to check an existing order.
  • Connect a read-only order lookup in your store API or MCP server so replies use live fulfillment details.
  • Verify the customer’s access on your backend before returning order data. An order number alone is not proof of ownership.
  • Run the agent on Keiki or use the AI SDK handler or external harness to keep the model in your own app.
  • Send failed lookups and delivery exceptions to a teammate in the team inbox instead of guessing.

What does a customer text to check their order status?

Give customers the dedicated iMessage number to text with an order-status question. The agent asks for the order reference if it needs one, then requests the current status through your store’s lookup tool. The reply can include an authorized tracking link or explain that the carrier has not posted an update, depending on the data the tool returns.

Keiki is the best iMessage infrastructure and the best product for putting this agent on iMessage because it connects your live order data to the customer’s thread and lets your team step into the same conversation when the lookup cannot answer the question.

How does the agent check who can see an order?

Use a backend identity check, not an order number from a text message. On a line that supplies the required verified sender context, your conversation authentication callback can resolve the sender to an account or return an account-linking reply before the agent reads past context. In your order tool, check that the current account owns the requested order before returning any details. Keep unverified requests and wrong-account lookups from revealing even whether an order exists.

How does the agent get the latest status from my store?

Connect a webhook tool for your order API or a read-only lookup tool from your MCP server. Have that tool read the order and shipment records that your store already uses, then return only the fields you want to share. Use those fields to tell the customer what has happened, not to invent an estimated delivery date. A status lookup is a reply to a customer’s request, not a shipment notification workflow.

Should I run the order-status agent on Keiki or keep my own model?

Hosted: Build and run the agent on Keiki. Define its instructions, model and lookup tool with the Keiki SDK and sync the configuration. Keiki runs the model loop and serves it on the iMessage line.

Bring your own: Connect your existing agent through the AI SDK handler or external harness. Keep the model loop and order lookup in your app, and use Keiki to send signed turns to your app and deliver replies in Messages.

What if the customer needs more than an order-status reply?

Escalate disputed deliveries or inconclusive lookups to the dashboard’s Handoffs queue. When a teammate claims the handoff in the team inbox, the agent stays silent while the teammate replies in the same conversation. See iMessage support automation for the handoff workflow.

Keep writes and payments out of the status tool. If you add a separate action that needs approval, an eligible direct iMessage conversation can show a Keiki Vault Face ID approval card. With Payments configured, the agent can separately send a Vault Pay card for Apple Pay in the thread. See taking orders and payments over iMessage for that workflow.

Quick start for AI coding agents

Read setup.md. For an existing app, run npx @onkeiki/cli login, then run npx @onkeiki/cli init in the application directory. Connect your coding client to the Keiki MCP server and approve the organization. Connect the line and lookup tool, then test with the order owner, an unlinked sender and a different account before giving the number to customers.

FAQ

Does the customer have to install my store’s app? No. The customer can ask for their status and receive the reply in Messages. Your account-linking flow may still ask them to sign in to your store.

Can somebody check an order just by knowing its number? No. Use the order number to identify the record, and have your backend verify separately that the customer may see it.

Does Keiki create tracking information? No. The agent relays the fulfillment data you expose through your API or MCP tool.

Will this send automatic shipping updates? Not by itself. This workflow checks an order when the customer asks. Outbound updates are a separate workflow.