Customer support over iMessage

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.

Customers tap. Messages opens.

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.

Fernside Goods
Today 9:41 AM
Hi! Where is my order #4821?
Hi Maya, this is Sam at Fernside Goods. I have your order up and I am checking it now.

The same thread, in Slack.

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.

# supportrelay
iMessage relay9:41 AM

Maya Chen (+1 310 555 0134): Hi, was I charged twice for order 4821?

Reply with /imsg +13105550134 your answer
Sam9:42 AM

/imsg +13105550134 We just refunded the second charge.

iMessage relay9:42 AM

Sent. Maya reacted to your reply with a heart.

/imsg +13105550134 We just refunded the second charge.
Fernside Goods
Today 9:41 AM
Hi, was I charged twice for order 4821?
We just refunded the second charge.

Order questions, answered.

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.

Fernside Goods
Today 6:12 PM
Where’s my order #4821?
It shipped Tuesday and is out for delivery. It should arrive by 8:00 PM today.
What the agent can useMCP tools and files you add
lookup_orderFind an order by its number. Only reads, so it is on.Called for order 4821
change_addressChange where an order ships. It changes something, so it starts off.
Size guideA file you added. The agent reads it.File

How customer support over iMessage works

One setting per line group decides who answers.

  1. The customer texts your numberUsually from a Message us button, link or QR code, or by hand. The thread stays in Messages on every device they own.
  2. We deliver itManaged by API, the message is posted to your webhook and shows in the console. Managed by AI Agent, the agent answers and the webhook is not called.
  3. Your team or your agent answersType in the console, send from your relay with POST /api/imessage/send, or let the agent reply.
  4. The answer arrives as a blue bubbleA send normally takes 2 to 5 seconds, so give your code a long timeout.
bash
# 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.

You choose who answers

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.

Console inbox

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.

Relay to Slack or a help desk

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.

Hosted AI agent

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.

Order status yourself

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 or managed by AI Agent

Managed by APIManaged by AI Agent
Inbound textsPosted to your webhookAnswered by the agent; the webhook is not called
Typing a reply in the consoleWorksOff
Sending from the APIWorksWorks; the agent treats your texts in the thread as its own
CreditsNone for textsOne for each text the agent sends

Getting customers to text you

Where to put it

Put a button or QR code where people look for help: the app, the order page, packaging, a receipt.

What to prefill

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.

Android

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.

Limits

Replies to people who text 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.

Starting a conversation yourself

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.

STOP

If a customer texts STOP, we stop sending to them. They can text again to reopen.

Marketing

Keep automated marketing out of the support thread. It is a different consent.

Send time

A send normally takes 2 to 5 seconds, so give your code a long timeout.

Not included

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.

A flat price per number

No per-message fees on API texts, and a 30-day money-back guarantee on Pro. Hosted-agent texts use credits.

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
Get started

Questions

Can customers text my business number for support?

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.

Do I need code to answer them?

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.

Can the AI agent check an order’s status?

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.

Are replies to customers who text first limited?

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.

Can I use the hosted AI agent and answer myself?

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.

Is there a Slack or Zendesk app?

No. A relay you run posts inbound texts to Slack, Intercom, Zendesk or Front through their APIs and sends replies through us.

Start with one number

Get a number and send your first order message to your own phone.