Company schedule overview
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains the organisation-wide working windows used as the baseline for provider availability and public slot generation.
What you’ll accomplish
Understand the organisation-wide working windows used as the baseline for provider availability and public slot generation. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
The company schedule stores enabled weekdays and opening/closing times, with a default pattern of Monday to Friday, 09:00 to 17:00.
Staff can inherit this schedule or use staff-specific working hours.
The slot engine combines the applicable daily window with service duration, buffers, blocked dates and conflicts.
Follow these steps
- Go to Company Schedule.
- Check every weekday and its enabled state.
- Verify opening and closing times.
- Save the baseline schedule.
- Test a provider who is configured to use company hours.
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
- Company hours do not by themselves assign a provider to a service.
- Closing a weekday affects inherited providers.
- Timezone and daylight-saving settings must match the organisation's operating context.
- 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.