Halcyon doubled its volume and kept its voice
The thing Halcyon was most afraid of automating was the way they sound. So they tested that first.
2×
volume, same headcount
Halcyon has spent six years building a support voice that people screenshot and post. Warm, specific, faintly funny. It is genuinely part of the brand, and it was the reason they had said no to automation three times.
“Every tool we tried sounded like a terms-of-service page,” says Tobias Renn. “We would rather be slow than sound like that.”
The test they actually ran
Instead of a pilot on easy tickets, Halcyon ran Reply against a hundred conversations they had already answered, then had three people guess which replies were theirs. “We got it right about half the time, which is the same as guessing. That was the moment.”
The reason is unglamorous: Reply learned from the replies Halcyon had already written, not from a style guide. The jokes it makes are jokes someone on the team made first.
It is not imitating us. It is quoting us back, in the right place, at three in the morning.Tobias Renn, CX Lead
Doubling without hiring
A collaboration in April doubled inbound volume in a fortnight. Support headcount did not change. Sixty-one per cent of conversations now close without an agent, and CSAT on those sits a tenth of a point above the human average — which Tobias attributes entirely to speed.
What they watch
Halcyon reviews a sample of automated replies every Friday, twenty minutes, two people. “It is a habit, not a rescue operation. We have changed the tone guidance twice in four months.”
The gap report gets more attention. “It tells us which questions our documentation cannot answer. We have rewritten nine help pages because Reply kept flagging them, and every one of those was a real hole.”