Conversation design for small business owners: seven rules for how your AI agent should talk, with before and after examples

You have written your agent's knowledge and the basics of its instructions, and the answers are correct, yet some chats still feel clumsy. That is a conversation design problem: who speaks when, how much, and what happens at the tricky moments. Here are the seven rules that fix most of it, each with a before and after chat and a line you can paste into your instructions.

By Ritchie, ReplyKit · Published 17 October 2026 · 9 min read

What is conversation design?

Conversation design is deciding how a chat between a customer and an automated assistant should unfold: the order of turns, the length of each message, where the assistant confirms, and how it recovers when things go sideways. Large companies have specialists for it. A small business owner can get most of the benefit from a handful of rules.

It matters because the failures people remember are rarely wrong facts; they are clumsy flows. In Nielsen Norman Group's study of chatbot usability, bots worked when users followed the expected path and broke down when users skipped steps, used unexpected wording or changed their minds. AI agents are far more flexible than the scripted bots in that study, but the same moments still need planning.

Your agent's knowledge decides what it knows. Its instructions decide how it behaves. If you have not written the instructions yet, start with our instruction template, then come back to tune the conversation.

Rule 1: answer first, then ask

When a customer asks a question, the next message must answer it. Questions back to the customer come after the answer, never instead of it.

Paste: "Always answer the customer's question in your first reply. Only ask for their details after you have answered, and only when needed for the next step."

Rule 2: one question per message

Ask one thing, wait for the answer, then ask the next. Customers on a phone answer the last question in a list and ignore the rest.

The exception: two tightly linked details can share a turn ("Which day and roughly what time?"). Lead qualification follows the same rule; our lead qualification questions put the questions in a sensible order.

Paste: "Ask at most one question per message. If you need several details, ask for them one at a time, in this order: [list]."

Rule 3: short turns that fit the channel

On WhatsApp, a good reply is usually one to three short sentences. On a website, it can be a little longer because the visitor is reading on a page, but walls of text lose people everywhere.

Paste: "Keep replies under 60 words unless the customer asks for detail. Use a short list only when comparing options. No greetings or sign-offs after the first message."

Rule 4: read it back before you commit

Before anything that is hard to undo, such as a booking or a recorded order, the agent repeats the key details and asks for a yes. This one rule prevents most "that's not what I booked" messages.

Read-backs should include the what, who, when and where, in that order, and nothing else. For how booking itself works behind the scenes, see how an agent books without double-booking.

Paste: "Before making a booking, repeat the service, staff member if any, date, time and location in one sentence, and only book after the customer confirms."

Rule 5: let people go off script

Customers change their minds, ask a side question mid-booking, or answer a question you have not asked yet. The agent should follow them, then return to the task without starting over.

The same applies when a customer gives everything at once ("table for 4 Saturday 7pm"): the agent should use it all and skip the questions already answered.

Paste: "If the customer asks something else in the middle of a booking, answer it, then continue from where you were. Never ask for information the customer has already given."

Rule 6: admit the gap and open a door

When the agent does not know, it should say so plainly and offer a route to a person, not guess and not loop. NN/g calls this "owning the failure and offering an escape hatch", and the WhatsApp Business Messaging Policy requires businesses that automate to have "prompt, clear, and direct escalation paths".

The "before" is the dangerous one: a confident guess that the business may have to honor. Write the full list of handover triggers using our escalation rules template.

Paste: "If the answer is not in your knowledge, say you don't have that information, tell the customer a team member will follow up, and do not guess. Hand over immediately if the customer is upset, asks for a person, or asks about refunds or complaints."

Rule 7: end with a next step

Every chat should finish with the customer knowing what happens next: they are booked, someone will call, or they have what they need. Avoid both the abrupt stop and the endless "anything else?".

Paste: "When the customer signals they are done, close in one sentence that restates the next step. Do not list other services unless they ask."

The paste-ready instruction block

Here are the seven rules as one block for your agent's instructions. Adjust the details in brackets.

For voice and personality, which sit on top of these rules, see writing an agent persona.

A five-chat test

After changing the instructions, play the customer in five short chats. Each one targets a rule that commonly breaks.

1. The direct question: "how much for a haircut". Pass if the price comes first (rule 1).
2. The all-in-one: "need a table for 6 sat 8pm, one vegetarian". Pass if no question repeats a given detail (rules 2 and 5).
3. The booking: pick a slot. Pass if it reads back details and waits for yes (rule 4).
4. The unknown: ask something not in your knowledge. Pass if it admits it and hands over (rule 6).
5. The goodbye: say "thanks that's all". Pass if it closes in one line (rule 7).

Putting it into ReplyKit

In ReplyKit, an agent's instructions are plain English, so the block above goes straight in. The rest of the design is built in: the agent answers only from your knowledge and says so when the answer is missing, you are notified when a chat needs a person and can take over with one click (the AI pauses for that chat) and hand back the same way, bookings use real open slots with double-booking protection, and it remembers the conversation history with each customer, so returning customers are not asked the same things twice. Questions it could not answer are listed for you to teach once.

Try the five-chat test on the live demo on our homepage, or start a free trial and run it on your own agent. Plans run from $29 to $99 a month; see pricing. If what you need is a button-menu flow with fixed paths and no AI, a visual flow builder is a better match than ReplyKit.

Frequently asked questions

ReplyKit is an independent product and is not affiliated with or endorsed by Meta or WhatsApp. Third-party pages were checked in October 2026 and may change. Example conversations are hypothetical.