Apple Messages for Business: setup, requirements, pricing and providers

Apple Messages for Business is a good product for one job: letting iPhone users start a support or sales chat with a brand from Maps, Safari, Search or a button on its website. It handles that well. It also has limits that many teams only find after they've signed a provider contract. The biggest one is that the customer has to start the conversation. Your business can't text first.

This guide covers what Apple requires, how registration and provider selection work, where the costs come from, and how Apple Messages for Business compares with plain SMS and with a blue line (iMessage sent from a business line, which can text first). We make Ready, and we sell the blue line, so we'll say plainly when Apple's product is the better fit.

What Apple Messages for Business actually is

Apple Messages for Business (formerly Business Chat) is a customer-initiated messaging channel inside the iOS, iPadOS and macOS Messages app. The customer taps a "Message" entry point. The thread opens in Messages, showing your verified brand name and logo. Your agents or bots answer from a customer service platform.

The common entry points are:

• A Messages button or link on your website or in your app
• Your place card in Apple Maps
• Results in Safari, Spotlight and Siri searches
• QR codes and links in emails or packaging that open the chat

Once a thread is open, Apple's rich features are available. These include list pickers, time pickers for appointments, Apple Pay inside the chat, forms and authentication flows. That interactive layer is the real reason to choose it over a regular text.

The key constraint: outbound starts are not allowed. You can't send an order update to a customer who has never messaged you through the channel. You can't run a campaign or a reminder program on it. It's an inbound support and commerce channel, not an outbound messaging channel.

Requirements before you apply

Apple reviews every brand. Its guidelines change, so treat Apple's current Messages for Business documentation as the source of truth. In practice, these are the requirements teams prepare:

1. An Apple Business Register account tied to a managed Apple account for your company.
2. Verifiable company details: legal name, website and contact information that Apple can check against public records.
3. A Messaging Service Provider (MSP). Apple doesn't give you an agent console. You need a supported customer service platform to receive and answer messages.
4. Brand assets that meet Apple's specs: logo, colors and display name.
5. Staffing and service commitments. Apple expects real response coverage during your published hours. It also wants a clear plan for messages that arrive outside those hours.
6. Entry points you'll actually ship, such as the website button, the Maps listing and any links you plan to publish.
7. A tested experience. Your MSP walks you through sandbox testing before Apple approves the account for launch.

None of these steps is hard. Together they add up to a project with an owner, not something you finish in an afternoon.

The registration steps, in order

The rough order teams follow:

1. Pick your MSP first. Your choice of provider shapes the rest of the setup, because you connect your Apple registration to it.
2. Create the Apple Business Register account and submit company details and brand assets.
3. Register for Messages for Business inside Apple Business Register. Select your MSP and describe your use case.
4. Build and test in the MSP sandbox: routing, agent queues, bot flows, and any Apple Pay or authentication features you plan to use.
5. Submit for Apple's review. Apple checks the experience against its guidelines.
6. Launch your entry points: turn on the Maps and Search placement, publish the website button and train agents.

Apple doesn't publish a guaranteed timeline. Plan in weeks, not days, especially if your MSP integration needs engineering work.

Choosing a messaging service provider

Your MSP is the vendor you'll live with, so this decision matters more than the Apple registration. The providers on Apple's list are mostly enterprise customer service and contact center platforms. Examples include LivePerson, Salesforce, Zendesk, Genesys and Sprinklr. Check Apple's current list before you commit, because it changes.

Questions worth asking each provider:

• Does it fit your existing helpdesk? If your agents already work in one of these platforms, adding Apple there usually beats a standalone console.
• Which Apple features does it support? Not every MSP supports every rich message type, Apple Pay flow or authentication method.
• How does it handle other channels? Most of your customers still need SMS, email or web chat. One inbox for all of them saves agent time.
• What does it charge? Pricing is usually seat-based or bundled into a contact center contract.

What Apple Messages for Business costs

Apple doesn't publish a per-message fee for businesses. Your costs come from three places:

• MSP fees. These are seat licenses, platform tiers or conversation-based pricing set by each provider. They vary widely, and we won't quote numbers for them. Get a written quote that names the Apple channel specifically.
• Engineering time. You'll need integration, routing, bot flows and Apple Pay setup if you use it. This is often the largest cost for smaller teams.
• Staffing. Apple expects real coverage during your published hours. A chat button nobody answers is worse than no button.

For a brand that already runs a large contact center on a supported MSP, the extra cost can be small. For a 10-person company without that stack, the MSP contract alone may outweigh the benefit.

How it compares with SMS and a blue line

This is the comparison most teams need before they choose. A blue line sends standard iMessage from a business line. It shows up blue on iPhones with your business name and photo, and it can text first. We cover the "who can start the conversation" question in depth in iMessage for business vs Apple Messages for Business.

Worked example: a blue line for follow-ups

Assume a team uses one blue line to follow up with leads and customers. In a month it sends 2,000 segments and receives 1,500 reply segments. Reactions are free.

• Line: $99
• Messages: 3,500 segments × $0.06 = $210
• Blue line total: $99 + 3,500 × $0.06 for the month

Now assume the account already had its own number, and 1,000 segments go to Android users from it on Standard. That's 1,000 × $0.0075 = $8, plus 1,000 × $0.0045 in carrier fees. This excludes the optional compliance surcharge for scrubbing or landline validation, which is $0.003 per segment each when switched on and off by default.

That number registration still applies here. Registration costs $25 at submit, which covers the first month. After that the monthly charge is $25/mo for registration and $2 per number. For the full breakdown, see 10DLC cost: every fee explained.

The two Apple-side options do different jobs. If the customer comes to you from Maps looking to pay inside the chat, Apple Messages for Business wins. If you need to reach the customer first, a blue line or SMS is the only route, because Apple's channel can't.

When each option is the right call

Choose Apple Messages for Business if:

• Most of your inbound demand comes through Maps, Search or your website
• You already run a supported MSP with staffed queues
• Apple Pay inside the chat or structured pickers would genuinely shorten your flows

Choose a blue line if:

• You need to text first, for example lead follow-up, appointment confirmations or "your order is ready"
• You want iPhone users to see a blue thread with your name and photo
• You can work within 50 new conversations a day per line. Add lines for more, or turn on "Add lines automatically" to add one when the day's new conversations are used up.

For sizing guidance, see blue bubble texting for business.

Choose registered SMS if:

• You run campaigns, drip campaigns or high-volume notifications
• Your audience has a lot of Android users
• You care most about per-segment cost and broad reach

Many teams combine options. They might run Apple Messages for Business for inbound support, plus SMS and a blue line for outbound. In Ready, blue-line replies, reactions and group chats land in the same inbox thread as SMS. For how platforms wire that up through one API, see SMS API with iMessage, plus the blue line docs at docs.tryready.com/guides/imessage and docs.tryready.com/api/imessage.

Compliance doesn't disappear on blue

Whichever channel you choose, consent rules still apply to business texting. Text only people who agreed to hear from you, and honor opt-outs. On Ready's SMS side, STOP handling, quiet-hours holds and optional litigator and DNC scrubbing reduce risk. They don't replace your own consent records, and compliance stays the sender's responsibility.

The practical takeaway

Apple Messages for Business is an inbound, customer-starts-the-chat channel. You'll need an MSP, Apple's review and staffed coverage. Its cost is mostly your provider contract and engineering time, not a per-message fee. It's excellent when customers come to you through Apple surfaces and you want Apple Pay or structured flows in the thread.

If you need to start conversations, reach Android users or run campaigns, it won't do the job alone. Pair it with SMS, or use a blue line to text first in blue. If you want to try the outbound side, sign up and use your first 20 free one-to-one texts before you register. Then compare the setup work against your MSP quote.