How to stop taking orders in your DMs

This is not a page about getting customers. You have customers. It is about the six places an order leaks between "how much?" and the handoff — and about the fact that none of them are your fault. A direct message is a conversation, and you are using it as an order form.

1. "How much?" — the question you answer over and over

What leaks. Someone sees a photo, likes it, and asks the price. You find the dish, remember what you charge, type it, and wait. Count how many of those end there this week, with no reply and no order. Whatever the number turns out to be, you never learn why. The rest continue, and next week you answer the same question again for someone else.

What it costs. Count your own: if you answer that twenty times a week and it takes two minutes to find the photo and type the price, that is forty minutes a week. Over a year that is about thirty-five hours. That is arithmetic on your number, not a statistic — run it with your own twenty and your own two minutes and the figure is yours.

The part that costs more is invisible: the people who did not ask. A person deciding whether to order dessert for twelve does not want to open a conversation to find out whether it is $40 or $400. If the price is not visible, that order never becomes a message at all.

Today, with no tool. Put your prices where they can be read without asking you. A pinned highlight with one photo per dish and the price written on it costs you twenty minutes once. Set up a saved reply for the price question too — most messaging apps have them — so the forty minutes becomes five.

The structural fix. Any order page does this much: one page listing every dish with its photo and its price, and one link to send. The question stops arriving, and the people who were never going to ask can order anyway.

2. "What time can I pick up?" — the negotiation

What leaks. You propose a time. She counters. You check whether you already promised that slot to someone else, scroll up to be sure, confirm, and then she changes it. Nothing has gone wrong; this is just what happens when two people agree on a time by typing.

What it costs. If settling one pickup time takes five messages and you take ten orders a week, that is fifty messages a week doing scheduling. Worse, it is where double-booking comes from: two people hold the same Saturday noon because the only record of the first promise is somewhere in a thread.

Today, with no tool. Stop offering open time and offer windows instead. "Saturday pickup is 10–12 or 4–6" is one message, and it ends the negotiation because there is nothing to counter. Write down how many orders you can actually finish in a window — not how many you could if nothing went wrong — and hold that line.

The structural fix. An order page can let the customer pick a window herself, from the ones you set, and close it when it is full. You stop scheduling and you stop double-booking, because the count is kept rather than remembered.

3. "I’ll send it later" — the money you chase

What leaks. She says she will send it tonight. You start baking on Thursday for a Saturday pickup, and by Friday you have either been paid or you are deciding whether to ask again. Asking feels rude, so often you don’t, and sometimes nobody comes.

What it costs. This one costs you money you have already spent — which is what makes it different from the forgotten order in section 4, where what you lose is money you would have earned later. A no-show on a custom order costs you the ingredients, the oven time, and the slot you could have sold to somebody else. One of those a month is a real number in your year, and you can work it out exactly: your ingredient cost plus what you would have charged for the slot.

Today, with no tool. Write one rule and apply it to everyone, including your cousin. "Custom orders are confirmed when a deposit lands" is not rude when it is printed next to the prices and applied without exception — it is rude when it appears for the first time in a message to one person. And write down who has paid somewhere other than your inbox — a notebook, a note on your phone, anything you can read at a glance on Friday night, without scrolling through conversations to work it out.

The structural fix. An order page can ask for the money, or a hold, at the moment she orders rather than in a conversation afterwards — so an unpaid order never becomes a baking day. You stop chasing, because chasing is no longer a step.

4. "Where did that order go?" — the orders in four different apps

What leaks. Two orders in one app’s messages, one under a comment on a photo, one in a text message, one your sister took at work and told you about. On Saturday morning you reconstruct the day by scrolling, and the order you forget is always the one that was never written down anywhere.

What it costs. One forgotten order a month costs you that customer and everyone she would have told. It is also the most stressful part of the week, and stress is the reason people stop doing this at all, which does not show up in any arithmetic.

Today, with no tool. One list, one place, every order copied into it the moment it arrives, wherever it arrived. A paper notebook genuinely works. Give each order a state — taken, paid, made, handed over — because "what still needs doing" is the question you actually need answered at six in the morning, and a chat thread cannot answer it.

The structural fix. An order page can put every order into one list with a state attached, whatever the customer did to place it, so the list itself tells you what is left. The copying step disappears — which matters, because copying is the step you skip when you are busy.

5. Your address, handed out too early

What leaks. Someone asks where to collect, and you send your street address to be helpful — before you know whether the order is real. Most of the time nothing comes of it, in either direction. But you have given your home address to a stranger who never ordered, and you cannot take it back.

What it costs. Almost every time, nothing at all. The cost is that you cannot take it back afterwards, so this is not a leak you measure — it is one you settle in advance. Decide the rule now, while nobody is waiting on a reply, because the moment someone is waiting is the worst moment to be weighing it up.

Today, with no tool. Change the order of two steps. Confirm the order first, then send the address — and if the conversation has not reached a confirmed order, the answer is your neighborhood or the nearest cross street, not your door. Write the sentence out once and reuse it, so you are not composing it politely every time.

The structural fix. An order page can show the area publicly and hand over the exact address only once you have accepted. The decision gets made once, in advance, and then it stops being a decision.

6. The thank-you nobody else ever sees

What leaks. She sends a photo of the cake at the party and three lines about how everyone loved it. It is the single most persuasive thing anyone will say about your food this month, and it is sitting in a private conversation where exactly one person can read it: you.

What it costs. Every new customer has to take the same risk the last one took, with nothing to reassure them, because the reassurance is locked in a hundred separate threads.

Today, with no tool. Ask. "Would you mind if I share that?" is almost always answered yes, and a screenshot with the name cropped out is enough. Put them somewhere a new customer will look before ordering rather than somewhere they scroll past. And ask on the day of the pickup, not a week later — it is the only moment she is thinking about it.

The structural fix. An order page can collect the review on the page where people are already deciding, instead of in your inbox. You still have to ask her. What changes is where the answer ends up: somewhere the next customer can read it, instead of somewhere only you can.

If you only change one thing this week

Change the price question first. It is the cheapest fix, it takes twenty minutes, and it is the one your customers notice immediately — a visible price is the difference between someone deciding and someone opening a conversation they may not finish.

Then the pickup windows, because double-booking is the mistake that costs you a customer rather than a few minutes. Then payment, which is the one that costs you money you have already spent.

Everything here works with a notebook and a pinned highlight. If you would rather have the page, the windows, the list, the private address and the reviews as one thing instead of five habits, that is what an order page is for.

One thing worth checking before you grow: what you are allowed to sell, and where, is decided by your state, and the answers are not similar from one to the next. We keep a sourced, dated page for each one — the rules in your state, all fifty-one compared.

Questions people actually ask

Do I have to stop using Instagram or WhatsApp?

No, and you should not. That is where your customers already are, and a following you built is worth more than any page. The change is narrow: keep posting and chatting where you are, and stop using the conversation as the order form. One link in the conversation does that.

My customers are older and will not use a website. What then?

Some will not, and you keep taking those orders by phone or in person — but write them into the same list as the rest, or you are back to reconstructing Saturday by scrolling. In practice the people who say they cannot use a link will tap one that opens in the browser they already have, with nothing to install. The ones who genuinely will not are usually a smaller share than you expect, and they are not a reason to keep everyone else in your inbox.

Is it rude to ask for payment up front?

It is rude when it is a surprise and applied to one person. It is not rude when it is written next to the prices and applied to everyone. The surprise is what offends, not the deposit — which is also why a written rule is easier on you: you stop having to decide, case by case, whether this particular person can be asked.

How do I keep from double-booking a pickup window?

Decide how many orders you can finish in a window on a bad day, not a good one, and write the number down before anyone asks. The double-booking almost never comes from losing count; it comes from not having set a limit, so each new request is judged on its own and they all sound manageable one at a time.

Should I put my address on my page?

No. Put the area — the neighborhood, or the nearest major cross street — and give the exact address once you have accepted the order. Buyers do not need your door to decide whether to order; they need to know it is a reasonable drive.

Do I need an order page at all, or will a form do?

A form will carry you a long way, and it is far better than a conversation: it collects the same fields every time and you can read the answers in one place. Where a form stops is capacity and money — it will happily take six orders for a window that holds four, and it does not know who has paid. If both of those are hurting, that is the point at which a page earns its keep.

Other states

Tools

More guides

Ready to take orders?

Once you are set up, take orders with your own Worknest page — your customers order from one link, you get notified, and you can take the money at pickup.

Get the app

No monthly fee. Your customers order in their browser — they never need an app.