Pass the Apple Messages for Business Experience Review

Before a brand can talk to customers on Apple Messages for Business, Apple reviews the whole experience: not just whether messages deliver, but whether the bot is honest, fast, and helpful, whether a person is always reachable, and whether each interactive feature is used the way Apple intends. That evaluation is the Experience Review. This page is Blooio's field guide to passing it on the first try, and staying compliant afterwards.

What Apple is actually checking

The review covers the journey end to end, in your internal test account: the entry point a customer taps, the automated welcome, how intent is captured, each use case, the move to a live agent, out-of-hours behaviour, and how the conversation wraps up. Reviewers judge tone, clarity, and flow as much as functionality. A build that works but reads like an SMS blast, dumps raw links, or leaves the customer stuck will fail.

Apple's own summary lives at Pass the Experience Review. The rest of this page turns it into an implementation checklist.

How the review works

Only your Messaging Service Provider can submit. With Blooio as your MSP the loop looks like this:

Click any step for detail. Drag to pan; use the controls to zoom or fit.

1. Finish the build. Apple does not review partial experiences. Every flow, entry point, and handoff must work in the test account.
2. Test on a real iPhone. iPhone is the primary surface. Test on a Mac as well, because layout and interaction differ.
3. Blooio submits. We capture an iPhone screen recording of the complete journey and send it to Apple with a summary of what each segment demonstrates.
4. Apple responds to the MSP. We forward every item, explain it, and fix it with you.

Most brands need one to three rounds. Brands that arrive with a complete, device-tested build usually finish in one or two. Brands on Blooio's managed bot typically finish in one, because the bot was built against this checklist.

The checklist

Each row below is something Apple evaluates, followed by the way to satisfy it on Blooio. If you use the managed bot, the right-hand column is already done.

Agent and bot

Conversation flow

The shape of a conversation that passes: disclosure, triage, a PII gate, a transparent handoff, and an open-ended close.

Rich content and interactive features

Naming, privacy, and policy

Apple's Conversation Design Standards and Policies are the source for these rules.

A conversation that passes

The Driftwood Home example above hits six rules in its first three bubbles: automated disclosure, a named assistant, the agent keyword, intro text before the interactive, a four-plus-one triage Quick Reply, and (further down) a yes/no gate before asking about the order. The same opening on Blooio:

curl -X POST https://api.blooio.com/v4/chats/chat_.../messages \
  -H "Authorization: Bearer bl_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Hi, I'\''m Juniper, Driftwood Home'\''s automated assistant. Type \"agent\" anytime to reach a person."
  }'

curl -X POST https://api.blooio.com/v4/chats/chat_.../messages \
  -H "Authorization: Bearer bl_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "text": "What can I help you with today?" }'

curl -X POST https://api.blooio.com/v4/chats/chat_.../messages \
  -H "Authorization: Bearer bl_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "interactive": {
      "kind": "quick_reply",
      "summary_text": "Option selected",
      "items": [
        { "id": "track", "title": "Track an order" },
        { "id": "return", "title": "Start a return" },
        { "id": "product", "title": "Product question" },
        { "id": "other", "title": "Something else" }
      ]
    }
  }'

Why brands fail

These are the findings we see most when brands come to Blooio after a failed review with another provider or a home-grown bot:

• Bot-only support. Apple requires a live agent during business hours. A bot with no escalation is rejected outright.
• A slow first reply. The welcome waits on a CRM lookup or an LLM call and lands after five seconds.
• No disclosure. A friendly AI persona that never says it is automated.
• Raw URLs and pasted policies. Links typed as text, or a privacy paragraph in the thread.
• Text-only flows. Asking customers to type "1, 2, or 3" instead of tapping a Quick Reply.
• Dead ends. A branch that answers and stops, with no follow-up offer or path to a person.
• SMS habits. "Reply STOP to opt out" and data-rate footers carried over from SMS.
• Wrong name. "Chat with us on iMessage" on the website button or in the bot copy.
• Asking for details too early. Requesting name and email in the welcome message.

The screen recording

Apple reviews a recording captured on an iPhone, submitted by the MSP. Blooio produces it, but it helps to know what it must show so you can sign off on the script:

1. The entry point being tapped (website button, QR code, Maps, or a link with an intent ID).
2. The automated welcome and disclosure, timed from the first message.
3. Triage, or direct routing when the entry point supplies intent.
4. Each top use case through to resolution, including every interactive feature you use.
5. A live agent handoff with the transfer notice, wait time, and agent introduction.
6. Out-of-hours behaviour.
7. Keywords: agent, help, menu.
8. The close: an offer of further help, with no "conversation closed" wording.

Feedback rounds

When Apple sends feedback:

• Read every item before touching anything. Several findings often share a cause (for example, one template that sends a bare URL in three flows).
• Bring in everyone who owns a piece. Copy, bot logic, agent training, and back-end integrations may all be involved.
• Fix all of it. A partial fix guarantees another round.
• Regression-test the whole journey on device, not just the flagged flows.
• Resubmit with a change summary that maps each change to a feedback item. Blooio writes this for you.

If an item is ambiguous, ask Blooio before changing anything. Misreading feedback is one of the most common causes of extra rounds.

Once Apple approves, the account is converted to commercial in Apple Business Register. Next you finish the brand assets and go live.

Experience drift

Passing once is not the end. Apple can re-check a live brand at any time and can turn the channel off if the experience stops meeting its standards. The usual cause is not a dramatic change but drift: a new prompt that makes the welcome slower, a campaign that adds a bare link, a new use case without a fallback, a model swap that drops the disclosure.

How Blooio and Apple keep a live experience in line with what was approved.

How Blooio handles drift:

• Continuous checks. Blooio replays your approved review script against the live configuration and checks response time, disclosure, Rich Link usage, triage options, keyword handling, and dead ends.
• Drift reports. When something moves out of bounds you get what changed, which rule it affects, and the fix. Managed-bot customers have the fix applied.
• Periodic reviews with Apple. Apple and Blooio review the experience from time to time. Keep your flows, copy, and agent playbooks in a state you would be happy to resubmit.
• Re-review for new scope. Adding payments, authentication, or new use cases is a material change. Blooio takes it back through review before it ships.

Treat every prompt or flow change like a code change: test it on device against this checklist before it reaches customers.

Have Blooio run it for you

Most of this page is engineering and process that doesn't differentiate your brand. Blooio's managed Apple Messages for Business bot is built against every rule above, keeps a person in the loop for every conversation that needs one, and plugs into your systems for orders, bookings, accounts, and payments. We record and submit the review, handle the feedback, and monitor drift after launch.

• Start a managed launch
• See how it works

Related

• Launch Apple Messages for Business
• Apple Messages for Business overview
• Interactive messages
• Rich links & media
• Conversation lifecycle
• Capabilities & limits
• Apple: Pass the Experience Review