You send important emails, then forget who never replied. Because most lost deals and lost candidates aren’t rejections, they’re just emails nobody followed up on.
| Manual step | One click label |
|---|---|
| Follow up wait | 3+ days, no reply |
| Review cadence | Weekly, every Friday |
| Send control | Draft only, never auto sent |
1. Label what needs a reply
The moment you send something important, a proposal, an introduction, an ask, tag it. In Gmail or Outlook this is a one click label called something like ‘Awaiting Reply’. It takes two seconds and it is the only manual step in this whole system.
2. Connect your assistant to that inbox
Most AI assistants now have a built in Gmail or Outlook connector, sometimes called an MCP connection, which just means the AI can look inside a specific app instead of only chatting with you. Turn it on for your inbox and give it access to that one label, nothing else.
3. Give it one weekly instruction
Tell it plainly: ‘Every Friday, look at emails I labeled Awaiting Reply that I sent more than three days ago and that have no reply in the thread. Draft a short two line follow up for each one, in my normal tone.’ That single sentence is the whole setup.
4. Keep it draft only
Do not let it send anything on its own. Have it write the follow ups and list them for you. This keeps you in control and means a badly worded draft never goes out by mistake.
5. Review and clear in one sitting
Every Friday, open the list, skim each draft, send the ones that still matter, delete the rest. What used to be scattered across your memory becomes a five minute task at the end of the week.
6. Set it and forget it
Once the instruction is saved, most assistants let you schedule it to run automatically every week without you asking again. If yours cannot schedule itself, put a five minute recurring event on your own calendar as the trigger.
A worked example
A consultant sends three proposals in one week and, as usual, forgets who replied by Friday.
Before
Sent Monday: proposal to Rahul Mehta. Sent Tuesday: introduction to Fatima Al Suwaidi. Sent Wednesday: quote to Priya Nair. By Friday, no memory of which ones got answered, no time spent checking.
After
1. Rahul Mehta, proposal, 4 days ago, no reply: ‘Hi Rahul, following up on the proposal I sent Monday, happy to answer any questions.’ 2. Fatima Al Suwaidi, introduction, 3 days ago, no reply: ‘Hi Fatima, wanted to check if the introduction reached the right person on your side.’ 3. Priya Nair, quote, 2 days ago, no reply: ‘Hi Priya, checking in on the quote I sent, let me know if you need anything else from me.’ All three drafted in under five minutes.
Three ways to bend it
For recruiters
Track candidates who went quiet after a good interview. Label the offer or next steps email, and let the assistant draft a warm nudge instead of losing a candidate to silence.
For salespeople
Apply the same label after every demo or proposal. The assistant drafts the nudge referencing the specific demo date, so it never reads like a generic template.
For job seekers
Label the thank you note you send after an interview. If the recruiter goes quiet for a week, the assistant drafts a polite check in instead of you agonising over whether to write one.
When it goes wrong
It keeps flagging emails that already got a reply.
Tell it to check the whole thread for any reply, not just count messages, and exclude anything already replied to. Most connectors can see thread status if you ask for it specifically.
I do not want it sending anything without me.
Keep it in draft only mode always. Never give it send permission for this task, only draft and list permission.
I have too many labeled emails and the list is long.
That usually means you are labeling everything, not just what genuinely needs a reply. Reserve the label for asks that matter, not every email you send.
When not to use this
This is not for anything sensitive, legal, contractual, or personal, where you would not want an AI tool reading the thread even to draft a nudge, and it is not a replacement for a proper CRM if you are tracking dozens of live deals with stages and owners. For a handful of important asks a week, it is exactly enough. For your entire sales pipeline, use a real pipeline tool instead.
What you can now do
You stop losing deals, candidates and introductions to nothing more than forgetting to hit send on a follow up.
Part of Making Life Easier With AI, a weekly walk-through of one small thing AI can take off your plate.
Take this further
Act as a blunt hiring manager who has read ten thousand resumes, not a career coach. I will paste my full resume and the job description I want. Rewrite the whole resume for that role, section by section, in this order: summary, experience, skills, education. Rules: every experience line leads with impact, not duty. Use bracketed placeholders like [8 percent] for any number I did not give you, and list at the end every placeholder I need to replace with a real figure. Keep it to one page of text. Plain formatting only, no tables or columns, so screening software can parse it. After the rewrite, tell me the three weakest claims that need evidence before I send this anywhere. My resume: [paste resume]. The role: [paste job description].
Takeaways
- Create an Awaiting Reply label in Gmail or Outlook and reserve it only for asks that genuinely need a response, not every email you send.
- Connect your AI assistant to your inbox through a connector (MCP) and scope its access to that single label, nothing else.
- Give it one written instruction to draft two line follow ups every Friday for labeled emails older than three days with no reply.
- Set the assistant to draft only, with no send permission, and add an explicit instruction to check full thread status so it stops flagging already answered emails.
- Schedule the check to run automatically each week, or add a recurring calendar reminder if your assistant cannot self schedule.
Questions people actually ask
How do I stop forgetting to follow up on emails I sent?
Create a single label in Gmail or Outlook, something like Awaiting Reply, and apply it the moment you send an important email. Connect an AI assistant to that one label only, and give it a standing weekly instruction to draft follow ups for anything older than three days with no reply. You review and send on Fridays.
What does it mean to connect an AI assistant to my inbox?
It means giving the assistant a scoped connector, often called an MCP connection, so it can read a specific part of your email account instead of only chatting with you. You control the scope, in this case a single label, so it never sees your whole inbox, and by default most connectors still require your approval before anything gets sent.
Can the AI send a follow up email without my permission?
Not if you set it up correctly. Keep the assistant in draft only mode and never grant it send permission for this task. It should only write the follow up and add it to a list for you to review each Friday. You then choose which drafts to send and which to delete, so nothing leaves your account automatically.
Why does it keep flagging emails that already got a reply?
This usually happens when the assistant is only counting messages in a thread instead of checking whether any of them are actual replies. Ask it explicitly to review full thread status and exclude anything already answered before drafting a follow up. Most inbox connectors can detect reply status if you specifically request that check.
Is this safe to use for legal or sensitive emails?
No. This workflow is meant for routine follow ups like proposals, introductions, and check ins, not anything legal, contractual, or personal where you would not want an AI reading the thread even to draft a nudge. It is also not a substitute for a real pipeline tool if you are managing dozens of active deals with stages and owners.
Sources
- Introducing the Model Context ProtocolAnthropic
- Use Google Workspace connectorsAnthropic Help Center
- Schedule recurring tasks in Claude CoworkAnthropic Help Center
What happens next
More Gmail and Outlook connectors are adding native scheduling and thread status detection, which should reduce the false positive follow ups that come from counting messages instead of checking for replies. Expect providers to keep tightening default permissions on connectors so draft only stays the safe default rather than something users have to configure themselves. Watch for this pattern extending into lightweight CRM style tracking for people managing more than a handful of live deals.
