# Conditional call forwarding for busy or unanswered calls

URL: https://tryroal.com/blog/conditional-call-forwarding-busy-no-answer
Published: 2026-10-28 · By Venkata Vamsi, founder of ROAL

**How do I set up conditional call forwarding for my restaurant phone so calls go to a backup only when I'm busy or don't answer?** Conditional call forwarding sends calls to another number only when your line is busy or unanswered, instead of forwarding every call. On many carriers, the codes are different, so confirm with your carrier and test the setup with a real call. For restaurants, it is a practical way to keep your main number while routing overflow calls to ROAL or another backup line.

Conditional call forwarding is when your restaurant phone sends calls to another number only if you are busy or do not pick up. It is a good fit for lunch rushes, short-staffed shifts, and times when the counter is too busy to answer.

For a restaurant, this lets you keep your main number and send overflow calls somewhere useful instead of straight to voicemail. ROAL can be the backup phone host, answering questions, taking orders, and sending a clean ticket to the kitchen screen when your line is tied up.

Key takeaways:
- Forward only busy or unanswered calls when you want a backup without changing your main number.
- Always confirm the exact forwarding code or web setting with your carrier or phone system.
- Test with a real call so you know ring timing, forwarding behavior, and ticket handoff are working.
- ROAL can answer overflow calls, take orders, and send clean kitchen tickets while staff keeps the main line.
- Keep forwarding flexible so you can turn it off any time if your staffing changes.

## What is conditional call forwarding, and when should a restaurant use it?

Conditional call forwarding is different from forwarding every call. It only kicks in when your line is busy or when nobody answers in time. That matters in a restaurant because your staff may still want to answer some calls directly during slower hours.

Use it when you want a backup for:
- lunch rush pickups
- dinner rush delivery orders
- after-hours calls
- shifts where one person is juggling the phone and the front counter

A simple example: say your shop gets a burst of calls from 6:00 to 7:30 p.m. Your host can answer the first ring, but if the line is tied up, the next call forwards to ROAL. ROAL can take the caller’s name, phone, items, modifiers, and ready time, then send the ticket to the kitchen screen. That keeps the phone from backing up while the crew keeps moving.

A useful rule: forward only the calls you are likely to miss. If you can still answer the phone reliably, keep it on your main line. If not, use conditional forwarding rather than sending every call away.

## Should you forward all calls or only busy and unanswered calls?

For many restaurants, the answer is: start with busy or unanswered calls. That gives you a safety net without giving up the phone when the dining room is quiet or a host is available.

Here is a simple way to decide:

| Situation | Best setup |
|---|---|
| One person at the counter, steady traffic | Busy/unanswered forwarding |
| Closed shop or holiday closure | Forward all calls |
| A manager is off-site but wants every call | Forward all calls |
| You want staff to answer when they can | Busy/unanswered forwarding |

A worked example helps. Say you usually get 40 calls in a dinner window, and your team answers 28 of them. If 12 go to voicemail or get missed, conditional forwarding can catch those overflow calls. That is often better than forwarding every call, because your staff still handles the easy ones and the backup handles the rest.

If you use ROAL, the restaurant keeps its own number and can turn forwarding off any time. That makes it easier to test during a busy week and back it out later if your staffing changes.

## How do I set up busy or unanswered forwarding on my line?

The exact steps depend on your carrier or phone system, so always confirm with them and test with a real call. Codes and menus vary, but the pattern is usually simple.

Use this checklist:
1. Decide where unanswered or busy calls should go.
2. Write down the forwarding number.
3. Ask your carrier whether your line uses dial codes or a web portal.
4. Turn on forwarding for busy, unanswered, or both.
5. Call your own restaurant number from a different phone and watch what happens.
6. Place a real test order or test question to make sure the backup line behaves the way you want.

Common US patterns include *72 and *73 on many landlines and some carriers for forward all calls on and off. On some GSM mobile carriers, **61*number# forwards unanswered calls, **67*number# forwards busy calls, **21*number# forwards all calls, and ##21# turns that off. Verizon Wireless often uses *72 and *73, and *71 for busy/no-answer forwarding. Business VoIP systems usually handle it in the web portal.

If you want a shortcut, [How to forward your restaurant calls](https://tryroal.com/blog/how-to-forward-restaurant-calls) and [Call forwarding codes by carrier](https://tryroal.com/tools/call-forwarding-codes) are good references before you change anything.

## What should I tell staff before I turn forwarding on?

Forwarding works best when the team knows what will happen. If staff expects every call to ring forever, they will think something is broken when unanswered calls start going to the backup.

Use a short staff script:
- “If the line is busy, the next call may go to our backup host.”
- “If you hear the phone ring twice and it stops, that call may have forwarded.”
- “For allergy questions, catering, or manager requests, the backup host will send a summary to us.”

A quick shop-floor checklist:
- keep the forwarding number near the register
- make sure managers know how to turn forwarding off
- tell staff what types of calls should stay with the team
- remind everyone that card numbers are not taken over the phone

This matters because restaurants need clear handoffs. ROAL can handle ordinary questions, pickup and delivery orders, reservations, and language matching. It sends tricky calls like catering, complaints, allergy-sensitive questions, and manager requests to staff with a summary. That way, the backup line is not trying to do everything; it is just covering the calls your team is likely to miss.

## How does ROAL fit into conditional call forwarding?

ROAL is built for the exact calls a restaurant misses during rush periods. It answers the phone, takes orders from your live menu, answers common questions about hours, address, parking, and the menu, and sends a clean ticket to the kitchen screen.

A typical setup looks like this:
- your main number stays the same
- you forward only busy or unanswered calls to the ROAL line
- staff still answers when available
- ROAL handles overflow calls and logs the conversation

That can be especially helpful if you do not want to pay a fixed monthly fee just to have a backup. Many AI phone tools charge a monthly amount per location, even when the phone is quiet. ROAL is priced per completed phone order, with calls, questions, and test calls unlimited and free. For a restaurant owner, that makes it easier to match cost to actual orders instead of paying for idle time.

If you want to see how it would sound, ROAL can be started from your website, Google Maps link, or restaurant name and city at /try. It reads public menu and hours information, and you can also upload a menu in any format. You can test-call it in the browser before you decide anything.

## How do I test forwarding so I do not lose calls?

Never turn on forwarding and walk away. Test it the same day, during a calm moment, and then again during a real rush if you can.

Use this simple test plan:
1. Call your restaurant from your cell phone.
2. Let the line ring until it should forward.
3. Confirm the backup number answers or rings as expected.
4. Ask a real restaurant question, like hours or pickup timing.
5. Place a sample order with one item, a size, and a modifier.
6. Confirm the ticket reaches the kitchen screen or the backup destination you planned.

Example test script: “Hi, can I place a pickup order for a large pepperoni with extra cheese?” Then ask, “What time will it be ready?” That gives you a full test of the forwarding path, the menu knowledge, and the handoff.

If you are using ROAL, also check the owner dashboard later. You can review call history, transcripts, recordings, kitchen tickets, menu edits, hours, FAQs, and upsell suggestions. If a question was not answered, it lands in the inbox, and the host learns from your reply the next time. That makes conditional forwarding more useful over time, because the backup gets smarter about your own restaurant.

## FAQ

### What is conditional call forwarding for a restaurant phone?

Conditional call forwarding sends calls to another number only when your line is busy or not answered. For a restaurant, that means your staff can still take calls when available, while overflow calls go to a backup line. It is useful during rushes and short-staffed shifts.

### How do I forward calls only when busy or unanswered?

Use the forwarding method your carrier or phone system supports, then choose busy, unanswered, or both. Many carriers use dial codes, while business VoIP systems often use a web portal. Always confirm the exact code or setting with your provider and test it with a real call.

### Should I forward my restaurant phone all the time?

Usually not, unless you are closed or want every call to go somewhere else. Many restaurant owners prefer busy or unanswered forwarding so the main phone still rings when staff is available. That keeps the line useful without sending away calls you could answer in-house.

### Can ROAL take over when my restaurant is busy?

Yes. ROAL can answer overflow calls, take pickup and delivery orders from your live menu, answer common questions, and send a clean ticket to the kitchen screen. It also passes along catering, complaint, allergy-sensitive, and manager calls to staff with a summary.