48.4k Log in Get started
Dashboard

What goes in a voice of customer overview dashboard?

A voice of customer overview combines the scores (NPS, CSAT), the requests (feature feedback and votes), and the response behavior (are customers heard, and told when things ship?) into one executive view. Its value comes from joining sources — survey tools, feedback boards, and support — on shared account and segment fields.

For: Product leadership, product ops, CX leads, and executives. Refresh: daily; weekly is fine for board-style reviews. Source: modeled feedback, survey, and product-usage tables in a Metabase-connected database.

Which cards belong on this dashboard?

  • Current NPS with response volume
  • Current CSAT with response volume
  • Feedback items received per week by source
  • Top feature requests by vote velocity
  • Feedback volume by product area and theme
  • Requests shipped last quarter
  • Close-the-loop rate on shipped requests
  • Feedback coverage: share of active accounts heard from

What data does this dashboard need?

  • NPS and CSAT responses with score, timestamp, and segment
  • Feedback items with status, product area, source, and created date
  • Votes at vote grain with voter company or account
  • Status-change history (or weekly snapshots) for shipped and closed items
  • Account dimension with segment and revenue for weighting

How do you build it?

  1. Sync the source tools into a database and retain raw IDs, timestamps, statuses, and segment fields.
  2. Build modeled tables at the grain this dashboard requires.
  3. Create one saved question per card and certify the shared models and definitions.
  4. Add dashboard filters for Date range, product area, segment, source, status.
  5. Show refresh time, and exclude internal and test activity from every headline card.

Example card SQL

Feedback volume by source and weekPostgreSQL
SELECT
  date_trunc('week', created_at) AS week,
  source,
  COUNT(*) AS feedback_items
FROM feedback_items
WHERE created_at >= CURRENT_DATE - INTERVAL '180 days'
GROUP BY 1, 2
ORDER BY 1, 2;

Dashboards

Feature request pipeline dashboardNPS & CSAT trends dashboardSurvey performance dashboardFeature adoption & engagement dashboardSession frustration signals dashboard

Integrations

Product & customer insights integrationsPendo + MetabaseProductboard + MetabaseAha! + MetabaseCanny + MetabaseTypeform + MetabaseSurveyMonkey + MetabaseQualtrics + MetabaseFullstory + MetabaseContentsquare + MetabasePostHog + MetabaseAmplitude + Metabase

Metrics

Net Promoter ScoreCSATSurvey response rateSurvey completion rateFeedback vote velocityTime to close the loopFeature adoption rateRage-click rate

Analytics

Product feedback analytics

FAQ

How is this different from an NPS dashboard?
NPS is one input. A voice of customer view puts scores next to what customers actually ask for (requests and votes) and whether the team responds (close-the-loop rate), so leadership sees the whole conversation, not one number.
Do I need every source connected on day one?
No. Start with your feedback board and one survey source, and add support tickets and in-app NPS later — the dashboard's card layout doesn't change, the volume cards just gain sources.