Notification Settings

Notifications keep your team in the loop when things happen — a booking comes in, a refund is processed, a customer alert fires. This guide covers who gets what, and how to tune it so inboxes don't drown in noise.

Where to configure

Go to Settings → Notifications. The page lists every notification type with checkboxes and recipient settings.

Notification types

Booking notifications

• New booking (widget) — customer self-booked through your website.
• New booking (POS) — staff booked on behalf of a customer.
• Booking rescheduled — date/time changed.
• Booking cancelled — by staff or by the customer.

Payment notifications

• Payment received — card charge went through.
• Refund processed — money returned to the customer.
• Payment failed — a card was declined.

Customer notifications

• Customer alert — triggered by flagged notes on a customer's record (see Customer Alerts and Notes).
• No-show recorded — staff marked a booking as no-show.

Operational notifications

• Daily summary — end-of-day email with today's takings and tomorrow's bookings.
• Weekly summary — week-at-a-glance digest.
• Low inventory — if you sell vouchers or add-ons with stock limits.

Setting recipients

Each notification can go to a different set of recipients. Common setups:

• Everyone gets everything — team@yourvenue.com (a shared mailbox) on every notification. Simple but noisy.
• Split by role — bookings to front desk, payments to the owner, alerts to managers.
• Hybrid — a shared mailbox for routine stuff, personal addresses for anything urgent.

Enter recipients as a comma-separated list of email addresses. Avoid mixing internal and external addresses in the same field — easy to accidentally send internal alerts to a customer-facing address.

Customer-facing emails

Don't confuse notifications (to your team) with transactional emails (to the customer). Those are separate:

• Booking confirmation — to the customer, sent automatically.
• Booking reminder — to the customer, typically 24h before.
• Cancellation confirmation — to the customer.
• Payment receipt — to the customer.

These are configured in Settings → Email Templates — the wording, branding, and scheduling. Customer emails can't really be "turned off" — they're part of the service contract — but you can customise the template extensively.

SMS notifications

If SMS is enabled on your tenant, you can configure customer-facing SMS for reminders, check-in instructions, and cancellations. Staff notifications via SMS are less common but available for urgent ones (e.g. customer alerts for VIPs). SMS costs money per message, so enable selectively.

Push notifications

If your team uses the mobile app or browser notifications, certain events (new bookings, urgent alerts) can push in real time. Configure per-user in their profile settings — there's no branch-wide toggle.

Muting during rollouts

If you're mid-deploy or running a bulk import that'll trigger hundreds of notifications, you can temporarily mute all notifications from the top of the settings page. Remember to un-mute when you're done — a muted branch is silent for real events too.

Tuning tips

• Start loud, then quiet down. Enable notifications generously on day one, then turn off the ones that prove noisy as you go.
• Separate digest from real-time. Put routine stuff (new bookings, payments) in the daily summary; reserve real-time email for exceptions (cancellations, alerts).
• Use filters on the receiving end. Rather than disabling notifications, Gmail/Outlook filters let you file them away so they're searchable without cluttering your inbox.
• Alert on outliers only. Treat customer alerts as an exception channel — if you flag every customer, the signal gets lost.