A support team of 12 answers 300 tickets a day from one shared inbox. Urgent issues get buried, and sometimes two agents reply to the same customer. Design the inbox and the ticket view so every agent always knows what to work on next.
Support agents on a laptop all day, switching fast between tickets and measured on response time and customer happiness. Plus a team lead who watches the whole queue.
Start the timer and think out loud, like you would with an interviewer.
60-minute interview
One clock for the whole interview. Each phase fills up as time passes.
60:00left
Each prompt gives the AI a role, the whole brief, every edge case and a palette. AI drafts, you decide.
Best for a clickable prototype, fast.
ROLE You are a senior product designer building a high-fidelity, clickable desktop web app prototype for a UX design interview. Make design decisions a hiring manager would respect, and keep the scope to the brief. THE CHALLENGE Tame the support inbox: A support team of 12 answers 300 tickets a day from one shared inbox. Urgent issues get buried, and sometimes two agents reply to the same customer. Design the inbox and the ticket view so every agent always knows what to work on next. THE USER Support agents on a laptop all day, switching fast between tickets and measured on response time and customer happiness. Plus a team lead who watches the whole queue. MUST-HAVES - See what's most urgent first - Make it impossible for two agents to answer the same ticket - Reply fast, with saved replies - See the customer's history without leaving the ticket EDGE CASES (every one must be handled) - A VIP customer who has been waiting 6 hours and is angry - The same customer opened 3 tickets about one problem - A ticket in a language the agent doesn't speak - An agent goes offline with tickets still open - A ticket is about to miss its response deadline (SLA) SCREENS TO BUILD 1. Inbox (1440×900): the queue of tickets, ordered by what needs attention first 2. Ticket (1440×900): one ticket: the conversation, the reply box, and the customer's context Link them so the main flow is clickable end to end. Show each edge case as a real state (an error, a warning, an empty state or a confirmation), not as a note. VISUAL STYLE - Navy #1C2B4B: primary buttons and the brand - Blue #2F6FEB: links, selection and the active view - Mist #F4F6FB: the sidebar and quiet panels - Ink #141B2D: text - Overdue red #C9302C: overdue and urgent, only - Amber #B76E00: due soon - Type: one clean sans-serif. One clear hero (a title or a number) per screen, then a clear order of importance. - Spacing: an 8-point grid, generous margins, touch targets of at least 44 px. - Accessibility: text contrast of at least 4.5:1, labels on every input, never colour alone to carry meaning. CONTENT Use realistic content: a B2B software company's customers from around the world (Lucía Fernández in Madrid, Priya Nair, Sam Okafor), prices in US dollars, agents called Riya, Arjun, Sam and Mei. No lorem ipsum. DON'T - Don't add features the brief doesn't ask for. - Don't use more than one primary button per screen.
2 strong answers, each with its own look and reasoning. Try it yourself first.
Done designing?
Compare your screens with 2 different solutions, decision by decision.