If nobody on your team has trained your Agent on how to communicate, it’s going to sound like an LLM when it speaks to your customers (because it is one).
Conversation design is an emerging discipline in AI-first support teams built to solve this exact problem. A conversation designer owns how your Agent communicates: tone, structure, level of detail, customer experience, handoff and escalation process.
Without a dedicated owner defining the communication guidance your Agent should follow, it starts making decisions itself. That could result in it giving too much detail when a short answer would do, replying in a flat tone when a customer is frustrated, or triggering a handoff too late.
The cost of all of these is measurable. Customers who get awkwardly structured responses aren’t likely to trust the answers, even when they’re accurate, so they’ll escalate to a human teammate to hear the same thing said differently. Others will skip the Agent entirely. When the Agent does hand off, a poor transition means the human support rep inherits a customer who’s already frustrated. Every one of these outcomes is avoidable, and conversation design is the discipline that ensures they don’t happen.
We saw this firsthand at Fin. We A/B tested two opening messages, one warm and conversational, the other our older default. The conversational greeting lifted CSAT from 72.8% to 78.4%. A single conversation design change, applied to the first thing a customer sees, made a measurable difference.
What conversation design covers
The role covers five distinct areas, each shaping a different part of the customer’s experience:
| Area | Description |
|---|---|
| Tone and personality | Voice, level of detail, how formal or casual the Agent sounds, and whether that changes based on the situation. |
| Response structure | Whether the Agent matches the level of detail to what the customer asked. |
| Handoff logic | When to escalate, how to communicate the transition, and what context to carry over. |
| Interaction flow | How a conversation progresses through question, answer, resolution or handoff. |
| Response quality | Whether the answer feels clear, helpful, and on-brand, even when it’s technically correct. |
How to put it into practice
Start with how the conversation should feel
Before tuning individual responses, define the voice. Write it down in one paragraph how you want your Agent to sound. You don’t need a full brand guide, just a reference point you can come back to when making decisions about tone.
Different conversation types may need different registers. A customer locked out of their account needs directness and speed, while someone exploring a new feature might appreciate more context. The voice stays consistent, but the register should adapt.
Design the handoff carefully
The transition from Agent to support rep is one of the highest-friction moments. Customers shouldn’t have to re-explain their issue. The rep should receive the full conversation history, the context behind the issue, what the Agent already did, and why the escalation happened.
The way the Agent communicates the handoff also matters. “Let me connect you with a teammate who can help with this” feels different from a silent handover.
Designing a failsafe is essential too. If the Agent can’t resolve the conversation cleanly, you need a fallback approach that still gives the customer a smooth handover experience. A customer may be frustrated with AI at that point, but a well-handled transition can turn that around.
Don’t forget the follow-up
Follow-ups need the same attention as handoffs. If someone dropped off mid-conversation, with your Agent or a support rep, how do you reach back out to make sure they got the help they needed? Most teams don’t think about this, and customers notice.
Know when the Agent should stop talking
One of the most common conversation design mistakes is over-explaining. The Agent has access to a lot of information, and left unguided, it can easily give more detail than the customer needs.
The Agent should match the level of detail to what the customer asked for. Someone asking how to reset their password doesn’t need three paragraphs. A customer asking about a complex integration might. If there’s more to share, it should offer it rather than give it all at once.
Design for the conversation the customer is having
Customers don’t follow scripts. They change direction mid-conversation or ask follow-ups unrelated to their original question.
The Agent needs to handle these transitions without forcing the customer back into a fixed flow. When the Agent keeps trying to resolve the original question after the customer has moved on, it can feel like talking to someone who isn’t listening.
Consider whether the same flow should apply across different channels, and whether different customer segments need different experiences.
Keep your instructions short
One of the biggest practical challenges is over-instructing the Agent. Teams keep adding rules every time a new edge case comes up. Before long, the LLM has paragraphs of instructions to process before it can respond.
I’ve seen this happen at Fin and I’ve heard the same from other teams. The instinct is always to add more, but the discipline is knowing when to stop.
My rule: if it’s about content or information, it belongs in the knowledge base. If it’s about tone or how to handle specific situations, it belongs in your Agent’s instructions. “Be direct about pricing” does more than a paragraph explaining the philosophy behind your pricing communication strategy.
If you’re using Fin, much of this work happens in Guidance. It’s where conversation design takes shape, helping you define how the Agent should sound, how much it should say, and how it should respond in different situations.
Getting started without a dedicated hire
Most teams won’t hire a dedicated conversation designer on day one – that’s fine. But someone needs to own how the Agent communicates, even if it’s part of an existing role.
Conversation design often starts within support ops or knowledge management. Someone on the team starts paying attention to how the Agent sounds. Over time, as your Agent handles more conversations, that becomes a formal responsibility, and eventually, a dedicated role.
Where to start
1. Name an owner
You need someone to be accountable for how the Agent communicates. It doesn’t need to be a new hire, but it does need to be explicit.
2. Pick one conversation type that isn’t landing well
Look at conversations where your Agent answered correctly but the customer still escalated or left negative feedback. Start there.
If you’re using Fin, CX Score can help you surface these. It shows which topics and conversation types are scoring poorly, and the reasons behind those scores so you can see whether the issue is answer quality, customer effort, or something else.
3. Audit your Agent’s instructions
If they’ve grown beyond a few focused rules, trim them. Move content into the knowledge base, keep the instructions focused on behavior.
4. Fix your worst handoff
Walk through a few conversations where the Agent escalated to a human. Did the customer have to repeat themselves? Did the support rep have enough context? Redesign that single transition first.
Small steps compound
The impact of each of these improvements compounds. A warm opening message improved our CSAT, while trimming instructions made responses sharper. Designing a better handoff meant support reps stopped inheriting frustrated customers.
None of those changes required new knowledge; they required someone paying attention to the conversation itself.
