I run our support inbox solo, and the same questions kept coming up. I wanted my team to see what members were actually writing in about instead of it living in my head. I just finished building this with Claude connected to our Gmail support inbox, plus Slack and scheduled tasks.

Weekly prompt: "Read this week’s support inbox threads. Ignore spam and automated emails. Group the real member questions by theme, then by the team that owns the fix. For each team, draft a short Slack post with the top issue members ran into, how many wrote in about it, and one suggestion. Keep each post to a few sentences."

Steps:

1. Every Thursday, Claude reads the week's support threads and filters out spam and noise.
2. It groups the real member questions by theme, then by the team that can fix them (Rundown University, product, newsletter, and so on).
3. It drafts one short post per team covering the top thing members ran into and a suggested fix. Each team only sees what's relevant to them.
4. I review, tweak, and send each post to that team's Slack channel before our Friday meeting.
5. At the start of each month, Claude audits the full month of tickets: what drove volume, what changed from last month, and what's a product gap versus a one-off.
6. It checks my saved replies against what members actually asked. Which are getting used, which are out of date, and which recurring questions still have no saved reply.
7. It refreshes a one-page readout for the team with one headline: the one thing to fix this month.

What I'm hoping it saves: this replaces a monthly Slack recap I had that wasn't action oriented. The goal is a short, useful nudge for each team every week, saved replies that stay current, and recurring tickets fixed at the source instead of answered over and over.