Override company hours for a provider
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Give one provider a different recurring weekly schedule without changing the organisation's baseline.
What you’ll accomplish
Give one provider a different recurring weekly schedule without changing the organisation's baseline. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
Turning off company-schedule inheritance activates the provider's own weekday configuration.
Public and staff slot generation uses the provider-specific window.
The override does not bypass blocked dates, service assignment or busy-time checks.
Follow these steps
- Go to the provider's Staff Working Hours.
- Disable Use company schedule.
- Enable the provider's working weekdays.
- Enter provider-specific opening and closing times.
- Save and test several days.
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
- Document unusual provider hours for scheduling staff.
- Do not use an override to bypass organisation-wide closure without approval.
- Review the override when the provider changes role.
- 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.