AI Phone Agent for Delis

At 12:05 on a Tuesday the deli phone stops being a customer. It is a foreman with eight names and a list: turkey on a hero, no onion, extra mayo; a chicken cutlet with provolone and hot peppers; two veggie wraps, one without tomato; and a half pound of Swiss, sliced thin, on the side.

That is one call. Eight sandwiches at $11 is $88, the largest ticket of the lunch hour, and it lands when the line at the counter is four deep.

Miss two of those calls a week and you are down $176, plus the platter that caller would have ordered later.

TL;DR

• A deli phone order is a stack of builds with names attached, and a ticket that flattens them into one list of ingredients is unusable.
• One lunch run of eight sandwiches at $11 is $88, the biggest ticket of the hour, and it arrives at 12:05 when nobody can answer.
• Kovo keeps each sandwich as its own build with its own name, reads the order back, and starts at $99 a month.
• Kovo sends an order up to the limit the shop sets, defaulting to 10 items and 8 of one item, so an eleven-sandwich crew order needs a raised limit or a person.
• By-the-pound items only exist for the agent if they exist in your menu, so the slicer list stays a counter conversation.

What a deli call actually is

Two things, and they are not the same order type.

A build. Bread, spread, protein, cheese, toppings, salt and pepper, oil and vinegar, cut in half or wrapped whole. Six decisions on one sandwich, and a caller changes three of them mid-sentence.

A weight. A half pound of coleslaw, three-quarters of Swiss, a pound of turkey sliced thin for a platter at home. There is no modifier menu for this. It is a scale and a price per pound.

Most delis handle both at the same register. The build needs structure; the weight needs a scale.

The failure that belongs to delis: the build that flattens

Here is the mistake that is specific to a sandwich shop. The voice sounds perfect, the order is complete, and the paper the counter gets is a paragraph.

"Turkey hero, no onion, extra mayo, chicken cutlet with provolone and hot peppers, two veggie wraps one no tomato." Four sandwiches, four builds, and one block of text. The counter now has to unspool the sentence at speed, guess which wrap has no tomato, and hope the crew does not care whose sandwich is whose.

A deli ticket has to keep the eater's name attached to the build. Eight sandwiches on one order is eight separate items, each labeled, each with its own modifiers. That is the structure the kitchen actually reads.

What the agent has to hear, per sandwich

• Bread. Hero, sub, ciabatta, wrap, a roll, or sliced rye. Your names, and the ones callers use for them.
• Build. Protein, cheese, and the three or four toppings that matter. "Everything on it" is a house rule, so write it down.
• Removals and additions. No onion, extra mayo, add avocado. Extra is a price, add is a price, and no onion is neither.
• The finish. Toasted, cut in half, oil and vinegar, salt and pepper, wrapped separately.
• The name. Who is eating it, and whether it goes on one check.

Then the read-back, sandwich by sandwich. Kovo reads the order back before it places it, which is the only point where a caller can catch a name attached to the wrong build.

By the pound is not a modifier

A caller asking for three-quarters of a pound of potato salad is not ordering a menu item with options. They are asking you to weigh something.

Kovo orders from the menu it imported, so a deli case sells by weight only if those items exist in the catalog with a price per half pound. If your POS menu is sandwiches and combos only, the agent has nothing to put that request into, and the honest outcome is a decline rather than a made-up price.

Two fixes, neither free. Put the case items in the menu you give the agent, quarter pound and half pound, priced. Or accept that the slicer stays a counter conversation and let the phone handle builds only. The menu sync mechanics explain what the daily pull does with either choice.

The 12:05 order, and the deli's rush hour

Every vertical has an hour it cannot answer the phone. Pizza's is 6:40 on a Friday. A deli's is 11:45 to 1:15, and it is not a spike in questions. It is a spike in builds.

During that window a phone call costs the counter more than a walk-in, because a call takes four minutes of a person who is already wrapping, and a walk-in takes ninety seconds that the line absorbs. So the phone is exactly the thing a busy deli drops first.

The QSR Magazine analysis of restaurant phone traffic estimates restaurants miss about 150 calls a month, worth $35 to $85 each, and that roughly 30–32% of calls go unanswered at the 5–8 p.m. peak. Move that window to lunch and it reads like a deli's Tuesday: the same share of calls missing, on the hour with the highest ticket count.

The arithmetic on a lunch run

Use your own numbers, because the national averages are somebody else's shop.

• 2 missed lunch calls a day × $88 a call = $176 a day.
• $176 × 5 days = $880 a week, if every one of those calls walked.

That second line is the honest one to doubt: not every missed call becomes a lost order, and a caller with a crew and a deadline often rings back. Cut it to a quarter and you are still at $220 a week.

Kovo Starter is $99 a month and Unlimited is $299. At the reduced figure the plan covers itself in a week of lunch.

The order limit and the lunch run

The limit belongs to the shop, and the defaults only apply to a deli that never opened the card: 10 items in total and 8 of one item. An owner can change either number, add an order-value limit, or set one to zero to remove it.

At a deli, the default bites in the middle of your most valuable order type. A crew lunch is eleven sandwiches, and a catering platter for twenty is past the defaults twice over. Eight sandwiches at $11 is $88, and that is fine: the count is the limit, and the value limit is a separate number you choose.

Above the limit, one of two things happens, and which one is up to you:

• With large-party routing on and a handset set, the call rings your counter.
• Otherwise the agent says the order is too large to send through, stays on the call, and keeps taking what fits.

What that means in practice:

• The agent handles the two-to-six sandwich order, which is most of the phone volume.
• Set the item limit for the crew order, or leave it and turn on large-party routing so it rings.
• Test the exact order your biggest account places. If it is declined, you learned that on a trial instead of on a Friday.

A shop that hears "we take every order" from a vendor should ask what that vendor's ceiling is, in dollars and in item counts, and who sets it.

Payment, and what the counter sees

Three paths, and a deli should pick by who is calling.

Pay at the counter. With cards off, the order is confirmed on the call and the caller pays at the register. That is how a deli already works, and the ticket and the payment stay where the staff can see both.

The account's card, charged on the line. A caller who paid by link last time has a card vaulted against a Stripe customer on the shop's own connected account, and the next call from that number can charge it off-session while the caller is still talking, so the ticket reaches the counter during the call. For a standing lunch account, that is the whole point.

A link for a first-time caller. Kovo texts a Stripe Checkout link and holds the line open while the caller pays, so the caller hears the payment land. There is a wait: nothing prints until the payment confirms, and a caller who ignores the link leaves the counter with nothing. Paying by link vaults the card, which turns the next call into the previous path.

No card number is spoken to the agent, recorded, transcribed, or sent to a model on any of the three, and the vaulted charge never exposes digits. The Loman comparison is where the line between a known card and any card is drawn.

The ticket goes to Toast, Square, Clover, Olo, or a receipt printer. The Toast ticket path walks through where the paper comes out, and the Square route covers the smaller register most delis run.

What a deli should test before signing

Four calls, on a live line, with your own menu.

• Three sandwiches, three names, one removal each. Check that each arrives labeled, not merged.
• An eleven-sandwich run. Confirm what your own limit does: prints, declines, or rings your handset.
• A half pound of something. See whether the agent prices it or says no.
• One plain order with cards on. Confirm the ticket waits for the link, and that a second call from the same number is charged without one.

If the third call is the one you care about, get the case into your menu before the trial.

Who a deli phone agent is wrong for

If your phone is mostly "are you open" and "do you deliver to the college," the answer is a better website and a recorded message, not an agent.

If the calls you actually lose are platters and corporate accounts, no phone agent fixes that under its limit. Those need a person who can quote, schedule, and invoice.

And if your whole menu lives at the counter and nowhere else, on a board the POS never learned, an agent has nothing to read. Fix the menu first. The missed-call math is worth a look either way.

FAQ

Final Thoughts

The decision is not whether a voice agent can say "no onion, extra mayo." Any of them can. The decision is whether the paper it prints lets the counter wrap eight sandwiches without asking a single question, and whether your menu is written down well enough for the agent to price what it sells.

If it is, Kovo takes the lunch builds, reads them back one at a time, and prints the ticket to Toast, Square, Clover, Olo, or a receipt printer, from $99 a month. If it is not, the sushi counter guide covers the same menu-first argument from a different room.

Take a test call with your own menu, no card, starting with the order your counter gets wrong at 12:05. Take a test call.