How do I choose which operational alerts each staff member gets?
Route operational alerts so the right staff hear cancellations and failed charges. Per-person staff mute toggles are only partially documented; use the notification controls your desk actually shows.
Route operational noise so the right host hears cancellations and the founder hears failed membership charges — without every seasonal staffer getting every email. Published FAQ covers customizing guest-facing SMS/email; per-staff operational alert preferences are a different job and are only partially documented in Zettlor today.
What Zettlor does today
Zettlor sends guest confirmations, reminders, waitlist notices, and similar messages when notifications are connected (see the live confirmation-emails guide: Advanced → Developer and staff notification tools). You can configure guest message content and timing per FAQ.
What is not clearly published as a full per-person alert matrix (email, in-app, or push toggles by category for each teammate) is a complete per-person staff alert preference how-to. Category labels vary by org — use only the names your desk shows. You need different people to hear different alerts — cancellations for hosts, failed charges for owners. Use the notification tools your desk actually exposes, and keep guest automations separate from staff ops alerts.
If your build only offers org-wide staff notification switches, say so to the team — do not promise personal mute toggles that are not on the screen.
Desk path
- Confirm notification delivery is connected (Advanced → Developer / staff notification test tools — same neighborhood as purchase confirmation emails).
- Review whatever staff / admin notification controls your org exposes (org-wide toggles, per-user preferences, or both).
- Do not use guest notification templates to silence staff inboxes — that would stop customers from getting receipts.
Do not invent a settings path beyond what is listed here. If the product does not include a per-person control, the desk workaround is the path: role-appropriate email aliases, filtering rules, or assigning one on-call inbox for money alerts.
Failure mode
Every host mutes “too much email,” and nobody sees a failed membership charge or a sold-out session cancel blast that needed a refill plan. The inverse failure: one shared founder inbox with every new booking ping, so real payment failures drown in noise. A third failure: turning off guest confirmation emails while trying to quiet staff — guests arrive without receipts and blame checkout.
Operator example
A sauna and cold plunge operator keeps money and platform alerts on for owners, lets weekend hosts keep cancellation pings only if the desk UI allows that split, and leaves guest reminder SMS untouched. When personal mute toggles are missing, they route Stripe / failed-charge notices to an owners@ alias and leave booking spam filtered — without disabling customer confirmations.
A sauna and cold plunge operator can copy the shape of this example without copying another brand’s private pricing or customer lists.
How to do this
- Separate two lists on paper: (A) emails guests must still receive, (B) operational alerts staff care about (new booking, cancel, membership failure, system/payment errors).
- Verify guest automations still send via Advanced → Developer notification tests.
- Open staff / team notification controls if present. Mute only categories each person does not act on. Keep at least one owner receiving money-at-risk alerts.
- If per-person toggles are absent, assign an on-call owner inbox for payment failures and train hosts not to filter those senders.
- After inviting a new staffer (see staff-roles), confirm they are not accidentally the only remaining recipient of a critical alert — or the opposite, drowning in booking mail they will ignore.
- Re-test after changes with a test booking and a test cancel so both guest and staff sides still behave.
Related questions
Is this the same as customizing guest notifications?
No. FAQ “customize notifications” is guest-facing copy and timing. This page is which staff hear operational alerts.
Can I turn off system / payment failure alerts for everyone?
Do not. Money-at-risk alerts need at least one human. If the product blocks muting the last recipient, that is intentional.
Do staff alert settings change what customers receive?
They should not. If a control would silence guest confirmations, you are in the wrong settings surface.
Follow-up guides
- How do I turn on purchase confirmation emails?
- How do I invite staff and control what each role can do at the desk?
- How do I see failed membership charges and retry them before we cut access?
Book a demo or get started.
Zettlor is booking and operations software for commercial sauna, cold plunge, and wellness facilities. See how it works.