Use the company schedule for staff
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Make a provider inherit the organisation's current working hours and closures.
What you’ll accomplish
Make a provider inherit the organisation's current working hours and closures. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
The staff schedule setting marks the provider to use company schedule values instead of a separate weekly pattern.
Future availability reflects later company schedule changes automatically.
Service assignments, blocked dates, buffers and busy records still apply.
Follow these steps
- Go to Staff Working Hours.
- Select the provider.
- Enable Use company schedule.
- Save.
- Search slots for an assigned service on open and closed company 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
- Do not expect inheritance to copy values into a permanent separate schedule.
- A company closure can remove future slots for all inherited providers.
- Existing appointments remain and should be reviewed separately.
- 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.