Skip to content
iMessage APIs
All answers

For business

Can you run customer support over an iMessage API?

Yes, and it works well — persistent threads, full-quality photos of the actual problem, and read receipts that remove the "did you get it" exchange. The catch is the expectation: a message in the same app as someone's family carries an implicit SLA of minutes, which is a staffing decision before it is a software one.

Which route

Apple Messages for BusinessThird-party API
Customer starts the conversationAlwaysEither
Entry pointsMaps, Safari, Search, your appA number you publish
Rich featuresPickers, forms, Apple PayText, media, reactions
SetupWeeks, via a CSPAbout an hour
Proactive outage noticesNot possibleYes

If support is inbound-only and you are large enough to work through an approved provider, Apple's programme is the better product. If you need to message customers first — an outage, a delayed order, a case update — only a third-party provider can.

Decide these before you publish the number

  1. Hours, published and honoured.
  2. A target first response — under fifteen minutes in hours, or the channel underdelivers on its own promise.
  3. A named rota, not "whoever sees it".
  4. An escalation path to a phone call.
  5. An out-of-hours auto-reply with a real time commitment and a genuine alternative.

The auto-reply that works

"Thanks — we've got this. Someone will reply by 9am. If it's urgent, call 555-0142." Specific time, real alternative. Not "we value your message", which reads as a machine and reduces trust in every later message from that number.

The full support playbook and who answers the replies.