At a hypothetical service company, a customer books 15:00. The specialist is free, but the required equipment is occupied. The calendar promised an appointment; reality offers an introduction to the sofa.
Before opening booking, describe everything the service requires.
Define the resource and duration
Bitrix24 online booking uses resources such as employees, rooms and equipment. Setup and reminders are covered in the official guide.
List constraints: service duration, workstation preparation, breaks and schedules. If several resources are required simultaneously, verify support in your configuration before making promises to customers.
Test booking changes
Run a small rehearsal:
- create an appointment manually and through a form;
- move it to another time;
- cancel it and check the freed slot;
- change an employee’s schedule;
- test a reminder using a test contact.
Write the expected outcome beforehand. In particular, a rescheduled customer should not receive the old time in a message.
Check available notification channels, the connected provider, restrictions and costs for your portal. A visible button does not confirm delivery to a particular recipient.
Agree how exceptions are handled
Who contacts late customers? How are cancellations recorded? Can someone book without confirmation? The company makes these decisions, then reflects them in configuration and instructions.
Assess outcomes rather than appointment counts alone: completed visits, cancellations and rescheduling, measured consistently. Record reasons using common wording.
To discuss the workflow with QQDev, prepare one service, its schedule and difficult booking examples. Start with a Bitrix24 audit: a useful calendar should match the team’s reality, rather than simply display attractive empty squares.