EMERALD VISTARETREATS · ADMIN
← Back to staging site
Demo data. In production this page sits behind a login. The same data powers the agent API below — Munnin (and Vera, or any agent you authorize) reads and writes it with a token, so anything you can do here, an agent can do from chat.

Retreat weekend

Spots by room

Room / spotUnitsSoldOpen

The weekend cap is women — spots stop selling at the cap even if a bed is technically free.

Reservations

CodeGuestSpotTotalDepositBalanceDietary / milkStatus

Agent API (same data, machine-readable)

GET /api/weekends — all weekends + spot counts GET /api/weekends/:id/reservations — who's booked POST /api/reservations — create a booking (site checkout uses this) PATCH /api/reservations/:code — mark paid, transfer, cancel POST /api/weekends — add a weekend (dates, tiers, cap)

Auth: a per-agent token. Every write is logged with which agent made it. Example questions an agent can answer from this data: “How many spots are left for the spring weekend?” “Who still owes a balance?” “What's the dietary list for the kitchen?”

What happens automatically

  • Guest pays a deposit in Stripe checkout → the reservation appears here, spot count drops, confirmation email goes out.
  • 14 days before the weekend → balance invoice link is sent; a reminder follows if it's unpaid at 7 days.
  • Every payment is written to QuickBooks as it lands (deposit held as a guest-deposit liability; it becomes retreat income when the weekend runs).
  • Morning-of summary to Carolina: arrivals, dietary notes, balances still open.

One reservation, as an agent sees it