Operator dashboard: webhooks, intake profiles, multi-tenant
A wave of features in the hosted dashboard, webhook dispatch on booking, per-tenant intake profiles, and a multi-tenant experience for agencies.
What shipped
This was a large wave in the hosted dashboard. The highlights:
Webhook dispatch on the booking lifecycle
The booking.confirmed event fires both at intake and on operator confirmation. Each subscription is isolated, one failing doesn't take the others down, and a subscription that keeps failing is disabled automatically.
Per-tenant intake profiles
Each operator picks the shape of intake at onboarding: booking, quote, or lead. The dashboard adapts to the profile, showing only the sections that make sense for that flow instead of a generic form that serves everyone badly.
Multi-tenant for agencies
Per-tenant scoped URLs, a tenant switcher in the sidebar, and navigation that adjusts to the access role. An agency running several locations now operates all of them from a single dashboard, each tenant in its own space.
Unified contact and newsletter intake
Contact and newsletter now use the same per-tenant authentication, the same CORS, the same attribution, and the same consent posture as booking. One intake model, three ways in.
Why we built it
These features share a theme: take work off the operator. Webhooks carry the booking event where it needs to go without anyone copying data by hand. Intake profiles avoid showing scheduling fields to someone who only collects leads. Agency mode replaces several loose accounts with one dashboard. Each removes a manual step between "the customer booked" and "the operation responded."