I Tried to Set Up Business-Hours Call Routing in the Console: Here's Why I Gave Up
I wanted something that felt like it should already exist: calls during the day ring the office, calls after 6pm and at weekends go to voicemail. I opened the Twilio Console and looked for the setting. There was not one. A few hours later I understood why, and why "business hours" is harder than it sounds.
Why business hours are not a setting on your number
A phone line has no idea what time it is unless something tells it. Left alone, it treats 2pm on a Tuesday exactly like 11pm on a Sunday. The moment you want different behaviour at different times, something has to check the clock on every single call, decide whether you are open, and route the call accordingly.
On Twilio or Telnyx, a plain number simply sends each incoming call to the instructions you gave it. There is no "opening hours" box. So the check has to live somewhere you build.
What it takes to build it in the console
On Twilio, the usual routes are:
- Your own code. A web server receives each call, checks the time, and answers with TwiML that rings the office or plays a voicemail greeting.
- Twilio Studio plus a Function. Studio draws the call flow, but deciding whether you are open usually means a small piece of code (a Twilio Function) that returns open or closed, and a split in the flow based on the answer.
Telnyx is the same idea with TeXML or its call control APIs: something you build has to look at the clock before the call is routed.
That is where my afternoon went: not on deciding my hours, which took a minute, but on the code around them.
The time zone trap
The hardest bug is not the schedule. It is the clock. Servers usually run on UTC, your customers live in your local time, and daylight saving moves that difference twice a year. A schedule stored as "UTC minus 5" is right for half the year and an hour wrong for the other half, which means calls go to voicemail at 4pm in the spring and nobody knows why.
The fix is to store each line's real time zone by name (for example America/New_York) and let the system work out the offset on the day of the call. We wrote a whole post about it: your business hours are probably wrong.
Decide what happens when you are closed
Before building anything, decide where an after-hours call should go. The common choices:
| After-hours option | Good for | Watch out for |
|---|---|---|
| Voicemail | Most small businesses | Many callers will not leave one; pair it with a missed-call text |
| Forward to an on-call phone | Emergencies, trades, healthcare | Someone has to carry that phone |
| A phone menu | Offering choices: emergency line, voicemail, a texted link | Keep it short at night |
| A closed message | Clear hours, nothing urgent | The call ends, so give your hours and website |
| An AI receptionist | Answering questions and booking at night | Uses AI minutes; check what it should and should not promise |
The settings-based way
In TelBuddy, business hours are a schedule on each number, not code:
- Check the number's time zone.
Each number has its own time zone, set once. Daylight saving is handled for you.
- Fill in the week.
For each day, open or closed, with opening and closing times. A half-day Friday is just a different closing time.
- Choose the after-hours route.
Voicemail, forward to another phone, a phone menu, a spoken closed message, or the optional AI receptionist. If AI minutes run out, after-hours callers go to voicemail rather than being turned away.
- Test it.
Call during open hours, then change a day to closed and call again. Two calls and you know it works.
For a holiday, mark that day as closed and switch it back afterwards. The business hours call routing page shows the full setup.
Sample schedules by type of business
A dental office. Monday to Thursday 8 to 5, Friday 8 to 1, closed weekends. After hours: a short phone menu with "press 1 for a dental emergency" forwarding to the on-call dentist, and voicemail for everything else.
A plumbing or HVAC company. Monday to Friday 7 to 6, Saturday 8 to 12. After hours: forward to the on-call technician, because a burst pipe at 9pm is the most valuable call of the week.
A real estate office. Seven days, 9 to 7. After hours: an AI receptionist that can answer questions about listings and take details, because buyers call from yard signs in the evening.
A salon or spa. Tuesday to Saturday, closed Sunday and Monday. After hours: a closed message with the hours and a reminder that booking is available online, plus a missed-call text so nobody is left waiting.
How business hours fit with the rest of your phone setup
- Missed-call texts catch callers who hang up instead of leaving a voicemail, day or night.
- A call queue holds callers during your busiest open hours, with an option to be called back instead of waiting.
- A phone menu can run in open hours, after hours, or both, with different options for each.
- The AI receptionist can cover only the closed hours, so your team handles the day and the AI handles the night.
A quick business hours checklist
- Is each number's time zone set to where its customers are?
- Does every day of the week have a deliberate open or closed setting?
- Does an after-hours caller always have a next step?
- Have you made one test call inside hours and one outside?
- Is there a plan for the next holiday?
Mistakes to avoid
- Trusting the server clock. If your phone system does not know your time zone by name, check it after every clock change.
- Forgetting the weekend. "Mon to Fri 9 to 5" leaves Saturday morning callers wondering if you are still in business. Decide on purpose.
- A closed message with no next step. Say when you open and how else to reach you.
- Never testing after a change. One call outside hours tells you more than any settings screen.
Why it is worth getting right
Business hours routing is a small setting with an outsized effect on how it feels to run a business. Set it once, and every call after 6pm goes exactly where you want, without you doing a thing, and without the guilt of a call that rang out during dinner. If missed calls are part of the problem, see how missed calls cost customers, and for the full phone setup on your own number, phone menu, call queue and AI receptionist setup.
Whatever you choose, write your hours down once, in one place, and let the phone system follow them. Your website, your voicemail greeting and your closed message should all say the same thing, so a caller at 8pm on a Sunday knows exactly when you will be back and how else to reach you.
Frequently asked questions
Does Twilio have a business hours setting?
No. A Twilio number sends every call to the instructions you gave it. Different handling by time of day needs code, a Studio flow with a Function, or a tool like TelBuddy that adds a schedule.
Can I have different hours on different days?
Yes. Each day of the week has its own open or closed setting and its own opening and closing times, so a half-day Friday or a Saturday morning is easy.
How do time zones and daylight saving work?
Each number has its own named time zone, such as America/New_York, and the offset is worked out on the day of the call, so daylight saving changes never shift your hours.
What can happen to a call outside business hours?
In TelBuddy it can go to voicemail, forward to another phone, play a phone menu, play a closed message, or reach the optional AI receptionist.
How do I handle a holiday?
Mark that day as closed for the week of the holiday, then switch it back afterwards. Your after-hours route handles the calls while you are closed.
Does this work on Twilio and Telnyx?
Yes. Business hours routing works the same on numbers from either carrier, on the account you already own.
Business Hours Routing in TelBuddy
Route calls differently when you are open, closed or on holiday.