Familiar blue bubbles
Reach customers through a connected iMessage line. Make a showroom visit, product question or follow-up feel like a continuing conversation.
Give customers a familiar way to stay in touch. Handle iMessage conversations in a dedicated messaging view or open the same thread in your shared Inbox, with your team and customer context nearby.
Confirm the appointment in the same thread.
A customer can ask about a product, leave their laptop and continue in Messages. Your agents keep working from Message Inbox, with AI and the conversation history beside them.
Reach customers through a connected iMessage line. Make a showroom visit, product question or follow-up feel like a continuing conversation.
Message AI can answer from your approved business knowledge and enabled sources. Give your team the conversation when someone needs a personal answer.
Assign and reply from the shared workspace. A customer doesn’t need a different contact for every person helping them.
| Your customer experience | iMessage | SMS / MMS |
|---|---|---|
| Where it arrives | Apple Messages on a supported iMessage destination | Text messaging across supported mobile networks |
| Business setup | A connected Message iMessage line | An enabled local, toll-free or short-code sender |
| Message pricing model | Monthly line subscription and setup | Per SMS segment or MMS, plus carrier fees |
| Your team’s workspace | Shared Inbox and dedicated messaging view | Shared Inbox |
| AI and customer context | Message AI with enabled knowledge and sources | Message AI with enabled knowledge and sources |
iMessage is useful when your customer uses Apple Messages. SMS extends your reach across mobile networks. Choose the right channel for the destination; automatic RCS fallback is not included in the current iMessage service.
Send through a connected line from your server-side workflow. The message belongs to a conversation in Message, so your team can see the context and take over.
This endpoint requires an authenticated workspace agent token with iMessage permission and an active full line. A Verify API key cannot authorize it.
const response = await fetch(
"https://app.message.com/api/v1/imessage/send",
{
method: "POST",
headers: {
Authorization: `Bearer ${process.env.MESSAGE_AGENT_TOKEN}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"lineId": "YOUR_CONNECTED_LINE_UUID",
"to": "+15125550134",
"body": "Your showroom appointment is confirmed for 10:30 AM."
})
}
);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const result = await response.json();Server-side example. Keep credentials out of browser code. Replace the line UUID and obtain an authorized agent session before sending.
A customer looking at a desk today might ask about a showroom visit tomorrow. Their next message should continue the discussion, wherever the team is working.
Read the conversation list, search a customer and open the thread in the iMessage workspace. The familiar layout makes everyday replies easy to follow.
Open the same conversation in Inbox when you need the wider customer record. The dedicated view reuses the conversation data instead of creating a separate copy of the support request.
The business’s messaging line belongs in a team workflow. Handle assignment and customer context through the Inbox so support does not depend on one person’s personal device.
Use eligible linked history to understand what happened before the customer reached out again. Keep private information behind the appropriate checks.
Related conversations can show what a teammate promised and whether an issue remains open. Confirm the link between records rather than assuming similar contact details identify the same person.
Supported connected sources can help your team understand products and orders. Customer-facing disclosure still needs the identity checks required for the information being requested.
Supported iMessage task-agent answers can use the configured business knowledge and guidance. Test the agent on common questions and handoff cases before activation.
Make it easy to keep the conversation going without turning support into a collection of personal phone threads.
Find a customer by name, number or message preview in the dedicated view. Search makes returning to an earlier discussion straightforward.
The sending line and its status matter. Select the configured line for a new conversation and keep an eye on the available allowance.
Open the thread in your shared workspace to reach assignment, customer history and the rest of your support workflow.
Line connection and policy checks can prevent a message from sending. Review the surfaced error rather than assuming an accepted action means the customer received it.
Use supported AI behavior with published knowledge and site scope. Keep factual product answers separate from private customer lookups.
New conversations and ongoing replies can have different allowances and restrictions. Use the line’s current policy and availability rather than treating it as an unlimited broadcast channel.
Start with a $49/month reply-only line or a $99/month full line. Connect the conversation to your support team, customer history and Message AI.
| What you’re comparing | Message.com | Sendblue | Linq |
|---|---|---|---|
| Inbound-first paid line | $49/line/month, reply-only | $100/line/month, AI Agent | No public API plan price on reviewed page |
| Start outbound conversations | $99/full line/month; $79 at 6+ full lines | Enterprise: custom price | API supports outbound; request a quote |
| Message setup charge | $99 one-time per line | Not specified on reviewed pricing page | Not specified on reviewed API page |
| Service focus | iMessage in Message Inbox, with tickets, chats and calls | Messaging API with webhooks and callbacks | Messaging API with webhooks |
| RCS / SMS fallback | SMS is separately priced; automatic RCS fallback not included | RCS / SMS supported; SMS fallback fees included | RCS / SMS fallback supported |
Message reply-only: $49 versus Sendblue AI Agent: $100. Message’s $99 setup is separate. These plans have different capabilities and limits: Sendblue lists 1,000 inbound contacts/day. Compare your sending needs before choosing.
Message AI is $5/workspace/month, included in Business. Workspace subscriptions, line setup and channel usage are separate. Provider feature sets are not identical; prices and service scope checked September 25, 2026.
See all Message iMessage rates →Choose a reply-only line for inbound conversations or a full line to start conversations too. Each line has a $99 one-time setup fee.
Receive conversations and reply to customers who message you.
Start now →Start conversations and reply from your connected business line.
Start now →The volume rate applies to every full line when you have six or more.
Start now →Message AI is $5/month and included in Business. iMessage line subscriptions and setup are separate. Message delivery remains subject to line availability, sending policies and platform limits. This is Message’s connected-line service, not Apple Messages for Business.
| Configuration | Monthly line subscriptions | One-time setup |
|---|---|---|
| 1 reply-only line | $49 | $99 |
| 1 full line | $99 | $99 |
| 6 full lines | $474 | $594 |
Use the iMessage setup in your workspace and review the current price, activation process and allowance. A purchased line may still need activation before use.
Send an authorized test message and reply from the receiving device. Confirm the thread appears in the iMessage view and the shared Inbox.
Decide who owns incoming requests and whether a task agent should answer. Review customer-history linking and handoff before using the channel broadly.
iMessage is a separate product. Line activation, allowances and messaging policies apply.