Handling kids' menu questions on restaurant calls

Most callers are asking the same few things. They want to know if you have a kids menu at all, what items are on it, what the portion size looks like, and whether it comes with fries, a drink, or another side. They may also ask if the meal can be made mild, plain, or without a sauce.

A good phone answer gives the caller the useful facts right away. You do not need to read the whole menu. Just give the item, the side, and the obvious change options.

Use a script like this:

• “Yes, we do have a kids menu.”
• “We have chicken fingers, grilled cheese, and buttered pasta.”
• “Each kids meal comes with fries or applesauce.”
• “We can do plain noodles or sauce on the side.”

If you want a place to keep these answers organized, the menu and FAQ tools in How it works and Questions owners ask are a good place to start. ROAL can use those details so the same answer is available every time, even when the line is busy.

Write the answer the way your staff would say it out loud. Keep it under 20 seconds if possible. A caller usually does not want a long explanation; they want to know what their child can eat and whether it will be easy to order.

A simple script can follow this order:

1. Say yes or no.
2. Name the kids items.
3. Mention what comes with them.
4. Say what small changes are allowed.
5. Offer to take the order.

Example script: "Yes, we have a kids menu. We have chicken fingers, grilled cheese, and pasta. Kids meals come with fries or applesauce. We can do plain, no spice, or sauce on the side. What would you like to order?"

If your menu changes by day, write down the standard items and the exceptions. That keeps the answer clean and avoids confusion. For phone greeting ideas that still sound natural, Phone greeting templates can help you shape the first few words of the call. If you use ROAL, you can also edit these answers in the dashboard so they match the current menu.

Kids menu calls often turn into allergy calls fast. A parent may ask about gluten, dairy, egg, nuts, or whether a fried item shares oil with other menu items. That is not a call to guess on. It is a call to slow down and hand the question to someone who can confirm it.

A safe phone flow is:

• Give the menu item only if you know it.
• Do not guess on ingredients.
• Do not promise a special prep unless the kitchen can do it.
• Send the question to staff with the caller’s name and phone.

Example wording: "I want to make sure we get that right for you. I’m sending this to the restaurant team now so they can confirm the ingredients."

If your menu has clear allergen notes, that helps a lot. You can pair this with your own menu labels and a post like Allergen labeling on your menu. ROAL is built to hand off allergy-sensitive questions to staff with a summary, so the caller is not left hanging and your team can answer with the right detail.

Yes. The cleaner your menu is, the easier it is for callers to get a fast answer. ROAL reads public pages, menu PDFs, menu photos, and uploaded menus, so the wording matters. If the kids menu is buried inside a long lunch menu, split it out if you can.

A good kids menu entry looks like this:

You do not need fancy language. Use plain item names and plain side choices. If a meal is only available at certain times, say so right on the menu.

For example, if you have three kids meals and each one comes with a side, make that obvious. If the caller can swap fries for applesauce, write that too. That saves time on the phone and reduces back-and-forth. ROAL can answer from the live menu, so the details should match what your kitchen actually serves.

A lot of kids menu calls are really pickup orders in disguise. The parent starts by asking about the kids meal, then adds one adult entree, one drink, and maybe a note like “no ketchup” or “extra napkins.” Your phone setup should make that easy.

Here is a practical flow:

1. Confirm the kids item.
2. Confirm the side.
3. Ask for any simple modifier, like plain or sauce on the side.
4. Collect the caller’s name and phone.
5. Quote the ready time.
6. Read the order back before sending it to the kitchen.

Example with numbers you can swap:

• Say a $10 kids meal
• Add a $16 adult entree
• Add a $3 drink
• Total example: $29 before tax and any local fees your restaurant already uses

That kind of call is a good fit for ROAL, because it can take items, sizes, modifiers, notes, name, phone, and ready time, then send a clean ticket to the kitchen screen. It does not take card numbers over the phone. Payment stays at pickup or wherever you already take it. For restaurants that get a lot of family calls, that can keep the line moving during dinner rush.

When the line is busy, the main goal is not to talk longer. The goal is to get the caller an answer and keep the phone from tying up your counter staff. That is where call forwarding and a phone host can help.

A simple busy-shift setup:

• Forward all calls when you are slammed, or only forward unanswered calls.
• Confirm the forwarding code with your carrier or phone system.
• Test it with one real call.
• Make sure someone can still see the ticket or callback if the caller has a special request.

For many carriers and plans, forwarding codes vary. Some lines use 72 to forward all calls and 73 to turn it off. Some mobile carriers use codes like *21number# for all calls, *61number# for unanswered calls, and *67number# for busy calls. Business VoIP systems usually let you set this in the portal. Always confirm with your carrier and test it.

ROAL gives each location its own phone line automatically after you claim the host, and you can forward your existing number to it or turn forwarding off any time. That makes it easier to keep answering questions like “Do you have a kids menu?” even when your team is in the weeds.

Before you lean on the phone, make sure the answers match what your kitchen can actually do. A caller with kids is usually in a hurry, so a wrong answer creates a headache fast.

Use this quick checklist:

• The kids menu is listed on your website or uploaded menu.
• Portion names are simple and readable.
• Sides are listed clearly.
• Any plain, mild, or sauce-on-the-side options are written down.
• Allergy questions have a staff handoff rule.
• Sold-out items are marked so they are not offered.

One useful habit is to keep a short FAQ for common phone questions. For example: “Do you have a kids menu?”, “Can I get plain pasta?”, and “Do the kids meals come with fries?” If your answers change seasonally, update them once and keep them consistent.

ROAL has a menu editor, call history with transcripts and recordings, and an inbox for questions it could not answer yet. That means you can answer a tricky kids menu question once, and the phone host learns it from then on. If you want to test the flow, you can Build a free test host from your website or menu file and call it right in the browser.