Apple Messages for Business vs iMessage API

The short answer

Apple Messages for Business is Apple's official channel, where the customer starts the chat through an Apple-approved provider. Flow gives your AI agent an iMessage line it can use like a contact, with its own rules, fallback and one codebase across channels.

Building on the iMessage API? Build on iMessage with Flow: one agent for iMessage, WhatsApp and Telegram. New to it? Read the iMessage API guide.

The short version

Both get called “iMessage for business”, and they are not the same:

Apple Messages for Business is Apple’s official service. Customers start a conversation from an Apple surface, such as a website button or Apple Maps, and a business replies through an Apple-approved provider.
A third-party iMessage API gives your server an iMessage line and a REST API with webhooks. Flow is one route built for AI agents.

Apple’s own FAQ says Messages for Business differs from consumer iMessage: the purpose is business-to-customer, it needs a business account registered with Apple, and it has business-specific features.

Side by side

	Apple Messages for Business	Third-party iMessage API
Who it is from	Apple	The API company
Who speaks first	The customer, from an entry point	Depends on the provider and plan
What the customer sees	A verified business in Messages, with an identifier Apple assigns	A phone number or handle the provider gives you
How you connect	Through an Apple-approved Messaging Service Provider	Directly to the provider’s REST API
Onboarding	A business account registered with Apple	An API key and a line
Automation	Allowed, with a live-agent escalation path required	Up to you, within the provider’s rules
Rich features	List picker and other business features	Tapbacks, effects, typing, media; varies by provider
Cost	Apple provides it free; the provider may charge	Provider pricing: per line, message or user
After the chat ends	You stop messaging until the customer starts again	Depends on the provider and plan

Sources: Apple’s Messages for Business FAQ for the first column. The second column describes the general model, and each provider’s rules differ. Checked October 2026.

How Apple Messages for Business works

A customer taps a Messages button and starts a chat. Apple’s FAQ lists these entry points: your website or mobile site, your iOS or iPadOS app, email marketing, QR codes and NFC tags, your Apple Maps listing, a registered business phone number (through Message Suggest) and Wallet passes.

The message goes from the customer to Apple, then to your provider, which routes it to an agent queue or to automation. The reply goes back the same way. Apple requires a blend of automated and human agents, so a way to reach a live agent is mandatory. Customers choose what personal information to share inside the chat. Apple’s rules also say you must respect STOP and UNSUBSCRIBE, and that once a customer ends a conversation you stop messaging them until they begin a new one.

You can’t build your own bot and connect it directly. Apple says automation must go through an approved Messaging Service Provider.

How a third-party iMessage API works

You get a line, a REST API and webhooks. Your server sends a message, and when someone writes to the line, you receive a signed event and reply. There is no Apple registration step on your side, because the provider runs the iMessage lines. What it does bring is provider-specific rules: who can write first, how many new contacts per day, groups, fallback, and what happens if Apple restricts a line. The iMessage API guide lists what to ask.

Which one fits

Use Apple Messages for Business when:

You want Apple’s verified business experience and entry points on your website, app and Maps listing.
Customers will start the conversation, and you have human agents ready to take over.
You are willing to work through an approved provider and register with Apple.

Use a third-party iMessage API when:

You want your server or AI agent on iMessage quickly, with a key and a line.
Your agent answers people who text a number, or you need the agent to write first (on providers and plans that allow it).
You want typing, tapbacks and effects in an agent that feels like a person texting.

Use both when your customers arrive from Apple surfaces and you also run a texting line for agents.

Where Flow fits

Flow is a third-party iMessage API built for AI agents. It gives your agent a US iMessage number, shared or dedicated, with typing, tapbacks, replies in groups the line is added to and SMS or RCS fallback. The same agent also answers on WhatsApp and Telegram and can expose its tools through MCP.

Flow is not an Apple Messages for Business provider. If you need Apple’s verified business channel, use an Apple-approved provider. If you need an AI agent that people can text like a contact, put it on iMessage with Flow.

Frequently asked questions

Is Apple Messages for Business the same as iMessage?

No. Apple's own FAQ says it differs from consumer iMessage. It is business-to-customer, it needs a business account registered with Apple, and it has business features such as a list picker. Apple also asks businesses to call it Apple Messages in customer-facing text.

Can I build my own bot for Apple Messages for Business?

Not directly. Apple's FAQ says automation and virtual agents must connect through an Apple-approved Messaging Service Provider, not through a direct technical connection.

Can my business start a conversation in Apple Messages for Business?

No. Apple says customers start a conversation by tapping a Messages button on a website, app, email, QR code, Apple Maps listing or similar entry point. When a customer ends a conversation, you must stop messaging them until they start a new one.

Do I need a human agent?

Yes for Apple Messages for Business. Apple's FAQ says deployments without a live-agent escalation path are not approved.

Does a third-party iMessage API need Apple approval?

Third-party iMessage APIs are not Apple products, so Messages for Business rules do not apply to them. Each provider sets its own rules, so ask what your line depends on and what happens if it is restricted.

Which is better for customer support?

If you need Apple's official, verified business experience with entry points on your website and Maps, use Messages for Business through an approved provider. If you need a simple line for an AI agent to answer customers who text it, a third-party iMessage API is quicker to start.

All posts: the Flow blog. The Flow docs have the reference.