You're offline — showing cached data

MC-4280

NCC overbooking social sentiment analysis + visual explainer HTML
2026-06-13 08:51:31 SAST
Home Board MC-4280

NCC overbooking social sentiment analysis + visual explainer HTML

Elmar request: sentiment analysis on the whole NCC overbooking issue for FlySafair using all accessible social media sources, then create a visual explainer HTML. Context / rel...
State Done Next Action Closed Owner Elmar Runtime Closed Age 17d ago
MC-4280
Ticket is done; runtime is closed. · profile claude_opus_1m_medium · cwd /home/lucienne/workspace · uptime 16d 23h · last activity 16d 20h ago

Description

MC-4280
Elmar request: sentiment analysis on the whole NCC overbooking issue for FlySafair using all accessible social media sources, then create a visual explainer HTML. Context / related MC tickets: - MC-3792: NCC v FlySafair Referral — 10% turnover penalty sought — Chris Charter / CDH Legal (done) - MC-3902: Keep Harith informed on NCC v FlySafair Tribunal referral (done) - MC-4017 / MC-4113: NCC referral response/meeting items (cancelled) - MC-4225: NCC Discussion notes (waiting) Initial X/XAI scan already performed from Telegram turn: - Query: `FlySafair NCC overbooking OR overbooked OR "National Consumer Commission"` - Query: `FlySafair overbooked denied boarding complaints` - Early themes: public sentiment mixed but materially negative among affected passengers; trust/stress complaints around confirmed/check-in passengers being bumped; voucher/compensation dissatisfaction; some defence that overbooking is industry-wide and NCC should not single out FlySafair; regulatory concern around “unconscionable conduct” and Consumer Protection Act. - Useful X sources surfaced: @TheNCC_RSA, @FlySafair, @dailymaverick, @KayaNews, @TheCapeArgus, individual complaint posts such as Miles_Nsala and SasaJantjies. Deliverable requirements: 1. Gather social-media/public conversation across accessible channels: - X/Twitter via x_search/xurl where available - Facebook/Instagram/TikTok/LinkedIn public posts if accessible via web search/browser - Reddit and forums where available - HelloPeter / Google reviews / consumer complaint sites if relevant - news social amplification and article comments where accessible - official NCC/FlySafair statements for baseline facts 2. Build a source ledger with URLs, date, platform, author/account type, text excerpt, engagement if visible, sentiment, theme, and reliability/access caveat. 3. Classify sentiment: - anger/frustration from affected passengers - consumer-rights/legal concern - industry-practice defence - compensation/voucher complaints - trust/brand-risk comments - jokes/memes/low-signal amplification - media/legal/regulatory commentary 4. Distinguish organic passenger experience from media amplification and political/regulatory commentary. 5. Quantify where possible: counts by platform/theme/sentiment; do not overclaim if platform access is incomplete. 6. Produce a self-contained visual explainer HTML under `~/workspace/reports/` with: - executive summary - timeline of NCC issue - sentiment split and theme cards - representative quotes with citations - risk map: brand, legal, operational, comms - recommended comms/ops response for FlySafair - source/caveat appendix 7. Also provide a short Telegram summary and MC report link. Use Tailscale/MC viewer links, not localhost. Expected check-in: today with first source ledger + HTML draft.

Activity

done
Luci is working...
Live
No activity yet
Help