Notifications
16 moments where somebody should hear something.
Half of them are for your customer and half are for your team. Each one can be switched on or off per audience and per channel, so the person who needs to know finds out and nobody else gets a phone full of noise.
Email
On by defaultSent from EzyConn on your behalf. This is the one that carries the booking confirmation.
In-app
On by defaultWaiting in the portal for whoever opens it next. The channel your own team actually reads.
SMS
Off by defaultSent through your own Twilio account, so every message spends your money. That is exactly why it ships switched off.
Why it matters
An appointment nobody was told about is not an appointment. The customer forgets, or turns up on the wrong day, or rings to check — which is the phone call the whole system was meant to remove.
On the other side, a team that is notified about everything stops reading any of it. Within a fortnight the alert that mattered is sitting under forty that did not.
So this is a settings page rather than a feature: you decide which of the 16 moments is worth interrupting somebody for, and on which channel.
How it works
- 01Pick the moment — a booking confirmed, an enquiry arriving, a process failing.
- 02Pick who hears about it: your customer, your team, or both.
- 03Pick the channel. Email and in-app arrive switched on; SMS does not.
Booking confirmations are queued the moment the appointment is committed, so the customer usually has the email before they have closed the tab.
Who uses it
Whoever gets blamed when somebody was not told.
Businesses with a diary
Trades, workshops, salons, studios, dental and healthcare reception. Confirmation and reminder are the two that pay for themselves in missed appointments.
Teams sharing an inbox
New enquiry, escalation and assignment tell the right person to look, so a conversation is not answered twice or not at all.
Owners who want the exceptions
Switch the routine ones off for yourself and keep a process failing — the one moment where nobody else will notice.
Anyone tightening the noise
Every setting is per moment, per audience and per channel, so you can turn the volume down without turning the useful ones off.
What it can do
All 16, named. 14 of them send today.
The two that do not are listed in the same tables as the rest, in the same order, with their real status. Hiding them until you noticed would be worse.
To your customer
What the person who messaged you hears about, on the channel you chose for them.
| Enquiry acknowledged | Available now |
|---|---|
| Booking confirmation | Available now |
| Booking reminder | Available now |
| Booking rescheduled | Available now |
| Booking cancelled | Available now |
| Booking request received | Available now |
| Handed to a person | Available now |
| Follow-up after a visit | Not built yet |
To you and your team
What lands in the portal, in your inbox, or on your phone if you have paid Twilio for it.
| New enquiry | Available now |
|---|---|
| New booking | Available now |
| Booking cancelled | Available now |
| Booking rescheduled | Available now |
| Escalated to a person | Available now |
| Conversation assigned | Available now |
| A process failed | Available now |
| Important customer message | Not built yet |
What it works with
Email and in-app need nothing from you — they are part of the account.
SMS runs on your own Twilio account, the same one the phone line uses. Your number, your rate, billed to you by Twilio with nothing added by us — which is also why we ship it switched off.
Anything you want somewhere else goes out as an event through Zapier or a signed webhook, so a booking can land in whatever your team already watches.
What plan includes it
Notification settings are part of every plan.
Choosing who hears what is account configuration, not a paid module — it is available on Free, Starter, Professional, Enterprise alike. What differs by tier is the machinery that produces the moments in the first place.
- All 16 moments, per audience and per channel
- Free
- Email and in-app delivery
- Free
- SMS deliveryYour own account and your own credit, at Twilio’s published rate.
- Paid to Twilio
- A process that creates the booking being confirmed
- Starter
Read this before you buy
What notifications cannot do.
The limit: Two of the 16 do not send yet, and we will not describe them otherwise. Follow-up after a visit and important customer message exist as settings you can switch on, and switching them on will not make anything arrive. Do not build a process that depends on either.
A cancellation tells your customer nothing
Your team is notified when an appointment is cancelled. The customer is not. There is one booking email template, and sending it for a cancellation would tell somebody their appointment is confirmed.
The confirmation email is best-effort
It is queued after the appointment is committed, so the appointment is safe even if the delivery is not. If the queue is down the email can be lost quietly, with nothing in the interface to tell you.
No process sends an SMS
SMS is a notification channel only. No published process sends an SMS confirmation or an SMS reminder, and no customer can reply to one and be understood.
SMS spends your money
It runs on your Twilio account. That is why it is off by default, and why turning it on for all 16 moments across a busy month is a decision rather than a setting.
Automations cannot raise one
The simple “when this happens, do that” layer can assign, message, tag and set priority. Creating an in-app notification from it is rejected by the platform.
No delivery guarantee, and no SLA
EzyConn publishes no uptime commitment for notification delivery or anything else. If a notification is the only thing standing between you and a missed job, keep the diary open too.
Decide who gets interrupted, once.
Two of the 16 are worth switching on for a customer, and about three for a team. The rest is quiet on purpose.