EXECUTIVE CASE STUDY • EDUCATION AND EVENTS • BOOKINGS AND SCHEDULING
How a children’s activity centre removed double bookings by syncing the calendar to operators’ phones
Birthday parties and group bookings are taken whenever the parent calls, by whoever answers. The failure mode is specific and expensive: two bookings in the same slot. Zuzu Land books straight into a shared calendar in a self-hosted CRM, pushed to operators’ phones in real time.
- Bookings entered asynchronously into one calendar
- Push synchronisation to operators’ phones
- Overlaps removed at the point of booking
The centre’s challenge
Bookings taken by different people, confirmed against different information
Party and group bookings arrived by phone and message, at any hour, and were written down by whoever took the call. The calendar on the wall and the calendar in someone’s head were not always the same calendar.
A double booking in this business is not a scheduling inconvenience — it is a child’s birthday party that has to be moved. The booking had to become shared state the moment it was taken.
Several calendars
Bookings were recorded individually and reconciled later, so two slots could be promised before anyone noticed.
One calendar, pushed
A booking enters the shared calendar as it is taken, and push synchronisation puts it on every operator’s phone in real time.
Client testimony
“Birthday bookings and group reservations are organised asynchronously straight into the calendar. Automatic push synchronisation sends the data to operators’ phones in real time, removing overlaps.”
A shared calendar with push synchronisation
Bookings are entered asynchronously into a single calendar in the installation, so the person taking the call is writing into the same place everyone else reads.
Push synchronisation sends the data to operators’ phones in real time, which means the schedule in the staff’s pocket is the schedule, not a copy of it from this morning.
Modules in use
- Shared calendar — bookings and group reservations in one place.
- Asynchronous entry — bookings recorded whenever they arrive, by anyone.
- Push synchronisation — real-time updates to operators’ phones.
- Conflict prevention — overlapping slots caught at the point of booking.
The modules are licensed separately, so an installation carries only what it uses.
See the pricingWhat changed in scheduling
Double bookings stopped being a periodic accident. Operators work from the live schedule on their phones, and the person answering the phone can commit to a slot with confidence rather than a promise to check.
One-time licence
The platform and the active modules are paid once, not every month, for as long as the company uses them.
Unlimited users
People are added without a per-seat cost, so the licence never decides the size of the team.
Own infrastructure
The installation and the database sit on the company’s own server, so the data stays where the company put it.
Related case studies
Other companies running on Zarina CRM
Sixteen deployments across eleven industries, each with the company named and the workflow described, so you can find one close to your own.
STRATEGIC PARTNERSHIP • ENTERPRISE
Move your operation onto a platform you own
The editions, the modules and the one-time licence are the same ones used in this deployment. The installation sits on your server, the users are unlimited, and the licence is paid once.
- Installed on your own server
- Unlimited users
- One-time payment