Taking custom cake orders over WhatsApp: getting the brief once

A custom cake enquiry rarely arrives as an order. It arrives as "do you do unicorn cakes", followed two hours later by a date, followed the next morning by a photograph from somewhere else, followed by a question about whether it can be gluten free. By the time you have a specification you have sent fifteen messages and you are still not certain what they want.

The fix is not a form — people abandon those on this channel. It is knowing which handful of things must be established before anything can be quoted, and asking for them in an order that matches how somebody actually decides.

What we'll cover

• Why it takes fifteen messages
• What the brief has to establish
• Allergens are part of the brief
• Building it with CodeWords
• The order to ask in
• Reference images and expectations
• Quoting from a brief
• Confirming what was agreed
• Saying no to an enquiry
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

Why it takes fifteen messages

The customer does not know what you need, and has no reason to.

They are deciding while they message, so the answer changes as the conversation goes.

Questions arrive one at a time from your side too, because each answer prompts the next.

Photographs come later, usually after the price has been discussed, and change everything.

Nobody is tracking what has been established, so the same thing gets asked twice.

It is not a customer problem. The exchange has no shape, and giving it one is your job rather than theirs.

What the brief has to establish

The date, first, because it determines whether anything else matters.

Servings or size, which customers express as "for about thirty people" rather than in tiers.

The occasion, which tells you more about the design than a description will.

Flavour, including whether they have a preference at all.

Allergens and dietary requirements, which are not an afterthought.

Collection or delivery, which affects price, structure and timing.

That is six things. Everything else is design conversation, and design conversation is what you are good at.

Allergens are part of the brief

Ask directly, early, rather than waiting for the customer to raise it.

A made-to-order cake and a boxed one sold from a counter fall under different labelling regimes in several jurisdictions, and which one you are making determines what you must provide.

In the UK, prepacked for direct sale food requires a full ingredient list with the major allergens emphasised, and cakes made to a customer's order are generally not in that category — but allergen information must still be provided on request.

Decoration counts, not just the sponge, which is the detail most often missed.

Cross-contamination is a real answer. If you cannot guarantee a kitchen free of something, say so plainly rather than agreeing.

Check your own position with your local food safety authority, since the rules differ by country and by how the item is sold.

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 the brief must establish, in what order, and what reaches you.
3. Authorize the connections to wherever orders are recorded and your WhatsApp Business Platform account.
4. Describe the exceptions: a date you cannot do, an allergen you cannot accommodate, a design question, an order below your minimum.
5. Run it against a fortnight of past enquiries and see how many would have reached a brief.

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 order to ask in

Date first, since a date you cannot do ends the conversation kindly and immediately.

Then size, because it is the largest driver of price and they can answer it.

Then allergens, before design, since they constrain what is possible.

Then the occasion and the look, which is where the conversation becomes enjoyable for both of you.

One question per message, since two in one message gets one answer.

Stop when you can quote. Further questions before a price is agreed are questions about a cake that may not be ordered.

Reference images and expectations

Ask for one early, since it establishes more than any description.

A photograph of somebody else's cake is a starting point, not a specification, and saying so early prevents the difficult conversation later.

Say what you will do differently and why, which sets the expectation while they are still deciding.

Attach the image to the order, so it is with the brief rather than scrolling in a thread on the morning you are baking.

Watch for the image that arrives after quoting, which frequently changes the price and needs saying.

Be honest about what you do not do. A style that is not yours is a disappointed customer however well you execute it.

Quoting from a brief

Quote once, from the six things, rather than piecemeal as details emerge.

Say what is included, since "a two-tier cake" means different things to you and to them.

Say what would change it — extra tiers, sugar flowers, a board, delivery — so a later change is expected rather than a surprise.

Give the quote a validity period, which is both normal and prevents an enquiry resurfacing at last year's price.

Say what happens next, specifically, which is what converts a quote into an order.

Do not negotiate in fragments. A price discussed across nine messages ends lower than one stated clearly.

Confirming what was agreed

Write it back: date, size, flavour, allergens, design summary, collection or delivery, price, deposit.

In one message, which is the record both of you will refer to.

Ask them to confirm, which catches the misunderstanding while it is cheap.

Put it somewhere other than the thread, since a thread is not an order book.

Any change after this is a change, which is easier to say when there is a confirmed version to point at.

This single message prevents most disputes, which is the argument for doing it even when you are busy.

Saying no to an enquiry

A proportion of enquiries should not become orders, and handling that well protects both the diary and the reputation.

A date you cannot do is the easy one, and offering the nearest you can is better than a flat no.

An allergen you cannot safely accommodate must be a no rather than a maybe, and saying why is reassuring rather than off-putting.

A design outside what you do is worth declining honestly, since executing somebody else's style badly costs more than the order was worth.

A budget that does not meet the work should be said kindly and early, with what is possible at that figure if anything is.

Refer where you can. A baker who sends somebody to the right person is remembered, and the favour tends to return.

Decline quickly. A no after four days of messages is worse for them than a no in an hour.

Making it survive

Record the brief outside the conversation, always.

Keep reference images with the order, not in the chat.

Flag the allergen answer so it is visible when you bake rather than buried.

Handle the customer who changes the date, which is common and affects everything downstream.

Report the outcome: enquiries, briefs completed, quotes sent, orders confirmed.

Limits worth knowing about

Customers do not know what they want early on, which is normal rather than difficult.

Design cannot be automated, and it is the part they are paying for.

Allergen rules differ by jurisdiction and by how the item is sold.

A brief does not prevent a change of mind, it makes the change visible.

Some enquiries should not become orders, and identifying those early is worth as much as converting the rest.

What to build first

The six-question brief, asked in order, with the date first. It turns a fifteen-message exchange into something you can quote from, and putting the date first means the enquiries you cannot fulfil end in two messages rather than twenty.

Two habits make the difference. Ask about allergens before design rather than after, since they constrain what is possible and finding out late means redoing a specification you have already quoted. And write the agreed brief back in one message and ask them to confirm it, because that message is the record that prevents nearly every dispute about what was ordered.

Frequently asked questions

Why do custom cake enquiries take so many messages?

Because the customer does not know what you need, is deciding as they go, and photographs usually arrive after the price has been discussed. The exchange has no shape, and giving it one is the baker's job rather than the customer's.

What does the brief actually need?

Six things: the date, servings or size, the occasion, flavour, allergens and dietary requirements, and collection or delivery. Everything else is design conversation.

Why ask about the date first?

Because a date you cannot do ends the conversation kindly after two messages rather than twenty, and it determines whether anything else is worth establishing.

When should allergens be asked about?

Before design, not after, since they constrain what is possible. Decoration counts as well as the sponge, and if you cannot guarantee a kitchen free of something, say so plainly rather than agreeing.

Do the same allergen rules apply to all cakes?

No. A cake made to a customer's order and one boxed and sold from a counter fall under different labelling regimes in several jurisdictions. In the UK, prepacked for direct sale food needs a full ingredient list with allergens emphasised; made-to-order cakes generally do not, though allergen information must still be given on request. Check your position with your local food safety authority.

How should reference images be handled?

Asked for early, treated as a starting point rather than a specification, with any differences said out loud while the customer is still deciding — and attached to the order rather than left in the thread.

How should the quote be given?

Once, from the complete brief, saying what is included and what would change it, with a validity period and a clear next step. A price discussed across nine messages ends lower than one stated clearly.

What prevents disputes about what was ordered?

Writing the agreed brief back in one message — date, size, flavour, allergens, design, collection, price, deposit — and asking the customer to confirm it.

How should I turn down an enquiry?

Quickly and with a reason. A no after four days of messages is worse for the customer than a no within the hour, and an allergen you cannot safely accommodate has to be a clear no rather than a maybe.

What if the budget does not meet the work?

Say so early and kindly, with what is achievable at that figure if anything is. Referring them to somebody who can help is remembered, and that favour tends to come back.

Related reading

• Stop losing custom cake orders
• Collecting bakery deposits and payments
• A baker's guide to WhatsApp automation