Meeting Room Bookings

Track 2 does not yet send a customer confirmation email. The customer has only the on-screen redirect to /meeting-booking-confirmation + the Stripe receipt.

Fix. Send a manual confirmation from admin@labourtemple.com with date, room, time, cancellation policy. Do not tell them to "check spam" — there's no email to find.

Priority. A MailerSend confirmation for Track 2 is a documented follow-up (see roadmap.md). Meanwhile, keep a manual-confirmation template in the team inbox.

Check.

• Worker logs filtered by PaymentIntent ID. Look for: "Gate 2 conflict" / "availability check failed" / "Google Calendar event creation failed" — in each case, an auto-refund should have fired.
• Stripe → Developers → Events → find the payment_intent.succeeded → check delivery. Failed/retrying = Worker had a transient error.

Fix.

• Auto-refund already fired → email customer: slot was taken at the moment of payment, card refunded, offer help finding an alternative.
• Webhook didn't reach us → Stripe → Developers → Events → "Resend" the event; Worker will process.
• Last resort → manually create the calendar event from PaymentIntent metadata (booking_dates, booking_time, customer info).

Same as #1 — we don't send an email yet. Send manually.

Check. Worker logs filtered by PaymentIntent ID.

• "Multi-day partial failure — cleaning up" → atomic cleanup fired. Confirm all events deleted and refund issued.
• Orphan events and no refund → cleanup itself failed. Worst case.

Fix.

• Cleanup + refund both succeeded → email customer and offer rebook.
• Cleanup failed → delete orphans manually + refund manually in Stripe + email customer.

Escalate to Chris same-day if cleanup failed — indicates a code path that needs hardening.

Check. Was one event added manually? Our Worker can't see manual additions — no race, just a human mistake.

If both were Worker-created, check log timestamps; both gates should have prevented this.

Fix. Contact one customer (usually the later or lower-commercial-value one) with goodwill gesture + rebooking offer. Refund if they can't rebook. Report to Chris for RCA.

Prevention. Do not add manual Google Calendar events to any bookable room's calendar. Use a separate "internal" calendar for non-paid events.

Check. Is the date within 24 h – 60 d? Is it a weekend (disabled)? Is it a Canadian holiday (currently not handled — customer can book, but space may be closed)? Check Google Calendar directly for capacity.

Fix. Suggest alternatives. If the day is staff-blocked by a manual calendar event, that's expected.

No self-service cancellation.

Fix. Confirm booking details → agree refund amount per policy → refund in Stripe (note reason if partial) → delete Calendar event → email confirmation.

Policy to publish. Typical: full refund 48+ h out, 50% 24–48 h, none under 24 h. Post near the booking form. Handle case-by-case until published.

Fix. Respond via Stripe Dashboard with: booking metadata, calendar event (showing the slot was reserved), published cancellation policy, any emails. Stripe + card network decide.

Dispute fee is $15–25 per case regardless of outcome. Losing also costs the original amount. Respond before Stripe's deadline.

Check. Did the customer actually see the Sonic extras on the form? Extras are triggered by the Sonic slug — if slug or JS is wrong, extras don't render.

Fix. Email the customer to gather podcast/show name, group size, set choice. Update the Calendar event description.

Happens when a new origin (staging, preview) hits the Worker without being in ALLOWED_ORIGINS.

Fix. Add the origin to ALLOWED_ORIGINS in worker.js and redeploy.