Appointment reminders over iMessage

We give your business an iMessage number to send reminders from. Your booking system calls our send API when a reminder should go out, and clients confirm or reschedule by replying.

Pro is $49/month per number. Limits apply to every send.

You pick the reminder time.

Your booking system calls POST /api/imessage/send when a reminder should go out. We do not schedule sends, so the timing is yours.

TomorrowYour booking system
Maya ChenCleaning, 3:00 PMScheduled
Dev PatelWhitening, 3:30 PMScheduled
Ana RuizCheckup, 4:15 PMScheduled
Sam OkaforCleaning, 5:00 PMScheduled
One POST per appointment.

Clients answer in one tap.

A reply or a tapback comes back to your webhook. A tapback carries the id of the reminder it was left on, so one tap confirms one appointment.

Harbor Dental
Hi Maya, your cleaning is tomorrow at 3:00 PM. Reply or tap a reaction to confirm.
Your booking system
Maya ChenCleaning, 3:00 PMWaiting
// waiting for a reply

Reminders start with their first text.

Reminders fit clients who text you first. People who text you first never count toward the daily limit.

Remind me

A button on the confirmation page

It opens Messages to your number with “Remind me” prefilled.

A QR code at the front desk

It does the same for in-person bookings.

What does a cleaning cost?
$120. Want me to book one?

A reply to a thread they opened

A question about pricing is enough.

Harbor Dental
WAITLIST
You are on the list.
A 2:30 PM slot just opened tomorrow. Reply YES to take it.
YES
Booked. See you at 2:30.

Offer a freed slot to the next client.

When a client cancels, offer the slot to waitlisted clients one at a time and book the first YES. Clients join by texting WAITLIST to your number.

How appointment reminders work

We carry the messages. Your booking system or calendar decides when to send and what changes when a client replies.

  1. Your booking system sends. A nightly job, a calendar event or a workflow step calls POST /api/imessage/send with the client’s number and the appointment details. We do not schedule sends, so the timing is yours. Save the returned message id on the appointment.
  2. The reminder arrives as an iMessage. It comes from your number, with your business name and photo.
  3. Replies come back by webhook. A text reply arrives as message.received. A tapback on the reminder arrives as reaction.received, with target_id set to the reminder’s id, so one tap confirms one appointment. Events are signed and reach your webhook about 1–2 seconds after the line gets them.
  4. Your code acts on the reply. Mark the appointment confirmed, move the booking, or hand a reschedule request to the front desk, who can answer from the ZeroSettle console.
  5. Optional: a cancellation waitlist. When a client cancels, offer the slot to waitlisted clients one at a time and book the first YES. Clients join by texting WAITLIST to your number, so the offers are ongoing conversations. Waitlist guide.
Send, then listen
POST /api/imessage/send
{"to": "+15555550142",
 "text": "Hi Maya, your cleaning is tomorrow at 3:00 PM."}

// a tapback on the reminder reaches your webhook
{"event": "reaction.received",
 "message": {"kind": "reaction", "reaction": "like",
             "target_id": 120, ...}}

// a text reply reaches it as message.received
The API reports that a message left the line (message.sent) or failed. It has no delivered or read event, so a tapback or a reply is your only sign the client saw the reminder.

The limit that decides who this fits

New contacts

Reminding someone who has never texted your number counts as a new contact. Pro allows 5 new contacts a day per number. Growth allows 25+ a day per number. A salon with 40 new clients booked tomorrow cannot send all 40 first reminders in one day on Pro. It can remind the clients who started the thread.

Two texts, then a reply

You can send at most 2 texts to a contact before their first reply. A contact who texts STOP is not messaged again.

The first text is the opt-in

Your handler records that first text as the opt-in. A link in a first message to someone who has never texted you may not be tappable on their Apple phone, so keep a first reminder plain text. Read how to get customers to text you first and what consent to store.

No scheduling

We do not schedule messages or run your calendar. Your system decides when to send.

SMS fallback

Eligible plain-text reminders can reach clients on Android from the same number.

No bulk or cold sends

Use it for clients who booked and opted in.

Plans

Pro is $49/month per number, with 5 new contacts a day and no per-message fees on API texts. Growth is $199/month per number and allows 25+ new contacts a day. Pro has a 30-day money-back guarantee. Numbers run on Apple hardware we operate. Plan details are on the iMessage API page.

Trigger reminders from your booking system

We post events to one webhook URL per account.

Your own code

A scheduled job reads tomorrow’s appointments and calls the send endpoint. A small receiver handles the signed webhook. See Send from Python, Node.js and curl and how webhooks work.

Zapier

Connect it from Settings > CRM > Zapier in our console (Open in Zapier). A Zap from your scheduling tool can use the Send iMessage action.

GoHighLevel

A workflow sends with a Custom Webhook action and a ZeroSettle API key. The official ZeroSettle app for GoHighLevel is on the way. Read GoHighLevel and agencies.

See all integrations.

Questions

Can I send an appointment reminder to someone who has never texted my number?

Yes, but it counts as a new contact. Pro allows 5 a day per number and Growth allows 25+. You can send at most 2 texts before their first reply, so one reminder and one follow-up is the most.

How does a client confirm?

They reply by text, or tap a tapback on the reminder. Both arrive at your webhook, and a tapback carries the id of the reminder it was left on.

Do you schedule the reminders?

No. Your booking system or calendar sends each reminder by calling the API when you want it to go out.

What happens if a client replies STOP?

We honour it. A send to that contact is refused, so do not retry it.

Can I use it with Zapier or GoHighLevel?

Yes. Zapier connects from Settings > CRM > Zapier in the console. GoHighLevel sends through a Custom Webhook workflow action with an API key.

Send your first reminder

Get a number, then send POST /api/imessage/send to your own phone.