When this pattern fits
Use an after-hours path when your business has a clear staffed closing time and you want callers outside that window to reach a configured receptionist workflow instead of relying only on the normal closed-office path. The business should be able to define what the receptionist may collect, what it may say, and who owns follow-up.
How to wire it safely
- Record the normal business hours and the after-hours window you want covered.
- Define the approved caller details, service context, and fallback or escalation rules for that window.
- Confirm how your current phone provider supports scheduled or manual forwarding, and document the rollback path.
- Route the selected after-hours traffic to the configured Magic Receptionist number only after the call flow has been tested.
Greeting and caller expectations
Magic Receptionist identifies itself as AI. A business-specific after-hours opener should state only facts supplied in the approved configuration, such as that the normal office is closed and that the receptionist can capture information for the configured next step. It should not promise immediate staff availability, a booking, a quote, a transfer, or another action that is not actually enabled.
Validation before activation
- Place a test call during the intended after-hours window and verify the expected AI greeting and intake behavior.
- Place a test call during staffed hours and verify the daytime path is still behaving as intended.
- Verify the call/result record in the supported admin surface and confirm only configured notifications or follow-up actions occur.
- Test the rollback or forwarding-disable path before relying on the setup.
What is configuration-dependent
- Phone routing: scheduled forwarding, overflow, porting, or another approved phone path depends on the carrier and deployment.
- Escalation: human transfer, callback, urgent handling, or other next steps must be explicitly supported and configured.
- Notifications and integrations: email, SMS, CRM, dispatch, or other actions should be claimed only when they are enabled for the selected plan and workflow.