Why do customers get lost looking for settings?
Settings pages grow by accretion. Every feature adds a toggle somewhere. Two years in, the one people need sits three levels deep under a name only your team uses.
Customers search in their words, not yours. They look for "turn off emails" and your setting is called "Notification preferences".
Most teams never count these tickets, because they get tagged as how-to questions and closed fast. Count them for a week. The number is usually uncomfortable.
Is screen sharing the answer?
Sometimes. Seeing their screen ends the guessing. The friction is getting there. On a Mac, the customer first has to allow Zoom to record the screen in System Settings, and if Zoom is already open it asks to restart. For someone already confused, that's a second support task on top of the first.
Co-browsing tools skip the install. They still need a person on the other end, during your hours.
How do you point at a setting without a call?
Put the pointing inside the product. A guide running on your pages can open the right screen, dim the rest, and highlight the exact toggle while it explains what it does. The customer clicks it, or asks the guide to.
| Approach | Customer effort | Your team's effort |
|---|---|---|
| Written reply with directions | Read, interpret, hunt | Low per ticket, but the ticket comes back next week |
| Screen share | Install, allow access, restart | A person on every call |
| In-product guide that points | Ask, then click | Set up once |
This is how agent247 works. If the setting is on another page, it gets there through your own links and buttons, the same path the customer would take. Then it highlights the toggle as it names it. The wider approach is in supporting customers who aren't tech-savvy.
Should you just redesign the settings page?
Yes, eventually. A guide treats the symptom. Use what it hears to fix the cause.
Every conversation shows up in your dashboard in the customer's own words. If people keep asking where invoice reminders live, that toggle belongs somewhere more obvious. Those questions are free usability research.