Pro
For numbers customers 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 store a dedicated iMessage number for order updates, delivery photos, back-in-stock requests, order-status support, text-to-buy and review requests, under your store’s name and photo. It is for stores whose customers mostly use an Apple phone and who opted in or texted first.
Pro is $49/month per number. Limits apply to every send.
Your store calls POST /api/imessage/send when an order ships, runs late or arrives. A delivery photo goes with its caption as one bubble.
POST /api/imessage/send
{"to": "+13105550134",
"text": "Hi Priya, order #4821 has shipped. It should arrive Thursday. Track it: alder.shop/t/4821"}
POST /api/imessage/send
{"to": "+13105550134",
"text": "Delivered to your front step at 2:14 PM.",
"image_b64": "..."}
// she replied earlier, so a photo can go
POST /api/imessage/send
{"to": "+13105550134",
"text": "Hi Priya, order #4821 is running a day late and will arrive Friday. Reply here if you would rather cancel."}
A button next to a sold-out size makes the shopper text your number. When the size returns, your server texts a photo and the product link.
A shopper texts a product question and gets the answer and a Stripe Payment Link in the same thread. They pay on Stripe’s page, and your server texts Paid when Stripe reports it.
Carts, renewals and reviews each open with one question and no link. The link goes out after the customer replies.
A named teammate asks about the product in the cart. The cart link follows their reply.
A few days before each renewal, one question. The reply becomes a call to your subscription platform.
Everyone who replies gets the same review link, whatever they said.
Your store system calls POST /api/imessage/send when an order ships or arrives. A local seller can send a proof-of-delivery photo with a caption as one bubble. A photo goes only to a customer who has replied at least once, and before that the send returns 403 attachment_before_reply. The API reports message.sent and message.failed, and has no delivered or read event. Proof-of-delivery guide and delivery status and retries.
A “Text us” link prefilled with the order number opens Messages on the customer’s Apple phone. We post the text to your webhook, your handler shows a typing bubble while it looks the order up in Shopify, then replies with status and tracking. The hosted AI agent can do the lookup instead, through an order tool on an MCP server you connect, so no handler is needed. Because the customer texts first, the new-contact limit does not apply. Order-status guide and customer support.
A “Text me when it’s back” button next to a sold-out size makes the shopper text your number. Your server stores the request from the signed webhook and texts a photo and product link when the size returns. Requests start with the shopper, so they do not use the new-contact limit. A number sends one message at a time, normally 2 to 5 seconds each, so 300 alerts take about 10 to 25 minutes. We do not watch your inventory, so your code triggers each alert. Back-in-stock guide.
For considered purchases, send one link-free question from a named teammate about the product in the cart, to shoppers whose marketing consent is on record. The cart link goes out only after the shopper replies. On Pro the 5 a day limit means following up the highest-value carts first. A discount to every abandoner is high-volume marketing, which our terms prohibit. Abandoned checkout guide.
A few days before each renewal, one link-free question asks whether to keep, skip or swap. Your webhook turns the reply into a call to your subscription platform’s API, so the platform needs an API that can skip a cycle or move the next date. Only the first text to each subscriber counts as a new contact, and later renewals are ongoing conversations. Skip and reorder guide.
A shopper texts a product question from a “Text us” link or a QR code on the packaging and gets the answer and a Stripe Payment Link in the same thread. The hosted AI agent (Beta) can run it with no code. It uses one credit per text it sends, and Pro includes 500 free credits. Your own model on the webhook can also send “Paid” back when Stripe reports checkout.session.completed. Card details go only into Stripe’s page. Text-to-buy guide.
After an order arrives, a question with no link, then your review link once the customer replies. Everyone who replies gets the same link, whatever they said. Customers already in a thread with you do not count as new contacts. Review request guide.
Message people who opted in or texted you first. A box ticked at checkout, unchecked by default, is the usual record. Text the purchaser, never the gift recipient. The consent guide covers what to store.
A customer your number has never texted counts as a new contact. Pro allows 5 a day per number and Growth allows 25+. People who text first, and ongoing conversations, are never limited.
Each contact can have at most 2 unanswered messages, so a third waits for a reply. At most 2 texts go out before a contact’s first reply, and we honour STOP.
We do not allow bulk promotional blasts. A store that wants more than 5 first messages a day can ask customers to text first, with a “Text us” link or QR code on the order page, packaging or shipping email. Or it can move to Growth.
Eligible plain-text order updates can reach customers without iMessage.
Payments go through a Stripe link. Nothing is paid inside the thread.
We do not read it. Order lookups, inventory and subscription changes are code you run, or a tool you connect to the hosted agent.
There is no Shopify app. Our guides describe two routes for a Shopify or other store.
Your store’s webhooks or a small server call our REST API to send, and our signed webhook returns replies. See send from Python, Node.js and curl and how webhooks work.
In our console, open Settings, CRM, Zapier and choose Open in Zapier to add the ZeroSettle app to your Zapier account. It has a Send iMessage action and triggers for received messages, so a Zap can send as one of its steps. All integrations.
We post events to one webhook URL per account. Point it at one receiver if several tools need the events.
No per-message fees on API texts, and a 30-day money-back guarantee on Pro. Name and photo sharing is included, so customers see your store’s name and logo.
For numbers customers text first
$49 /mo per number
For stores that start conversations with opted-in customers
From $199 /mo per number
No. Our guides use your store’s webhooks and a small server that calls our API, or a Zap that uses the Send iMessage action in the ZeroSettle app for Zapier.
To customers who opted in or texted you first. A customer your number has never texted counts as a new contact: 5 a day per number on Pro and 25+ on Growth. Customers who text first, for example from a “Text us” link on the order page, are never limited.
No. We do not allow bulk or cold promotional messages, and each contact can have at most 2 unanswered messages. Use it for order messages, replies and requests from opted-in customers.
Yes, once the customer has replied at least once. Before that, a photo send returns 403 attachment_before_reply. The text and photo go as one bubble with a caption.
Yes. The hosted AI agent can call an order lookup tool on an MCP server you connect. You can also run the lookup yourself in a small webhook handler. Either way the customer texts first, so the new-contact limit does not apply.
A shopper can get a Stripe Payment Link in the thread and pay on Stripe’s page. Card details are never taken in the conversation.
Pro is $49/month per number and Growth is from $199/month per number, with no per-message fees on API texts. Pro has a 30-day money-back guarantee.
Get a number and send your first order message to your own phone.