Design & run

Conversation design: the words that make a bot feel helpful

The voice, scripts, answers and handover messages, written in plain English, researched from real customer questions and tested with people before launch.

Most bot problems are writing problems

Customers describe bad bots as rigid and unhelpful. Ofcom’s research found many people find chatbots poor at understanding their needs, and some try to get around them (opens in a new tab). Often the platform is fine; the answers are vague, the scripts are long and the bot does not know when to stop.

Conversation design fixes that: answers that lead with what people need, scripts that ask one thing at a time, kind messages when the bot does not understand, and a handover that tells people exactly what happens next.

What’s included

Every item is quoted as part of a fixed price for the scope we agree. Pick what you need.

  • Voice and personality

    A name, a tone and the words to use and avoid, written down so every answer sounds like you.

  • Conversation scripts

    Greetings, flows, confirmations and error messages, short and clear.

  • Answer writing

    Plain-English answers to the questions you really get, with the right links.

  • When the bot does not understand

    Helpful replies for the questions it cannot answer, and a quick way to a person.

  • Handoff messages

    What people see when a person takes over, in hours and out of hours.

  • Plain English and accessibility

    Readable answers, sensible button labels and messages that work with a screen reader.

  • Bot disclosure wording

    A clear, friendly line telling people they are talking to an automated assistant.

  • Question research

    Your inbox, chats and calls mined for the questions people actually ask.

  • Testing with people

    Real people try the bot while we watch, then we fix what trips them up.

  • Channel copy

    WhatsApp templates, widget prompts and button labels, each fitted to its channel.

How it works

  1. Research

    Real questions from your inbox, calls and reviews, grouped and counted.

  2. Voice

    How the bot sounds, what it calls itself, and how it says it is a bot.

  3. Write

    Answers, scripts, fallback and handover messages, short and plain.

  4. Test with people

    Real people try it; we rewrite what confuses them.

Is it right for you?

A good fit when

  • Your bot works but customers do not like it
  • You have content but it reads like a policy document
  • You want the bot to sound like your business
  • You are planning a bot and want to get the words right first

Probably not yet when

  • The bot’s real problem is a missing connection or wrong data
  • Nobody has decided what the bot is for
  • You need legal wording reviewed by a lawyer (we can work alongside one)
  • There are no real customer questions to start from yet

Plain English, accessible by default

We write to a reading age most people find easy, avoid jargon, and make sure messages make sense to screen reader users, with status updates announced as WCAG 2.2 expects (opens in a new tab). Every bot says it is automated in its first message, which the CMA expects where it could affect people’s decisions (opens in a new tab).

The guide on writing your bot’s answers shows the approach.

Questions people ask

Can you work on a bot someone else built?

Yes. Conversation design works on any platform. We review the current conversations, rewrite the answers and scripts, and hand them to whoever runs the bot.

Do you write in other languages?

We write in English and work with native-speaking translators for other languages, then test the translations with people.

How do you test with people?

We ask a small group, ideally your own customers or staff, to try real tasks with the bot, and watch where they get stuck.

Talk to us about conversation design

Send your plan or a few lines about your business. We reply within two working days with questions or a fixed-price quote.