You sit down at a nice restaurant. The wine list has 200 options. You don't know what to order. The sommelier approaches.

A bad sommelier says: "I recommend the 2019 Châteauneuf-du-Pape. It's excellent."

A good sommelier says: "What are you having for dinner? Do you prefer something light or full-bodied? What's your typical price range?"

In two minutes and three questions, the good sommelier has narrowed 200 options to 4. You feel confident choosing from those 4 because the recommendation is tailored to your actual preferences, not the sommelier's.

The best support agents work the same way. Instead of jumping to a solution ("Try clearing your cache"), they ask questions that narrow the problem space until the right answer becomes obvious.

Why Agents Jump to Solutions

Agents are measured on speed. The faster they resolve, the better their metrics look. Asking questions takes time. Giving an answer takes less time.

So agents develop pattern-matching shortcuts. "Can't log in? Clear your cache." "Export not working? Try a different browser." "Billing issue? Here's the billing FAQ." These shortcuts work maybe 30% of the time. The other 70% of the time, they generate follow-up messages: "I tried that and it didn't help."

The follow-up messages take longer than the questions would have. A 2-minute template response that works 30% of the time generates, on average, 1.4 additional exchanges. A 4-minute consultative response that asks the right questions resolves 70% of issues on the first try.

Do the math: the "slow" approach (asking questions) is faster in total resolution time.

The Three Questions

Adapt the sommelier's framework to support with three questions:

"What are you trying to accomplish?" Not "what's the problem?" but "what's the goal?" The customer who says "the export is broken" might be trying to generate a report for their boss, back up their data before a migration, or pull records for a tax filing. Each goal has a different best solution.

"What have you already tried?" This avoids repeating troubleshooting steps the customer already attempted. It also reveals their technical level: a customer who's tried clearing cookies and checking the console is different from one who's tried "clicking the button really hard."

"When did this start?" / "What changed?" Timing is the most powerful diagnostic question. "It stopped working yesterday" combined with "we updated our SSO configuration yesterday" is an instant diagnosis. Without the timing question, you'd spend 20 minutes troubleshooting before discovering the root cause.

These three questions take 30 seconds to type and save 5 to 15 minutes of misdirected troubleshooting.

Teaching Guided Discovery

Guided discovery means helping the customer find the answer themselves, with your guidance, rather than giving them the answer directly.

"When you go to Settings, do you see an Export tab on the left sidebar?" is guided discovery. You're walking them through the product, checking each step, and identifying where they get stuck. When they say "I don't see an Export tab," you've found the problem (they're on a plan that doesn't include export, or the UI is different on their platform).

"Go to Settings > Export > CSV" is a directive. If they get stuck at any point, they have to come back and say "I did that but the next step didn't work." You're playing telephone with their screen.

Guided discovery takes longer per message but fewer messages per resolution. And the customer learns the product better, which reduces future tickets.

When Not to Use It

The sommelier approach isn't for every interaction. Some tickets should get immediate, direct answers.

"What are your business hours?" Answer: your hours. Don't ask "when were you hoping to reach us?" That's condescending.

"How do I reset my password?" Answer: the reset link. Don't ask "tell me more about your login issue." It's a password reset.

"I was charged twice." Answer: "I see the duplicate charge. Refunding now." Don't ask "what were you expecting to be charged?" They expect to not be charged twice.

The sommelier approach works for ambiguous problems, complex troubleshooting, and situations where the customer's stated question isn't their real question. For direct, clear requests, just answer.

Supp's classification helps determine which approach to use. Intents classified as "how-to" or "feature question" often benefit from guided discovery. Intents classified as "billing error" or "password reset" benefit from direct resolution. The classification tells the agent (or the AI) which mode to operate in.