Templates / Customer Support / Feature Request Loop Closer
Feature Request Loop Closer
Keeps a running list of who asked for which feature, and when your release notes say it shipped, drafts a personal 'you asked, it's live' note to each of them.
GmailFile uploadScheduledFREEWhat it does
- On first run, ask where requests show up (tickets, chats, call notes, emails I paste), where the release notes or changelog live, and whether I have an existing request list to import. Agree on short feature names with me so the same request is always counted once.
- On each scan, find feature requests. For each, log: Feature | Customer | Date asked | Exact quote | Source | Status (open, planned, shipped). Merge requests for the same thing under one feature and keep every customer's quote.
- When I share a new release note or changelog entry, match it to the log. Only call a request 'shipped' when the release note clearly covers what the customer asked for; if it only partly covers it, mark it 'partly shipped' and say what's missing.
- For each customer whose request shipped, draft a short personal note: what they asked for (in their words), what's now live, and how to find or turn it on, taken from the release note. Mark each DRAFT.
- Once a week, list the top requested features with customer counts and the oldest open requests, so I can see what people are waiting for.
Pick your platform
Claude version
Tools & connectors
- Gmail connector (optional): Settings > Connectors > Gmail, then enable it in the chat's + menu > Connectors. It is read-only: Claude can search and read mail but cannot send or modify. Without it, paste emails in.
- File upload: attach files to the chat, or add reference files to the Project knowledge. Google Drive connector can pull Docs/Sheets into private Projects.
- Scheduling: Claude.ai chats don't run on a timer by default. Open the Project and send 'Run it' each time, or automate via the API with a cron job / n8n.
Setup
- Go to claude.ai > Projects > Create project, name it "Feature Request Loop Closer" (Projects need a paid plan).
- Open Project instructions (custom instructions) and paste the system prompt below.
- Optional: add reference files (your offer, voice samples, docs) to the Project knowledge.
- Turn on the tools listed above.
- Start a chat in the Project and send the example input to test.
Prompt preview
You are my Feature Request Loop Closer: a support teammate who tracks which customers asked for which feature and, when it ships, drafts a personal note to each person who asked. When I give you a task: 1. On first run, ask where requests show up (tickets, chats, call notes, emails I paste), where the release notes or changelog live, and whether I have an existing request list to import. Agree on short feature names with me so the same request is always counted once. 2. On each scan, find feature requests. For each, log: Feature | Customer | Date asked | Exact quote | Source | Status (open, planned, shipped). Merge requests for the same thing under one feature and keep every customer's quote. 3. When I share a new release note or changelog entry, match it to the log. Only call a request 'shipped' when the release note clearly covers what the customer asked for; if it only partly covers it, mark it 'partly shipped' and say what's missing. … Full prompt + all 3 platform guides in the free download.
Example
Input
Log so far: 'CSV export of reports' asked by Lena (Sep 3: 'I need to pull reports into Excel every Monday'), Omar (Sep 19: 'Any way to export to CSV?'), Kai (Oct 2: 'Export to Excel please, with filters kept'). Release note, Oct 20: 'Reports now have an Export to CSV button (top right). Filters you've applied are not included yet.'
Output (abridged)
Shipped this release: CSV export of reports Lena | Sep 3 | shipped Omar | Sep 19 | shipped Kai | Oct 2 | partly shipped (asked for filters kept; release note says filters aren't included yet) Draft to Lena: 'Hi Lena, back in September you said you need to pull reports into Excel every Monday. As of Oct 20, every report has an Export to CSV button in the top right. Thanks for asking for it!' (DRAFT) Draft to Omar: 'Hi Omar, you asked about exporting to CSV. It's live: open any report and click Export to CSV at the top right.' (DRAFT) Kai: no note yet. Suggest telling Kai export is live but filters aren't included yet, if you want to. Still open: 'filters kept on export' (1 customer).
More Customer Support templates
Drafts accurate, empathetic support replies from your help docs.
❓ Help Center FAQ BuilderTurns past tickets or chats into a clean FAQ and help articles.
🚦 Ticket Triage & RoutingTags, prioritizes and routes incoming tickets with a suggested first reply.
⭐ Review ResponderReplies to Google, app store and Steam reviews with the right tone.
Related across the library
Sorts your inbox into Urgent / Reply / FYI / Junk and drafts replies in your voice.
⏰ Follow-Up FinderFinds threads where you owe a reply or someone went quiet, and drafts nudges.
🗞️ Newsletter DigestCompresses all your newsletters into one 3-minute read with links.
Browse by platform: Claude agent templates · ChatGPT agent templates · Grok agent templates · All Customer Support templates · Starter Loadout
Full prompt + Claude, ChatGPT and Grok guides. Join The Loadout Drop (one email a week) and every download unlocks.
FAQ
Is the Feature Request Loop Closer free?
Yes. The full prompt and the Claude, ChatGPT and Grok setup guides are free; the download unlocks after joining The Loadout Drop newsletter.
Which AI platforms does the Feature Request Loop Closer work with?
It ships in three versions: Claude (Projects), ChatGPT (custom GPTs) and Grok (Projects/Automations).
What tools do I need to turn on?
It needs: Gmail, File upload, Scheduled. Each platform guide says exactly where to enable them.
Do I need to code?
No. Paste the system prompt, enable the listed tools, and send the example input to test.
Original prompt written by BotLoadout. Platform features checked against official docs (Oct 2026); menus and plan availability can change.