Academy › Build › WhatsApp and customers

Write the ending first, not the beginning

By the end, you'll have identified the four possible endings of a conversation and written out one full branch backward from its last line, to check that your business data covers each ending and to use when you're the one answering.

By Yodai · Published on September 6, 2026 · Updated on October 12, 2026

The stops in a WhatsApp conversation are the points where the bot decides what to say based on what the customer just said. When it's time to write what gets said at each one, almost everyone starts in the wrong place. They sit down to think up the greeting, then the first reply, then the next one, and halfway through the script they get stuck because they don't know where the conversation is supposed to end up.

Think about a customer who texts you on a Saturday at ten at night. What has to happen for that conversation to end well? If you can't answer that question in one sentence, you're not ready to write the greeting yet.

The question to ask first isn't how the script starts. It's how it ends. If you start with the greeting, you write loose lines and then try to make them fit together. If you start with the ending, every line you write after that already knows where it needs to take the customer.

Your script's four endings

There are only four ways a conversation with your bot can end well, and you already know all four, because they're the same ones that happen today, without a bot, when you're the one answering from your phone.

The first is a booking made: the customer picked a time and got scheduled, with or without payment up front. The second is a quote requested: what you sell doesn't have a fixed price, so the ending isn't an appointment but a link where the customer leaves their details and you send them the number later. The third is a handoff to a person: the question can't be answered by a script, and someone has to pick up the thread with their own name and voice. The fourth is a simple goodbye: the customer asked something, got the answer, and there's nothing to book or charge yet.

Four endings, not two. If your script only covers booking and handoff to a person, the conversations that should end in a quote or a simple answer slip through the cracks and end up in someone's hands too, even when they didn't need to. That's a bot that just turns WhatsApp into live chat with extra steps: it answers the greeting, but hands off everything that actually matters.

Each ending also has its own closing line, and that line is different depending on the business. At a hair salon, a booking made closes with the day and time requested, the name of who's doing the cut, and when you'll confirm it. For a bathroom remodel, a quote requested closes with the timeframe for when the number arrives, not the number itself, because that number doesn't exist yet.

Look at the breakdown in this example: more than half of conversations end in a booking. If you're writing all four branches and only have time for one this week, write that one. The branch that shows up least, the simple goodbye, is also the shortest: it barely needs two lines, and it doesn't include any kind of link.

Write each branch backward, not forward

For each of the four endings, don't start with the greeting. First write down, on a sheet of paper, the last sentence of the conversation: the one that truly closes that branch, whether the bot says it or you do. Then work backward one question: what did the customer need to say right before that, to land on that sentence and not another one? Repeat the step until you reach the stop where this branch split off from the other three.

This isn't a writing trick. It's the only way to check, before your bot starts answering customers, that every branch actually has an ending, and that none of them stall halfway through, leaving the customer to guess what to do next. A script written front-to-back almost always has a branch like that, and it's usually the quote request: it explains how to ask for a quote perfectly well, then forgets to say what happens after you ask.

The hand-off-to-a-person branch works the same way, except its ending isn't a link, it's a named person taking over. If your bot lets you write the message that hands off the conversation, the name goes there: "Marta's handling this one directly, she'll write back as soon as she sees your message." If that message is fixed and can't be changed, the name goes in the first thing you write when you pick up the conversation: "Hi, this is Marta, I've got this." Without a name, it sounds like an excuse. With one, it sounds like someone actually took charge.

The plain sign-off is the branch that gets written fastest and cared for least, because it seems like it doesn't matter. It does: it's your bot's first impression on someone who hasn't bought anything from you yet. A reply like "We're open Tuesday through Saturday, 10 a.m. to 8 p.m. Want me to book you a spot?" does in one sentence what other conversations take three exchanges to ask, and your bot can only give that answer if your full hours are in the business information it reads from.

Where what you write gets used

If your bot lets you write its own lines, keep each branch separate, one block per ending, so you can change one without touching the others. If it answers using your business information and its lines aren't editable, the branches still help: check that your business information covers what each ending needs (services with prices, hours, how to book, and how to request a quote), and use its closing lines when you pick up the conversation yourself. If you're answering from the WhatsApp Business app, you can save these as quick replies. Either way, test it by writing as if you were the customer, and check that the conversation lands on the right branch using the words a real person would use, not the perfect words you'd use while writing the script.

There's still one piece missing from all four branches: the moment the booking or payment link shows up, and what the message carrying it needs to name. That's what's next.

Every branch now ends in a real sentence, not a made-up one. One of them includes the booking or payment link, and when it appears and what it's named decide whether the customer clicks it.

In Yodai the WhatsApp bot answers with your prices and your hours, and hands the chat over when someone asks for a person. See how the WhatsApp bot for your business works.