Reliability in Zimun means the same availability rules run on every surface customers and your team can book through, so a confirmed slot stays confirmed.
Same rules across every channel
Your public booking page, the API, the MCP endpoints, and the chat agent all consume one availability service. There is no separate “web only” logic, so a slot you see on the website is the same slot the API and chat see.
Conflict prevention at booking time
- Each service can require specific team members; a slot only appears when at least one assigned member is free for the full duration.
- Each service can require specific resources; every required resource must be free for the full duration, or the slot is hidden.
- Appointments held, scheduled, or confirmed all count as busy for staff and resource allocation, so two channels cannot claim the same slot.
Customer self-service without conflicts
- Confirmation emails include secure reschedule and cancel links, so customers change their booking without phoning the front desk.
- A reschedule offers only slots that pass the same availability check the original booking did.
- Cancellations free the slot immediately for the next booking through any channel.
Operator visibility
- The dashboard agenda shows upcoming and earlier-today appointments with a status pill that reflects the customer’s RSVP.
- The popup on each appointment exposes team member, resource, customer contact, and the current execution state for a single source of truth.
- Every action — reschedule, cancel, attendance — is recorded so the change history is auditable.