A schedule is a routing rule
Opening-hours logic chooses a destination based on time and configured conditions. The result depends on the PBX's time zone and clock as well as the schedule itself. A correct-looking local workstation time does not prove the server is using the intended zone.
Include holidays, timezone and a manual override in the operating plan. Test both branches and the transition between them.
Separate ordinary and exceptional days
Document normal hours, holidays and unexpected closures. Choose the open and closed destinations and make each announcement accurate. Avoid overlapping schedules whose priority is unclear to the administrator.
Control the override
A manual open/closed override can help during weather or staffing disruptions, but it needs an owner and a visible reset procedure. An override forgotten after a holiday can keep callers away from a staffed team.
Test the boundary
Validate both sides of an opening or closing condition through a supported controlled test. Check overnight hours, weekends and daylight-saving transitions where relevant. Call the published number to confirm the complete upstream route. Keep a simple calendar review task in the operating process rather than relying on callers to report stale greetings.
Applying the reference
The Sangoma reference explains PBX feature concepts; some screenshots and interface instructions describe older releases. This planning guide does not rely on those screenshots as a FreePBX 17 setup procedure. Confirm the installed module and current provider feature behavior before rollout.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.