Deck

Customer Feedback Audit: What Your Team Actually Knows

Audit every feedback source, integration, and theme in Deck, find the gaps, and get one next step for each. Run it in the app or hand it to your AI agent.

By Matt TeixeiraUpdated

Run it in Deck
Time to Run
15 min
Uses
Integrations,Themes,MCP Server
You Get
Customer Feedback Audit Checklist
Run It
In Deck or with your agent

What Is a Customer Feedback Audit?

A customer feedback audit checks where your feedback comes from, whether each source is still flowing, and which parts of the product it covers. It ends with a short list of gaps, such as a broken integration or a theme no channel feeds, and one next step for each. Run it before every planning cycle.

Why Teams Guess What Customers Are Saying

Before a planning cycle, someone asks what customers are telling you, and the honest answer is a guess. Support tickets live in one tool, interview notes in another, and the survey export nobody opened. You cannot tell which channels are missing, which ones broke last month, or whether a quiet theme is quiet because customers are happy or because nothing is feeding it.

How Deck Audits Feedback Coverage for You

Deck already counts what it has: every source, every connected integration, the themes those sources produce, and the credits left to process more. The audit reads those numbers instead of asking the team to remember them. Every gap it finds comes with one next step, and running the audit changes nothing in your workspace.

How to Run a Customer Feedback Audit in Deck

Run it yourself in Deck, or hand it to your AI agent. Same steps, same result.

  1. 01

    Open the Setup Checklist

    Start from the Setup checklist in the app header. It shows which setup jobs are still open, such as uploading feedback, connecting an integration, or setting up MCP, and links straight to the page that finishes each one.

  2. 02

    Check Which Sources Feed Deck

    Open Settings → Integrations and look at the state of each connection. An integration that needs attention is a gap, even if it worked last quarter. Then check Manage → CSV Uploads and Manage → User Interviews for imports with failed or waiting rows.

  3. 03

    Look at the Credits Left

    Open Settings → Billing. If credits are low, new feedback can wait instead of being processed. Fix that before you trust any count in the next step.

  4. 04

    Read Coverage in Themes

    Open Visualize → Themes and sort by insight count. The biggest themes show where feedback is concentrated. Themes with few or no insights are either solved problems or channels you are not hearing from yet.

  5. 05

    Turn Each Gap into One Next Step

    Write the gaps down in order of impact: no second channel, a broken integration, waiting work, empty themes. Give each one owner and one action, such as reconnecting Intercom or importing last quarter's interviews.

Feedback Audit Template

customer-feedback-audit-checklist.md
## Sources
[ ] More than one feedback channel feeds Deck (support, interviews, surveys, sales calls, in-app)
[ ] No CSV or interview import has failed or waiting rows
[ ] Last import or sync date: ________
## Integrations
[ ] Every connected integration is active, none need attention
[ ] Slack channels you care about have Deck invited
## Credits
[ ] Credits are not low, and no feedback is waiting for credits
## Coverage
[ ] Top 3 themes by insight count: ________ / ________ / ________
[ ] Themes with no insights reviewed (solved, or a missing channel?)
[ ] Opportunity Backlog has items with enough evidence to act on
## Gaps (most important first)
1. Gap: ________  Next step: ________  Owner: ________
2. Gap: ________  Next step: ________  Owner: ________
3. Gap: ________  Next step: ________  Owner: ________
Plain text. Pastes into Docs, Notion, or your agent.21 lines

Frequently Asked Questions

Before each planning cycle, and after you connect or disconnect a tool. It takes minutes because Deck already has the counts.

No. It only reads. Fixing a gap, such as reconnecting an integration, is a separate step you choose to take.

Anyone with access can run it. Some fixes, like changing integrations, settings, or billing, need an organization admin. When the agent runs it for a member, it writes those fixes as requests to send to an admin.

Only one source type, a broken or idle integration, failed or waiting imports, low credits, themes with no insights, or a backlog where most items lack enough evidence.

Yes. With Deck MCP connected, paste the prompt on this page. The agent reads the same numbers through Deck's tools and writes the audit in five sections: sources, integrations, credits, coverage, and gaps.