Design a distributed customer support case routing platform
PremiumBackend systemMedium
- Queue architecture
- Priority scheduling
- Resource allocation
Quick answer
This backend system interview question asks you to design a distributed customer support case routing platform. Aim for a design that meets its requirements at the stated scale, then explain its main components, data flow and trade-offs. Interviewers want to see how you scope the problem, size it and defend each choice.
The problem
Design a Distributed Customer Support Case Routing Platform (similar to Zendesk Routing or Salesforce Omni-Channel). Large enterprise clients use this system to ingest customer support requests across multiple channels (live chat, email, web forms). The system must automatically classify cases, place them into priority-aware queues based on business rules (e.g., language, product, customer tier), and assign them to the most appropriate available agent. It must also monitor Service Level Agreements (SLAs) and escalate cases if they wait too long.
What must a distributed customer support case routing platform do?
- Ingestion & Classification: Accept cases from diverse channels and fetch metadata (tier, language) to determine the correct skill queue.
- Priority Queuing: Hold unassigned cases in queues ordered by severity and customer tier.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Queue architecture
- Priority scheduling
- Resource allocation
- Async processing
- State management
How you’ll practise
- Requirements
- Estimate
- API and data
- High-level design
- Deep dives
- Wrap-up
Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.
What do interviewers look for?
In any backend system design round.
- Clarifies the requirements before drawing anything
- Uses a few numbers that actually change the design
- Draws a clear path from the client to storage
- Picks storage and caching with reasons, not by habit
- Explains what breaks first under load and how to fix it
- States trade-offs openly instead of claiming a perfect design
Questions people ask about this interview question
- Which design type is this question?
- It is a backend system question. You design a distributed customer support case routing platform and explain your choices the way you would in an interview.
- Is this question asked at entry level?
- It is marked Medium. Entry-level engineers can practise it, but it expects you to reason about requirements and trade-offs, not only list components.
- What should I cover first?
- Start with the requirements: what the system must do, how well it must do it and which numbers change the design. Agree on scope with the interviewer before you design anything.
- Can I practise it for free?
- It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.
Related questions
Updated · Written by the SevyDevy team