Most owners assume a custom cake call is too involved to hand to a phone agent. That assumption is half right, and the half that is wrong is the expensive one.
Closing a cake order on the phone is genuinely hard. Qualifying one is not, and qualification is where the calls are being lost. A caller who wants a birthday cake for Saturday and reaches a voicemail on Thursday afternoon has already started dialing the next shop by the time the beep finishes.
What a cake call actually contains
Sit with one for a minute. The caller wants a cake, but they have not decided the size, they are not sure about the flavor, they want writing on it and have not settled the wording, someone in the party has a nut allergy, and they are asking what it costs before any of that is fixed.
A person handles this by asking questions in an order that narrows the price. An agent can ask the same questions and record the same answers. What it cannot do is quote a price on a design that does not exist yet, and it should not pretend otherwise.
The split that works
Let the agent take the date, the pickup window, the size, the base flavor, the occasion, the allergen flags, and a confirmed callback number. Then have it say a person will call back within a stated period to finish the design and the price.
That call is now captured. The customer has been answered by something that knew your lead times and your calendar, and your decorator calls back at a moment of their choosing instead of being pulled off a piping bag. The handoff logic is worth configuring deliberately rather than accepting a default, and the reasoning is in human handoff and failover.
The same shape applies to any order where the price depends on a conversation, which is why this looks a lot like catering lead qualification.
Lead times are a policy, and policies are what these systems are good at
Your rule might be 48 hours for a standard round, 72 for anything tiered, a week for a sculpted cake, and nothing at all in the four days before Mother's Day. Everyone who works there knows the rule and half of them bend it, usually for a caller who sounded upset.
An agent applies it the same way every time. It will tell a caller on Thursday that Saturday is not available for a tiered cake, offer Sunday, and never negotiate. That consistency is worth more than it sounds, because the cost of a bent lead time is not the cake, it is the decorator staying until eleven and everything behind it slipping.
Configure the rule per category. A sheet cake and a three-tier do not share a deadline, and a single global lead time will either block orders you could have taken or accept ones you cannot make. Decide separately whether a human is allowed to override, and who.
Pickup windows, not pickup times
A caller who says "Saturday afternoon" has told you nothing your production schedule can use.
Windows solve this. Offer a set of blocks, cap each block at a number your decorators can finish, and let the agent book against those caps. When a block fills, it is gone, and the caller picks another one during the call rather than finding out at pickup that the cake is not ready.
The caps are the hard part and you have to set them yourself. Nobody else knows how many cakes your team finishes in an hour on a Saturday morning. Start low, watch two weekends, adjust. The general version of quoting rules is in quoting accurate pickup times, and the capacity math is in order throttling and kitchen capacity.
Say the deposit out loud
Dessert shops lose money on no-show custom orders more than almost any other format, because the product cannot be resold. A name cake for a party that never happens is waste, not inventory.
Whatever your deposit policy is, the agent should state it during the call, in dollars, before the order is treated as booked. A caller who hears "there is a fifty dollar deposit on custom cakes, and someone will call you shortly to take it" is not surprised later, and the shops that skip this step spend real time arguing at the counter.
Collecting the deposit is a separate decision. Many shops route payment to a person or a payment link rather than taking card details by voice, and the handling questions around that are covered in collecting payment over the phone safely and in deposits for large catering orders. Read those before you switch anything on, not after.
Holidays are their own configuration
Mother's Day, Valentine's Day, and the week before Christmas will generate more cake calls than the rest of that month put together, and your normal rules will fail during all three.
Treat each as a separate schedule with its own lead times, its own pickup blocks, and its own caps, set before the season starts. A system running your ordinary Tuesday configuration into Mother's Day weekend will book past your capacity by Friday morning, and unwinding that is a day of apology calls. The mechanics are in holiday hours and overrides and the broader seasonal pattern is in the holiday rush playbook.
Allergen questions spike in the same weeks, because a party has more people in it than a walk-in purchase. Decide what the agent is permitted to say. The safe configuration is that it reads your stated ingredient information and routes anything beyond that to a person, and the reasoning is in allergen and dietary questions.
Count minutes, not calls
The usual way to size this decision is to count inbound calls, and for a dessert shop that measure is misleading.
Cake calls are long. A shop taking twenty calls a day can burn more staff time on the phone than a pizza counter taking sixty, because each conversation runs several minutes and lands on whoever is decorating. So count minutes during your busiest weekend instead, and count how many of those minutes came out of production rather than out of a slow moment.
X1 Voice connects directly to Square, Clover and OrderCounter, and reaches Toast, Lightspeed, TouchBistro, SpotOn, Aloha, Revel, PAR Brink and Micros through Deliverect. Plans start at $250 a month and setup is typically under 24 hours, though for a shop with a custom-order flow the configuration decisions above take longer than the connection does. The closely related version of this problem is in voice AI for bakeries.
If your Saturday phone minutes are coming out of decorating hours, and if you have ever discovered a booked cake nobody could make, the fix is a booking policy your phone can enforce. The agent is how you enforce it, and the policy is still yours to write.