Your organization: name, slug (booking page /book/{slug}), time zone, currency and how guest messages are answered

Booking page: /book/{slug}

IANA time zone, e.g. America/Denver. Weekly hours and dates are local to it.

ISO 4217 code in lowercase, e.g. usd

When guests can expect a reply, e.g. "We reply by 9 AM"; part of the acknowledgement

Emails a guest who writes "Thanks, we got your message", at most once a conversation a day

While set: shown on the booking page and sent with the acknowledgement

Guests may cancel from their booking page until this many hours before the start, and change their time inside the same window; null: off, they write to you instead. Each booking keeps the window it was made with

Where guests leave a review; the ops agent's thank-you links it

Assistants booking for a guest may hold places with no key, at /api/mcp/book/{slug}; each guest confirms by email

Gift cards are sold on the booking page (/book/{slug}/gift) while the business takes payments at booking

The local hour of the ops agent's morning brief

The most the ops agent does on its own in 24 hours; past it, it asks

Quiet hours start (local hour): the agent sends guests nothing on its own until quiet_to

Quiet hours end (local hour)

The ops agent refunds on its own up to this; null means a refund always waits for approval

ISO 8601 timestamp (UTC)

ISO 8601 timestamp (UTC)

ISO 8601 timestamp (UTC)