<\/p>\n
A support lead opens the weekend queue and finds the same complaint three times, each from a different customer: the chatbot sounds like a chatbot. One person called it polite but weirdly stiff. Another said it felt like talking to a brochure. The third asked, flatly, whether a human was available.<\/p>\n
The underlying model is fine. It answers accurately, follows the prompt, stays on topic. What it fails to do is sound like the brand around it, and customers pick up on that within two exchanges. That’s the decision product teams are wrestling with right now: ship the generic voice that comes in the box, or put in the work to train a model that sounds like the company it works for.<\/p>\n
The first choice sits earlier than most teams realize. Voice gets filed as a configuration task \u2014 a sentence or two in the system prompt, a dropdown labeled “tone,” maybe a few style rules copied out of the brand book. That framing hands the most audible part of your product to whichever vendor you happened to pick.<\/p>\n
A Harvard Business Review<\/a> piece on AI voice argues that this is a behavioral variable the business should own, rather than an infrastructure detail. Own it, and the budget conversation shifts \u2014 owning the voice can mean anything from a tighter prompt to a private LLM<\/a> trained on your own material. File it as a vendor setting and you get what the vendor ships to everyone else.<\/p>\n There are roughly four moves available, and each one costs more and controls more than the last. The right answer depends on how distinctive your voice really is and how much of your business runs through the model.<\/p>\n Most teams land between the second and third rung. The mistake is skipping to the fourth because it sounds serious, or staying on the first because it’s easy.<\/p>\n Fine-tuning a model on your voice means building a dataset that shows the model, over and over, what a good answer from your brand looks like. OpenAI’s supervised fine-tuning documentation describes the shape of the work: prompts paired with the responses you want, enough of them to shift the model’s defaults toward your style.<\/p>\n The pipeline is the easy part; the hard part is agreeing on what the voice is. Pull a hundred recent support replies and you’ll find three different writers, two different reading levels, and at least one tone nobody wants to repeat. Curating the dataset is where the brand decisions get made.<\/p>\n If marketing, support, and product can’t agree on what a good reply reads like, the model can’t either. Pick the reviewers before you pick the training set.<\/p>\n A trained voice is still a work in progress. Someone has to read what the model is saying in production, flag the drift, and feed corrections back into the next training run. Put that loop on the roadmap before launch, not after a customer screenshots something awkward.<\/p>\n The teams that get this right treat voice the way they treat any other product surface: shipped in versions, measured against examples, improved on a schedule. The teams that don’t end up with a chatbot that sounds like everyone else’s, and a quarterly meeting about why engagement is soft.<\/p>\n The temptation on a project like this is to over-build \u2014 bigger model, more data, custom everything. Ship the smallest version that passes a blind read against your own writing samples. If a reviewer can’t tell your human-written reply from the model’s reply, you’re done for now. Scale up when the product needs it, not before.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" A support lead opens the weekend queue and finds the same complaint three times, each from a different customer: the chatbot sounds like a chatbot. One person called it…<\/p>\n","protected":false},"author":37,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[280],"tags":[],"class_list":["post-42062","post","type-post","status-publish","format-standard","hentry","category-tech"],"permalink_manager":null,"_links":{"self":[{"href":"https:\/\/thedesigninspiration.com\/news\/wp-json\/wp\/v2\/posts\/42062","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thedesigninspiration.com\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thedesigninspiration.com\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thedesigninspiration.com\/news\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"https:\/\/thedesigninspiration.com\/news\/wp-json\/wp\/v2\/comments?post=42062"}],"version-history":[{"count":1,"href":"https:\/\/thedesigninspiration.com\/news\/wp-json\/wp\/v2\/posts\/42062\/revisions"}],"predecessor-version":[{"id":42063,"href":"https:\/\/thedesigninspiration.com\/news\/wp-json\/wp\/v2\/posts\/42062\/revisions\/42063"}],"wp:attachment":[{"href":"https:\/\/thedesigninspiration.com\/news\/wp-json\/wp\/v2\/media?parent=42062"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thedesigninspiration.com\/news\/wp-json\/wp\/v2\/categories?post=42062"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thedesigninspiration.com\/news\/wp-json\/wp\/v2\/tags?post=42062"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/a>Decide How Far to Go Down the Customization Stack<\/h2>\n
\n
<\/a>What Does “Your Voice” Actually Mean in Training Data?<\/h2>\n
<\/a>Decide Where the Human Review Lives<\/h2>\n
<\/a>Pick the Smallest Version That Still Sounds Like You<\/h2>\n