Practice

Benchmark answer for this question

Fictional example for learning only. It is not your experience; replace every detail with facts that are true for you.

I keep every request in the ticket system — at my last job that was Zendesk — with one ticket per customer issue. I tag each ticket by type, set a due date when I've promised a reply, and write a two-line note after every contact so anyone can pick it up. At the start of each shift I sort my view by due date and handle anything overdue first, then the oldest open tickets. For example, last March I had about 60 open tickets during a product recall. Because of the due-date view, I spotted three customers who had been promised a callback that day and called them before noon, instead of letting them wait over the weekend. That routine is how I use customer support systems: the tool holds the details so nothing depends on my memory.

Why this example works

It names a concrete tool and routine, explains how the routine works daily, and proves it with a specific example.

• Names a concrete method or tool: Zendesk, tags, due dates, two-line notes, a due-date view
• Gives an example: “last March I had about 60 open tickets during a product recall”
• Specific, not general: “about 60 open tickets”, “three customers”, “before noon”
• Claims are supported: The routine is backed by the recall example
• Connects to the role: Names Zendesk and customer support systems

What you can learn from it

Name only tools you have actually used; explain how your process prevents requests from disappearing.

Make it yours — with true details only

Replace Zendesk with the tool you really used (Freshdesk, a shared inbox, a spreadsheet, even a notebook). Use your real daily routine and one real time it caught something.

From generic to evidence

Generic: “I'm very organized, so I just keep track of everything and make sure nothing falls through the cracks.”
With evidence: “I log one ticket per issue, tag it, set a due date and sort by due date each morning; during a recall that view showed me three promised callbacks I made before noon.”

Mistakes that cost points

• Naming tools you have not used — Name only what you can talk about in detail
• “I'm very organized” — Describe the actual system
• No example — Add one time the system prevented a problem
• Relying on memory — Show how the tool holds the details