Back to blog
Product

Designing an agent that sounds like you

Owen Rivera · March 30, 2026 · 9 min read

The thing nobody warns you about with customer-facing AI is that the agent is now a brand asset. It writes more sentences in your name in a single afternoon than your blog has shipped all year. Voice cannot be an afterthought.

Three layers of voice

We split voice into identity (who the agent is), register (how formal it is in the moment), and refusal style (how it declines, escalates and apologises). Each layer compiles into a system prompt, a small set of style few-shots and runtime guards.

  • Identity: a one-paragraph charter -- what the agent is, what it is not, what it cares about.
  • Register: a slider for formality, plus a default channel-by-channel mapping.
  • Refusal: how the agent says no, when it must escalate to a human, and what it never speculates about.

Why we chose tokens over templates

Templates feel safe. They are also brittle. A token system lets the brand team change a single source of truth -- say, the way the agent greets returning customers -- and have it ripple across web, Slack, SMS and in-app. No find-and-replace, no forks.

Want to see this work on your stack?

Most teams ship in under a week. Take the trial for a spin.