AI Phone Agent for Bakeries

The call that matters at a bakery rarely arrives in front of you. It comes on a Wednesday afternoon: a half sheet, white cake, raspberry filling, buttercream, "Happy Birthday, Nora" in pink, picked up Saturday at two.

That order is worth several mornings of coffee: $60 to $90 for a decorated half sheet, against $9 for a latte and a croissant. It also needs three things nobody at the counter can give at 8 a.m.: a lead time, a deposit, and a slot on the decorator's bench.

Two missed cake calls a week at $65 is $130 a week, about $520 a month.

TL;DR

• A bakery phone call is usually a pre-order, which is a date and a lead time before it is a cake.
• Two missed cake calls a week at $65 is $130 a week, roughly $520 a month, hidden in the morning rush.
• Kovo takes the pre-order, reads the size, filling, writing, and pickup time back, from $99 a month.
• Kovo's limit is the shop's own, defaulting to 10 items in total and 8 of one item. A decorated half sheet is one item, so it clears the cap; the deposit conversation is what still needs a person.
• The case sells out at 10:40 and the POS never learns it. Sold out is a toggle in Kovo's menu board, and Square or Clover availability survives the pull.

A bakery phone is two lines wearing one number

There is the case line and the pre-order book, and they behave nothing alike.

The case line is 40 seconds: is there rye left, how much is the quiche, a box of six. Half the time the answer is "we're out."

The pre-order book is four to six minutes: a size, a sponge, a filling, a frosting, a message, a writing color, a pickup date and window. It is worth eight to ten times a case ticket, and it has a deadline the case line never has.

An agent built for the case line will confirm a date your bench cannot hit.

Lead time is the order, not the cake

Here is the failure that belongs to bakeries specifically: the double-booked bench.

An agent can take three Saturday custom cakes in one Thursday afternoon and stay faithful to every word the caller said. The shop still rings two of those callers back on Friday, because fondant takes two days, buttercream takes one, and the decorator goes home at noon on Saturday.

Nothing in the call tells an agent that. A kitchen absorbs a surprise pizza. A bench cannot absorb a surprise hundred-layer cake.

What the agent can and cannot know

Kovo answers from first-party knowledge: your site, your menu, your FAQs, your hours. If your site says custom cakes need 48 hours, it says 48 hours, every time. If your site says nothing, it takes whatever date the caller asked for and hands you a ticket to fix.

What it does not have is a production calendar. It cannot see that Saturday is full, and it does not reserve a bench slot when it takes an order.

The workaround that holds

Write the rule into the words the agent reads. "Custom cakes: 48 hours notice, call for wedding cakes," in your site copy and in the FAQ text you hand over, not only on a chalkboard by the register.

Then decide what happens to the caller who wants Saturday anyway. Kovo hands off to a person when the caller presses 0, clearly asks for one, or the order is over a limit you chose to route, and only if you have set a handset number, so say so where callers will hear it. A bakery selling six or more custom cakes a week should keep those on a human.

The case empties before the POS finds out

A bakery menu in a POS is a catalog, not an inventory.

At 10:40 the last almond croissant goes into a box, the tray is bare, and nothing in the system records it. The cashier writes it on the sold-out board. A phone agent reading the menu will take six of them at 11:05, and the caller arrives at 11:20 to a tray of crumbs.

Kovo pulls the menu once a day, and the call path only refreshes when the menu is two days old. Sold out is an owner toggle in Kovo's menu board: your 86 outranks a source that still says available, a restock brings the item back, and a Square or Clover shop carries its own flags through the pull.

When the tray empties, toggle it before you go back to the register. What the toggle does not cover is a sold-out choice — the six-inch that went first is still offered as a size — so check that case yourself. The menu sync mechanics cover the merge rules.

What the agent has to hear on a cake call

Five things, and the read-back is the sixth.

• The size. Six-inch round, quarter sheet, half sheet, three dozen cupcakes. Your names, not a vendor's.
• The build. Sponge, filling, frosting. "Chocolate, raspberry, buttercream" is three choices, not a sentence.
• The writing. Message, color, spelling. Nobody wants to correct a name at pickup with the cake already boxed.
• The date and window. Saturday between one and three, not "Saturday."
• The thing you cannot screen. Allergy questions. Kovo reads your own allergen note back with a disclaimer and tells the caller to confirm with the kitchen; it never says a dish is safe.

Then the agent reads the whole order back before it is placed: one half sheet, white cake, raspberry, buttercream, pink writing, Saturday at two. A caller who hears the wrong filling can fix it before anything prints.

Kovo keeps nested choice groups, so a sheet cake opens its own size, filling, and writing fields instead of collapsing into one notes field. The pizzeria guide makes the same argument about half-and-half pies: structure survives, or the ticket is wrong.

The arithmetic, on your own pre-order book

Count the cake calls you did not pick up last month. Ring-outs, hang-ups, the ones where a voice said the box was full. Call it six.

• 6 cakes × $65 average half sheet = $390 a week.
• $390 × 4 weeks = $1,560 a month.

Kovo Starter is $99 and Unlimited is $299. At a third of that lost volume, the plan covers itself on cakes alone, before you count pastries.

For scale: a QSR Magazine analysis of restaurant phone traffic estimates the category loses about $20 billion a year to unanswered calls, with the average shop near 150 missed calls a month at $35 to $85 each.

Your number is different, and this is where bakery pages go wrong. The wall is not 7 p.m. It is 7 to 9 a.m., when the rack is coming out and two people are boxing twelve orders. Industry estimates put 30–32% of calls unanswered at the evening peak; at a bakery that lands on the hour with the highest ticket count of the day.

The order cap and the tiered cake

The limit belongs to the shop: defaults of 10 items in total and 8 of one item, either one editable, an optional value limit, and any of them can be set to zero. Above a limit the call rings your handset if you enabled large-party routing, and otherwise the agent says the order is too large and keeps taking what fits.

For a pizzeria that rule catches the Friday party order. For a bakery the shape is different: a tiered cake is one item, so the cap never touches it. What stops a wedding cake is not the cap but the work around it, a lead time and a deposit and a conversation nobody wants to have with a voice agent. The default catches the ordinary box order instead: a dozen pastries plus four coffees is 16 items.

• Keep a person on tiered and wedding work. Do not buy a phone agent expecting it to book a $400 cake.
• Ask what a dozen counts as. Whether "dozen scones" is one menu item or twelve of one item decides whether a standing Friday order goes through, and that depends on how your menu is built.

Say so in the greeting, too, so a caller with a four-tier order asks for a person early.

Payment, and the deposit a bakery actually needs

Most bakeries should start with cards off. The order is confirmed on the call and the caller pays when they collect. A $22 box of pastries does not need a payment step.

With cards on, a caller the shop already holds a card for is charged off-session while they are still on the line, and the ticket reaches the kitchen during the call. A first-time caller gets a Stripe Checkout link by text with the line held open, and paying it vaults the card. Either way no card number reaches the call, the recording, the transcript, or the model. The tradeoff is honest: a first-time caller has to tap a link. The Loman comparison sets that beside a vendor that captures any card in the call.

There is no deposit step in the call: a charge is the order total, paid once, before the ticket prints. Custom work that needs $20 down still collects it at the counter, so say that in the FAQ text the agent reads.

Who a bakery phone agent is wrong for

If your phone is mostly "are you open" and "do you have any left," you need your hours at the top of the site and a board people can read from the door, not an agent.

If pre-orders already come through a web form and an Instagram inbox, on time, the phone is not the bottleneck.

And if custom work is the business, six wedding cakes a week with tastings and sketches, a person beats any voice on the market. The missed-call math is worth reading either way, because it is arithmetic instead of opinion.

FAQ

Final Thoughts

The decision is not whether a voice agent can read back a half sheet. The decision is which half of your phone you hand over: the case line, where the failure is "we're out," or the pre-order book, where the failure is a date nobody can bake.

Most bakeries should start with the first and keep the second on a human until the rules are written down. Kovo reads your menu, takes the case order, reads it back, and prints the ticket to Toast, Square, Clover, Olo, or a receipt printer. The Toast ticket path shows where the paper comes out.

Try it for 14 days, no card, and call in the order your counter gets wrong on a Saturday. Take a test call with your own menu.