A well-built Qualtrics CX dashboard does three things: it shows the right metric to the right person at the right level of detail. Getting that balance right requires decisions about page structure, widget selection, filter strategy, and who sees what. This guide covers the practices that experienced CX teams apply to dashboards that stay useful after the first week.
Page Hierarchy: Build for Your Audiences
The most common Qualtrics CX dashboard mistake is building a single page that tries to serve everyone. Executives, programme managers, and frontline teams need fundamentally different views of the same data. Structure your dashboard with distinct pages for each audience rather than filtering a single page for different uses.
- Executive Summary — headline NPS or CSAT score, top-level trend, and key driver. No diagnostic detail. Maximum three to four widgets.
- CX Manager / Programme View — driver analysis, segment breakdown, response rate, and period-over-period comparison. This page answers "why is the number what it is."
- Frontline Ops / Team View — broken down by agent, location, or shift. Individual performance visible, actionable at the team level.
- Voice of Customer — open-text themes, sentiment, and verbatim comments for teams focused on qualitative signal.
- Quality / Compliance — question-level review, flagged responses, and individual records for QA and audit purposes.
Pirai AI Flow includes layout templates built for each of these audience types. Rather than building each page from scratch, you select the template and Flow fills in the real fields from your dashboard automatically.
Widget Selection for NPS, CSAT, and CES
The metric type should drive the widget type. Using the wrong widget for a metric makes the dashboard harder to read and less actionable.
| Metric | Primary Widget | Secondary Widget |
|---|---|---|
| NPS | Number Chart (score) | Breakdown Bar (Promoters, Passives, Detractors) |
| CSAT | Gauge Chart (against target) | Line Chart (trend over time) |
| CES | Number Chart (average) | Bar Chart (by touchpoint) |
| Open text | Word Cloud | Record Table (verbatims) |
| Response volume | Number Chart | Line Chart (daily or weekly) |
Filter Strategy
Page filters in Qualtrics should be applied consistently across all widgets on a page. A common issue is applying a date filter to some widgets but not others, creating inconsistent views within a single page. Before finalising a dashboard, review every filter on every page to confirm consistent application.
For multi-region or multi-segment programmes, build the base page once and clone it for each segment. Pirai AI Flow handles page cloning in a single instruction, including applying the segment-specific filter to each cloned page automatically.
Document Before Making Changes
Before modifying an existing dashboard, extract the current configuration as a CSV using the Dashboard Field Mapper. This gives you a rollback reference showing every field, widget type, and data source mapping in the current state. Changes made without documentation are difficult to reverse if the updated dashboard does not behave as expected.
Dev, Test, and Prod Consistency
CX programmes running across Dev, Test, and Production Qualtrics environments need consistent dashboard configurations. A field mapped in Dev that does not exist in Prod causes widget failures that are difficult to diagnose. Extract configurations from both environments using the Dashboard Field Mapper, then compare the CSVs with the Pirai AI CSV Comparator before promoting a dashboard to Production.
Dashboard review checklist before going live
- Every page has a clearly defined audience and no extraneous widgets
- Filters are applied consistently across all widgets on each page
- Multi-region pages have been cloned and segment filters verified
- Configuration has been extracted and documented as a CSV
- Dev and Prod configurations have been compared for field mapping consistency
- Executive page contains no more than four widgets
Frequently Asked Questions
There is no fixed number, but a well-structured CX dashboard typically has three to five pages: an Executive Summary, a CX Manager view with driver analysis, a Frontline Ops view broken down by agent or location, a Voice of Customer open-text page, and optionally a Quality or Compliance view. Each page should serve a clearly defined audience.
A Number Chart is the primary widget for displaying the overall NPS score. Pair it with a Breakdown Bar to show the distribution of Promoters, Passives, and Detractors, and a Line Chart to show the NPS trend over time.
Clone pages within the same dashboard for regional breakdowns. Separate dashboards create maintenance overhead when the programme changes. Cloning the base page and applying a region filter to each clone keeps the structure manageable. Pirai AI Flow handles page cloning with a single instruction.
Use the free Pirai AI Dashboard Field Mapper to extract all field types and data source mappings as a CSV in under two minutes. This gives you a complete reference of the current configuration before any changes are made.
Build Your CX Dashboard Faster with Flow
From document to platform-ready survey in minutes. No manual programming required.
Learn About Flow