Literary Agents Drown in Queries. Email AI Sorts the Signal.

Slush is math with feelings attached. Keep taste human. Let mail handle the mechanical lift.

It is Tuesday. The slush inbox is not a metaphor. It is a number that keeps climbing while you still have client reading to do.

Publishing moved queries from mailrooms to Gmail, but the math got sharper, not kinder. Working agents publicly describe query volumes in the high hundreds or low thousands across a few open months; experienced desks sometimes see hundreds of submissions in a single month. Writer’s Digest’s <a href="https://www.writersdigest.com/query-math-an-agents-take-on-tackling-queries" target="_blank" rel="noopener noreferrer">query math column</a> makes the time cost explicit: minutes per query compounds into serious weekly load before anyone reads a manuscript. Nour Sallam’s <a href="https://www.noursallam.com/publishing-blog/inside-an-agents-inbox-2025-insights" target="_blank" rel="noopener noreferrer">2025 inbox reflections</a> and Jenna Satterthwaite’s <a href="https://jennasatterthwaite.substack.com/p/2025-query-stats-from-my-2nd-year-agenting" target="_blank" rel="noopener noreferrer">2025 query stats</a> are grounded, non-theoretical voices in the same conversation.

Harvard Business Review’s <a href="https://hbr.org/2014/07/the-cost-of-continuously-checking-email" target="_blank" rel="noopener noreferrer">July 2014 piece on continuous email checking</a> is still relevant for a different reason than productivity Twitter thinks: fear of missing heat makes “batch queries twice a day” psychologically hard, even when it is strategically right.

How can agents survive query volume without ruining discovery for authors?

They survive by separating mechanical triage from artistic judgment, keeping every model-assisted step inside user-forwarded text, and refusing automation that pretends to replace taste. The industry’s anxiety about AI is real. The practical problem is throughput: boilerplate openers, repeated formatting fixes, and blurbs drafted from synopsis text the agent already has.

The Authors Guild’s <a href="https://www.authorsguild.org/" target="_blank" rel="noopener noreferrer">resources hub</a> is a useful anchor for the professional context: this is a small industry with loud incentives and fragile trust. Poets & Writers’ <a href="https://www.pw.org/" target="_blank" rel="noopener noreferrer">submission resources</a> remind you how many writers are learning the etiquette from the outside. Publishers Weekly and The Bookseller are trade weather, not workflow software.

The pain point: the slush pile lives in the same inbox as your life

Assistants answer authors, coordinate editors, chase contracts, and try to protect reading time. Agents do taste work on nights and weekends. Everybody feels guilty about delay. Guilt is not a workflow.

Status detail: a junior agent in Brooklyn starts her morning with coffee and a spreadsheet tab of “queries to answer” beside a personal inbox of dentist reminders. By 10 a.m., both feel equally urgent. By 2 p.m., she has answered forty people and read zero pages of fiction. That is not procrastination. It is structural.

What does ethical AI assistance look like in publishing workflows?

Ethical AI assistance in publishing means every model-generated sentence is treated as disposable until a human signs it, every input is supplied intentionally by the professional, and every output is checked for accidental claims about representation, offers, or facts that were not provided. If the tool “fills in” comps, dates, or credentials, you stop and rewrite by hand. The standard is not “plausible.” The standard is “defensible in a room with your client.”

The workflow before: reread the same opener five hundred times

Before, the team rereads variants of the same hook, manually extracts comp titles from messy paragraphs, and rebuilds the same “pass with dignity” language while trying not to sound like a form letter. Speed pressure makes tone brittle. Brittle tone becomes a reputation problem.

Sharp turn: the cruelty is not the volume. It is wasting human taste on repetition.

How should assistants triage without turning authors into enemies?

Triage without cruelty uses consistent, predictable response shapes: what you received, what happens next, and what timeline means in plain English. It avoids fake warmth and avoids performative scarcity. It also avoids asking authors to “just hop on a call” for a query that does not warrant it.

When assistants forward a query draft internally, the forward should include the author’s stated genre, word count, and any submission requirements they followed. That bundle reduces back-and-forth and reduces the chance that a rushed reply misstates what the author actually sent.

Ethics boundaries that are non-negotiable

Never invent comp titles, offers, or representation. Never scrape submissions from the web. Never promise outcomes the human has not decided. The technology only processes what the professional pastes or forwards. If a tool suggests language that feels like a commitment, delete it and write the commitment yourself.

That constraint is a feature in an industry allergic to black-box automation.

The via.email workflow after: forward, draft, human send

via.email routes tasks to specialist agents by email. It does not access your inbox, remember across separate threads, or send on your behalf.

Polish Query Letter at polish.query.letter@via.email helps tighten a query the author or assistant supplies as text—clarity and structure, not fake credentials.

Craft Book Blurbs at craft.book.blurbs@via.email drafts marketing-adjacent blurbs from synopsis facts you include, for human editing before anything goes external.

Distill to Three at distill.to.three@via.email forces a three-bullet memo when a manuscript pitch thread is too long for a Tuesday.

Reject Candidate with Empathy at reject.candidate.with.empathy@via.email drafts humane pass language for hiring-adjacent mail; many agencies also need kind, firm “no” language at scale without becoming cruel.

Extract Action Items at extract.action.items@via.email ends the loop where six people replied and nobody owns the follow-up.

Micro-scene: an assistant forwards a query with a strong premise buried under three paragraphs of biography. The agent returns a tightened hook and a cleaner structure. The agent still does not know if the manuscript is good. The assistant still has to decide whether the premise is commercially viable for this list. The win is that the decision happens sooner, with less eye strain.

What should a skeptical agent test for one week?

Forward five queries you would have edited anyway. Measure two things: minutes saved on formatting and clarity, and whether any suggested line felt like a commitment you did not authorize. If the second number is above zero, your guardrails are too loose. Tighten inputs: require the assistant to paste the author’s comps, not ask the model to invent comparable titles.

What remains human-only?

Taste. Offers. Editorial strategy. Anything that could be read as representation or a promise. Anything that requires reading art.

Broader implications: assistants deserve a map, not a hero narrative

The bookmark moment is a workflow map a senior assistant can hand a new hire on day one: how queries enter, how triage happens, where drafting help lives, where humans veto.

Publishing is not unique in needing “professional kindness at scale.” It is unique in how quickly unkindness becomes Twitter screenshots. That is why the ethical frame matters more than the novelty frame.

Related industry reads: how editors triage relevance, how teachers lose time to mail that is not the job, and how independent workers resist another app layer when coordination is already fragmented.

It is a throughput problem with dignity attached.

If you want a single rule for your desk, make it this: AI may shorten the path between intention and language, but it may not shorten the path between intention and commitment. Commitment stays human, always.

Forward the text. Keep the judgment. Protect the reading time that actually discovers writers.

The inbox will never be quiet. It can be less wasteful.

Treat model drafts like slush: most lines will not make the final list. The win is not volume. The win is getting to the few pages that deserve your weekend without burning out on the envelope.

What is via.email?

AI agents that each lives at an email address. Just send an email to get work done. No apps. No downloads.

How to use?

Send or forward emails to agents and get results replied. Try it without registrations. Join to get free credits.

Is it safe?

Absolutely, your emails will be encrypted, deleted after processing, and never be used to train AI models.

More power?

Upgrade to get more credits, add email attachments, create custom agents, and access advanced features.