2 min lesson
One loud voice versus fleet-wide impact
Work through this: "A vocal enterprise customer is escalating loudly over an issue that has a working single-account workaround. The same day, a quiet ticket turns out to be a regression affecting many users. How should empathy guide your prioritization?"
Step 1 of 2
One loud voice versus fleet-wide impact
The hardest empathy call is prioritization. A single loud enterprise account can pull all your attention while a quieter bug blocks a thousand users. Empathy without judgment over-serves whoever shouts; judgment without empathy ignores the person in front of you.
- Situation
- Loud enterprise user, single-account workaround exists
- Where empathy points you
- Acknowledge, give the workaround, set expectations - don't let volume jump the queue.
- Situation
- Quiet ticket, but it's a fleet-wide regression
- Where empathy points you
- Escalate now. Empathy here means protecting the thousand users who haven't filed yet.
- Situation
- Angry user who is actually mis-using a feature
- Where empathy points you
- Coach to self-serve, link the doc and flag the doc gap if many hit the same wall.
- Situation
- Blocked user, real bug, no fix today
- Where empathy points you
- Be honest about the timeline; over-promising a fix is the cruelest option.
| Situation | Where empathy points you |
|---|---|
| Loud enterprise user, single-account workaround exists | Acknowledge, give the workaround, set expectations - don't let volume jump the queue. |
| Quiet ticket, but it's a fleet-wide regression | Escalate now. Empathy here means protecting the thousand users who haven't filed yet. |
| Angry user who is actually mis-using a feature | Coach to self-serve, link the doc and flag the doc gap if many hit the same wall. |
| Blocked user, real bug, no fix today | Be honest about the timeline; over-promising a fix is the cruelest option. |
"I see you're blocked on the SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition. loop and it's holding up your whole team - that's a real problem. I've reproduced it on my side, it looks like a regression in this week's build and I've filed it as high-severity. I don't have a fix to promise you today, but here's a local-auth workaround that unblocks you now and I'll update you by end of day tomorrow either way."
There's a category of work a support engineer deliberately keeps out of the model: billing and account-specific issues that need context you don't want to hand an LLM. The line isn't absolute - you can pipe contractual or use-case details from a CRM into Cursor through MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. when it's safe and useful. Knowing where that line sits is a judgment call interviewers respect, because it shows you treat customer data as something to protect, not just feed in.
Things like billing that require account-specific context don't necessarily want to go to an LLM.
Learn more
Full explanation
Full explanation
When you tell an angry-customer story, make the turning point technical, not emotional. "They calmed down once I showed them the exact line in their config" is the Cursor-flavored version of empathy. It proves you de-escalate by being good at the job, which is the bar for supporting demanding developers.
Over-promising a timeline to make someone feel better is a truth-seeking failure dressed as kindness. A missed promise costs more trust than honest bad news ever does. Say what's true, give a workaround and commit only to an update time you'll actually hit.