iMessage API vs Apple Messages for Business
Apple’s branded channel or a phone-number iMessage API: who starts the chat, what customers see, and which phones you reach.
Who texts first
Apple Messages for Business: the customer. A phone-number API: either side.
Which phones
Apple’s channel is Apple devices only. A phone number also reaches Android over RCS or SMS.
Approval
Apple’s channel needs an approved provider and Apple’s review. A phone number does not.
The short answer
Reviewed . Current product facts
Use Apple Messages for Business when customers come to you first, from a Messages button on your website, app, email or Apple Maps listing, and you want them to see your verified brand name and logo. Use a phone-number iMessage API when you need to start conversations, text people who already have your number, include Android users or run group chats.
They are different products. Apple Messages for Business is Apple’s own business channel and requires an Apple-approved messaging service provider, Apple Business Register and Apple’s experience review. A phone-number iMessage API, including Comms by Osis, is offered by an independent provider; it is not an Apple product or an Apple-sanctioned channel. Facts below were checked against Apple’s documentation on 18 October 2026.
Side by side
Apple’s column comes from Apple’s published documentation. The Comms column describes Comms by Osis; other phone-number providers differ on price, outbound rules and fallback.
| Apple Messages for Business | Phone-number iMessage API (Comms) | |
|---|---|---|
| Who starts the conversation | The customer, from a Messages button, link, QR code, Maps listing or Wallet pass. Follow-up notifications such as order updates and appointment reminders are allowed with an opt-in notice; marketing needs the customer to have sent “subscribe”. | Either side on a dedicated line, subject to consent, spam prevention and line health. On shared test lines the contact texts first. |
| What the customer sees | Your brand name and logo. No business phone number, and you see an opaque customer ID unless the customer shares their number. | An ordinary phone number, with an optional contact card name and photo on a dedicated line. |
| Devices | Apple devices only. | iPhone over iMessage; Android over RCS on eligible lines, otherwise SMS. |
| Approval | An Apple-approved provider, Apple Business Register, brand assets and Apple’s experience review. Apple is not currently onboarding businesses that primarily offer medical or health services. | No Apple registration. Shared test lines start free; a dedicated number depends on available inventory. |
| Human agents | Required. Apple does not approve deployments without live agent support. | Optional. Hosted AI agents can hand off to people in the team inbox. |
| Group chats | Not supported; conversations are one to one. | Supported on dedicated lines: start an iMessage group chat through the API. |
| Rich features | Apple Pay, list and time pickers, forms, authentication, rich links and iMessage apps. | Tapbacks, typing indicators and read receipts where the channel supports them, polls (iOS 26 or later) and contact cards. Checkout links where Payments is enabled; native in-thread Apple Pay is coming soon. |
| Cost | Apple charges nothing; the provider sets the price. | Free shared line; Plus $50/month; Dedicated $200/month with $0 setup. AI usage is billed separately. |
Who can text first
No. Apple’s policies prohibit unsolicited messages: the customer has to start the conversation. After that, a business may send messages in the customer’s direct interest, such as order and delivery updates, appointment reminders, booking changes and account alerts, with Apple’s opt-in notice and an unsubscribe option. Promotional messages require the customer to have explicitly sent “subscribe”. When a conversation ends, the customer must start a new one before the business can message again.
A phone-number API can send the first message, but that does not make cold outreach a good idea. Providers apply their own pacing and safety rules, and a number that sends unwanted messages can be restricted. Message people who expect to hear from you.
Which to choose
Choose Apple Messages for Business if most conversations start on your website or app, your customers are on Apple devices, you staff live agents and you want Apple Pay and pickers inside the thread. Expect to work through an approved provider and Apple’s review before launch.
Choose a phone-number iMessage API if you need to reach customers who already have your number, start conversations such as reminders and follow-ups, include Android users, use group chats, or connect an AI agent or MCP client quickly. Some teams use both: Apple Messages for Business for inbound support from the website, and a phone number for everything else.
What Comms provides
Comms offers a hosted messaging API, signed inbound webhooks, a team inbox, optional agents and hosted MCP. Free is a shared test line with 100 messages/day. Plus is $50/month on a shared platform line. Dedicated is $200/month with $0 setup; it is a different plan with a dedicated number.
API line claiming requires workspace approval and available inventory. A denied claim returns line_claim_not_allowed; unavailable inventory returns no_available_line.
RCS requires a supported dedicated line, carrier enablement, and a compatible recipient. Sending currently supports one plain-text message to an E.164 phone number.
Porting requires approval and a supported number. Confirm port-in, port-out, geographic availability, fees, and timing before planning a migration. You can cancel replacement setup before submitting the transfer; a submitted transfer cannot be canceled from the setup panel.
AI usage is billed separately from messaging plans, through prepaid Comms credits or a connected customer OpenRouter account. No messaging plan includes AI usage. Review credit-purchase fees and model costs before enabling a hosted agent.
Test each provider
Use a consenting recipient and an eligible test line. Send a message with a stable retry identity, receive a reply, verify the webhook signature, replay an event, and reconcile a delivery receipt. Test explicit channel failures and uncertain sends separately. An accepted request is not a delivered message.
For a SaaS integration, use two tenants and prove that a reply cannot reach the wrong tenant. Check human handoff, opt-outs, credential scopes and line offboarding. Ask each provider for number control, supported countries, throughput and service terms in writing.
Get a dedicated line.
Dedicated is $200/month with $0 setup. Book a call to scope lines for your team, or start on a free shared line to test.