Follow-Up Email Tracker AI Prompt

Never drop a follow-up with this AI prompt. Track emails awaiting replies and get nudges before they go cold. Try this email follow up tracker prompt free.

The prompt

Role: You are a follow-up guardian. You make sure no important email thread dies from neglect.

Context: I send emails waiting for replies, then forget to chase them. Deals stall, requests vanish. I need a tracking system for emails awaiting responses.

Task: Build my follow-up tracking system from these sent emails.
Emails I sent awaiting reply (who, what, when): [SENT_AWAITING]
How important each is: [IMPORTANCE]
My follow-up style: [STYLE] (gentle / direct / persistent)
My tools: [TOOLS]

Deliver:
1. A follow-up table: each thread with recipient, ask, date sent, days waiting, and urgency rating
2. A chase schedule: exactly when to follow up on each (e.g., "3 business days, then 7"), with dates
3. Draft nudge emails for each thread in my style — polite, brief, with the original ask restated
4. Escalation rules: when to change channel (call instead), when to loop in someone else, when to let go
5. A weekly 10-minute follow-up ritual: steps to review the tracker every Friday
6. Templates: 3 reusable nudge templates (gentle bump, direct check-in, final attempt)

Format: Table first, then schedule, drafts, and templates. Professional, persistent tone — follow-up is service, not nagging.

Constraints: Nudges must be short (under 80 words) and never guilt-trip. Every thread gets a "let go" date — infinite chasing is denial. Restate the ask in every nudge; don't make them search the thread. Match my style: gentle stays gentle.

Variables to fill in

Replace each [variable] in the prompt with your own details:

[SENT_AWAITING] [IMPORTANCE] [STYLE] [TOOLS]

Example input

SENT_AWAITING: proposal to Acme (5 days), invoice approval from Ben (9 days), intro request to Dana (2 days); IMPORTANCE: Acme high, others medium; STYLE: gentle; TOOLS: Gmail + spreadsheet

How to use this prompt

Run the Friday ritual weekly — 10 minutes prevents most dropped threads. Personalize each nudge draft slightly; templates are starting points. Set the let-go date when you send the follow-up, not when you're frustrated.