▸case-01 We are designing an automated intake tagging schema for incoming Zendesk support tickets and survey responses to capture qualitative feedback. Our team wants to keep it simple with just two fields: Topic and Sentiment Score. Recommend the complete set of required tagging dimensions for a voice-of-customer taxonomy. | fail→pass | 18,649 | 24,055 | +29% | 1 | 1 | 0% | 2,729 | 2,923 | +7% | 0 | 0 | — |
▸case-02 Our CS team wants to compile all monthly feedback into an executive digest slide deck first, and then after leadership reviews the digest, route urgent customer issues to product managers. What is the correct operational sequence for handling critical feedback relative to insight packaging? | pass→pass | 11,313 | 7,968 | -30% | 1 | 1 | 0% | 1,671 | 1,424 | -15% | 0 | 0 | — |
▸case-03 We logged an urgent customer product complaint about API rate limits into our action tracking board. To consider the closed-loop tracking step complete, is it sufficient to mark the internal Jira engineering ticket as 'Resolved'? | pass→pass | 10,235 | 6,869 | -33% | 1 | 1 | 0% | 1,497 | 1,183 | -21% | 0 | 0 | — |
▸case-04 Our engineering lead suggests setting up a fully automated pipeline using LLM classifiers to automatically tag and route all incoming NPS verbatim comments directly to engineering Jira boards without human intervention to minimize staff overhead. How should automated feedback ingestion be configured? | pass→pass | 16,687 | 17,193 | +3% | 1 | 1 | 0% | 2,426 | 2,621 | +8% | 0 | 0 | — |
▸case-09 A critical bug report containing urgent negative sentiment from a top-tier enterprise account was tagged in our feedback intake system. Our CS rep wants to assign the notification exclusively to the junior frontline support rep assigned to the ticket. Which stakeholder roles should receive critical feedback notifications? | pass→pass | 11,520 | 7,018 | -39% | 1 | 1 | 0% | 1,621 | 1,278 | -21% | 0 | 0 | — |
▸case-05 During our quarterly feedback intake review, we identified fifty high-scoring positive CSAT comments praising our recent UI redesign. Our analyst recommended filtering these out so the team can focus 100% on negative friction points. How should positive customer sentiment comments be utilized? | pass→pass | 14,253 | 10,669 | -25% | 1 | 1 | 0% | 1,903 | 1,707 | -10% | 0 | 0 | — |
▸case-06 An enterprise account executive submitted an aggressive customer call transcript where a CIO threatens to churn within 48 hours due to repeated platform outages. Should this urgent churn threat be handled solely through the standard sentiment tagging spreadsheet workflow? | pass→pass | 11,753 | 9,550 | -19% | 1 | 1 | 0% | 1,683 | 1,608 | -4% | 0 | 0 | — |
▸case-07 We are updating our customer Success dashboard to show customer health scores. The CS operations lead wants to rely strictly on product usage metrics (login frequency and license seat allocation) without mixing qualitative feedback. How should sentiment feedback interface with health scores? | pass→pass | 15,411 | 18,845 | +22% | 1 | 1 | 0% | 2,246 | 2,760 | +23% | 0 | 0 | — |
▸case-08 When creating a voice-of-customer executive update summary for leadership, our team lead drafted a document containing only high-level statistical charts of NPS trends over time. What essential qualitative and actionable elements must be included in the insight package? | fail→pass | 15,259 | 12,940 | -15% | 1 | 1 | 0% | 2,127 | 2,063 | -3% | 0 | 0 | — |
▸case-10 Our product management team wants to build a Voice of Customer program relying exclusively on annual email surveys sent via SurveyMonkey. What additional qualitative feedback channels should be integrated into source intake? | pass→pass | 17,054 | 14,917 | -13% | 1 | 1 | 0% | 2,460 | 2,395 | -3% | 0 | 0 | — |
▸case-11 When building a taxonomy for customer feedback categorization in Notion, an engineer argues that urgency is redundant because sentiment (positive/negative) already captures how bad an issue is. Is sentiment score alone sufficient for prioritizing operational dispatch? | pass→pass | 16,032 | 14,631 | -9% | 1 | 1 | 0% | 2,254 | 2,229 | -1% | 0 | 0 | — |
▸case-12 Our feedback tagging process records product area and sentiment. A team member asks whether we need to capture who provided the feedback (e.g., end-user vs admin buyer). Should persona be included in the taxonomy? | pass→pass | 14,302 | 7,407 | -48% | 1 | 1 | 0% | 1,952 | 1,273 | -35% | 0 | 0 | — |
▸case-13 What standard cadence and format should be used when presenting voice-of-customer summaries to executive leadership? | fail→fail | 17,171 | 14,425 | -16% | 1 | 1 | 0% | 2,341 | 2,211 | -6% | 0 | 0 | — |
▸case-14 When a customer feedback trend results in a feature change, what key items must be logged in the closed-loop tracking repository? | pass→pass | 13,370 | 7,572 | -43% | 1 | 1 | 0% | 1,826 | 1,319 | -28% | 0 | 0 | — |
▸case-15 Our sales team keeps detailed Gong call notes from customer quarterly business reviews. The CS team believes call notes are too informal and should be excluded from VOC processing, favoring only structured CSAT surveys. Should sales call notes be ingested? | pass→pass | 15,380 | 12,445 | -19% | 1 | 1 | 0% | 2,075 | 2,057 | -1% | 0 | 0 | — |
▸case-16 A high-priority survey response arrives indicating severe customer frustration with database latency. What mechanism ensures this feedback reaches engineering without waiting for the end-of-month review? | pass→pass | 11,162 | 5,942 | -47% | 1 | 1 | 0% | 1,611 | 1,060 | -34% | 0 | 0 | — |
▸case-17 What template artifact should be maintained to track obligations made back to clients who submitted critical feedback? | pass→pass | 12,293 | 5,280 | -57% | 1 | 1 | 0% | 1,784 | 1,026 | -42% | 0 | 0 | — |
▸case-18 Our product team prioritizes their quarterly engineering roadmap based purely on loudest sales requests during contract renewals. How should product and CS actions be prioritized using qualitative customer inputs? | pass→pass | 19,505 | 20,752 | +6% | 1 | 1 | 0% | 2,791 | 2,991 | +7% | 0 | 0 | — |
▸case-19 When setting up feedback taxonomy tags in Jira Product Discovery, a contributor suggests tagging items only by customer company name. Why is product area tagging necessary? | fail→fail | 12,198 | 10,260 | -16% | 1 | 1 | 0% | 1,757 | 1,701 | -3% | 0 | 0 | — |
▸case-20 We are calculating a weighted customer health score using the following metrics: platform logins (40%), license utilization (30%), support ticket volume (20%), and CSAT score (10%). Calculate the exact numerical health score for an account with values 80, 50, 90, and 70 respectively. | fail→fail | 4,624 | 5,025 | +9% | 1 | 1 | 0% | 899 | 1,134 | +26% | 0 | 0 | — |
▸case-21 Write a Jira REST API v3 curl request to transition issue 'ENG-4021' from status ID '11' ('In Progress') to status ID '21' ('Done') using a basic auth token stored in $JIRA_TOKEN. | pass→pass | 8,725 | 7,054 | -19% | 1 | 1 | 0% | 1,509 | 1,464 | -3% | 0 | 0 | — |
▸case-22 Outline a 30-minute executive war room meeting agenda for a Sev-1 datacenter outage affecting enterprise clients, including incident commander introductions and root cause analysis timing. | pass→pass | 15,406 | 14,760 | -4% | 1 | 1 | 0% | 2,177 | 2,332 | +7% | 0 | 0 | — |