Customer Ticket Handling System

Airbnb's "Customer Ticket Handling System" appears to be a specialized system design interview question, but no exact match for a titled problem statement with the specified tags (web, Ticketing, machine_learning, Multi-channel, System Design, mobile, Routing, backend) was found across available sources.[1][2]

Closest Matches

Searches revealed Airbnb-related system design discussions on customer support ticketing, often as part of broader platform designs (e.g., messaging, notifications, trust & safety). Key elements from these include:

• Tiered support: Self-service FAQs, chatbots, then human agents for escalations.[1]
• Ticketing workflow: Generates tickets linked to user history (bookings, payments); automates routing via workflow engines.[1]
• Core components: Support portal UI, ticket DB (relational/NoSQL), analytics for resolution times/agent performance.[1]

No full problem statement, input/output examples, or explicit constraints (e.g., QPS, data scale) were identified for this precise title.

Inferred Design Scope

Based on tags and context, the question likely requires designing a multi-channel (web/mobile/email/chat) ticketing system with:

• ML routing: Prioritize/assign tickets using models for urgency, sentiment, agent expertise.[2][1]
• Backend scale: Handle millions of tickets, sharded DBs, async queues for notifications.[1]
• Challenges: Global multi-language support, real-time updates, integration with booking/messaging services.[2]

Recommendations

Check Airbnb's internal LeetCode/HackerRank (not public) or sites like Glassdoor/TeamBlind for candidate-shared versions. Public resources focus on generalized Airbnb designs (e.g., booking/search) rather than this specific ticket system.[8]