Problem
Fin handles chat well — short turns, fast iteration, low downside if a reply needs a follow-up. Email is a different beast. Threads are longer, context spans days or weeks, and the stakes are higher: customers expect a considered, accurate response, and a wrong reply is much harder to walk back than in a live chat.
That makes full autonomy a poor fit for most email conversations. But it doesn't mean Fin can't help. Right now, the gap between "Fin resolves it autonomously" and "agent writes from scratch" is too wide for email — there's nothing in between.
Proposal
When a new email arrives, Fin generates a draft reply using:
- The full thread context
- Connected knowledge sources (help center, macros, past resolved threads)
- Brand voice and tone settings already configured for Fin
The draft sits in the conversation ready for an agent to review, edit, or send. A confidence indicator and visible source citations would let agents verify in seconds rather than re-researching the answer.
Why this is valuable
- Cuts response time without giving up the human-in-the-loop check that email genuinely needs.
- Captures Fin's value on conversations that today are 100% manual.
- Creates a feedback loop: agent edits become signal for improving future drafts, and eventually for moving simpler email categories toward autonomous resolution.
Use case
We run a marketplace where most supplier-side conversations happen over email. They're rarely fully automatable, but most of what we write is a variation of something we've written before. A Fin draft would save the majority of the writing time per reply while keeping us in control of what actually ships.