Weekly Front support themes into Linear issues and a Slack digest

Every Monday, spot the recurring bugs, feedback, and feature requests in Front, file them in Linear with customer quotes, and drop a summary in Slack.

Agentic Task
FrontLinearSlackProductCustomer SupportFeedback TriageAI ReportsDaily Digests
PromptCreate

Every Monday at 9am, roll up the last seven days of Front conversations into a set of Linear issues that capture recurring product themes, and post the rollup as a digest in our #product Slack channel.

Trigger: cron, weekly, Mondays at 9am in the org's local timezone.

Step 1. Pull the raw material from Front. Call Front's List Tags to fetch every tag the token can see, then identify the tags that mean bug, feedback, or feature request (default names to look for: bug, feedback, feature-request, but let me override the list). For each of those tags, call List Tagged Conversations and keep only conversations updated in the last 7 days. For each of those conversations, call List Conversation Messages and read the inbound (customer-authored) messages. Ignore outbound replies from teammates and internal comments.

Step 2. Cluster the customer messages into recurring themes. Group by the underlying issue people are describing, not by keyword or tag. Rank themes by the number of distinct supporting Front conversations. Drop any theme with fewer than 3 supporting conversations so we don't file noise.

Step 3. For each remaining theme, use Linear's Create Issue to file an issue in our product team. Each issue should have: a plain-language title that names the pattern; a description that summarizes the theme in a paragraph, then quotes the top 3 most representative customer snippets verbatim (with a light attribution like the requester's company or first name); and a footer that lists the count of supporting conversations. Then, for every supporting Front conversation, call Linear's Add Link to Issue once with the Front conversation URL so the product team can click straight back to the source thread.

Step 4. Post the digest to Slack using Send a Message in the #product channel. The message should list every top theme in ranked order (most supporting conversations first). For each theme include: the theme title, a one-line summary, the count of supporting conversations, and a link to the newly created Linear issue. Keep the tone factual and skimmable, not editorial.

Edge cases: if the week has zero qualifying themes (nothing hit the 3-conversation threshold), skip Linear entirely and post a short 'no recurring themes this week' note to Slack with the raw tagged-conversation count so the team still knows the job ran. If Front returns a merged conversation redirect, follow it and use the merged conversation. Respect Front's rate limits when paging.

Additional information

What does this prompt do?
  • Reads the last seven days of Front conversations tagged as bug, feedback, or feature request and skims the actual customer messages.
  • Clusters the recurring themes and ranks them by how many separate conversations support each one.
  • Files a Linear issue for every top theme, complete with quoted customer language and links back to the original Front conversations.
  • Posts a ranked rollup to your #product Slack channel every Monday at 9am so the team starts the week with real customer signal.
What do I need to use this?
  • A Front account with tags for bugs, feedback, and feature requests (or whatever tag names your team already uses).
  • A Linear workspace and a team where the agent can create issues.
  • A Slack workspace and a channel like #product for the weekly digest.
How can I customize it?
  • Change which Front tags count as feedback, or shift the window from weekly to biweekly, monthly, or daily.
  • Raise or lower the minimum number of supporting conversations before a theme becomes a Linear issue (three by default).
  • Send the digest to a different Slack channel, cross-post to multiple channels, or route issues to a specific Linear team or project.

Frequently asked questions

How does the agent decide what counts as a theme?
It reads the customer messages across every tagged conversation from the past week and groups them by the underlying pattern people are describing, not just by keyword. Themes with fewer than three supporting conversations are dropped so you only see recurring signal.
Will it create duplicate Linear issues if the same theme shows up week after week?
The agent doesn't automatically merge across weeks by default. If you want it to check for an existing open issue with a similar title before creating a new one, ask for that when you set it up and it will look first and add a comment instead of filing a duplicate.
What if our Front tags are named differently?
Just tell the agent which tag names to include. It fetches your tag list from Front, so you can point it at any combination like bug, churn-risk, feature-request, or NPS-detractor.
Can we run this more or less often than weekly?
Yes. The schedule and time window are both easy to change. Daily standups, biweekly digests, and monthly retros all work with the same setup.
Does the Slack digest link back to the original customer conversations?
Yes. Each theme in the Slack post links to its new Linear issue, and every Linear issue has the supporting Front conversation URLs attached, so product can jump straight to the source thread in one click.

Turn your support inbox into a weekly product signal.

Connect Front, Linear, and Slack once, and every Monday the top customer themes show up as issues and a digest without anyone reading through tickets.