Voice guides, sample-pair fine-tuning, lexicon files, and the eval that catches off-brand replies before customers see them.
The number-one reason marketing teams kill a chat agent in week three is that the replies sound like every other chat agent. Generic, hedged, lots of bullet points, lots of corporate sandpaper. The fix is a layered prompt + lexicon + eval setup that any team can ship in a week. What we would do differently next time Looking back at the last six deployments in this category, three things we would do differently: Start the eval harness on day zero. We have always said this and we have always slipped it.
We have always said this and we have always slipped it. The first time we shipped without a regression eval, we caught a prompt change that silently degraded conversion by 11 percent for two weeks before anyone noticed. Now we treat the eval harness as the first deliverable, before the first prompt. Get the executive sponsor in the first user-acceptance session. Not the project manager, not the ops lead.
Voice guides, sample-pair fine-tuning, lexicon files, and the eval that catches off-brand replies before customers see them. It is filed under AI Strategy because that is where operators looking for this problem actually start, and it is written from production work rather than from a content calendar.