Draft follow-ups for every email that never got a reply

Every weekday at 4pm, your silent outbound threads get a short, personal follow-up waiting in drafts, ranked by the deals still worth winning.

Agentic Task
Zoho MailZoho CRMSlack BotSalesPersonal ProductivityEmail AutomationDaily Digests
PromptCreate

Every weekday at 4pm, find the outbound emails I sent that never got a reply and write the follow-ups for me. Save them as drafts for my review. Never send anything automatically.

Start in Zoho Mail. Use Search Emails to pull the messages I sent between three and fourteen days ago. Anything newer than three days has not had a fair chance to get a reply yet, and anything older than fourteen days is usually cold enough that a follow-up reads as odd. Use Get Email Details and Get Email Content where you need the subject, the recipients, the timestamps, or the body of the original message.

For each of those sent messages, check the thread for an inbound response from the recipient. If anyone replied, drop the thread entirely. I do not want to chase someone who has already come back to me. Use List Emails in Folder against my inbox, together with Search Emails on the recipient address or the subject line, to confirm whether a reply exists before you treat a thread as silent.

For the threads that are genuinely silent, cross-reference the recipient's email address against Zoho CRM using Search Records. Look for a matching contact or lead and any deal attached to them. Threads tied to an open deal are the priority, so chase those first and carry the deal name and value through to the summary. Threads with no CRM match and no clear commercial purpose, meaning receipts, notifications, scheduling confirmations and other dead admin mail, should be ignored rather than chased. Treat this whole step as optional prioritisation: if I have not connected Zoho CRM, or a particular contact simply is not in it, still chase the thread on the strength of the email itself, just without the deal context.

For each thread worth chasing, compose a short follow-up. It should be non-pushy and context-aware. Reference the specific thing I originally asked for or offered, acknowledge how much time has passed in natural language rather than a blunt day count, and give the recipient an easy way to respond even if the answer is no. Keep it to a few sentences, match the tone of my original message, and do not restate the entire earlier email. Write it as a reply within the existing thread, keeping the original subject, so it reads as a genuine follow-up rather than a fresh cold email.

Save each one with Zoho Mail Save Draft so it lands in my drafts folder. This is the important part: nothing goes out automatically. I want to read, edit and send every follow-up myself, which is exactly why this is safe to run daily.

When you are done, post a single summary with Slack Bot Send a Message. List each person being chased, how many days of silence, and the related deal name and value where one exists, ordered with the highest value open deals first. Finish with a count of how many drafts are now waiting in my drafts folder. Send one message for the whole run, not one per draft. If nothing was silent, say so in a single line rather than posting an empty list.

What does this prompt do?

  • Looks through the emails you sent between three and fourteen days ago and checks every thread for a reply, so anything already answered is left alone.
  • Cross-references each silent contact against your CRM, so threads attached to an open deal get chased first and one-off admin threads are skipped.
  • Writes a short, friendly follow-up for each one that refers back to what you originally asked and how long it has been.
  • Saves every follow-up as a draft for you to review, then posts one Slack summary of who is being chased and how many drafts are waiting.

What do I need to use this?

  • A Zoho Mail account for the mailbox you send from.
  • A Slack workspace and a channel where the daily summary can be posted.
  • Optionally a Zoho CRM account. Without it the workflow still runs, it just chases every silent thread instead of ranking them by deal.
  • A few weeks of sent email, so there is something for the first run to find.

How can I customize it?

  • Change the silence window. Three to fourteen days suits most sales cycles, but you can chase sooner or leave threads open longer.
  • Change when it runs and where the summary lands, for example first thing in the morning instead of 4pm, or into a private channel.
  • Tell it which threads to ignore, such as newsletters, internal colleagues, or whole domains, and adjust how warm or how brief the follow-ups read.

FAQs

Will this send emails on my behalf?
No. Every follow-up is saved as a draft in your Zoho Mail drafts folder and waits for you. Nothing leaves your mailbox until you open it, edit it if you want, and hit send yourself. That is what makes it safe to run every day.
Do I need Zoho CRM for this to work?
No. The CRM lookup is an optional extra that helps rank the list, so threads tied to an open deal get chased first. Without it you still get a draft for every genuinely silent thread, just without the deal name and value in the summary.
What happens if someone already replied?
That thread is dropped. The workflow checks each conversation for an incoming response before it writes anything, so you will never chase someone who has already come back to you.
Will it chase people I would rather leave alone?
You can tell it to ignore internal colleagues, newsletters, or entire domains. It also skips dead admin threads such as receipts and scheduling confirmations, since those almost never need a nudge.
How many drafts should I expect each day?
Only as many as there are genuinely silent threads in your window, which is usually a handful rather than dozens. The Slack summary gives you the count up front, so you know what is waiting before you open your mailbox.

Related templates

Build a credential rotation checklist when someone leaves

When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.

1Password
Rippling
Slack Bot
+1
Agentic Task
Weekly Amazon S3 bucket security audit posted to Slack

Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.

Amazon S3
Slack Bot
Google Sheets
Agentic Task
Log Agorapulse social conversations to HubSpot contacts

Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.

Agorapulse
HubSpot
Slack Bot
Agentic Task
Clean up HubSpot contacts from your Amazon SES suppression list

Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.

Amazon SES
HubSpot
Slack Bot
Agentic Task
Draft polite follow-ups for emails that never got a reply

Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.

Aurinko
Google Sheets
Slack Bot
Agentic Task
Replay failed SQS messages when a bug fix is merged

When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.

Amazon SQS
GitHub
Slack Bot
Agentic Task

Stop letting good threads go quiet.

Get review-ready follow-ups waiting in your drafts every weekday afternoon, so chasing takes minutes instead of memory.