Configure service buffers
Reserve preparation and follow-up time around appointments so adjacent bookings do not overlap operational work.
What this feature does
Reserve preparation and follow-up time around appointments so adjacent bookings do not overlap operational work. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Buffer before and buffer after are added to the service duration when the availability engine checks busy periods.
The customer-facing appointment duration remains separate from preparation and clean-up time.
Slot generation rejects proposed times whose buffered interval overlaps existing busy data.
Step-by-step workflow
- Open the service.
- Enter the preparation time in Buffer before.
- Enter the follow-up or clean-up time in Buffer after.
- Save the service.
- Test adjacent slots and confirm the reserved gap is enforced.
Important fields and decisions
What happens after completion
After this workflow completes, Britixo keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Britixo database save.
- Open the saved appointment and confirm the final status and source.
- Check the participant, provider, timing and timezone from the full detail page.
- Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.
Controls, checks and common mistakes
- Do not include the same preparation time in both duration and buffer.
- Large buffers reduce available slots by design.
- Retest all providers after changing a shared service.
- Use the least destructive correction and retain the appointment history when the booking existed operationally.
- Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.
