Retention offers over iMessage

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.

Pick when the offer goes out.

One trigger per offer, one offer per user per week. Each text comes from your number under your name and photo.

Calorie App
Today 8:14 PM
wait
we saved your spot
how about 30% off?

2 to 3seconds to the first text

The offer hits their Lock Screen in seconds.

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.

They reply YES. You answer with a tapback.

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.

Calorie App
Today 8:14 PM
want 30% off Pro to keep it going? Reply YES and I’ll send it
YES
Done. 30% off is on your account: go.example/pro30
Your backend, on message.receivedMatches the sender to the offer
apply_offerYour billing applies the discount.Applied: 30% off, good for 24 hours
react loveA tapback on their YES, not another text.A heart on their YES
send the linkIt is tappable now that they have replied.Sent
stop sendingA STOP is honoured: we stop sending to that number.Marked opted out. Nothing more is sent.

How retention offers work

The app tells your backend the moment the user leaves. Your backend owns the number, the consent record, the cooldown and the send.

  1. Consent in onboardingA phone field with a Text me my offers toggle. Store when the user switched it on.
  2. The app tells your backendOnly the paywall arms the offer, once per visit. On 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.
  3. Your backend checks and queuesIt skips users without consent, users with an offer in the last 7 days, and times outside 8 am to 9 pm in the user’s time zone. It marks the offer sent, queues the work and answers 200 at once. Create the discount before the first text.
  4. Three texts, offer lastEach 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.
  5. YES, then the linkThe reply reaches your webhook as a signed 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.
python
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.

Four moments that work

Pick one trigger per offer and debounce it.

TriggerWhere you see itTypical message
App goes to the background on the paywallUIApplication.willResignActiveNotification“wait”, then “we saved your spot”, then “how about 30% off?”
Cancel flow reached the last stepYour cancel flow“Before you go: 2 months free if you stay.”
Trial ends tomorrow, no cardYour billing system“Your trial ends tomorrow. Reply YES to keep your plan at $4.99.”
No session for 7 daysA nightly job“We miss you. Your streak is still saved: 30% off to pick it back up.”

Rules that keep offers welcome

Rare on purpose

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.

Three texts, not ten

Every message after the first arrives after they have already looked at the phone, and a long script reads as spam.

Make the offer real

“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.

Waking hours

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.

STOP

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.

Limits

New contacts

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.

Before the first reply

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.

No link until they reply

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.

The first offer may not notify

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.

Exits that are not exits

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.

Test on a real device

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.

SMS fallback

Eligible plain-text offers can go by SMS to customers who agreed to account texts.

A flat price per number

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

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

Questions

Will Apple reject my app for texting offers?

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.

Will the offer show my app’s name or a bare number?

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.

Why three texts instead of one?

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.

Can I send the checkout link right away?

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.

Start with one number

Get a number and send your first offer to your own phone.