Email AtlasAtlasIndexHomeOpen raw ↗
Meetings extras · Meetings — recordings, cancel/reschedule

Booking cancelled guest

member transactional shadow 98/100

In plain English — what this does

The moment this happens in ClubOS, the system automatically emails the member within seconds. Because it's time-sensitive, it always sends right away — and it's never sent twice for the same event.

Dark-inbox is a simulated backdrop — the email is pinned light by design (best-effort dark preview).

Delivery

Audiencemember · Meetings extras
Mail-classtransactional
Statusshadow
Fromnotifications@thequantumclub.nl
Reply-Toconcierge@thequantumclub.nl
Recipientscandidate
Triggermeeting_booking_cancelled_guest

Source

Builder filemeetings-bodies.ts ↗
Renderaudit-artifacts/mt-booking-cancelled-guest.html

Wiring

Trigger sourcelifecycle event → emitIntent
Dispatch actionengine-dispatch
Channelemail
Brain policyexpress · mc:transactional — uncapped, bypasses quiet-hours/frequency-cap
Idempotencysha256(meeting_booking_cancelled_guest · entity · candidate · window)
Engine stateshadow (engine dormant until ramp)

Wiring is auto-derived from RECIPIENT_MAP + the notification registry — it cannot drift from the real engine wiring.

Audit

Lens-minimum 98/100 — scored on six lenses: component fit · copy & register · completeness · CTA integrity · purpose / managed-service · intelligence. ≥98 = converged.

Versions

Builder source history on GitHub →

History

No curated entries for this email yet. When you edit it, append a line to email-changelog.jsonl — see the changelog.

Feedback

Open GitHub issue ↗ Saved ✓
← Weekly digestBooking cancelled host →