> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tuco.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Apple Messages for Business vs an iMessage API

> Two different products. Messages for Business is Apple's inbound support channel on your brand entry points. An iMessage API sends outbound from a real line.

**They are different products solving opposite problems. Apple Messages for Business is Apple's official programme that lets customers start a conversation with your brand from Apple entry points, and it is inbound-first — the customer messages you. An iMessage API like Tuco sends outbound iMessage from a real, dedicated Apple line you control, so you can follow up with a contact who already engaged.** If you want a support channel customers discover through Apple, you want Messages for Business. If you want your CRM to send a blue-bubble follow-up, you want an iMessage API.

## Side by side

|                | Apple Messages for Business                                 | iMessage API (Tuco)                                                     |
| -------------- | ----------------------------------------------------------- | ----------------------------------------------------------------------- |
| Direction      | Inbound-first — the customer opens the conversation         | Outbound and inbound                                                    |
| Who starts it  | The customer, from Maps, Safari, Search or your buttons     | You, to a contact who already engaged with you                          |
| Identity shown | Your brand, with logo and brand name                        | A real phone number or Apple ID on a dedicated line                     |
| Approval       | Apple programme approval, plus a messaging service provider | No Apple programme approval; your line runs on dedicated Apple hardware |
| Typical use    | Customer support, order status, pre-sales questions         | Speed-to-lead follow-up, appointment reminders, re-engagement           |
| CRM sending    | Through your provider's integration                         | Direct from HubSpot, GoHighLevel, n8n, or the API                       |

## Why people confuse them

Both put your business into the Messages app, so search results treat them as the same thing. The practical difference is who is allowed to send first.

Messages for Business is designed so a customer taps a button and lands in a conversation with your brand. It is excellent for support, and Apple gives it brand identity — your name and logo. What it does not give you is the ability to initiate outbound campaigns to a list.

An iMessage API is the other half. Tuco provisions a dedicated line on real Apple hardware, checks whether each contact can receive iMessage, sends from that line, and routes anyone who cannot to your SMS fallback. That is what makes CRM-triggered follow-up possible.

<Info>
  Outbound capability is not permission to cold-message. Tuco is for warm contacts who already engaged — form-fills, ad opt-ins, replied prospects and customers. See [iMessage compliance and TCPA](/guides/imessage-compliance-tcpa) and the [anti-spam guidelines](/features/anti-spam-guidelines).
</Info>

## Which one you actually need

<Steps>
  <Step title="Customers should be able to find and message you">
    That is Apple Messages for Business. Apple approval plus a messaging service provider.
  </Step>

  <Step title="Your CRM should send a blue-bubble follow-up after a lead engages">
    That is an iMessage API. Start with [Send iMessage from HubSpot](/guides/send-imessage-from-hubspot) or [from GoHighLevel](/guides/send-imessage-from-gohighlevel).
  </Step>

  <Step title="You need both">
    They coexist. Messages for Business handles inbound support; a Tuco line handles outbound follow-up.
  </Step>
</Steps>

## Getting started with the API side

Check availability, then send. Both are single calls — see [Check iMessage availability](/features/check-availability) and [Send messages](/features/send-messages), or the [API reference](/api-reference/introduction). Non-iMessage contacts come back as `fallback` so you can route them to SMS: [Failures, fallbacks and delivery outcomes](/features/failures-and-fallbacks).

## Related

* [Does iMessage need A2P 10DLC registration?](/guides/imessage-a2p-10dlc-carrier-filtering)
* [iMessage vs SMS for sales](/guides/imessage-vs-sms-for-sales)
* [Automate iMessage sales outreach](/guides/automate-imessage-sales-outreach)