Zlot Manager is a configurable booking layer that lets an operation define slot categories, slot types, master data, statuses, and conditional rules. It can generate recurring slots or accept one-off slots, evaluate every applicable condition, and allow booking only when the slot is valid.
A reusable booking layer configured around an operation, maintained by its administrators, and extended through CNC implementation support.
Conventional calendars expose empty time but do not model why a slot exists, which operational records it depends on, which statuses control it, or which conditions must pass before somebody can book it. Teams then rebuild those decisions in spreadsheets, manual checks, and application-specific code.
Each layer has one responsibility. Together they let an operation create as many slot types and master tables as its operating model requires without burying every rule inside a separate booking application.
The published configuration becomes the operating context used by every booking decision.
Create categories and reusable slot types, then generate recurring availability or add one-off slots under the same operating model.
Maintain operation-specific tables that describe the people, services, places, equipment, packages, and other records used by slot rules.
Define slot and booking statuses with controlled transitions so availability, holds, confirmation, cancellation, and operational states remain explicit.
Attach conditions to each slot type using master data, status, availability, capacity, compatibility, eligibility, dependency, lead-time, and policy rules.
Evaluate every applicable condition, exclude invalid candidates with a clear reason, and expose only slots that the operation can fulfil.
Use the valid slot set inside white-label customer, staff, and administrator interfaces, then continue the booking into connected operational workflows.
Zlot Manager owns slot configuration and booking eligibility. Ranking is optional and can never make an invalid slot bookable.
Capture the requested service, date context, customer, location, or other known inputs.
Select the configured slot definition and the rules that belong to it.
Bring the relevant resources, entitlements, current statuses, and dependencies into the decision.
Create recurring candidates or retrieve configured one-off slots.
Apply the availability, capacity, compatibility, eligibility, dependency, and policy checks for that slot type.
Block failed candidates with their reason and retain only operationally valid slots.
Apply configured priorities or AI only after eligibility has been established.
Confirm a selected valid slot and move it through the configured status model.
Continue into CRM, reminders, service delivery, attendance, billing, or other implementation-specific actions.
Choose an illustrative booking model and operating condition. Zlot evaluates the configured rules, explains why candidates are blocked, and sends only valid slots to optional ranking.
Two candidates satisfy every doctor, room, machine, and package condition.
Eligibility is evaluated first. Optional priority or AI ranking can order the valid set, but it cannot make a failed candidate bookable.
Codes 'n' Coffee Tech models the initial domain, integrations, validation scenarios, and branded experiences. After rollout, customer administrators can maintain standard slot types, master data, statuses, and conditions while CNC supports advanced changes and continued implementation work.
These implementation stories show Zlot Manager configured as the booking-eligibility engine for two different combinations of slot types, resources, capacity, services, and customer entitlements.
Explore how the same capability is applied to a specific operational constraint.
My Pain Clinic GlobalPain management and wellness
Sweat Fit WellnessFitness and wellnessDescribe the slot types, master data, statuses, conditions, resources, and customer rules involved. We will assess how a Zlot Manager implementation could support the operation.
