What problem does it solve?
Organizations collect far more feedback than they read. Survey platforms, app store reviews, social media, chat logs and call recordings produce tens of thousands of comments a week (Majid Al Futtaim Retail's marketing team processed 60,000 to 70,000 customer responses a week by hand, according to Microsoft), and most of the value sits in the free text: why a customer gave a low score, what broke, what they wanted instead. Analysts read a sample, tag it by hand against a codebook that drifts over time, and report weeks later, by which time the issue has cost more customers.
Keyword based text analytics helped with volume but struggled with sarcasm, mixed sentiment, several topics in one comment, other languages and new themes nobody had a keyword for. Language models change the economics: every comment can be classified against the organization's own taxonomy, summarized per theme and linked to operational data, so a product owner sees the problem in days. The discipline that remains is human: someone has to own each theme, decide what it means and close the loop with customers.
How does it work?
- Collect every source. Survey exports, reviews, social mentions, chat logs and transcribed calls land in one store with their metadata (channel, product, date, score, segment).
- Clean and protect. Personal data is masked before analysis; duplicates, spam and empty answers are removed.
- Classify against your taxonomy. Each comment is tagged with one or more themes from the organization's own codebook, a sentiment per theme and, where present, a suggested action or a statement of customer effort. New clusters that fit no theme are flagged for review.
- Quantify and explain. Themes are joined to scores and operational data (store, product, journey step), so dashboards show which themes drive detractors and how they trend.
- Summarize for owners. Each theme owner gets a short summary with representative, anonymized quotes and the change against last period.
- Close the loop. Individual comments that need a response (a complaint, a safety issue, a vulnerable customer) are routed to the right team; systemic fixes are tracked to completion.
- Audience
- Back office
- Autonomy
- Copilot
- Adoption
- Mainstream
- Channels
- Internal tools, API and system to system
What is it worth?
Benchmarks are computed from the public deployments below: one data point per organization per KPI, with who made each claim.
| KPI | Median | Reported range | Data points | Claimed by |
|---|---|---|---|---|
| Accuracy | Too few to pool | 84% | 1 | 1 vendor |
| Cost reduction | Too few to pool | about 95% | 1 | 1 vendor |
| Cycle time | Not pooled | 3 hours | 1 | 1 vendor |
| Cycle time | Not pooled | 1 minutes | 1 | 1 vendor |
Value drivers: Customer experience, Employee productivity, Speed and cycle time, Revenue growth.
Indicative value
A consumer brand or public service that receives 300,000 free text feedback items a year
USD 72,000 to USD 378,000
Manual feedback coding cost avoided per year
How this is calculated
Formula: feedbackItems * hoursPerItem * shareAutomated * analystCost. The low scenario uses every low input, the high scenario every high input.
| Input | Low | High | Basis |
|---|---|---|---|
| Free text feedback items per year feedbackItems, items per year | 300,000 | 300,000 | The reference organization, across surveys, reviews and chat. |
| Analyst time to read and code one item by hand hoursPerItem, hours per item | 0.01 | 0.02 | Editorial assumption of 36 to 72 seconds per comment. Replace with your own coding time. |
| Share of manual coding the AI replaces shareAutomated, fraction of items | 0.6 | 0.9 | Conservative against the benchmarks on this page (Google Cloud reports that SBF Group eliminated manual data analysis work and cut annual costs by about 95%), because theme review and quality checks stay with people. |
| Fully loaded analyst cost analystCost, USD per hour | 40 | 70 | Editorial assumption, replace with your own. |
What it leaves out: Counts only the analyst time to read and code comments, and assumes the organization would otherwise read all of them (most read a sample). It leaves out the platform cost and the larger value: issues found and fixed weeks earlier, and churn or complaints avoided.
Who already uses it?
10 public deployments, strongest evidence first. Grades: A regulator or audit, B the organization itself, C vendor case study, D anonymous or estimate.
U.S. Department of Housing and Urban Development
United States · Government and public sector · 2024
The customer experience team in HUD's Office of the Chief Financial Officer runs a Voice of the Customer application that applies transcription, speech and text analytics to customer feedback surveys and to contact centre calls and chats. It produces dashboards that trend sentiment and identify the key drivers of customer sentiment and service delivery performance, which HUD uses to manage its programs and contact centre providers. The department lists it as deployed since August 2024; no outcome figures are published.
No outcome disclosed.
U.S. Social Security Administration
United States · Government and public sector · 2021
SSA's customer survey system includes an AI text analytics capability that reads the free text of survey answers and returns sentiment ratings, categorized themes, suggested actions, customer effort indicators and machine translation. The agency uses it to spot emerging trends early and to see the positive and negative drivers in customer interactions. It is listed as deployed since August 2021; no outcome figures are published.
No outcome disclosed.
Community Health Network
United States · Healthcare · 2026
Community Health Network, an Indianapolis based not for profit health system, had managers spending hours manually reviewing caregiver comments and building action plans from them. As one of the first organizations to adopt Qualtrics AI, it gave managers AI generated summaries, identified themes and recommended next steps over caregiver feedback. Qualtrics reports that what once took hours of manual comment review now happens in minutes, and that giving leaders the ability to analyze caregiver feedback instantly drove a 91% increase in caregiver survey response rate.
No outcome disclosed.
Elevance Health
United States · Healthcare · 2026
Elevance Health, a health insurer, could not see a member's dissatisfaction until a CAHPS survey result arrived up to eighteen months later, by which time the member may already have disenrolled. It built a unified, AI powered member view with Qualtrics that turns every survey, call and chat signal into a real time flag on at risk members, feeding a closed loop recovery process that connects each signal to a specific intervention. What began as a proof of concept in January 2024 has grown into a program that Qualtrics reports now analyzes more than 10 million member calls, chats and surveys a year.
- Interactions handled: at least 10 million, per year
"What began as a proof of concept in January 2024 now analyzes more than 10 million calls, chats, and surveys every year, powering closed-loop recovery that connects every member signal to a specific intervention."
Claimed by: vendor
SBF Group
Brazil · Retail and ecommerce · 2026
SBF Group (Grupo SBF), the Brazilian sporting goods retailer behind Centauro and Fisia, the official Nike distributor in Brazil, uses Google Cloud AI to analyse customer feedback and customer satisfaction (NPS) forms. Google Cloud reports that the solution eliminated manual data analysis work, cut annual costs by about 95%, raised feedback classification accuracy from 16% to 84% and made it possible to process daily feedback that previously went unanalysed.
- Cost reduction: about 95%, per year (the cost base is not specified)
"The solution reduced annual costs by approximately 95% and eliminated manual data analysis work, in addition to increasing the accuracy rate in feedback classification from 16% to 84%, allowing daily processing of information that was previously not analyzed."
Claimed by: vendor - Accuracy: 84%
"The solution reduced annual costs by approximately 95% and eliminated manual data analysis work, in addition to increasing the accuracy rate in feedback classification from 16% to 84%, allowing daily processing of information that was previously not analyzed."
Claimed by: vendor
Majid Al Futtaim Retail
United Arab Emirates · Retail and ecommerce · 2025
Majid Al Futtaim Retail, which runs Carrefour in the Middle East, Africa and Central Asia, built a text analytics solution called "Excellence" on Azure OpenAI Service. Before it, the marketing team manually processed 60,000 to 70,000 customer responses a week. The solution captures customer emotion and categorizes feedback by aspects such as delivery, quality, hygiene and checkout queue times, generating actionable insights for improvement. Microsoft reports that feedback processing fell from seven days to three hours; the same story quotes the Chief Digital Officer as saying it now takes three to four minutes.
- Cycle time: 3 hours
"The company saved USD1 million annually, cut feedback processing time from seven days to three hours, and improved geographic targeting, boosting efficiency with AI-driven solutions."
Claimed by: vendor
Mattel
United States · Manufacturing · 2025
Mattel built a feedback classification system on BigQuery, Vertex AI and Gemini that analyses millions of consumer feedback points from customer reviews, social media and the contact centre. Google Cloud reports that analysis time fell from a month to a single minute and that data processing capacity rose a hundredfold.
- Cycle time: 1 minutes
"The system analyzes millions of feedback points from a diverse range of sources (customer reviews, social media, contact center) in seconds — delivering a staggering 100x increase in data processing capacity and slashing analysis times from a month to a single minute."
Claimed by: vendor
Great Southern Bank
Australia · Banking · 2024
Great Southern Bank, an Australian customer owned bank serving more than 414,000 customers, expanded its existing NICE CXone contact centre platform with AI powered Interaction Analytics, alongside a revamped IVR and omnichannel routing. With Interaction Analytics the bank automatically measures call drivers and pinpoints core issues on demand, instead of manually searching for calls that match specific criteria, giving it a view of trends and customer sentiment across all interactions.
No outcome disclosed.
Open Network Exchange (ONE)
United States · Travel and hospitality · 2024
Open Network Exchange (ONE), a US travel and loyalty company, used NICE's CXone XO interaction analytics to analyze its customer service calls. The analysis surfaced that 30 to 40 percent of calls were payment related, an insight ONE's Ryan Romero, Senior Vice President of Global Technology Strategy and Innovation, called the lightbulb moment. ONE then used that finding to prioritize a separate self service, conversational IVR project for payments, which is not the deployment recorded here.
No outcome disclosed.
TruGreen
United States · Cross industry · 2024
TruGreen, North America's largest lawn care company, relied on reps picking a reason code from a dropdown after a cancellation call to understand why customers left, and that data pointed to price. In 2024 it partnered with Qualtrics to deploy AI powered conversation analytics across 100% of its care and sales calls, analyzing what customers said in their own words across 1.4 million cancellation calls. That analysis showed that 71% of cancellations were driven by service quality and experience rather than price, which redirected TruGreen's retention work toward the customer experience.
No outcome disclosed.
How do you implement it?
A model agnostic playbook: what to prepare, the order to build in, and what goes wrong.
Data you need
- Exports or APIs from survey, review, social listening and contact centre systems
- A theme taxonomy (codebook) agreed with the business, with an owner per theme
- Metadata that links feedback to product, location, journey step and score
- A labelled sample of a few hundred comments to measure classification accuracy
Systems to integrate
- Survey and experience management platforms
- Review sites, app stores and social listening tools
- Contact centre recordings and chat logs, with transcription
- Data warehouse and BI dashboards
- Case or CRM system for comments that need an individual response
Complexity: Low
Classifying text is a mature task and the data is usually already exported from survey and review tools. The effort goes into an agreed taxonomy, joining feedback to operational data, masking personal data and building the habit of acting on the output.
- 1
Agree the taxonomy before the model
Start from the themes the business already reports, add the top new clusters found in a sample, and name an owner for each. A model that classifies against themes nobody owns produces dashboards nobody acts on.
- 2
Build a labelled test set
Have two people code a few hundred real comments per language, resolve their disagreements, and use the set to measure accuracy per theme on every prompt or model change.
- 3
Mask personal data at intake
Remove names, account numbers and contact details before analysis and keep the link to the original record only where a response is needed.
- 4
Join feedback to operations
Link each comment to the store, product, order or journey step it concerns, so a theme can be traced to a cause rather than reported as a trend.
- 5
Route individual cases, report systemic ones
Send comments that are complaints, safety issues or signs of vulnerability to the teams that respond to individuals, and give theme owners a periodic summary with trend and quotes.
- 6
Review the codebook every quarter
Look at the unclassified cluster, retire themes that no longer occur and add new ones with an owner, then rerun the test set.
Guardrails
- Classification only against an approved taxonomy, with an explicit "other or new" bucket reviewed by people
- Personal data masked before comments reach a model or a dashboard
- Quotes shown to wide audiences are anonymized and checked
- Comments that indicate a complaint, a safety risk or a vulnerable customer are routed to a person, not only counted
- No inference of emotion from voice or face in call and video feedback without a separate legal assessment
KPIs to instrument
- Classification accuracy per theme and language on the labelled test set
- Share of feedback analysed (coverage) versus the previous sampling approach
- Time from feedback received to theme reported to its owner
- Share of themes with an owner and a tracked action
- Share of individual cases routed correctly (complaints, safety, vulnerability)
Human in the loop
Analysts own the taxonomy, check a weekly sample of classifications against the test set, and validate every theme before it is reported as a finding. Theme owners decide what action to take; the AI suggests, it does not commit changes to products or policies.
Common failure modes
- Dashboards without owners
- The analysis is excellent and nothing changes. Give every theme an owner and track actions to closure.
- Confident but wrong themes
- The model fits comments into the nearest theme and hides new issues. Keep a "new or other" bucket and review it.
- Sentiment that misses the point
- A positive score on a comment that describes a serious failure. Report themes and drivers, not sentiment alone.
- Personal data spread into reports
- Verbatim quotes with names or account details reach wide audiences. Mask at intake and review quotes before sharing.
What are the risks and rules?
EU AI Act
Depends on design
Classifying and summarizing text feedback is minimal risk. The tier changes if the system infers emotions from customers' voices or faces in calls or video: emotion recognition based on biometric data is listed as high risk in Annex III point 1(c) and triggers the Article 50(3) duty to inform the people exposed. Analysing feedback from employees to evaluate individual workers moves it towards Annex III point 4(b), and emotion recognition in the workplace is prohibited by Article 5(1)(f), except for medical or safety reasons.
Rules that apply
Guidance
- Regulation (EU) 2024/1689, the Artificial Intelligence Act (European Union, Europe). Official text on EUR-Lex. Annex III point 1(c) lists emotion recognition systems and point 4(b) systems that monitor and evaluate the performance and behaviour of workers; Article 5(1)(f) prohibits emotion recognition in the workplace and in education, relevant when employee feedback or staff calls are analysed; Article 50(3) requires deployers of emotion recognition systems to inform the people exposed to them.
Controls to put in place
- Data protection impact assessment where feedback includes personal data or call recordings
- Documented taxonomy with owners and a change log
- Accuracy testing on a labelled set per language before each change
- Retention limits on raw verbatims and recordings
- Access control on dashboards that show individual comments
Frequently asked questions
- How accurate is AI at classifying customer feedback?
It can be accurate enough to replace most manual coding, but only your own labelled comments tell you whether it is. Google Cloud reports that SBF Group raised feedback classification accuracy from 16% to 84% with Google Cloud AI. Measure accuracy per theme and per language, because averages hide weak themes.
- How much faster is AI feedback analysis?
Days become minutes or hours. Microsoft reports that Majid Al Futtaim cut feedback processing for Carrefour from seven days to three hours (the same story quotes its Chief Digital Officer as saying three to four minutes), and Google Cloud reports that Mattel cut analysis from a month to a minute. The binding constraint then becomes how fast owners act.
- Is sentiment analysis of customer calls high risk under the EU AI Act?
Analysing the words people say or write is not. Inferring emotions from their voice or face is emotion recognition, which Annex III lists as high risk, with a duty under Article 50(3) to inform the people exposed. Inferring the emotions of your own staff, such as contact centre agents, is prohibited by Article 5(1)(f) except for medical or safety reasons. Keep voice analysis to transcripts unless you have done that assessment.
- How is this different from complaints root cause analysis?
Complaints root cause analysis works on regulated complaints, where every case must be handled and systemic causes reported. Feedback analysis covers the much larger stream of surveys, reviews and comments, most of which are not complaints, to find what drives satisfaction and where to invest.
How to cite this page
Blits.ai AI Use Case Library, "AI for voice of the customer and feedback analysis", last verified 27 September 2026, https://www.blits.ai/ai-use-cases/customer-feedback-analysis. Licensed under CC BY 4.0. Method: how we verify use cases.
Changelog
- 29 September 2026: Added deployments: Elevance Health, TruGreen, Community Health Network.
- 27 September 2026: First published