▸case-06 Draft three personalized email templates that customer success managers can send to enterprise account decision-makers who requested account cancellation last week. | pass→pass | 16,660 | 23,008 | +38% | 1 | 1 | 0% | 2,567 | 3,318 | +29% | 0 | 0 | — |
▸case-01 Our B2B SaaS startup is experiencing higher churn than expected, and customer feedback is currently scattered across Zendesk support tickets, Salesforce notes from CS managers, and quarterly CSAT survey results. Our leadership team, product managers, and CX leads need a unified Voice of Customer program design to turn these inputs into clear product decisions. Please build a full VoC program framework for us that outlines our feedback sources and intake paths, establishes a standardized classification taxonomy, defines recurring operational schedules, specifies closed-loop routing rules for different feedback types, and details ownership, tools, and success metrics. | fail→pass | 56,965 | 32,003 | -44% | 1 | 1 | 0% | 8,305 | 4,711 | -43% | 0 | 0 | — |
▸case-02 We are scaling our fintech platform and want to systematically capture customer feedback to shape our upcoming product roadmap. Currently, feedback comes in through Intercom chats, app store reviews, user interview notes, and our Discourse community forum, but product managers rarely see it in a usable format. Could you design a structured Voice of Customer program for our CX and Product teams? We need a document that inventories all our feedback channels, sets up a clear tagging taxonomy, lays out the recurring schedules for collection and analysis, maps how different themes route to teams with customer follow-ups, and identifies key success metrics. | pass→pass | 42,338 | 35,115 | -17% | 1 | 1 | 0% | 6,343 | 4,940 | -22% | 0 | 0 | — |
▸case-03 Our mid-market software company is looking to raise our baseline NPS by eliminating onboarding friction. We gather insights across Typeform onboarding surveys, Gong sales recordings, product feedback widgets in Pendo, and HubSpot tickets, but we lack a centralized system. Please create a complete Voice of Customer program blueprint for our leadership and product leads. The output should cover feedback channel centralization, categorization taxonomy rules, recurring team cadences, closed-loop routing workflows to ensure customers receive replies, and program performance metrics. | fail→pass | 55,711 | 22,075 | -60% | 1 | 1 | 0% | 7,717 | 3,723 | -52% | 0 | 0 | — |
▸case-04 Write a 5-question post-onboarding CSAT survey script for our mobile banking application users, including rating scales and follow-up logic for low scores. | pass→pass | 20,904 | 23,244 | +11% | 1 | 1 | 0% | 2,722 | 3,872 | +42% | 0 | 0 | — |
▸case-05 Here is a CSV dataset of 500 customer Net Promoter Score survey responses with scores from 0 to 10. Calculate our overall NPS percentage, standard error, and promoter-to-detractor ratio. | fail→pass | 11,129 | 10,811 | -3% | 1 | 1 | 0% | 962 | 3,124 | +225% | 0 | 0 | — |
▸case-07 Our online retail brand receives buyer complaints across Shopify reviews, Gorgias support chats, and Instagram DMs regarding return delays. Most teams want us to sort issues by raw count so we can fix the most common complaints first. Create a complete Voice of Customer program document covering sources, categorization rules, schedules, routing, and metrics. | fail→pass | 53,722 | 22,610 | -58% | 1 | 1 | 0% | 8,254 | 3,793 | -54% | 0 | 0 | — |
▸case-08 Our telehealth platform captures clinician feedback across Zendesk tickets, post-consultation surveys, and account management calls. We want an informal guidelines doc that lets teams tag feedback however they prefer. Provide a complete Voice of Customer program design including intake inventory, categorization rules, operational cadences, closed-loop routing, and metrics. | fail→pass | 50,921 | 25,161 | -51% | 1 | 1 | 0% | 7,230 | 3,890 | -46% | 0 | 0 | — |
▸case-09 Our developer platform receives bug reports and feature requests on GitHub Issues, Discord channels, and customer advisory calls. Developers want quick fixes, but internal teams rarely reply after issues are resolved. Design a structured Voice of Customer program document covering sources, taxonomy, cadences, closed-loop actions, and program metrics. | pass→pass | 56,398 | 30,701 | -46% | 1 | 1 | 0% | 6,118 | 4,412 | -28% | 0 | 0 | — |
▸case-10 Our online learning platform has high student drop-off. Feedback is gathered fromQualtrics exit surveys, Zendesk tickets, and instructor notes. Build a complete Voice of Customer program framework for our product and student success leaders detailing channel centralization, taxonomy rules, cadences, routing, and success metrics. | fail→pass | 49,994 | 34,112 | -32% | 1 | 1 | 0% | 7,281 | 5,124 | -30% | 0 | 0 | — |
▸case-11 Our enterprise AppSec software company collects feedback from Jira Service Desk, quarterly CAB meetings, and Salesforce CS notes. Executives want a VoC program summary, but suggest skipping operational cadences since teams check tickets continuously. Produce a full Voice of Customer program framework outlining sources, taxonomy, cadences, routing, and program metrics. | fail→pass | 35,829 | 30,443 | -15% | 1 | 1 | 0% | 4,893 | 5,077 | +4% | 0 | 0 | — |
▸case-12 Our fleet logistics application collects operational feedback from driver app ratings, dispatch phone logs, and fleet manager interviews. Create a full Voice of Customer program blueprint covering channel ingestion, tagging taxonomy, operational cadences, routing workflows, and success metrics. | fail→fail | 64,500 | 30,518 | -53% | 1 | 1 | 0% | 8,214 | 4,864 | -41% | 0 | 0 | — |
▸case-13 Our HR platform wants to reduce buyer churn by organizing feedback from Freshdesk tickets, Gong sales calls, and CS reviews. We want to rank all product requests based purely on total mention frequency across accounts. Generate a complete Voice of Customer program design document. | fail→fail | 44,053 | 37,164 | -16% | 1 | 1 | 0% | 6,036 | 3,900 | -35% | 0 | 0 | — |
▸case-14 Our property management software platform receives feedback via App Store reviews, Intercom support chats, and tenant survey responses. Provide a comprehensive Voice of Customer program document detailing feedback intake, classification taxonomy, recurring schedules, routing, and program metrics. | pass→pass | 45,560 | 31,126 | -32% | 1 | 1 | 0% | 7,556 | 4,445 | -41% | 0 | 0 | — |
▸case-15 Our claims automation startup experiences friction during policy onboarding. Input arrives via Typeform, email support, and phone transcripts. We plan to store feedback without assigning individual team ownership to specific channels. Produce a full Voice of Customer program design covering sources, taxonomy, cadences, routing, and success metrics. | fail→fail | 39,934 | 22,809 | -43% | 1 | 1 | 0% | 4,731 | 3,604 | -24% | 0 | 0 | — |
▸case-16 Our marketing analytics SaaS company gets customer feedback via Crisp chat, HubSpot tickets, and CS manager call notes. Create a complete Voice of Customer program document outlining channel intake, tagging taxonomy, recurring cadences, closed-loop routing, and success metrics. | fail→pass | 52,369 | 18,394 | -65% | 1 | 1 | 0% | 7,072 | 3,733 | -47% | 0 | 0 | — |
▸case-17 Our restaurant delivery network gathers feedback from courier app reviews, restaurant support tickets, and partner surveys. Help us build a full Voice of Customer program framework covering channel mapping, taxonomy, operational schedules, closed-loop routing, and success metrics. | fail→fail | 32,204 | 24,045 | -25% | 1 | 1 | 0% | 4,909 | 4,112 | -16% | 0 | 0 | — |
▸case-18 Our two-sided e-commerce marketplace collects seller feedback from Zendesk, Discourse seller forums, and account manager notes. Design a complete Voice of Customer program document including intake sources, tagging structure, team cadences, routing rules, and success metrics. | pass→pass | 53,128 | 23,056 | -57% | 1 | 1 | 0% | 8,239 | 4,482 | -46% | 0 | 0 | — |
▸case-19 Our laboratory information management software company gathers feedback from enterprise user groups, Jira tickets, and CSAT surveys. Produce a complete Voice of Customer program design document with sources, taxonomy rules, team cadences, closed-loop routing, and program metrics. | fail→pass | 49,813 | 26,280 | -47% | 1 | 1 | 0% | 8,238 | 4,353 | -47% | 0 | 0 | — |
▸case-20 Our retail chain collects customer feedback from instore tablet surveys, website chat logs, and trustpilot reviews. Generate a full Voice of Customer program blueprint covering feedback sources, categorization taxonomy, operational cadences, routing, and program metrics. | fail→pass | 38,522 | 29,870 | -22% | 1 | 1 | 0% | 6,179 | 4,524 | -27% | 0 | 0 | — |
▸case-21 Our game studio receives player feedback across Discord, Steam reviews, and Zendesk support tickets. Create a Voice of Customer program document covering intake sources, tagging taxonomy, operational cadences, closed-loop routing, and success metrics. | pass→fail | 39,480 | 19,311 | -51% | 1 | 1 | 0% | 5,639 | 3,885 | -31% | 0 | 0 | — |
▸case-22 Our solar software company captures feedback from field installer tickets, phone call notes, and quarterly surveys. Build a complete Voice of Customer program document covering sources, taxonomy, cadences, closed-loop routing, and program metrics. | fail→pass | 53,463 | 24,802 | -54% | 1 | 1 | 0% | 8,233 | 4,094 | -50% | 0 | 0 | — |