Your Menu on the Phone, Not Last Month's
A caller hears whatever menu the phone was handed. How it stays current, what arrives 48 hours late, and the dish that comes back from a dead page.
On this page
A caller asks whether the short rib is still on. It came off in March, when your supplier stopped carrying it, and nobody has touched that page since.
The phone offers it back. The caller drives over, and the pass has to say no.
That is the whole risk in putting your menu on a phone: whatever the phone was handed, it reads out with total confidence, at 7:40 on a Friday, to someone who is already hungry.
TL;DR:
- A phone that answers 300 calls a month reads your menu 300 times, so one stale dish is not one wrong answer. It is every answer until the menu changes.
- An edit you make on your menu board shows up immediately; a price changed at your POS lands at the next daily read.
- The copy the phone works from can be up to 48 hours behind the source, which at 30 calls a day is a day and a half of quoting the old menu.
- Your 86 wins over a source that still says available, and a restock brings the dish back.
- Kovo re-reads your menu every day, keeps your edits, and a dish you deleted stays deleted, for $99 a month.
Your menu is a set of permissions, not a list
A menu is not a list of dishes. It is what your kitchen will build today, at what price, with which choices attached, and what it will refuse.
None of that costs you anything while a person answers the phone. Someone who has been on since four knows the short rib is gone, that the fryer is backed up, and that a large goes in a different box. The phone only knows what it was handed.
So the part of a phone agent that decides whether it works is not the voice. It is where your menu comes from, and how that menu keeps up with the kitchen.
The two clocks your menu runs on
You have two versions of your menu, and they are not the same document.
The first is the board. When you fix a price at 9:40 in the morning because the cheese rep put his up, the board shows it before you put the phone down, because that is your edit on your copy.
The second is the read. Your POS catalog, or the ordering page your listings already point at, is read once a day in the background. A change made over there lands at the next read. On a call, the phone only goes back to the source when its copy is two days old, so nobody on the line waits for a vendor's page to load.
One honest sentence comes out of that: your edit is instant, a change at the source waits for the next read, and a caller can hear a menu that is up to 48 hours behind.
Most owners shrug at 48 hours. Do the multiplication. At 30 calls a day, with one caller in five asking about a specific dish, that is six dish-specific answers daily and a dozen chances over two days to quote a price your kitchen will not honor. A wrong price you can eat at the counter. A dish that does not exist is a wasted trip, a refund, and a table that spends its Friday somewhere else.
The difference shows up in week two
The gap between a menu somebody imported once and a menu sync that keeps itself current appears in the second week, when you have fixed the same three item names twice.
Four things have to be true, and you can test all four:
- Your edit stays. You rename the chicken parm and the next read does not undo it.
- Their change lands. The source raises a price or adds a choice group, and it shows up without you retyping 80 items.
- Their deletion deletes. They stop carrying the short rib, and it comes off your menu.
- Your deletion stays deleted. You took it off in March, and June does not put it back.
That last one is the one that gets skipped, because the easy version of this is to wipe your copy and write the source's copy over the top. It passes every demo. Then the first read after you clean up the menu puts everything back, and you stop cleaning up the menu.
The dish that comes back
A stale price is quiet. The caller pays what you quoted, the ticket matches, and nobody learns.
A resurrection is loud. You pulled the short rib in March. In June a read finds it still sitting on a page nobody cleaned up, a caller orders it at 6:20 on a Friday, and your pass has to say no. The kitchen refuses something the phone offered with confidence. The cost there is not the ticket. It is the trip, the refund, and the neighbor who is told the short rib is off anyway.
The same problem runs the other way with the 86, and that one is yours to control.
| What you do | What the phone does on the next call |
|---|---|
| Flip sold out on your menu board | Stops offering it, even if the source still says available |
| Restock it | Offers it again |
| Let one size sell out instead of the dish | Still offers that size, so mark the dish |
When the caller says it their own way
A menu that keeps up perfectly and is read back badly still fails you, because nobody orders in item numbers.
They say "a large, half pepperoni, half mushroom, extra crispy, cut in squares". They say "the spicy tuna roll, no cucumber". They name a size three ways, then ask whether the combo comes with a drink. Half of that is a dish, and half is a structure.
The structure is where a flattened menu breaks. A nested choice group, where each half of a pizza opens its own toppings, cannot live in a note field. Your kitchen builds two modifier paths; it cannot build a paragraph at 8:15. The pizzeria guide puts that order through its paces, and the Toast walkthrough shows what the finished ticket looks like when the structure survives the trip.
There is a price wrinkle too. A marketplace menu usually carries a markup your in-store menu does not, so a phone reading a delivery page quotes delivery prices to someone who is picking up. Check the markup before the phone answers for you.
What Kovo does with your menu
One source per shop, picked once: your POS catalog, the ordering page your listing already returns, or a link you paste in. That is Toast, Square, Clover, Olo, DoorDash, Uber Eats, Clover online ordering, or Slice.
From there it reads your menu once a day in the background. Your edits on the board survive the read, the source's other changes land, a source deletion deletes, and a deletion you made stays deleted. Nested choice groups are kept, including half-and-half, where each half opens its own groups. A menu imported from a marketplace page can carry a markup percent, so a pickup caller hears your price and not theirs.
The pricing plans cover minutes and what a subscription includes. Kovo is $99 a month for 750 connected minutes, which is roughly 300 calls and about one shift's wage at the counter. This page is only about your menu.
Six things to try with your own menu
Half an hour on a trial tells you more than any feature list. Run these in order.
- Count. Import your menu, then count categories, dishes, and prices against the source, because the first number that disagrees is your answer.
- Rename a dish. Change one name on the board, wait for the read, and check that your name survived.
- Change a modifier at the source. Add or rename a choice group in your POS, then check it lands on the right dish.
- Delete one on the board. Take a dish off, let it read twice, and confirm it does not come back.
- Delete one at the source. Pull a dish in the POS and confirm the phone stops offering it.
- Order the hard thing. Call in a half-and-half with a doneness instruction, then read the kitchen ticket rather than the transcript.
A menu that passes one through five and fails six is clean data about an order your kitchen cannot build. That is still a fail.
When a menu on the phone does not matter
If your calls are mostly "are you open" and "do you deliver to 112th", your menu is not the problem, and your hours plus your website will do the job.
If you keep six dishes and you answer the phone yourself, nothing on a phone beats you.
If the menu changes daily on a chalkboard, an imported catalog is wrong by design, and the honest setup is a short list you keep by hand.
And no read fixes a source that is already wrong. If your POS says $14 and the printed menu says $16, the phone will quote $14 with total confidence. The blog has the rest of the guides.
FAQ
How often does the menu on the phone get updated?
Once a day is enough for most shops. Kovo re-reads your menu in the background every day and only goes back to your POS or ordering page when its copy is two days old, so a caller never waits on a vendor's page. If you change a price yourself on the menu board, that shows up immediately, because it is your edit on your copy.
Why did an item I deleted come back?
Because the refresh reads the source, and the source still has the item on it. The easy version of this wipes your copy and writes the source's copy over the top, so the first read after you clean up the menu puts everything back. Kovo remembers that you deleted it, and the dish stays gone until the source drops it or you add it back.
Can I 86 something in the middle of service?
Yes, and you should. Sold out is a switch on your menu board: flip it when the short rib goes and the phone stops offering it on the next call, even if your POS still says available. A restock brings it back. The one gap is a size inside a choice group. If the large sold out and the small did not, mark the dish, because the phone still offers the size.
What is the difference between an import and a menu that keeps up?
An import happens once and leaves you a copy. A menu that keeps up is read again on a schedule and merged, so a price change or a new choice group lands without anyone retyping 80 items. The test is the second week: if you are fixing the same three item names every Monday, you bought an import.
Can two locations share one menu?
Not on one Kovo subscription. One subscription covers one store, so a second location is a second line, a second number, a second menu, and a second subscription, and none of it is pooled. A group with three shops that share most of a menu keeps three menus, which is also what your POS does.
Final Thoughts
The voice is the part you notice on a demo. Your menu is the part that decides whether the hundredth call of the week is right, and it comes down to one question: when you and the source disagree, who wins, and does the thing remember that taking a dish off was a decision.
Try it with your own menu, in the order above. Kovo reads once a day, keeps your edits, keeps your deletions dead, and never makes a caller wait on a vendor's page. Two weeks free and no card is long enough to watch a read land and a deleted dish stay gone. Take a test call.