Pro
For customers who text first
$49 /mo per number
- 5 new contacts a day per number
- People who text first never count
- No per-message fees on API texts
- 30-day money-back guarantee
We give your business an iMessage number that customers text for support. You answer from our console inbox, relay the thread to Slack or a help desk, or let the hosted AI agent reply.
Pro is $49/month per number. Limits apply.
The console inbox shows every conversation live, and you type replies there. There is no code to write. Inviting team members is part of Growth.
A Message us button, link or QR code opens Messages with your number addressed and the first text filled in. The thread stays in Messages on every device they own, under your business name and photo.
We post each inbound message, signed, to your webhook. A relay you run puts it in Slack, Intercom, Zendesk or Front and sends your team’s answer back through us.
Maya Chen (+1 310 555 0134): Hi, was I charged twice for order 4821?
Reply with/imsg +13105550134 your answer/imsg +13105550134 We just refunded the second charge.
Sent. Maya reacted to your reply with a heart.
The hosted AI agent answers from a business context you write, files you add, and the tools of MCP servers you connect. The customer texted first, so the new-contact limit does not apply.
lookup_orderFind an order by its number. Only reads, so it is on.Called for order 4821change_addressChange where an order ships. It changes something, so it starts off.Size guideA file you added. The agent reads it.FileOne setting per line group decides who answers.
POST /api/imessage/send, or let the agent reply.# your team's answer, sent from your relay
curl -s -X POST \
-H "Authorization: Bearer $TOKEN" \
-H 'Content-Type: application/json' \
-d '{"to":"+13105550134",
"text":"We just refunded the second charge."}' \
https://portal.zerosettle.io/api/imessage/send
Your sends come back to the webhook as message.sent. How webhooks work has the rules.
Each line group is managed by API or managed by AI Agent. It is one or the other, and every number in the group behaves the same. A new signup starts on the AI agent. Our docs list what changes.
With the line managed by API, our console at portal.zerosettle.io/imessage shows every conversation live, and you type replies there. There is no code to write.
There is no native Slack or help desk app. Our docs include an example Slack relay. Your sends come back to the same webhook as message.sent, so the thread can show both sides. A tapback on a message can mark it as seen without a canned reply. Support in Slack or a help desk.
It answers every inbound text from a business context you write in the console. It needs no server or model of your own, and you set its personality and how fast it replies. Texts it sends use credits. Tools that only read turn on by themselves, and a tool that can change something starts off. Your business context can say when to send people to support. Start with the hosted agent guide and our console walkthrough.
You can run the lookup yourself: your webhook gets the text, finds the order in your store and replies. Order-status guide and online stores. Orders and products in the demo above are examples.
| Managed by API | Managed by AI Agent | |
|---|---|---|
| Inbound texts | Posted to your webhook | Answered by the agent; the webhook is not called |
| Typing a reply in the console | Works | Off |
| Sending from the API | Works | Works; the agent treats your texts in the thread as its own |
| Credits | None for texts | One for each text the agent sends |
Put a button or QR code where people look for help: the app, the order page, packaging, a receipt.
An sms: link prefilled with a short reference such as an order number opens Messages on Apple phones. Use a reference, never an email or a secret.
On Android the same link opens the SMS app. Customers can text your number and receive eligible plain-text replies there. How to get customers to text you first.
They never count against the new-contact limit. Each number handles up to 10,000 messages a day, sent and received, with known contacts.
A first message to someone who has never texted you is a new contact: 5 a day per number on Pro, 25+ on Growth. At most 2 texts go out before a contact’s first reply.
If a customer texts STOP, we stop sending to them. They can text again to reopen.
Keep automated marketing out of the support thread. It is a different consent.
A send normally takes 2 to 5 seconds, so give your code a long timeout.
There is no native Slack or help desk app. While a group is managed by AI Agent, you cannot type replies in the console. See the AI apps page for building your own agent on the same number.
No per-message fees on API texts, and a 30-day money-back guarantee on Pro. Hosted-agent texts use credits.
For customers who text first
$49 /mo per number
For teams that also start conversations
From $199 /mo per number
Yes. They text your iMessage number from a Message us button or by hand. The conversation stays in Messages, with your business name and photo.
No. With the line managed by API, you can type replies in the console inbox. With it managed by AI Agent, the hosted agent answers. Code is only needed to relay texts to Slack or a help desk.
Yes. Connect an MCP server that has an order lookup tool and the hosted agent can call it when a customer asks where their order is. Tools that only read turn on by themselves, and a tool that can change something starts off.
Not by the new-contact limit. Anyone who texts you first never counts against it. Each number handles up to 10,000 messages a day, sent and received, with known contacts.
Not at the same time on one line group. The setting is either-or. While the group is managed by AI Agent, the console composer is off, but sends from the API still work.
No. A relay you run posts inbound texts to Slack, Intercom, Zendesk or Front through their APIs and sends replies through us.
Get a number and send your first order message to your own phone.