Appointment reminder
Confirms or reschedules a booking before the customer misses it.
Notifications and reminders · Notif
Notifications and reminders that get confirmed
When your system fires an event, Notif sends the message at once on WhatsApp, SMS or email. If the message goes unread or unanswered, an AI agent calls to confirm it.
Sent the second the event fires.
WhatsApp, SMS or email, set per event type.
Unread or unanswered? An agent calls.
The call already knows what the message said.
Message first, call second
A call happens only when the message was not enough.
A message is faster and cheaper than a call, so Notif sends it first. The event becomes a call only when the message was not read, or was read but not answered where an answer was expected.
- The message carries the same event context the agent uses on the call
- A read or a reply closes the notification, and no call is placed
- The wait before calling is set per event type, not fixed for every event
EventOrder shipped
WhatsAppYour order #48213 has shipped and should arrive Wednesday.
StatusDelivered, not read
Wait windowElapsed, calling now
AI agentHello, I'm an AI assistant calling about your order 48213. It shipped today and should reach you on Wednesday.
CustomerOh, I hadn't seen the message. Thank you.
OutcomeDelivered and confirmed
How an event becomes a confirmed outcome
Five steps, and the call is step four.
The call is the exception, not the default. A read or a reply at step three ends the notification.
- Event
Your system fires it
The same trigger interface Connect already exposes starts the notification, with the event context attached.
- Message
Sent instantly
WhatsApp, SMS or email, whichever the event type calls for, written in your voice, with no queue to wait in.
- Read or answered
Closes cleanly
A read receipt, or a reply where one was expected, ends the notification with nothing further to do.
- Call
An AI agent calls
If the wait window passes with no read or no answer, a call goes out through the same trigger used for any DRING call.
- Outcome
Written back
Delivered, read, replied, or called and confirmed. The result reaches your CRM like any other call outcome.
Where Notif is used
Events worth a read receipt.
Any event where a message alone does not tell you the customer knows. Appointment and payment reminders run here.
Payment reminder
Follows an unread due-date message with a call that explains the options.
Order shipped
Confirms the delivery window when the shipping update goes unread.
Driver arriving
Checks someone is at the door when the arrival message goes unanswered.
Document missing
Explains exactly what is missing when the request is not opened.
Back in stock
Confirms the order when a waitlist alert does not get a reply.
Refund processed
Confirms the amount and timing when the completion message is not read.
Booking confirmed
Verifies the details when a new reservation confirmation goes unread.
Which product does what
Notif next to After-call workflows and Reach.
All three can end in a call. What starts them, and what happens before the call, is different.
| Question | Notif | After-call workflows | Reach |
|---|---|---|---|
| What starts it | An event in your system: a reminder date, an order shipped, a payment due | A finished call and its outcome | A contact list loaded into a campaign |
| First move | A message on WhatsApp, SMS or email | The step your rule sets for that outcome: a CRM update, a ticket, a webhook, a team alert or a message | A call, inside the window you set |
| When a call happens | Only if the message goes unread or unanswered | When your rule for that outcome schedules a follow-up call | On the first attempt and on each retry |
| What it writes back | Delivered, read, replied, or called and confirmed | The step taken and its result, on the call record | Each attempt's result and the final outcome |
Notif's call starts through the same trigger as Connect's call-start service, and its outcome is written back like any other call, where After-call workflows can pick it up. It does not replace either one.
Scope
What Notif does.
- Sends an event-triggered message the moment your system fires it
- Runs appointment and payment reminders. On DRING they belong to Notif, not to Reach
- Waits the window you set, then calls if the message was not enough
- Carries the event context from the message into the call, so the customer does not start over
- Writes back one of four outcomes: delivered, read, replied, or called and confirmed
What Notif does not do. It does not work a contact list on a schedule: that is Reach. It does not decide the next step after a finished call: After-call workflows do. It does not hold a two-way support conversation: that happens in Co-chat. Notif's job ends when the event is confirmed, by a read, a reply or a call.
Rules you set
Your event, your threshold.
Notif does not decide on its own when a message is not enough. Your team sets each rule below before an event type goes live.
Wait window
How long to wait after the message before calling, set per event type.
What triggers the call
Unread after the window, or read but not answered where a reply was expected. Each can have its own rule.
Quiet hours and consent
The call respects the same calling windows, do-not-call flags and consent as any other DRING call.
FAQ
Notif questions.
Does every notification end in a call?+
No. A call only happens if the message is not read or not answered within the wait window set for that event type.
Which channel does Notif use first?+
WhatsApp, SMS or email, chosen per event type. The voice call comes second, only when the message was not enough.
Should appointment and payment reminders run on Notif or Reach?+
On Notif. A reminder starts from a date in your system, so Notif sends the message first and calls only if it goes unread or unanswered. Reach is for calling campaigns over a list.
How is this different from a message sent by After-call workflows?+
After-call workflows can send a message as the next step after a finished call. Notif starts from an event in your system, before any call, and runs the wait-then-call rule you set for that event.
Does the call respect do-not-call and consent?+
Yes. The call follows the same calling windows, do-not-call flags and consent rules as every DRING outbound call.
Can the call's outcome trigger a further step?+
Yes. When the call ends, its outcome is written back like any DRING call, so an After-call workflow can start from it.
Give one event a message, and a call if it needs one.
Leave your number and DRING calls you in two minutes. Bring one event type, such as an appointment reminder or a shipped order, and we will walk through the message, the wait window and the call.