Define the overnight and weekend workflow
Start with your opening hours and the calls you accept outside them. Routine inquiries can use approved FAQs and intake. Requests that need review can become a callback message with the information your team needs when it returns.
The caller should hear whether a booking was confirmed, an on-call transfer occurred, or a request is pending. “We have your message” is different from “Someone will arrive tonight.”
Urgent and routine calls take different paths
An urgent flag is a business routing decision based on the caller’s description and your approved rules. It is not a medical diagnosis, safety guarantee, or dispatch confirmation. Configure the on-call destination, when it is available, and what the AI says if it cannot be reached.
An illustrative weekend call
A plumbing caller reports an active leak Saturday evening. The AI can capture the service location, contact details, and issue, then use the urgent routing rule. A maintenance inquiry can follow the ordinary callback path. The team receives the reported concern and actual action status, not an invented repair recommendation.
Make the fallback explicit
A real live transfer requires a configured, reachable destination. If a person is unavailable, the AI can collect a message or callback request. Set expectations based on your actual service policy; do not guarantee a response time that staff have not agreed to deliver.
Connected scheduling can still use real availability for approved appointments. Without it, a preferred time is captured as a request. Avoid treating an overnight request as an accepted service commitment.
Prepare the morning handoff
Choose which fields make after-hours follow-up useful: callback number, reason, location where relevant, urgency flag, and pending action. Assign a team owner to review requests. Test an ordinary evening inquiry, an urgent scenario, and an unavailable on-call destination before activation.
Size the plan around covered minutes
Estimate the connected call minutes that occur during the hours you want covered. Launch includes 250 minutes for $199/month, with larger Growth and Scale allowances available. No setup fee. Cancel anytime. This is AI answering coverage; it does not include a claim of 24/7 human staffing.
Questions about this workflow
Will someone answer every urgent call?
AI can answer calls routed to it. Human availability depends on your configured on-call arrangement, with a message fallback when a person cannot be reached.
Can it cover weekends?
Yes, when phone routing is configured for that coverage. The rules and available actions should match your weekend operations.
Does it promise emergency dispatch?
No. Dispatch and arrival claims require actual confirmed workflows and should never be inferred from message capture.