▸case-01 We are preparing our weekly social listening update for leadership. A team member suggested relying solely on Twitter/X mentions to gauge sentiment. Create a signal source plan for our community sentiment dashboard. | fail→pass | 18,006 | 21,067 | +17% | 1 | 1 | 0% | 2,713 | 2,884 | +6% | 0 | 0 | — |
▸case-02 Design the core metrics section for an executive sentiment dashboard. The team wants to include only a single average sentiment percentage score. Outline the full sentiment stack components. | fail→pass | 19,543 | 15,104 | -23% | 1 | 1 | 0% | 2,973 | 2,525 | -15% | 0 | 0 | — |
▸case-03 Set up a risk and issue tracking table for our crisis monitoring board. A reviewer suggested listing only the issue text and flagging status to keep it clean. What fields should be included on this board? | pass→pass | 13,454 | 12,036 | -11% | 1 | 1 | 0% | 1,958 | 2,083 | +6% | 0 | 0 | — |
▸case-04 We are adding an advocate section to our community dashboard. The proposed layout only shows a list of VIP usernames. Specify what elements belong in the advocacy spotlight. | fail→pass | 13,437 | 11,251 | -16% | 1 | 1 | 0% | 1,960 | 1,963 | +0% | 0 | 0 | — |
▸case-05 Draft an action register workflow for post-launch feedback. The operational plan currently routes all follow-up items strictly to the social media community manager. Define the cross-functional routing structure. | pass→pass | 17,451 | 14,992 | -14% | 1 | 1 | 0% | 2,740 | 2,435 | -11% | 0 | 0 | — |
▸case-06 Outline a slide layout structure for our monthly community executive briefing. The draft presents a single wall of qualitative text quotes. Detail the necessary visual and structured components. | fail→pass | 14,618 | 16,090 | +10% | 1 | 1 | 0% | 2,256 | 2,719 | +21% | 0 | 0 | — |
▸case-07 Create the column schema for an operational escalation tracking sheet during a product incident. The team provided a basic two-column table with 'Incident' and 'Notes'. What required operational fields are missing? | fail→fail | 13,282 | 13,166 | -1% | 1 | 1 | 0% | 2,266 | 2,280 | +1% | 0 | 0 | — |
▸case-08 Specify the data schema for our community advocate database. The draft sheet only tracks member handle names and total follower count. What key operational details must be added? | fail→fail | 15,703 | 15,169 | -3% | 1 | 1 | 0% | 2,465 | 2,621 | +6% | 0 | 0 | — |
▸case-18 A community sentiment audit revealed recurring complaints about a billing bug and confusing feature documentation. The dashboard manager logged them in a notes doc. How should these issues be processed? | pass→pass | 14,004 | 11,647 | -17% | 1 | 1 | 0% | 2,042 | 1,865 | -9% | 0 | 0 | — |
▸case-09 We are setting up automated monitoring across Discord, Reddit, and Twitter. The manager suggests using a single global threshold of 100 negative mentions per hour across all channels equally to trigger alerts. Recommend the alerting configuration strategy. | pass→pass | 16,192 | 17,436 | +8% | 1 | 1 | 0% | 2,437 | 2,720 | +12% | 0 | 0 | — |
▸case-10 Format the executive summary section for our product launch sentiment report. The current draft presents raw charts without qualitative feedback snippets. How should the insight visuals be presented? | pass→pass | 13,933 | 15,655 | +12% | 1 | 1 | 0% | 2,068 | 2,474 | +20% | 0 | 0 | — |
▸case-11 We want to automate the generation of our recurring community sentiment briefing packets. Which specialized skill or function should be paired with the dashboard workflow to handle automated packet generation? | fail→pass | 11,866 | 2,419 | -80% | 1 | 1 | 0% | 1,717 | 575 | -67% | 0 | 0 | — |
▸case-12 Our engineering team reported a major outage affecting 20% of users. The communications lead wants to wait until the end-of-month report to review sentiment. Recommend the monitoring cadence and application. | pass→pass | 11,859 | 14,007 | +18% | 1 | 1 | 0% | 1,916 | 2,176 | +14% | 0 | 0 | — |
▸case-13 We are launching a major feature next Tuesday. The marketing team plans to review feedback exclusively via ad-hoc Slack messages. Structure the structured reporting framework to run during the launch. | fail→pass | 16,013 | 19,688 | +23% | 1 | 1 | 0% | 2,282 | 2,873 | +26% | 0 | 0 | — |
▸case-14 When evaluating volume spikes during a brand campaign, the analyst groups all accounts into one total sentiment score. How should user influence be categorized in the sentiment stack? | pass→pass | 12,242 | 12,111 | -1% | 1 | 1 | 0% | 1,778 | 1,964 | +10% | 0 | 0 | — |
▸case-15 In our sentiment stack summary, we currently report volume and positive/negative percentages. What critical operational status metric is missing from this stack overview? | fail→pass | 12,041 | 4,669 | -61% | 1 | 1 | 0% | 1,682 | 903 | -46% | 0 | 0 | — |
▸case-16 Our team is receiving dozens of low-priority Slack notifications every hour from minor social media post mentions, leading to alert fatigue. How should the monitoring criteria be adjusted? | pass→pass | 12,721 | 13,798 | +8% | 1 | 1 | 0% | 1,805 | 2,208 | +22% | 0 | 0 | — |
▸case-17 Our executive team wants to see user reaction content in our monthly readout, but the current deck only summarizes text sentiment percentages. Where and how should visual community posts be included? | fail→pass | 15,594 | 14,936 | -4% | 1 | 1 | 0% | 2,097 | 2,339 | +12% | 0 | 0 | — |
▸case-19 Prepare a monthly community sentiment presentation structure for C-suite executives who have 5 minutes to review. The team proposed sending a 30-page raw transcript of community posts. Design the layout format. | fail→fail | 19,481 | 14,518 | -25% | 1 | 1 | 0% | 2,717 | 2,371 | -13% | 0 | 0 | — |
▸case-20 A customer opened support ticket #4821 complaining about a delayed refund for order #9921. Draft a direct customer support email response resolving their refund issue. | pass→pass | 6,416 | 5,257 | -18% | 1 | 1 | 0% | 1,022 | 998 | -2% | 0 | 0 | — |
▸case-21 Write a Python script using `requests` to authenticate against the Twitter/X v2 API endpoint and fetch raw JSON response payloads for a search query. | pass→pass | 11,993 | 8,540 | -29% | 1 | 1 | 0% | 2,241 | 1,745 | -22% | 0 | 0 | — |
▸case-22 Write an official corporate press release announcing our company's Series B funding round for distribution to PR Newswire. | pass→pass | 14,813 | 10,362 | -30% | 1 | 1 | 0% | 2,042 | 1,659 | -19% | 0 | 0 | — |