How To Write Chatbot Copy That Doesn't Annoy Your Customers

I spent years as the sole copywriter at a tech startup, writing chatbot scripts full-time. 

The role didn't exist before I arrived. It was created especially for me. 

There was no template, no predecessor and zero documentation to help guide me as a writer. There wasn't another writer on staff to mentor me, either. 

I built the practice from scratch, made every mistake available, and learned what actually works through thousands of conversation flows and hundreds of customer interactions.

What I've learned is that most chatbot copy is bad. Writing for a chatbot isn't like writing marketing copy, website content, or email campaigns. It has its own constraints, its own logic, and an entirely unique definition of what "good" means.

Here's what I learned.

Make Your Answers As Generic As Possible

This sounds like terrible advice for any other kind of writing, but for chatbot copy, it's the foundational principle.

• When you're chatting through the bot, you don't know who you're talking to. 
• The customer might be a first-time visitor or a long-standing client.
• They might be calm or furious. 
• They might be technically sophisticated or completely unfamiliar with your product. 

You have no context, no history, no demographic information at the point of script-writing.

This means you can't use language that assumes anything about the person reading it. 

• Avoid pronouns that assume gender or any specific qualities about the person
• Avoid references to previous interactions you can't verify the bot has access to
• Avoid a tone that works for one emotional state but alienates another - the breezy, casual response that feels friendly to a relaxed customer can feel dismissive to an angry one

The goal is to write copy that works for every possible reader (chat visitor, really), in every possible state. 

I appreciate that sounds impossible. 

In practice, it means writing with radical clarity, using sentences where the meaning is entirely contained in the words themselves, with no reliance on shared context or assumed knowledge.

I always used: 

• Plain language
• Short sentences
• Direct answers
• I avoided jargon unless your audience is exclusively technical
• I never used personality quirks that might charm one customer and irritate another

My goal was to produce copy that felt like a helpful, neutral, slightly warm presence, or the conversational equivalent of a well-designed sign that everyone can read.

One Answer Should Address Ten Questions

A customer asking about pricing might phrase it as "how much does it cost," "what are your rates," "is there a free plan," "what's included in the basic tier," "can I see pricing," or half a dozen other variations. 

Your chatbot cannot have a separate answer for each phrasing. 

It needs one response that addresses the underlying need regardless of how the question was worded.

This means writing answers that respond to the intent behind the question rather than the specific words used. 

The pricing answer doesn't just quote a number; it acknowledges that the customer wants to understand the cost, directs them to the pricing page, and offers to connect them with a person if they need more details. 

That single response handles every variation of the pricing question because it addresses the need and not the phrasing.

As a chatbot writer, you need to identify what the customer actually wants to know. This differs from what they literally typed, instead focusing on what they're trying to accomplish. 

Once you're writing to the intent rather than the words, one well-crafted answer can handle a surprising number of surface-level variations.

Build The Longest Possible FAQ List

This is the discipline that makes everything else work, and most companies skip it or do it superficially.

Before writing a single chatbot script, compile every question a customer might conceivably ask. 

Not just the obvious ones - "what does it cost," "how do I sign up," "what's your refund policy." 

Instead, come up with edge cases, frustrated variations, and questions that arise from misunderstandings of the product/service. List the questions that customers ask when the real issue is something they haven't articulated yet.

This will need research. 

• Talk to your support/customer service team or review your history of customer service enquiries
• Read your existing support tickets (if you offer this)
• Look at your competitors' FAQ pages and see what they address
• Think about the customer journey from first visit to purchase to post-purchase, and identify every point where a question might arise

The longer the list, the better your scripts will be. You'll see which topics generate the most variations, which areas of your product cause the most confusion, and where the gaps in your existing communication are.

A Fluid List Of Answers

Update the list of answers regularly. 

New questions will emerge as your product/service changes, as new customers arrive and as situations you didn't anticipate appear in your support data. 

The FAQ list and responses should be a living document, one you constantly review and add to. 

When I say 'review,' I also mean continually tweak your chat box responses. Some scripts won't land as you want them to. Some answers won't be enough or will cause more questions. Be willing to improve them. 

Always Have A Generic Chat Bot Answer

Your chatbot will encounter questions it can't answer. This is inevitable, and it's not a failure. No script library, however exhaustive, will anticipate everything a customer might ask.

What matters is how the bot handles the gap.

The worst possible response is silence or a generic error. The second-worst is a response that pretends to answer the question but clearly doesn't, which customers recognise immediately and destroys their trust faster than anything else.

The best fallback answer to a question with no scripted answer is honest, helpful, and redirects to a human. 

Something like: "I don't have the answer to that specific question, but I can connect you with someone who does. Would you like to speak with our support team?" 

Or: "That's a great question - let me get you to someone who can help with the details."

The fallback should feel natural, not robotic. It should acknowledge the limitation without apologising excessively. And it should always offer a clear next step, which should be a handoff to a person, a link to a contact form, or a phone number. 

The customer's question matters, but it will happen when the bot can't answer it. The bot's job is to make sure the question still gets answered.

Write several variations of your fallback response so the bot doesn't repeat the exact same phrasing every time it hits a gap. Even small variations - "Let me connect you with the team" versus "I'll get you to someone who can help" - prevent the repetition that makes the bot feel mechanical.

Write Like A Person, Always

The customer probably knows they're talking to a bot. That's fine. The experience is still better - less frustrating, more productive, more likely to resolve the issue - if the language doesn't constantly remind them of that fact.

This means writing in the most natural register you can manage within the constraints. 

• Avoid corporate formality
• Avoid stiff constructions
• Don't use language that sounds like it was assembled by a committee and approved by legal

To make sure you're hitting the mark, read every script out loud. If it sounds like something a helpful colleague might say in conversation, it's working. If it sounds like a terms-of-service document, rewrite it.

Contractions help. "We're happy to help" instead of "we are happy to help." First person where appropriate. Short sentences for clarity, occasional longer ones for warmth. 

The voice should feel consistent - the same helpful presence throughout every conversation flow - without feeling scripted.

The paradox of chatbot copy is that the best scripts sound like no one wrote them. The customer gets their answer, feels helped, and moves on without ever thinking about the words themselves.

That invisibility is the goal. It's also the hardest thing to achieve because it requires a writer who understands that the best version of this work is the version where their skill is undetectable.

Get A Professional Copywriter

If writing a chatbot script isn't your thing, hire someone to do it for you. Get someone who intimately understands the complexities of this style of communication and how to warmly convert visitors on your website. 

Or, if I'm being honest, avoid the chatbot feature of your website. And if you can't produce answers that don't sound genuine, or don't answer the questions of your visitors, avoid it altogether. 

As I've learned, it's one of those all-or-nothing features. Getting it right is paramount, and getting it right can destroy all of your hard work. 

---

I write about the emotional and practical reality of being a writer - drafting, doubt, discipline, and publishing while still figuring it out.

Mostly for people who write because they have to, need to, want to | linktr.ee/ellenfranceswrites