ConnectWiz Booking
The appointment book with a database spine.
Booked by an agent, the AI, a flow, or the customer themselves — every appointment lands in one ledger where rooms, devices and practitioners intersect correctly, double-booking is blocked by the storage layer itself, and your real calendars sync both ways.
Four doors
Everyone books against the same truth
The team, in the diary
A day-view diary and full booking management — types, locations, practitioners, service variants, tenant-defined status labels, no-show handling and line items.
The AI, in two verbs
Wiz offers real free slots, then books the one the customer picks — deliberately two steps, because auto-reserving the first free slot for someone is a demo trick, not service.
Flows, as a step
The booking node drops slot-offering into any automation — the reminder flow that ends in a rebooked appointment, without a human in the loop.
Visitors, self-serve
The website widget's booking mini-app lets customers pick from live availability themselves — appearing only when you actually offer bookable services.
The resource model
Rooms, devices, people — intersecting like reality does
"Available" is a three-way question: the practitioner, the room and the device must all be free together. Most booking tools model one axis and hope; this one models the intersection.
Roles & containers
A booking holds multiple resources by role — room, device, practitioner — and container links mean a device inside a busy room is correctly unavailable, even though nobody booked the device.
The constraint, not a rule
Overlap prevention lives in the storage layer as an exclusion constraint — two racing requests can’t both win, because the second write is physically rejected. A rule engine promises; a constraint guarantees.
Capacity as units
A class with eight seats is eight units, not a counter — so "one left" is a fact about a specific unit, and refunds don’t corrupt arithmetic.
Eligibility, separately
"Can this room host this service" is its own matrix, apart from occupancy — so a free-but-wrong resource is never offered, and the reason is inspectable.
Calendar sync
Your calendars, subtracted from availability
Bookings push out
Appointments appear as events in Google, Outlook or Apple calendars — and disappear on cancel. The practitioner’s phone calendar is never a day behind the diary.
Busy time pulls in
External events subtract from availability — the AI never offers Thursday 15:00 when your personal Google Calendar already has the dentist there.
Role & direction per source
Each connected source has its own setting — read from, write to, both, or busy-only — so a shared clinic calendar and a personal one can play different parts without a fight.
Reminders & operations
The follow-through, automated
Reminders that fire
Customer confirmations and reminders at your configured lead time — email, with optional SMS — plus staff alerts on new bookings. "Circling back" stops depending on memory.
Bookings consume stock
A service appointment can consume parts from the stock ledger — the treatment and the materials it used reconcile in one motion.
History migrates in
Switching from another CRM? The migration engine imports your existing appointment history into the same ledger — the diary doesn’t start amnesiac.
The honest fine print
Stated before you plan around it
No standalone booking link yet
Self-serve booking lives inside the website chat widget — there’s no Calendly-style public booking page you can send by email yet. If that’s your core motion, tell us; it shapes the roadmap.
External CRMs carry less
When a booking writes out to a connected CRM, device and consumption detail may not survive — vendor APIs don’t publish those axes, and the sync says what it dropped instead of dropping it silently.
The ledger is ours, always
Whatever calendars and CRMs connect, the booking ledger stays ConnectWiz’s own table — external systems are sources and mirrors, never the master. That’s a design position, stated.
Every "when are you free?" can end in a held slot.
Set up your resources once — then agents, AI, flows and customers book against the same truth.