use case

Manage high-volume email with drafts in your voice, not copy-paste templates

the short answer

High email volume usually forces a trade-off between speed and sounding human — templates are fast but canned, writing each reply by hand keeps your tone but doesn't scale; echo drafts one or two replies per email in your own learned voice, drawing on the thread and a personal knowledge base, so you edit instead of compose and clear volume without flattening how you sound.

Past a certain volume, email stops being a series of messages and becomes a queue. Support, sales, recruiting, community — anyone fielding dozens of replies a day hits the same wall: there isn't time to write each one well, so quality slips, tone goes flat, or the backlog grows.

The common escape hatch is templates, but templated replies are exactly what makes high-volume email feel like a call centre. echo takes a different route: it drafts each reply individually in your voice, so you get the speed of not starting from scratch without the sameness of canned text. This page lays out how to run a high-volume inbox that still sounds like a person.

1–2 draftsper email, so you edit a near-finished reply instead of writing one
open echo →about echo

Why volume flattens your tone

When replies pile up, something has to give. People either paste the same template into every thread, or rush each reply and let it get terse and generic. Both solve the time problem by sacrificing the thing that made your email feel human, and recipients can feel the difference between a real reply and a form one.

Templates also break the moment a message is slightly non-standard — which is most of them. You end up editing the template so much that you've lost the speed anyway, just with a worse starting point than a blank page would have given you.

Per-email drafts beat templates

echo doesn't hand you one canned block to reuse. For each email it writes one or two replies tailored to that thread, in your voice, so the draft already fits the specific message instead of being a generic shell you have to bend to fit.

Because the draft is close to what you'd write, your job shrinks to a quick edit and send. You keep the per-message personalisation that volume usually kills, and you keep the pace, because you're editing rather than composing every time.

Let the knowledge base carry the repeats

In high-volume inboxes a lot of replies hinge on the same facts — pricing, policies, how something works, your standard answer to a common ask. Re-typing those is where a surprising amount of the time goes.

A personal knowledge base you control lets echo pull those details into drafts automatically, so the repeated answers come back accurate and consistent without you sourcing them by hand. The recurring stuff handles itself; you spend your attention on the replies that genuinely need it.

how it works

  1. 01

    Open the next email

    Work the queue one message at a time — echo has already drafted replies for the ones that need them.

  2. 02

    Read the one or two drafts

    Each is written for that thread in your voice, not a reused template.

  3. 03

    Edit and send

    Adjust anything that needs it and send from your own Gmail — a quick pass, not a rewrite.

  4. 04

    Rate to sharpen

    Tap good draft or needs work so echo gets closer to your voice on the next ones.

frequently asked

Isn't this just templates with extra steps?
No. Templates give you one canned block to reuse; echo writes a fresh reply for each thread in your voice. You get per-message personalisation at template speed.
How many drafts does echo give me per email?
Usually one or two options per email that needs a reply, so you can pick the closer one and edit from there rather than starting blank.
Can it keep recurring answers consistent?
Yes — a personal knowledge base lets echo reuse your standard facts and answers across replies, so repeated questions stay accurate without manual copy-paste.
Does higher volume mean more risk of a bad send?
echo only drafts, so volume doesn't change the safety model — every reply is reviewed and approved by you, and nothing sends on its own.

Last updated June 9, 2026

more on echo

ready to try echo?

open echo →