AI Email Assistant in Slack: What to Hand Off Before You Hire One to Manage Your Inbox

If you run a 5 to 100 person firm out of Slack, you probably still answer your own email. The mailbox is the one place where customers, partners, candidates and vendors reach you directly, so you keep it, and it eats an hour or two of every day. The two usual fixes are to hire a virtual assistant (VA) or to buy an AI email assistant, and most buyers pick one before deciding which part of the inbox they want to give away. This guide splits the email job into four parts, shows which of them a VA, an inbox tool and an agent in Slack can each take, and gives you one low-risk workflow to try before you hire anyone.

The short answer: hand off sorting and summaries first

Email is four jobs with different risk, so hand them off in this order.

A VA is good at the first job. An inbox tool such as Fyxer, Superhuman or Shortwave covers the first three. A Slack agent can give you a morning brief where you already work, write drafts into your own Drafts folder, and send only after you approve each message. None of them removes your judgment from the messages that carry a relationship, a contract or money.

Why handing the whole inbox to an assistant fails

Nitin Gupta, writing in the On Delegation newsletter, gave his assistant access to his inbox and asked her to ghost-write replies. He reports that "My assistant barely had enough context to cover 5% of the emails in my inbox", and that he spent more time reviewing and correcting her drafts than he would have spent writing the replies. Sorting worked. His assistant put each message into one of three piles: act on it, read it, or throw it away. He says that took 5% of the effort to train and kept 75% of the benefit he had expected from delegating his inbox.

That is one executive's report, not a study, and the helper was a human who knew him. The mechanism is still easy to see. A reply needs the history of the relationship, the price you quoted last month, the mood of the person on the other end, and whether you want to say yes. A sorter needs a rule: this thread is waiting on me, this one is informational, this one is a notification. Gupta's numbers suggest the rule is much cheaper to teach than the reply.

Hand off reading before writing: have the assistant tell you which emails need a reply, which can wait and which are only to be read, and keep drafting and sending for later, because drafting is the step that needs the context a new assistant does not have.

When you compare a VA, an AI tool and an agent, ask which one gives you the shortest list of messages that need you before you ask which one writes the best reply. Drafting quality is the second purchase.

What each option takes, and what it leaves with you

A human assistant with delegate access

A VA works through Gmail's delegate feature. Google's help page says a delegate is someone who can read, send, and delete emails in your account for you, and that a delegate cannot chat with anyone or change your password. A personal account can have up to 10 delegates, and a work or school account up to 1,000. On a work account you can only add people in your own organization as delegates, so an outside VA needs an address in your domain.

A staffing firm that sells VAs, Somewhere, lists the usual reasons owners hesitate: privacy, fear of missing important conversations, and the urge to micromanage. Treat that page as a seller's view, because the firm has a stake in you hiring.

The VA route has one property the guides rarely spell out. A Gmail delegate can read, send and delete in your account with no review step of its own, so a human assistant with delegate access has more unchecked power over your name than an agent whose every send waits on an Approve card.

A good VA earns trust, and you extend it over time. Until then, give a new VA sorting and summarising first and ask for drafts you send yourself, even though the permission would let them send. Gmail does not enforce that restraint. You do.

An inbox tool

Most buyers start with the tool roundups, which mostly compare how good the drafts are. Fyxer's own comparison says that when an email arrives it has a draft reply ready for your review, written in your tone, and that it organizes your inbox by priority. Its paid plans start at $18 a month, and the same page lists Superhuman at $30 a month and Shortwave with a free tier. Inbox Zero's roundup describes triage, labeling and voice-matched drafts on your existing Gmail or Outlook account.

Both pages are written by vendors, so read the comparisons as claims. They agree on one point that matters to you. On whether these tools send without approval, Inbox Zero says that "By default, the credible tools draft and wait for you", and it advises you to "start in draft-only mode and expand automation as you build trust". So draft-and-wait is the standard and will not set one tool apart from another. The roundups do not say which of the four jobs to give the tool first, who in your firm sees its output, or what happens when it is wrong.

An inbox tool suits you if you want your mailbox sorted, labeled and drafted inside the mailbox. It adds one more place to look and one more vendor holding your mail.

An agent in Slack

If your team already starts the day in Slack, the other design brings a short email summary to Slack so you do not move into another inbox. The Kipwise agent works that way, and its documented Gmail abilities are narrower than an inbox tool's. It searches and reads your Gmail, lists drafts, and writes a draft or a reply in your Drafts. Before sending, it shows the recipient, subject and message preview on an Approve or Deny card, and nothing goes out unless you approve. It can also send later and cancel a send that is still waiting.

Sorting and labeling inside Gmail are not on that list, so if you want your mailbox rearranged, keep an inbox tool or a person for that job. The agent adds the brief and the approval, in the place you already work.

The Slack route has a cost you can compute. The agent is $10 per user per month with a minimum of 3 users, so a team of three pays $30 a month. A workspace on a paid Slack plan with at least three people gets a trial of $10 of credit for 14 days; a workspace on Slack's free plan gets $2 of credit for 7 days, answered by the fast model only. Each person has $5 of personal credit a month, with a shared team credit behind it. I do not have a per-brief cost, so ask the agent what credit is left after the first week instead of assuming one.

One workflow to try before you hire

The example below is made up. Dana runs a 12-person design agency. She is the only person who sees client email, and she spends about an hour every morning deciding what is urgent.

Step 1: ask for the brief once. In a direct message with the agent, Dana writes: "Every weekday at 8 am, look at my Gmail and tell me which emails need a reply from me today, which can wait, and which are only for reading. One line each." The agent uses her Slack timezone when it is available, and it asks her to approve the scheduled task once, when it is created. Later runs use the same tools and permissions as a live request from her.

Step 2: connect Gmail as yourself. The agent reads mail with the Google grant of the person who asked. Dana connects her own Gmail, and the agent can open only what she can open. Connecting Gmail does not grant Drive or Calendar, so a request that touches them asks her to connect them separately.

Step 3: read the brief for a week, and keep doing your normal inbox pass. Each morning the brief arrives in Slack:

• Reply today (3): Northwind asking to move Thursday's review; a candidate waiting on a decision since Monday; an invoice question from a client.
• Can wait (5): two vendor follow-ups, a newsletter you replied to last week, a thread where a teammate already answered.
• Read only (11): receipts, a product update, calendar confirmations.

That example is invented. What matters is the shape: a short list with a verdict on each message, in a thread you can answer.

Start with a read-only morning brief for one week, because a scheduled task is approved once and a brief changes nothing, while every email send still needs its own approval.

The approval model explains why. A scheduled task or automation is approved when it is created, together with the list of changes it may make on its own, and later runs do not ask again for those. A brief that only reads has nothing to ask about. A send is a different change: before a live request posts a message or changes a connected service, the agent shows a card, and any change outside the approved list shows a fresh card too. So the one-time approval does not widen into permission to send.

Step 4: when the brief is right, ask for one draft. Dana replies in the same thread: "Draft a reply to the second one, say yes, and ask whether Thursday afternoon works." The agent writes the draft into her Gmail Drafts and shows an Approve or Deny card with the recipient, subject and message preview. Only the person who asked can approve. The card expires after 30 minutes, and if it is denied or expires, the email is not sent.

What stays with a person

An agent in Slack does not replace your judgment. These stay with you, and you should say so to anyone you hire or set up:

• Messages where a relationship is at stake, such as an unhappy customer, a partner renegotiating, or a candidate you are about to lose.
• Anything involving money, contracts, legal or HR, where the cost of a wrong sentence is higher than the cost of writing it yourself.
• Replies that depend on context that is not in the mailbox: a call you took, a decision made in another channel, a promise made out loud.
• The decision to send. Even with a good draft, the Approve card is the point where you read the message once more.

This list is my recommendation, not a vendor rule. It follows from Gupta's 5% figure above: the more a reply depends on context outside the thread, the less an assistant, human or AI, can safely do alone.

For tighter control, you can reduce the agent's reach before you start. Your workspace can turn lookups or changes for a connected service off, and you can list or cancel your scheduled jobs and ask what happened on previous runs, including failures. If you want the broader pattern for running recurring jobs without silent failures, see Schedule Slack AI agent jobs without silent failures. For approval design beyond email, see Add human approval to AI agent workflows in Slack.

Handle failure and edge cases

Plan for four failures before the first week starts.

A missed message. The worst failure of a brief is a message that needed a reply and landed in "can wait". The brief is the agent's reading of your mail, not a guarantee, and nothing in the product documentation says it is complete. That is why Step 3 keeps your normal pass running for a week. Count the misses. If the same kind of message is misfiled twice, tell the agent in the thread; the agent re-reads and corrects itself when you tell it in the thread, and it prefers saying it could not find something to inventing an answer.

A wrong draft. Drafts go to Drafts, not out. Edit them, or delete them. The cost of a bad draft is the minute you spend reading it.

A wrong recipient or an expired card. The card shows the recipient before anything goes. Read the address, not just the preview. If you do not answer within 30 minutes, the send does not happen, which is the safe direction.

A shared inbox. Treat it as a separate problem from your personal one; triaging the Slack inbox without hiring a virtual assistant covers the messages that arrive in Slack itself.

Verify it works

Pick numbers before you start so the week ends with a verdict.

1. Misses. In five working days, how many emails that needed a reply today did the brief file under "can wait" or "read only"? Target: zero. One is a warning, two is a reason to stop and adjust.
2. Time. How long does your own inbox pass take with the brief, compared with last week's pass? If it is not shorter after five days, the brief is not earning its place.
3. Draft keep rate. For the drafts you request in week two, how many do you send with only light edits? If it is under half, keep drafting for yourself.
4. Approval discipline. Did any email go out that you did not read in full? If yes, tighten how you approve, because the card only helps when you read it.
5. Credit use. Ask the agent what credit is left and compare it with your $5 personal credit for the month.

Compare the result with the VA option on the same measures. If a person still gives you a better list of what needs you, hire the person and give them sorting and summaries first, with delegate access and a rule that they draft but you send. If the brief is right and the drafts are usable, you have your first reading of whether you need to hire at all.

What to do next

Tonight, write the sentence you would give an assistant for tomorrow's brief: which emails need a reply from you, which can wait, which are only for reading. Install the agent, send it that request in a direct message, and approve the scheduled task once. Read the first brief tomorrow at 8 am next to your own inbox, and count the misses. If you would rather decide on hiring first, the before you hire a virtual assistant page sets the hire against the Slack route side by side.

References

• Google: Add or remove Gmail delegates: what a Gmail delegate can and cannot do, the delegate limits, and the same-organization rule for work accounts.
• On Delegation: You're doing email delegation wrong: a practitioner's report that ghost-writing replies failed on context and sorting worked (author report, not a study).
• Somewhere: How to delegate email to a virtual assistant: the human VA route and the barriers owners name (staffing firm with a selling interest).
• Fyxer: Best AI email assistants: draft replies for review, priority sorting and plan prices (vendor).
• Inbox Zero: Best AI email assistants: draft-and-wait as the default and the advice to start in draft-only mode (vendor).
• Kipwise: Schedule Slack AI agent jobs without silent failures: scheduled-job practice for recurring agent tasks.
• Kipwise: Add human approval to AI agent workflows in Slack: the approval pattern in Slack workflows.
• Kipwise: Triage your Slack inbox without hiring a virtual assistant: the Slack message inbox, a separate problem from email.
• Kipwise: Before you hire a virtual assistant: the hire-versus-Slack comparison page.