Where cake enquiries die: the gaps between message and order

Ask a cake maker why they lost an order and the answer is usually price. Look at the actual conversations and the picture is different: a large share never got far enough to discuss price. Somebody asked on a Saturday and got an answer on Tuesday. A quote was sent and never followed up. A deposit was requested and nobody chased it.

Those are not selling problems. They are gaps in a process that does not exist, and each one is visible and fixable if you know where to look.

What we'll cover

• Enquiries die in four places
• The reply that came too late
• The quote nobody followed up
• Building it with CodeWords
• The deposit that was never chased
• The enquiry for a date you were full
• Seeing the pipeline at all
• What is not worth chasing
• The enquiries you want more of
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

Enquiries die in four places

Before a reply, which is the largest and the most avoidable.

After a quote, where nothing happened next.

After a deposit request, where the customer meant to pay and did not.

On a date you could not do, where the conversation ended rather than moving.

Almost none die on price once a conversation is actually had, which is the finding most cake makers are surprised by.

Count yours for a month, by where it stopped, and the shape of the problem becomes obvious.

The reply that came too late

Enquiries arrive when people are thinking about the event, which is evenings and weekends.

You are baking then, which is the whole difficulty.

They message three bakers, and the first useful reply frequently wins regardless of price.

An acknowledgement is not a reply and is still worth sending, because it stops them assuming you are unavailable.

Say when you will answer properly, which converts waiting into expectation.

Answer the easy ones immediately: whether you have the date, roughly what something costs, whether you do that style.

The quote nobody followed up

Quotes go out and vanish, and the customer is frequently still deciding rather than declining.

One follow-up converts a meaningful share, and most cake makers send none.

Time it to their decision, not yours — a few days after quoting, well before the date.

Ask something rather than repeating the quote: whether they have questions, whether the date is still right.

One is enough. A second and third reads as pressure on a personal channel and costs goodwill.

Record the outcome either way, since a no is information and an unanswered quote is a question.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: what happens on an enquiry, after a quote, and after a deposit request.
3. Authorize the connections to wherever orders are recorded and your WhatsApp Business Platform account.
4. Describe the exceptions: a date you cannot do, a customer who declined, a quote already accepted, somebody who asked not to be messaged.
5. Run it over last month's enquiries and see where each one stopped.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

The deposit that was never chased

A requested deposit is not a confirmed order, and treating it as one is how a date is held for nobody.

Customers forget, genuinely, particularly when the event is months away.

Give it a deadline — the date is held until then — which is fair and makes chasing unnecessary.

One reminder before the deadline, with the payment link in it.

Release the date when it passes, and tell them, which occasionally produces the payment.

Make paying trivial, since a deposit requiring a bank transfer from a customer at work is a deposit that waits.

The enquiry for a date you were full

This is a real order you turned away, and most cake makers treat it as nothing.

Ask whether the date is flexible, since for some occasions it is.

Offer the nearest date you have, specifically rather than in general.

Keep the enquiry rather than discarding it, since cancellations happen and this is the list to call.

Tell them if the date frees up, which occasionally recovers the whole order.

Refer them on when you genuinely cannot help, which costs nothing and is remembered.

Seeing the pipeline at all

Most cake businesses cannot answer how many enquiries they had last month.

Four states is enough: enquired, quoted, deposit requested, confirmed.

Anything that has not moved in a week is the list to work.

A number beside each state turns an impression into a decision about where the problem is.

It does not need software, though it does need to live somewhere other than a chat thread.

This is the whole article in one habit, and it is the one that makes everything above visible.

What is not worth chasing

Somebody who said no, which should be recorded and left alone.

A price-shopper asking only for a figure, who is comparing and will return if they want to.

An enquiry for something you do not do, which is not yours to convert.

Anybody who asked not to be messaged, obviously and permanently.

A date long past, which should be closed rather than left open in the list.

Chasing everything costs goodwill, and this trade runs on recommendation more than most.

The enquiries you want more of

Improving conversion is one half. The other is that not all enquiries are worth the same, and most cake makers do not know which of theirs are.

Record where each came from — Instagram, a recommendation, a wedding fair, the website — which takes one field and almost nobody does.

Recommendations convert far better than anything else in this trade, and knowing that changes where effort goes.

Note what converted, not just what arrived, since a source producing volume and no orders is costing you replies.

Watch the enquiries you turned down for a pattern — a style, a budget, a date range — which is information about positioning.

Ask how they found you in the brief, which is one question and is answered honestly.

Review it quarterly, since the mix shifts and effort tends to stay where it was two years ago.

Making it survive

Record the state outside the conversation, or none of this works.

Check the state before any follow-up, since the customer may have paid or cancelled.

Send follow-ups inside the service window where possible, since a template costs money and reads more formally.

Cap the chasing at one per stage.

Report the outcome: enquiries by state, conversion at each step, and where they stop most.

Limits worth knowing about

A faster reply does not fix a price problem, though it reveals whether you have one.

Seasonal peaks change everything, and December enquiries behave differently.

Some enquiries were never real, which is normal in every business.

Following up costs a message on a channel where messages are noticed.

Automation does not make a cake, and capacity is the real ceiling for most of this trade.

What to build first

The acknowledgement with a stated response time. It takes an afternoon, it addresses the largest of the four gaps, and it stops the customer who messaged three bakers on Saturday evening from concluding you are unavailable before you have read it.

Two habits make the difference. Send one follow-up after every quote, timed to their decision rather than your convenience, since most cake makers send none and the customer is usually still deciding rather than declining. And give every deposit request a deadline with the date held until then, because that single sentence converts chasing into an expectation the customer manages themselves.

Frequently asked questions

Where are cake orders actually lost?

Before a reply, after a quote with no follow-up, after a deposit request nobody chased, and on a date you could not do. Very few are lost on price once a conversation is genuinely had.

Why does reply speed matter so much?

Because enquiries arrive in evenings and at weekends when you are baking, and customers message several bakers. The first useful reply frequently wins regardless of price.

Should I follow up on quotes?

Once, timed a few days after quoting and well before the date, asking a question rather than repeating the price. Most cake makers send none, and the customer is usually still deciding rather than declining.

How many follow-ups is too many?

More than one per stage. A second and third reads as pressure on a personal channel and costs goodwill in a trade that runs on recommendation.

How should deposits be handled?

With a deadline — the date is held until then — one reminder before it with the payment link, and the date released afterwards with a message. That makes chasing largely unnecessary.

What about enquiries for dates I am already full?

Ask whether the date is flexible, offer the nearest you have specifically, and keep the enquiry rather than discarding it. Cancellations happen, and that is the list to call.

What is the minimum pipeline I need?

Four states — enquired, quoted, deposit requested, confirmed — with anything that has not moved in a week as the list to work. It does not need software, but it does need to live somewhere other than a chat thread.

What should I not chase?

Anybody who said no, price-shoppers comparing figures, enquiries for work you do not do, anybody who asked not to be messaged, and dates long past.

Should I track where enquiries come from?

Yes, and it takes one question in the brief. Recommendations convert far better than anything else in this trade, and a source producing volume without orders is costing you replies rather than earning them.

What do declined enquiries tell me?

Look for the pattern — a style, a budget band, a date range. Repeated declines of the same kind are information about positioning rather than a series of unrelated nos.

Related reading

• Taking custom cake orders over WhatsApp
• Collecting bakery deposits and payments
• WhatsApp or Instagram DMs for bakery orders