The Order Lived in a DM Thread. So Did the Refund.

Forty-seven messages, zero agreements

Here's how a custom cake order usually happens. A customer DMs a bakery on Instagram. Over a week, the conversation covers flavours, a Pinterest screenshot, a colour change, a date that moves once, and an inscription typed from a phone at 11pm. Forty-seven messages. Friendly, enthusiastic, and completely unstructured.

Then collection day arrives and the cake says "Happy 40th Sarah" when the customer swears she typed "Sara". She did, in message 31. The baker read message 19. Someone's eating the cost of that cake, and whoever it is leaves the exchange angry.

Bakers know the fix is a written confirmation. The problem is that writing one means re-reading the whole thread, extracting every detail, and spotting what was never agreed at all. That's 20 minutes per order, so it gets skipped on busy weeks, which are exactly the weeks disputes happen.

The prompt that reads the thread for you

Confirm a Custom Cake Order So There's No Dispute on the Day takes the raw conversation (the pasted DM thread, emails, or call notes) plus your standard terms, and produces a single order confirmation: collection details, servings, flavours per tier, the design described in words, the inscription as exact quoted text, allergens, price, deposit status, and the change cutoff.

The clever part is what it does with gaps. Anything the thread never settled comes back as a list of direct questions you can send in one message, so "we never discussed the topper" surfaces before the deposit, when it's a 2-minute reply instead of a counter argument.

A worked example

Paste in a thread like this:

• "Hiya! Do you do custom cakes? Thinking something for my mum's 60th"
• "Love the one in your third photo, could it be lilac instead?"
• "Oh and my sister is coeliac, does that matter?"
• "Party is the 14th but I could collect the day before?"

The confirmation comes back with the lilac redesign described in words, collection pencilled for the 13th, and a questions list that catches what the thread missed: no servings count ever given, no inscription agreed, and a flag that "does that matter?" about a coeliac guest was never answered, with a ready-to-send line asking whether the whole cake needs to be gluten free or whether a warning label is enough.

That last one is the difference between an awkward conversation now and a guest having a reaction at the party.

Where the value sits

The confirmation itself is nice. The gap list is the money. Disputes grow out of details each side assumed, and the gap list drags every assumption into the open before money moves. A baker who sends this before taking a deposit has a written record of every choice, a customer who explicitly approved it, and a change-cutoff date to point at when the WhatsApp arrives 36 hours before collection asking to make it a three-tier.

At one saved dispute a month (a £90 cake remade free, plus the hour of apology messages) the prompt pays for the 5 minutes it takes roughly 20 times over. And the allergen line gives you a declared, dated record of what you were told, which matters for more than money.

How to use it

1. Copy the prompt and paste your whole conversation thread where it asks, however messy. Add your deposit and cutoff terms once; they rarely change.
2. Send the questions list to the customer first, then the full confirmation once they've answered. Take the deposit only after they reply confirming it.
3. Save the confirmed version against the order. On a busy Friday, the bake sheet comes from this confirmed document.

Works the same for any made-to-order business where the spec lives in chat: florists, signwriters, picture framers, caterers. The cake is just where it hurts most often.