Remaining features

Built
No-show flag and block:
Two new numbers under Booking Rules (blank means off).
A symbol appears on the clients list, client page, calendar entries and appointment pages.
Online booking is refused at the block number, and customers are told at the details step.
Staff can still book a blocked customer in, and an owner can reset someone with a two-tap button.
The count resets when they attend, and matches the same email or phone, so a guest can’t dodge it with a new profile.
Email rules: staff and owners get email only for customer cancellations, schedule changes and invitations. Routine events (new booking, reschedule) are push-only. Nobody is told about their own action. A barber reassignment sends one customer email instead of two. Reward expiry sends one warning.
Email redesign: your brand colour, a details card, Add to calendar and View on map links, a preferences link, hidden preview text, and dark mode. Replies now go to the business’s own email.
WhatsApp “due now” queue: a list in time order with a highlighted next one, an owner setting for how many hours ahead (12–72), and a once-a-day push telling each barber how many reminders are waiting.
Monitoring: /api/health now reports whether notifications are actually going out. The worker resets stuck deliveries and alerts the owner on the first setup failure (such as a bad SMTP login). The app emails your operator address about server errors, and the manager pushes that address to each business.
Google scope: now only calendar.app.created. Events go to a calendar the app creates in the staff member’s Google account, called “<Business> bookings”.

.env.business.example

@@ -53,10 +53,14 @@ INSTALLATION_TOKEN="replace-me"
 # generate with: openssl rand -hex 32. Without something actually calling
 # those on a schedule, queued notifications (staff invites, reminders,
 # etc.) never get sent — see the root README's "Notification delivery"
-# section and stacks/infra/scripts/process-cron.sh for the one-time
-# crontab setup this requires.
+# section: the Manager's built-in scheduler normally does this (the host
+# crontab script is only a fallback).
 CRON_SECRET="replace-me"
 
+# Where the app emails unhandled server errors (one email per distinct error per hour, max 20 a day).
+# The Manager fills this in from Settings > Monitoring. Blank = no error emails.
+OPERATOR_ALERT_EMAIL=""
+
 # ── Super Administrator (optional — see scripts/ensure-super-admin.ts) ──
 # Platform-level account with every Owner permission for THIS business.
 # Runs automatically on every container start (see docker/entrypoint.sh)