LoopMessage

An omnichannel API covering iMessage, SMS, RCS and WhatsApp behind a single number — but no cold outbound.

Overview

LoopMessage's positioning is omnichannel rather than iMessage-specific. You get one number and one API, and messages route across iMessage, SMS, RCS and WhatsApp depending on the recipient. For a business whose customer list is genuinely mixed — some iPhone, some Android, some international on WhatsApp — that is a materially simpler architecture than running two vendors.

The iMessage feature surface is deep. Group chats with attachments and reactions, typing and read status, message threads for threaded replies, audio messages with automatic speech transcription, and expressive send effects. Transcribed voice notes in particular is a feature nobody else in this comparison lists, and it is genuinely useful if customers reply by voice.

The constraint you must understand before evaluating it: LoopMessage does not support cold outbound messaging. That is not a fair-use guideline, it is a product boundary. If your intended use is reaching prospects who have not messaged you first, this is the wrong tool and no plan tier changes that. If your use is replying, supporting, confirming and following up with people already in a relationship with you, the restriction may never bind.

Pricing is per dedicated sender with daily active contact ceilings rather than message counts, and there is a separate cheaper shared-sender track aimed specifically at AI assistants. They also advertise no sales calls and no upfront payment to test, which matches the developer-first posture of the rest of the product.

What stands out

What LoopMessage does well

Four channels, one number

iMessage, SMS, RCS and WhatsApp behind a single API and a single sender identity.

Voice notes with transcription

Audio messages arrive transcribed automatically — nobody else in this comparison offers it.

Threaded replies

Message threads are addressable, so a reply attaches to the message it answers rather than the bottom of the chat.

Group chats with reactions

Multi-recipient threads carrying text, attachments and tapbacks.

Automation-platform native

Zapier, n8n and Slack integrations mean a non-developer can wire a workflow without an engineer.

Cheap AI-assistant track

A shared-sender tier priced well below a dedicated line, aimed at assistant use cases.

Pick LoopMessage if

Businesses with a genuinely mixed iPhone, Android and international list
Teams that want WhatsApp in the same API as iMessage
Reply-first and support workflows rather than outreach
Developers who want Zapier, n8n, Slack and CRM hooks out of the box

Look elsewhere if

Cold outbound — explicitly unsupported, at any tier
Teams needing a shared inbox for non-developers
Businesses outside the supported number registration countries

The API

Send a message

Note the link in the message body — it carries UTM parameters, so when the customer taps it the visit is attributed to this exact campaign instead of vanishing into direct traffic.

Illustrative only

How the tagging works

bash

# Shape is illustrative. Confirm against LoopMessage's docs.
curl --request POST 'https://server.loopmessage.com/api/v1/message/send/' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "recipient": "+19998887777",
    "text": "Your booking is confirmed. Details: https://acme.co/visit?utm_source=imessage&utm_medium=messaging&utm_campaign=appointment-confirm"
  }'

Illustrative shape only — confirm the current endpoint and field names against LoopMessage's own API documentation before building against it.

Pricing

What LoopMessage costs

Tiers as listed on loopmessage.com. Prices are quoted as 'from', and the dedicated tiers are metered on daily active contacts rather than messages — model your own contact concurrency before comparing against a flat per-line competitor.

Sandbox

Test the API before paying. Capped at 5 contacts.

Full API access
Up to 5 contacts
No upfront payment

Light

$59.99/month, from

A dedicated sender for lower-volume conversation workloads.

Dedicated sender
300 daily active contacts
iMessage, SMS, RCS and WhatsApp

Regular

$99.99/month, from

The standard production tier.

Dedicated sender
1,000 daily active contacts
Full channel and integration access

Shared sender

$20/month, from

A cheaper shared-number track restricted to AI assistant use cases, with a free tier below it.

Shared sender number
Free tier available
AI assistant workloads only

Check current pricing

Last checked August 2026.

Feature checklist

Capabilities

Outbound iMessage(limited)
Two-way replies
SMS / RCS fallback
Group chats
Typing indicators
Read receipts
Reactions / tapbacks
Rich media
Webhooks
Shared team inbox
Dedicated number
Free sandbox

Before you commit

Do this first

The sandbox is free on every provider in this category. There is no reason to sign a contract before you have sent yourself a message.

Create the free sandbox account and send a message to your own phone.
Check what share of your customer list is actually on iPhone — your CRM may already know.
Write the three messages you would send most often, and read them out loud.
Tag the links in them before the first send, not after.
Run one play on a slice of your list and compare it to what you send today.

Independent guide, commercial links

We are not affiliated with LoopMessage. Links to providers on this site carry tracking parameters that identify us as the referrer. Everything above comes from LoopMessage’s own public pages, and vendor marketing figures are labelled as such rather than presented as findings.

Compare with the alternative

Before you decide

Worth reading first

Comparisons