After-hours call routing is one of those operational tasks that looks simple on paper and turns into a half-day project when you actually do it. The forwarding rules, the time-of-day logic, the integration with your answering service, the testing, there's a workflow that works and several that don't. This post walks through the working setup, step by step.
The four pieces of the setup
1. Your business phone number (the one customers call). 2. Your VoIP or carrier platform (RingCentral, Dialpad, Vonage, OpenPhone, Google Voice, traditional carrier). 3. Your answering service number (live or AI). 4. Your on-call tech contact methods (phone, SMS).
Each of these has configuration. The trick is connecting them in the right order without dropping the line during the switchover.
Step 1: Document your current setup
Before changing anything, write down:
- Your published business phone number(s).
- Your current voicemail handling (own VoIP voicemail, carrier voicemail, none).
- Your current after-hours behavior (rings forever, voicemail, IVR, forwarded to a person).
- Who has admin access to your phone platform.
- Which CRM or dispatch system the calls need to feed into.
If you don't know one of these, find out before you continue. The setup will fail at exactly that point.
Step 2: Configure your time-of-day rules
In your VoIP platform, set up a "business hours" rule that defines:
- Weekday hours when calls route to your normal handling (your office, your phone, your daytime answering service).
- After-hours: weekday evenings, full weekends, holidays.
- Holiday schedule for the year ahead.
The typical pattern for contractors:
- Business hours: Mon-Fri 7 AM - 6 PM local time.
- After-hours: All other times.
- Holidays: Federal holidays + any local closures you observe.
Some VoIP platforms have a "schedule" or "auto-attendant" object that holds this. Others have it per-forwarding-rule. RingCentral, Dialpad, and OpenPhone all support time-of-day routing natively.
Step 3: Set up after-hours forwarding to your answering service
The answering service (live or AI) gives you a phone number to forward to. The setup in your VoIP platform:
- During business hours: route to your normal handling.
- After business hours: forward to the answering service number.
Test the forwarding by calling your main business number from a personal phone at 7:01 PM. You should hear the answering service's greeting. If you hear voicemail or it rings forever, the forwarding rule is wrong.
Step 4: Configure the on-call handoff
Your answering service needs to know who to call when an emergency triggers. The configuration:
- Primary on-call: Phone number, contact name, days/times when this person is on call.
- Secondary on-call: The backup if primary doesn't accept.
- Tertiary on-call: Usually you, the owner.
- Failover SLA: How long the answering service waits before rolling to the next contact (30-60 seconds typical).
Make sure each on-call contact knows they're configured and how the handoff works. A tech who gets a call from an unfamiliar number at 2 AM may not answer if they don't know the answering service's caller ID.
Step 5: Set up the CRM / dispatch feed
The answering service captures intake; that intake needs to land in your system. Common patterns:
- Email: Intake sent to dispatch@yourshop.com. Your dispatcher creates the SO from the email.
- SMS to dispatcher: Intake summary texted to your dispatch contact.
- Webhook to CRM: Direct API push to ServiceTitan, Housecall Pro, Jobber, or other.
- Manual review portal: Dashboard where dispatch can see all captured intake.
Native API integration with the major contractor CRMs is improving but uneven in 2026. OnCrew's current approach is assisted setup today with native API integrations on the roadmap for Q3 2026. In the meantime, captured intake flows to your team via email and SMS, and your dispatcher books from there.
Step 6: Set up testing protocol
Before flipping the forwarding live, run these tests:
- Routine test call. Call your business number after-hours. Verify the answering service answers, runs intake, books an appointment, sends the intake to your CRM/email.
- Emergency test call. Call with an emergency intent ("my CO detector is going off"). Verify the AI runs the safety branch, captures intake, alerts the on-call tech. Verify the on-call accepts and gets the transcript.
- Failover test call. Same as emergency, but with the primary on-call deliberately not answering. Verify the rollover to secondary fires.
- Off-hours-edge test. Call at 6:55 PM (still in business hours) and 7:05 PM (after-hours). Confirm both route correctly.
- Holiday test. Use a manual override to set "today is a holiday" and confirm calls route to after-hours.
If any test fails, fix it before going live. Don't ship a setup with a broken failover.
Step 7: Go live with monitoring
The first week is monitoring week:
- Listen to every captured call recording in the first week.
- Verify each emergency handoff completed correctly.
- Check that intake landed in your CRM/dispatch.
- Confirm no calls dropped or routed wrong.
Issues in the first week are setup issues. Issues after the first week are usually script issues or edge cases. Track both separately.
Common setup mistakes
1. Forwarding to the wrong number. Easy to mistype the answering service number. Test before going live.
2. Time-of-day rules in the wrong timezone. Make sure your platform is set to your local time, not UTC or a vendor default.
3. On-call rotation not configured. "It's just me" is fine for a 1-truck shop. For 5+ trucks, set up the rotation in advance.
4. CRM integration set up but not tested. Send a fake call through the full pipeline and verify the SO lands. Don't assume.
5. Voicemail still on as a fallback. Some VoIP platforms have voicemail as a final fallback even when forwarding is set. If the answering service is down, you want the call to retry or alert you, not silently drop into voicemail.
Switching answering services without dropping a call
If you're moving from one answering service to another:
- Configure the new service fully.
- Test the new service with internal calls.
- Schedule the cutover for a low-call window (a weekday morning).
- Update the forwarding rule.
- Monitor for the first 24 hours.
- Don't cancel the old service until the new one has handled 48 hours of live calls cleanly.
The overlap cost is usually one prorated month. The risk of dropping a call during the switch is much higher than the overlap cost.
For more, see the emergency call routing setup guide, the answering service setup checklist, and the after-hours answering service guide.
FAQs
How long does the full setup take?
For a 1-truck shop with a simple VoIP setup: 2-4 hours. For a 10-truck shop with complex routing, multiple departments, and CRM integration: 1-3 days, spread over a week.
Can I do this without IT help?
Most VoIP platforms have admin UIs that don't require IT. The hard parts are the time-of-day rules and the CRM integration. If those are configured, the rest is straightforward.
What if my phone system is from a traditional carrier (not VoIP)?
You can usually set up call forwarding through the carrier (dial *72 or use their web portal). Time-of-day routing is harder; you may need to switch to a VoIP platform that supports it. RingCentral, Dialpad, and OpenPhone all do this well.
How do I test without using real customer numbers?
Use your personal cell to call your business number. The answering service can't tell the difference between a test caller and a real customer; the configured intake fires for both.