"How Do I Reset My Password?" for the 47th Time Today

Last Tuesday, a Shopify store owner told me she answers the same question about international shipping rates at least 12 times per day. She has a FAQ page. She has a shipping policy page. She even added a note to the product description. Nobody reads any of it.

She's not alone. Industry data from Zendesk shows that 40% of support tickets across all industries are repeat questions. For e-commerce, it's closer to 55%. That's more than half your ticket volume going to questions you've already answered somewhere.

The instinct is to blame customers for not reading. But customers aren't lazy. They're looking for answers in the places that make sense to them, and the answer isn't there.

Step 1: Find Your Top 10 Repeat Questions

Before you fix anything, you need data. Pull your last 500 tickets and sort them by topic. If you're using a tool with intent classification (like Supp's 315-intent system at $0.20 per classification), this takes minutes. If you're doing it manually, block off two hours and go through them with a spreadsheet.

You're looking for the questions that show up more than 15 times in those 500 tickets. Most businesses find that 6-10 questions account for 35-50% of their entire ticket volume.

A typical top 5 for e-commerce looks like this:

• Where's my order / tracking status
• How do I return this
• Do you ship to [country]
• What's your refund policy
• Can I change my order after placing it

For SaaS, it's usually:

• How do I cancel my subscription
• Password reset issues
• How to connect [integration]
• Billing questions about proration
• Feature access on different plans

Write them down. Rank them by frequency. This is your hit list.

Step 2: Figure Out Where the Answer SHOULD Be

This is the step most people skip, and it's the whole game. For each of your top 10 questions, ask: at what point in the customer experience does this question come up?

"Do you ship to Canada?" comes up on the product page, during checkout, or right after someone finds you through a Google search. The answer should live on the product page AND the checkout page AND a standalone shipping page that ranks in search.

"How do I return this?" comes up after delivery. The answer should be in the order confirmation email, the delivery notification email, and the packing slip.

"Can I change my order?" comes up within minutes of placing it. The answer should be on the order confirmation page and in the confirmation email.

See the pattern? The FAQ page is where answers go to die. Customers don't visit your FAQ page when they have a question. They look at whatever they're staring at right now.

Map each question to the exact touchpoint where it occurs:

• Pre-purchase questions go on product pages and the checkout flow
• Post-purchase questions go in transactional emails and order status pages
• Account questions go in the app settings or dashboard
• Billing questions go on the pricing page and in billing emails

Step 3: Put the Answer There Proactively

Now do the work. For each of your top 10 questions, place the answer at the touchpoint you identified.

This doesn't mean adding a paragraph of text to every page. It means strategic placement of short, direct answers. A single line under the "Place Order" button that says "You can modify your order within 30 minutes of placing it" eliminates hundreds of tickets per month.

Some specific tactics that work:

Add a shipping estimate widget to product pages. Not a link to a shipping policy. An actual calculator that shows "Ships to Canada in 7-10 business days for $12.95."

Put return instructions in your shipping confirmation email. Not "visit our returns page." Actual steps. "To start a return, go to yourdomain.com/returns and enter order number #12345."

Add inline help text in your app's settings pages. Next to the "Cancel Subscription" button, show what happens: "Your access continues until March 31. You won't be charged again."

A DTC brand called Rothy's reduced their "where's my order" tickets by 38% just by adding proactive shipping notifications at three points: order placed, order shipped, and out for delivery. The information existed before. They just moved it to where people actually look.

Step 4: Automate What's Left

Even with perfect proactive placement, some customers will still contact support. Maybe they didn't see the shipping info. Maybe their situation is slightly different. Maybe they just prefer talking to someone.

For these remaining tickets, automation makes sense. An AI classifier can detect "where is my order" and instantly pull tracking information from Shopify or your fulfillment system. A "how do I return this" message can trigger an automated return flow.

The key insight: automate AFTER you've reduced volume through proactive placement, not before. If you automate first, you're building elaborate systems to handle questions that shouldn't exist. You're treating the symptom.

With Supp, the classification costs $0.20 and the automated resolution costs $0.30. If you're handling 200 repeat tickets per month and automate 80% of them after reducing volume, you're paying around $80/month instead of the 40+ hours those tickets would consume manually.

Measuring What Changed

Track your repeat question volume weekly for the first month after making changes. You should see a 20-30% reduction in the first two weeks from proactive placement alone. Automation picks up another 15-25% of the remainder.

One metric most teams forget to track: first-contact resolution rate for the questions that DO still come in. If customers are asking the same question but now it takes 3 messages to resolve instead of 1, your proactive content might be confusing people rather than helping.

The goal isn't zero tickets. It's zero unnecessary tickets. Some customers will always prefer human contact, and that's fine. The win is making sure every ticket your team handles is one that actually needs a human.