Monthly Voice of Customer to Jira: Social Feedback Synthesis

Build me a monthly voice-of-customer synthesis workflow that turns social feedback about our product into Jira tickets the PM team can triage.

Trigger: a cron schedule that runs at 8am local time on the 1st of every month.

On each run, the agent should:

1) Query Infegy Starscape for posts from the trailing 30 days that mention our product paired with feature-request or complaint language (configurable search terms, with a default seed list the agent can edit). Use Get Topics Analysis to cluster the matching conversations into theme groups with size and sentiment.

2) For each cluster above a configurable mention threshold (default 25 mentions), use Download Post Records to pull a representative sample of posts for that theme, then call Generate AI Summary to write a tight description that covers the underlying user pain, who is asking (audience or persona signal from the post records), frequency relative to the prior month, and 2 or 3 example quotes.

3) For every qualifying cluster, use Jira Create Issue in the configured product backlog project. The issue summary is the theme name. The description body contains the synthesized write-up plus the example quotes. Apply a 'voice-of-customer' label and the configured issue type (default Task). If a Jira filter or epic is configured, link the issue to it.

4) After all tickets are filed, use Slack Send a Message to post a digest in the configured product channel. The digest should include the total number of tickets filed this run, the top 3 themes by mention volume with a one-line summary each, the run window, and a link to the Jira filter view that shows all tickets with the voice-of-customer label.

Configurable inputs the workflow should expose: Infegy search terms and brand/product scope, mention threshold per cluster, Jira project key, Jira issue type, Jira label, optional Jira epic or filter URL, Slack channel, and the run timezone. If a month produces zero qualifying clusters, still post a Slack note saying so instead of going silent.

Keep ticket bodies skimmable: short paragraph for the pain, a 'who is asking' line, a 'month-over-month' line, and a quotes section with at most 3 quotes and their sources.

Additional information

What does this prompt do?

Runs once a month and gathers public posts that mention your product alongside feature-request or complaint language from the last 30 days.
Groups the conversations into themes, then writes a tight description of each one with the underlying user pain, who is asking, and example quotes.
Files a Jira ticket for every theme that crosses your mention threshold, tagged as voice of customer so PMs can triage it next to other intake.
Posts a digest to your product Slack channel with the ticket count, the top three themes, and a link to the Jira filter view.

What do I need to use this?

An Infegy Starscape account with access to social listening data for your product or brand.
A Jira project where the workflow can file tickets and a label or filter set up for voice of customer.
A Slack workspace and the channel where your product team reviews customer signal.

How can I customize it?

Change the cadence from monthly to weekly or quarterly, or shift the run day to match your roadmap rituals.
Adjust the mention threshold so only themes above a certain volume become tickets, or compare against the prior period before filing.
Swap the Slack channel, the Jira project, the issue type, or the label, and tune the search terms used to pull feedback from Infegy.

Frequently asked questions

Why monthly instead of weekly or daily?

Monthly cadence keeps the backlog from filling up with noise. You get a fresh batch of themes that are big enough to act on without burying PMs in a constant stream of one-off mentions. You can move it to weekly or quarterly if that fits your roadmap better.

Will every mention turn into a Jira ticket?

No. Only themes that cross your configured mention threshold become tickets. Smaller, one-off complaints stay in the underlying data so you can still review them, but they do not clutter the backlog.

Can I point this at a specific product line or brand?

Yes. The Infegy search is configurable, so you can scope it to a product name, a brand, a sub-brand, or a particular set of competitor terms. You can also narrow it by language or region.

What does the Jira ticket actually look like?

Each ticket uses the theme as the title and includes the synthesized description, the underlying user pain, who is asking, frequency relative to last month, and a few representative quotes in the body. It also gets a voice of customer label so it shows up in your existing triage filters.

Do I need a paid Slack or Jira plan?

Any standard Slack workspace and Jira Cloud project will work. You just need permission to post in the channel you choose and permission to create issues in the project you choose.