Pro
For offers to opted-in users
$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 app an iMessage number with your name and photo. When a user leaves the paywall or reaches the last step of cancelling, your backend sends a short offer text with a tapback on it.
Pro is $49/month per number. Limits apply.
One trigger per offer, one offer per user per week. Each text comes from your number under your name and photo.
2 to 3seconds to the first text
Measured on a real device, the first text reached the Lock Screen 2 to 3 seconds after the user left the app, and the third by about 9.
Your backend matches the reply to the offer, applies it in your billing and puts a heart on the YES. The link follows, now tappable because they replied.
apply_offerYour billing applies the discount.Applied: 30% off, good for 24 hoursreact loveA tapback on their YES, not another text.A heart on their YESsend the linkIt is tappable now that they have replied.Sentstop sendingA STOP is honoured: we stop sending to that number.Marked opted out. Nothing more is sent.The user gives you their number for messages from you. A phone field that says you will text them, or a Text me my offers toggle, with the time stored. Without it, do not send.
The app tells your backend the moment the user leaves. Your backend owns the number, the consent record, the cooldown and the send.
UIApplication.willResignActiveNotification the app pings your backend inside beginBackgroundTask, started before the first await. SwiftUI’s scenePhase lands a run loop later. The app never calls us, so the token stays out of the binary.POST /api/imessage/send returns once the line has handed the text to Apple, normally in 2 to 5 seconds, which keeps the order and sets the cadence. Then POST /api/imessage/reactions puts an emphasize tapback on the offer.message.received event about 1 to 2 seconds after the line receives it. Your backend applies the offer, sends a love tapback and the link.SCRIPT = ["wait", "we saved your spot", "how about 30% off? reply YES and it's yours"]
def send_offer(user_id):
user = users.get(user_id)
code = billing.create_promo(user, percent_off=30, expires_in_hours=24) # make it real first
last_id = None
for text in SCRIPT:
r = zs.send(user.phone, text) # POST /api/imessage/send
if not r.ok:
break # a half-sent script beats a re-sent one
last_id = r.id
if last_id:
zs.react(last_id, "emphasize") # POST /api/imessage/reactions
pending_offers[user.phone] = Offer(user, code=code)
Register the receiver with PUT /api/imessage/webhook and verify X-ZeroSettle-Signature before you read a reply. Webhooks, step by step has the rules. This is the Retention offers section of our docs.
Pick one trigger per offer and debounce it.
| Trigger | Where you see it | Typical message |
|---|---|---|
| App goes to the background on the paywall | UIApplication.willResignActiveNotification | “wait”, then “we saved your spot”, then “how about 30% off?” |
| Cancel flow reached the last step | Your cancel flow | “Before you go: 2 months free if you stay.” |
| Trial ends tomorrow, no card | Your billing system | “Your trial ends tomorrow. Reply YES to keep your plan at $4.99.” |
| No session for 7 days | A nightly job | “We miss you. Your streak is still saved: 30% off to pick it back up.” |
One offer per trigger, one trigger per user per week. Enforce it on your backend. The app’s once-per-visit flag is a debounce, not a policy.
Every message after the first arrives after they have already looked at the phone, and a long script reads as spam.
“30% off” in a text is copy until your billing grants it. Create the code before the first send, as a web-checkout promo code or an App Store offer code, attach it to the pending offer and apply it on YES.
Send nothing promotional before 8 am or after 9 pm in the user’s time zone. The app knows it, so pass it to your backend.
Honour it in the same webhook: mark the handle opted out and never message it again. A send to that handle returns 403 recipient_opted_out.
The first text to a user who has never texted you is a new contact: 5 a day per number on Pro, 25+ on Growth. Only the first text to each user counts. Queue offers and drain them at that rate. A 429 new_contact_limit says how long to wait in error.retry_after_s.
At most 2 texts go out before a contact’s first reply, and a burst within 5 minutes counts as one, so a three-text offer is one unanswered message.
A link to someone who has never texted you can’t be tapped. Ask for the YES first and send the link with the confirmation.
Screen Unknown Senders (iOS 26) moves texts from unknown senders into a separate list without a notification, so a first offer to a user with it on may go unseen.
willResignActiveNotification also fires for a phone call, Control Center, the notification shade and a Face ID prompt. The once-per-visit flag caps that at one stray text. Waiting for didEnterBackgroundNotification instead costs an extra half second, and clearing the flag when the user taps your buy button keeps a system sheet from texting a buyer a discount.
Background tasks and iMessage delivery do not exist in the Simulator. Our console at portal.zerosettle.io/imessage shows every send and its status as it happens.
Eligible plain-text offers can go by SMS to customers who agreed to account texts.
No per-message fees on API texts, and a 30-day money-back guarantee on Pro.
For offers to opted-in users
$49 /mo per number
For apps with a wide funnel
From $199 /mo per number
We answer no, citing App Store guideline 3.1.3: “Developers can send communications outside of the app to their user base about purchasing methods other than in-app purchase.” Point the link at a purchase path your app may use, such as an offer code’s redemption URL, and read the current guideline yourself.
Your name and photo share automatically with the first text. The user sees “<name> shared a name and photo with you” and can save it. Customers see “Maybe: Your Company” and your photo even if they have never saved your number, though their contact settings can change what shows.
Three texts a few seconds apart read like a person typing, and one paragraph reads like a campaign. We advise against more than three, because a long script reads as spam.
It goes out, but not as a link they can tap. Until the user replies or saves your number, Apple phone shows it as plain text, and our response adds warning.code: "link_not_tappable". Ask for YES first.
Get a number and send your first offer to your own phone.