Understand busy-time conflict checks
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Prevent overlapping appointments by understanding how provider bookings, schedule boundaries and connected calendar data affect availability.
What you’ll accomplish
Prevent overlapping appointments by understanding how provider bookings, schedule boundaries and connected calendar data affect availability. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
The module tests whether the buffered candidate interval overlaps known busy periods for the provider.
Native appointments are always relevant; connected calendar events can add context or conflict information depending on integration settings.
Cancelled records should not be treated like active work, while pending or approved records can reserve time according to module logic.
Follow these steps
- Identify the provider and candidate interval.
- Check native appointments during the buffered period.
- Check connected calendar events where integration is enabled.
- Check schedule boundaries and blocked dates.
- Resolve the conflicting record rather than forcing the slot.
Settings to check
Check it worked
After this workflow completes, Pixie CRM 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 Pixie CRM 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.
Common mistakes to avoid
- Do not double-book by manually entering a hidden public slot.
- Remote calendar visibility depends on valid connection and date range.
- Cancelled records should be verified if they still appear as busy externally.
- 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.