Written by Rook, Rinzo’s AI operations assistant. This is AI-authored guidance, not a claim of personal experience. Check the linked sources and current product documentation before making changes.
Your opening hours need a call plan
Business-hours call routing sends callers to different destinations depending on when they call. During opening hours, that might be your team. At lunch, on holidays, and after closing, it might be a greeting and a business mailbox. The useful part is deciding what happens when the schedule and the people do not line up: someone calls just before closing, nobody answers during open hours, or a holiday falls on an ordinary workday.
Start with a written schedule and a destination for every unanswered call. You can use that plan yourself or give it to an agent to configure. Rinzo supports hours, holidays, ring groups, and auto-attendant menus; its call-routing guide explains where to manage them.[1] The example below is a planning worksheet, not a preconfigured account or a report of a live call test.
Write the schedule before recording the greeting
Imagine a small workshop with a front-desk person and an owner who also works on jobs. The workshop wants callers to reach a person when someone is available, without ringing the owner's cell phone all evening. This is an illustrative schedule:
| When | What the caller gets | If nobody answers |
|---|---|---|
| Monday–Friday, 9 a.m.–5 p.m., except lunch | A short greeting, then the front-desk ring group | Business voicemail |
| Weekday lunch, noon–1 p.m. | A lunch greeting, then business voicemail | The same mailbox |
| Evenings and weekends | A closed-hours greeting, then business voicemail | The same mailbox |
| Listed closure dates | A holiday greeting, then business voicemail | The same mailbox |
Add the business's time zone to the worksheet, using a location such as America/Vancouver. If an administrator works in a different zone, the schedule still needs to follow the business. In Rinzo, a time-based route uses its configured time zone, or the account's time zone if the route does not specify one. Check the account with rinzo account show rather than assuming the laptop's clock controls calls.[3]
Name the person responsible for the mailbox. A correctly routed message is still a missed opportunity if nobody reviews it. Choose an honest review routine before promising callers a response time.
Treat holidays and lunch as exceptions to the week
A weekly schedule cannot tell you which Monday the business has decided to close. Keep a separate list of actual closure dates, including observed holidays and one-off shutdowns. A named holiday is not automatically the day your business observes it.
Rinzo's auto-attendant recipe evaluates a holiday first, then a break, then open hours, and otherwise uses the closed route.[2] In the workshop example, a closure date should therefore use the holiday message even if the caller dials during a normal lunch break.
Boundary times deserve their own checks. The same recipe documents inclusive time windows: for a noon–1 p.m. break, exactly 1:00:00 p.m. is still in the break.[2] Write down what you want at 12:59:59, 1:00:00, and just afterward, then simulate those times. Do not assume a label such as 'closes at 5' expresses every boundary rule you intended.
Give temporary closures an end date and put a review on your calendar. Recheck recurring rules when working hours change, and after a clock change if your business observes one. That is a maintenance recommendation, not a claim that the platform changes every holiday rule for you.
Use a greeting that explains the next step
The caller usually needs to know which business answered and what happens next. These example scripts fit the worksheet; replace the name, hours, and promises before recording them.
During open hours
Thanks for calling Cedar Workshop. Please hold while we try the front desk. If we cannot answer, you can leave a message.
Lunch break
Thanks for calling Cedar Workshop. The front desk is closed for lunch until 1 p.m. Please leave your name, number, and a short message for the team.
Closed hours
You have reached Cedar Workshop outside our opening hours. We are open Monday through Friday, 9 a.m. to 5 p.m., with a lunch break from noon to 1. Please leave a message for the team.
A specific holiday closure
Thanks for calling Cedar Workshop. We are closed today and reopen on the date listed on our website. Please leave your name, number, and what you need help with.
A specific reopening date is better if you will reliably update it. Avoid 'someone will call you right back' unless someone is actually assigned to do that. Listen to the full greeting on a phone before using it: a correct script can still have an unclear business name or an unexpectedly long pause.
Open does not mean someone will answer
Give the open-hours ring group an explicit no-answer destination. If the front desk is busy, callers should reach the planned business mailbox rather than ring indefinitely. Only add a backup person when they have agreed to take those calls.
If the backup is a cell phone, distinguish a plain forwarding destination from a route with business voicemail afterward. Rinzo documents that an unanswered plain outside-number target ends the call. For an on-call cell that must fall back to a business mailbox, its recipe uses a ring group with a cell-number member, answer confirmation, and a voicemail overflow.[2][3] Our business-number forwarding guide explains that distinction in more detail.
Forwarding to a cell phone is an outbound call, so review the phone-system offer and current calling rates before making it the default backup.[3] Do not create an after-hours on-call option simply because the software can route one. The business needs someone willing to answer it.
Test a week of calls without waiting a week
Rinzo's CLI can simulate a call at a chosen time without dialing anyone.[4] Have your administrator or agent check the planned route for these cases and record the expected destination alongside the result:
- A normal weekday morning, with a person answering.
- The same morning, with nobody answering.
- Just before lunch, exactly at its start and end, and just after it.
- Just before and after the day's closing boundary.
- A weekend and a listed holiday during ordinary weekday hours.
- Each menu choice, an invalid key, and no key at all, if you use a menu.
Simulation checks the configuration, not the caller's audio or the receiving phone. Follow it with real calls from a phone outside the ring group. Listen to the greeting, answer and decline calls, leave a voicemail, and confirm the responsible person can retrieve it. Avoid changing live office hours just to test a scenario unless you have a controlled plan and will restore the schedule. Never use an emergency number for testing; Rinzo does not support 911 or emergency calling during early access.
If an agent builds your hours and menus, Rinzo places that routing in Advanced Callflows in the Control panel; do not set up the same main number again in SmartPBX.[1][5] Keep the worksheet with your configuration handoff. When a teammate asks to change Friday's hours, you will have both a clear instruction and a test to run afterward.
Ready to configure it? Use the call-routing guide for the Control panel, or the agent setup guide to give an agent the schedule and destinations.
