Admin & Operations

Appointment booking

Full lifecycle management — create, confirm, cancel, complete — with recurring availability slots and exceptions for blocked dates and vacations. Notification emails can be resent on demand, and booking has its own statistics.

Two support channels, cleanly separated

An admin-side inbox (filterable by status, priority, category, assignment, with canned quick replies) and a public-facing chat that works for logged-in users and guests alike. Notifications for both are computed on demand from the underlying conversation and order data, refreshed every 30 seconds — a deliberately simple, reliable approach over a more fragile real-time push system.

User and company management

Full admin CRUD for users and companies: role changes, bulk activation/deactivation, team invitations with expiry, and per-user purchase history at a glance.

Compliance that's actually tracked, not just displayed

Terms of Service are versioned, with per-user acceptance records — not just a static page. Cookie consent choices are logged individually, giving you a real audit trail for GDPR rather than a cosmetic banner.

A system-wide audit log

Most sensitive actions across the app write to a central log, with automatic pruning of old entries and email delivery history tracked separately.

Add admin screens without building them

A metadata-driven UI layer lets a new admin module — a form, a table, a full CRUD screen bound to a Payload collection — be declared rather than hand-built. This is the same mechanism an AI agent can drive through the propose_feature_module MCP tool: describe the module in plain language, and the screen exists.