Office lunch catering orders by phone

Start with the details that save you time later. The goal is to find out who the order is for, when it is needed, and how it is getting to the office.

A simple script line works well:

"Thanks for calling. Is this for pickup or delivery, and what time do you need it ready?"

Then collect the basics in the same order every time:

1. Office name and contact name
2. Call-back phone number
3. Pickup or delivery
4. Ready time or delivery time
5. Headcount or number of trays
6. Menu items, sizes, modifiers, and notes
7. Floor, suite, gate code, or parking instructions if needed

For office lunch, the details matter. A deli platter for 12, a pizza mix for 18, or boxed lunches for 25 all need different kitchen timing. If you use ROAL, it can collect items, sizes, modifiers, and notes from your live menu, then confirm the order back before it sends the ticket. That gives staff less guessing and fewer callbacks.

Office callers often want speed. They may be ordering for a team meeting, a sales lunch, or a last-minute office celebration. A short, calm flow helps.

Use a three-step pattern:

• Ask what they need
• Confirm timing and contact info
• Repeat the order back

Example phone line:

"I can take that now. What time do you need it ready, and how many people are we feeding?"

If the caller starts listing items fast, do not try to memorize everything. Break it into chunks:

• First course or mains
• Sides and drinks
• Special instructions
• Payment timing, if your shop already handles it at pickup or on delivery

Here is a worked example you can copy and swap for your own numbers. Say the office needs 8 sandwiches, 2 salads, and 4 drinks. If your average lunch order is $28, a 4-person office order might be small, while a 12-person office order can add up quickly. The exact total depends on your menu, so plug in your own prices and portions. The point is to confirm the count early so the kitchen can plan the pack-out.

A clean ticket is what keeps the kitchen moving. The person on the phone may be busy, distracted, or calling from a noisy office, so the ticket should carry the key details in plain language.

A useful ticket format includes:

That is the kind of structure staff can read fast during lunch rush. ROAL sends a clean ticket to the kitchen screen, and the dashboard also keeps call history with transcripts and recordings. If you need to review an office order later, you can check exactly what was said.

For more on ticket clarity, see what a clean phone order ticket looks like.

Not every office lunch order should stay on the phone host alone. Some calls need a person to step in.

ROAL is designed to hand catering, complaints, allergy-sensitive questions, and manager requests to staff with a summary. That matters for office lunch because callers may ask things like:

• Can you make 20 boxed lunches for Thursday?
• Which items are safe for someone with a food allergy?
• Can you do a custom platter for our office meeting?

A safe handoff line sounds like this:

"I can get a team member for that request and pass along the details."

For allergy-sensitive calls, keep the wording careful and direct. Do not guess. Do not promise what you have not checked. The phone host should gather the request and send it to staff, not try to improvise.

If the caller asks for a manager, treat it the same way. Collect the office name, callback number, and the issue in one pass, then hand it off with a short summary so your team is not starting from scratch. That is better than losing the thread during lunch service.

Before lunch rush, make sure your call flow is simple. Many restaurants forward their existing number to a phone line so the restaurant keeps its own number while calls are routed where they should go.

Basic steps:

1. Confirm how your carrier or phone system handles forwarding.
2. Choose whether to forward all calls or only busy and unanswered calls.
3. Test the setup with a real call.
4. Make sure your staff knows where office orders are landing.

Codes vary by carrier and plan, but many landlines and some carriers use 72 to forward all calls and 73 to turn it off. On some GSM mobile carriers, *21number# forwards all calls and ##21# turns it off; *61number# forwards unanswered calls and *67number# forwards busy calls. Verizon Wireless often uses 72 / 73, and *71 for busy/no-answer forwarding. Business VoIP systems usually let you set forwarding in the web portal. Always confirm with your carrier and test with a call.

If you want a handy reference, use call forwarding codes by carrier.

ROAL is built for restaurants that need the phone to work during lunch, not just ring. It answers the restaurant's phone, takes pickup and delivery orders from the live menu, answers questions about hours, address, parking, and the menu, and sends a clean ticket to the kitchen screen.

For office lunch orders, that means the phone host can:

• Speak the caller’s language
• Take items, sizes, modifiers, and notes
• Collect the caller’s name and phone
• Quote a ready time
• Confirm the order back before sending it through

It also skips sold-out items, which helps avoid awkward calls back to the office. And it never takes card numbers over the phone. Payment happens at pickup or however your restaurant already handles it.

Setup is simple. The owner pastes the restaurant website, Google Maps link, or "Name, City" at /try. ROAL reads public menu, price, hours, and address pages and builds a phone host in about two minutes. Owners can test-call it right in the browser with no sign-up needed. Once it is live, each location gets its own phone line automatically, and the restaurant can forward its existing number to it.

If you want the pricing details, see Pricing.

The call is only half the job. The other half is what happens before the food leaves the kitchen.

Use a short checklist for office lunch orders:

• Check the kitchen screen for the order status
• Confirm the ready time against your prep pace
• Pack utensils, napkins, sauces, and drinks if your order includes them
• Label platters or bags clearly
• Add delivery instructions or pickup notes for the driver or front counter

If you are short-staffed, a phone host can help your team stay on task during the lunch rush. The dashboard also gives you live tickets with statuses like new, preparing, and ready, plus call history, transcripts, a menu editor, hours, FAQs, upsell suggestions, and multi-location menus.

A practical example: say an office places a $96 lunch order for 6 people at 11:20 AM and wants it at 12:15 PM. Your kitchen can see the ticket early, set the order in motion, and check the timing against the rest of the rush. That is easier than re-listening to a voicemail or trying to decode handwritten notes. If you want a broader view of phone handling for busy shifts, see short-staffed shifts.

Keep the process short enough that a new staff member can follow it on a busy day. Here is a practical version you can post by the phone.

1. Answer with your normal greeting.
2. Ask whether the caller wants pickup, delivery, or catering.
3. Get the office name, callback number, and ready time.
4. Take the order in menu order, item by item.
5. Repeat the full order back.
6. Send it to the kitchen or hand it to staff if it needs review.

A good opener is:

"Thanks for calling. I can help with a lunch order. What time do you need it ready?"

That simple line keeps the call moving and gives the caller confidence that someone is paying attention. If your team wants a test run, you can build a free test host from your website, menu, or Google Maps link and see how it sounds before you forward calls.

ROAL was built by Venkata Vamsi in Jersey City, NJ, and it works for any US restaurant, not just the first locations in Jersey City and Hoboken. It is a practical fit for restaurants that want phone orders to feel organized during the lunch rush.