Weekly Customer Feedback Report Template (and How to Automate It)

Six sections, in this order, each answering one question your reader has.

Three short lists close the report and keep it honest: Follow-up from last week, Still open (big themes with no change, one line each), and Notes on the data (missing sources, failed syncs). Leave out all-time totals, a chart per theme, and unexplained sentiment scores; they fill space without telling anyone what to do. If sentiment matters for a theme, track it the way how to track customer sentiment over time describes and report only the change.

Paste this into a doc, a Slack canvas, or a Notion page. Replace the brackets, and delete any line you have nothing real to put on.

# Customer Feedback Weekly: [Mon date] to [Sun date]
Scope: [All customers / one segment]
Sources: [Tool (items)], [Tool (items)], [Tool (items)]
Owner: [Name]

## Headline
[One sentence: the biggest change this week, with a number and the segment it affects.]

## Top Changes
1. [Theme]: [New / Rising / Falling]. [X] accounts this week vs. a 4-week average of [Y]. [Segment, ARR, or renewal note.] ([link])
2. [Theme]: ...
3. [Theme]: ...

## New and Rising Themes
| Theme | Status | Accounts this week | 4-week avg. | Segments | Evidence |
|---|---|---|---|---|---|
| [Theme] | New | [n] | [n] | [Segment (n), Segment (n)] | [link] |
| [Theme] | Rising | [n] | [n] | [Segment (n)] | [link] |

## Segment Notes
- [Segment]: [what is different for these customers this week]
- [Segment]: No change this week.

## Quotes
- "[Verbatim quote]" ([role], [segment], [source + link], [date])
- "[Verbatim quote]" ([role], [segment], [source + link], [date])
- "[Verbatim quote]" ([role], [segment], [source + link], [date])

## Decisions Needed
- [Question with a yes/no or A/B answer]? Owner: [name]. Needed by: [date]. Evidence: [link]
- [Or: No decisions needed this week.]

## Follow-Up From Last Week
- [Last week's decision or fix]: [status]. [What feedback shows since.] [Customers told: yes/no]

## Still Open (No Change)
- [Theme]: [n] accounts a week, steady for [n] weeks. [Roadmap status.]

## Notes on the Data
- [Source that went quiet or failed to sync, holiday weeks, imports still processing]

Compare this week with the average of the prior four weeks, not with last week alone, because one week swings with holidays, outages, and big rollouts. Four weeks is shorter than the eight-week baseline in the trending guide on purpose: this report flags what is worth discussing now, so a Rising label means "look at this," not "confirmed trend." These rules of thumb suit a team that sees roughly 50 to 500 feedback items a week:

• New: no accounts in the prior four weeks, and at least two this week.
• Rising: at least three accounts this week, and at least 1.5 times the four-week average.
• Falling: half the four-week average or less, two weeks running.
• Steady: everything else. It goes under "Still open" as one line.

Count each account once: an admin who files four tickets and posts in Slack is one account. Below about 10 accounts, print counts, never percentages; two accounts becoming five reads as "+150%." Before you escalate a Rising theme as a trend, check it against the eight-week rules in how to tell which support ticket pain points are trending.

Block 30 minutes on Monday morning, before your weekly product meeting, so the report sets its agenda. Use the same Monday-to-Sunday window every week. The time box assumes feedback already lands in one place with account and segment attached; if it doesn't, start with how to centralize customer feedback.

Step 1: Pull Last Week's Feedback (10 Minutes)

• Filter every source to the same window: tickets, the Slack feedback channel, call notes, and survey comments.
• Write each source's item count next to last week's. A source that drops to zero usually means a broken sync or a tagging lapse, not happy customers, so flag it under Notes on the Data.
• Note any release, outage, or price change that could explain a spike.

Step 2: Find What Changed (10 Minutes)

• Put each theme's unique accounts this week next to its four-week average, and apply the New, Rising, Falling, and Steady labels.
• If more than three themes qualify, keep the three with the most at stake. Segment, ARR, and renewals in the next 90 days break ties.
• Check last week's decisions. If a fix shipped, did its theme fall?

Step 3: Write the Quotes, Decisions, and Headline (10 Minutes)

• Quotes: pick one per top change, the most specific line rather than the angriest. "The export spins for ten minutes, then gives me an empty file" tells engineering more than "your product is broken."
• Decisions: phrase each as a yes/no or A/B question, with an owner and a date. If nothing needs deciding, say so.
• Headline: write it last. One sentence with a number, a segment, and the likely cause if you know it.

This example is illustrative: the company, numbers, and quotes are invented. It is a B2B SaaS company with about 300 customers, reporting on October 26 to November 1, 2026:

# Customer Feedback Weekly: Oct 26 to Nov 1
Scope: All customers
Sources: Zendesk (142), Intercom (64), Slack #customer-feedback (31), Gong (9 calls), NPS (48)
Owner: Priya (PM)

## Headline
CSV export timeouts rose from 2 accounts a week to 9 after the Oct 27 reporting release. Six are Enterprise, and two of those renew before December 31.

## Top Changes
1. Export timeouts: Rising. 9 accounts vs. 2 average. 6 Enterprise, 2 renewing this quarter. (link)
2. SSO setup confusion: New. 3 accounts, all trials in their first week. (link)
3. Bulk edit requests: Falling. 1 account vs. 5 average since bulk edit shipped Oct 14. (link)

## New and Rising Themes
| Theme | Status | Accounts this week | 4-week avg. | Segments | Evidence |
|---|---|---|---|---|---|
| Export timeouts | Rising | 9 | 2 | Enterprise (6), Mid-market (3) | link |
| SSO setup confusion | New | 3 | 0 | Trial (3) | link |

## Segment Notes
- Enterprise: export timeouts are now this segment's top theme.
- Trial: SSO confusion is the only new theme. Two of three accounts opened a ticket on day one.
- SMB: No change this week.

## Quotes
- "The export spins for ten minutes, then gives me an empty file. I present to our board tomorrow." (Finance lead, Enterprise, Zendesk ticket, Oct 28)
- "I couldn't tell if SSO gets set up in your app or in our identity provider." (IT admin, Trial, Gong call, Oct 30)
- "Bulk edit saved me an afternoon." (Ops manager, Mid-market, NPS comment, Oct 29)

## Decisions Needed
- Roll back the Oct 27 export change, or ship a fix by Nov 6? Owner: Sam (Eng lead). Needed by: Tue Nov 3.
- Add an SSO step to the trial checklist this sprint? Owner: Priya. Needed by: Thu Nov 5.

## Follow-Up From Last Week
- Bulk edit (shipped Oct 14): requests fell from 5 accounts a week to 1. All 11 requesting accounts were told.

## Still Open (No Change)
- Mobile app speed: 4 accounts a week, steady for 6 weeks. Planned for Q1.

## Notes on the Data
- Intercom sync failed Oct 29 to 30, so about two days of chats are missing.

Notice what the report skips. Mobile app speed is the biggest theme by volume, but nothing changed, so it gets one line. The Intercom gap gets a note, because two missing days can make a theme look like it fell.

Write one report and let each reader stop where they need to. Separate versions triple the work and drift apart within a month.

Post it in Slack with the doc linked, so pushback stays in one thread. Never cut the follow-up section to save space: it shows support, success, and sales that logging feedback leads somewhere, and without it they log less. When a fix ships, tell the customers who asked and record it there.

Give the report one owner, usually a PM or product operations lead, and don't rotate it. Whoever wrote last week's report is the one who notices this week is different.

Automate the pulling, counting, and quote-finding; keep the headline and decisions for a person. As a rule of thumb, good automation turns 30 minutes of assembly into 10 minutes of review.

If you start from an export, this prompt keeps the model honest about counts and quotes:

You are helping me write our weekly customer feedback report.

Files:
- feedback_this_week.csv: date, source, account, segment, arr, theme, quote, link
- theme_accounts_last_4_weeks.csv: week, theme, unique_accounts

Rules:
- Count unique accounts per theme from the account column. Never count rows or mentions.
- Label each theme: New (0 accounts in the prior 4 weeks, 2+ this week), Rising (3+ accounts and at least 1.5x the 4-week average), Falling (half the average or less), or Steady.
- Use only quotes that appear word for word in the file, each with its link.
- If a section has nothing new, write "No change this week."
- Do not write the Headline or Decisions Needed. Instead, list up to three questions the data raises.

Fill in this template:
[paste the template]

Whatever you pick, keep one human step: someone reads the draft, writes the decisions, and sends it. If you can schedule the prompt, have the draft ready by 8 a.m. Monday and reviewed by 9.

• Percentages on tiny numbers. "+200%" on three accounts starts a fire drill. Print the counts.
• Paraphrasing inside quote marks. Trim with an ellipsis if you must. Once someone finds one quote that isn't verbatim, they stop trusting the rest.
• Padding quiet weeks. "No change this week" is information. Recycling last month's complaints teaches people to stop reading.
• No decision ask. Without a question and an owner, the report becomes the email everyone archives by week three.
• Skipping the data notes. A source that failed to sync looks exactly like a theme that fell.