Restaurant host duties and the phone go together because the same person often has to greet walk-ins, keep a wait list moving, and answer calls. The host should handle simple questions, take pickup orders when possible, and hand off anything sensitive, detailed, or time-consuming.
For a busy pizza shop, deli, or family restaurant, the goal is not perfection. The goal is a short, repeatable phone routine that protects the front door, keeps orders accurate, and gives staff a clean handoff when the caller needs more help than the host can give.
Key takeaways
- The host stand should answer simple phone calls, take orders, and protect the flow at the front door.
- Use the same short script every time so callers get a clear answer and the kitchen gets clean details.
- Hand off catering, allergy, complaint, and manager calls with a summary instead of making the caller repeat everything.
- Set up call forwarding based on your real rush patterns, and confirm it with a test call.
In this post
- What should the host handle on the phone during a busy shift?
- How do you keep phone calls from slowing down the front door?
- What details should the host collect every time?
- When should the host hand the phone off to staff?
- How do you answer hours, parking, and menu questions without guessing?
- How should you set up the phone so the host stand is not stuck all day?
- Questions owners ask
What should the host handle on the phone during a busy shift?
The host stand should handle the calls that can be answered quickly and clearly without slowing service. That usually means hours, address, parking, menu basics, pickup orders, reservation requests, and simple status questions.
A good rule: if the answer is on the public menu or can be confirmed in one quick check, the host can usually take it. If it needs judgment, a manager, or a long back-and-forth, send it to staff with a note.
Use a simple script line like: "Thanks for calling. I can help with pickup orders, hours, and menu questions. If you need catering or have an allergy question, I’ll get someone to help."
Concrete checklist for the host stand:
- Answer with the restaurant name first.
- Ask whether it’s pickup, delivery, reservation, or a question.
- Repeat the order back before hanging up.
- Get the caller’s name and phone number.
- Quote a ready time.
- Send special cases to staff with a short summary.
If you want a cleaner handoff for busy nights, short-staffed shifts is a good place to start.
How do you keep phone calls from slowing down the front door?
The problem is not the phone itself. The problem is the interruption. A host who is seating a table, checking a wait list, and taking calls can lose track fast.
Make the phone routine short and predictable. The host should not improvise every time. Keep the same order: greeting, reason for calling, details, confirmation, close.
Worked example: say your host spends 3 minutes on a call and 4 walk-ins arrive during that time. That can create a bottleneck. If the phone call is trimmed to 90 seconds for a simple pickup order, the front door stays moving. Plug in your own times and see where the pinch point is.
Here is a practical front-counter script:
- Greet the caller in one sentence.
- Ask for the order type.
- Take the details in one pass.
- Confirm the total and ready time.
- End with the name and pickup reminder.
If you need a stronger phone routine, phone greeting templates can help your staff sound consistent. ROAL uses a similar idea on the phone: short, clear, and focused on the order or question, not a long conversation.
What details should the host collect every time?
For phone orders, the host should collect the same core details every time so the kitchen gets a usable ticket. That keeps the line from guessing later.
A solid phone order should include:
- Items and sizes.
- Modifiers and notes.
- Name and phone number.
- Pickup time or ready time.
- Any special instructions the kitchen needs.
Example script: "Can I get your name and number, and then I’ll repeat the order back to you?" That one line helps prevent confusion.
Here is a simple order capture table you can copy into staff training:
| Detail | Example |
|---|---|
| Name | Maria |
| Phone | 201-555-0148 |
| Item | Large cheese pizza |
| Modifier | No onions, extra crispy |
| Ready time | 25 minutes |
| Notes | Call on arrival |
ROAL follows this same pattern on calls: it takes items, sizes, modifiers, notes, name, phone, and a ready time, then confirms the order back and sends a clean ticket to the kitchen screen. It also does not offer items marked sold out.
When should the host hand the phone off to staff?
The host should not try to solve every call. Some calls need a person with the right context, and those should go to staff quickly with a summary.
Send these to staff:
- Catering requests.
- Complaints.
- Allergy-sensitive questions.
- Manager requests.
- Anything the host cannot answer from the menu or hours.
A good handoff sounds like this: "One moment please, I’m getting someone to help with that." Then the caller should not have to repeat everything from scratch if the handoff is done well.
A simple staff note should include the caller’s name, phone number, issue, and what was already asked. Example: "Caller: Tony. Wants a catering quote for Saturday. Needs manager call back after 2 p.m." That is much better than a bare transfer.
If your team is deciding who handles which calls, what calls should reach the manager is a useful companion topic. For restaurants using ROAL, the host can send these tricky calls to staff with a summary, while the owner answers the uncommon question once and the host learns it from then on.
How should you set up the phone so the host stand is not stuck all day?
The phone setup should match how your restaurant actually works. Many owners want all calls forwarded to one place. Others only want forwarding when the line is busy or unanswered.
US call forwarding codes vary by carrier and plan, so always confirm with your carrier and test with a live call. Common examples are:
- Many landlines and some carriers: 72 to forward all calls, 73 to turn it off.
- Verizon Wireless: 72 / 73 for all calls, and *71 for busy or no-answer forwarding.
- Some GSM carriers: *21number# for all calls, ##21# to turn it off, *61number# for unanswered calls, and *67number# for busy calls.
- Business VoIP systems often use a web portal.
A practical setup checklist:
- Decide whether to forward all calls or only overflow calls.
- Test from a mobile phone.
- Confirm the restaurant’s main number still stays live.
- Tell staff how to turn forwarding off if needed.
- Keep the routing notes in one place.
ROAL gives each location its own phone line automatically, and the owner forwards the restaurant’s existing number to it. The restaurant keeps its own number, and forwarding can be turned off any time. You can build a free test host from your website, Google Maps link, or restaurant name and city, then test it right in the browser before going live.