Why don't help articles work for these customers?
An article assumes the reader can map words onto a screen. "Go to Settings, then Billing" only helps if you know where Settings lives. Someone unsure never gets that far. They close the tab and phone you, or they quietly stop using the product.
The UK government's service manual calls the help these people need assisted digital support. Its list of reasons includes a lack of confidence and a lack of digital skills. Its advice is plain: help them over the phone or in person, and sometimes by webchat.
What are your options, from most personal to most scalable?
| Option | Works well when | Where it breaks |
|---|---|---|
| Phone call | The customer wants a person | Nobody can see the screen |
| Screen share | The problem is visual | Setting it up is a support task of its own |
| Video walkthroughs | The task is the same for everyone | It goes stale after every redesign |
| In-product voice guide | The same questions arrive daily | It only knows what you've taught it |
Start with calls and screen share if you get a handful of these a week. They're personal, and they show you exactly where people get lost. Once the same question arrives daily, a person repeating the same walkthrough is the expensive part.
What does good in-product guidance look like?
It happens on the customer's own screen, on the page they're stuck on. It speaks, so they don't have to read. And it points. When it says "the blue Export button", that button lights up.
Timing matters. A highlight that lands a second early sends a nervous user's eyes to the wrong place. agent247 fires the highlight on the sentence that names the button, and finds the button by the words printed on it.
It can also do the step for them: click a button, or fill a field with something they just said. It never fills passwords or payment details. Those stay with the customer.
How do you set this up without a support team?
With agent247 it's one script tag on your pages. It reads each page as the customer uses it, and learns the rest from notes you add to its knowledge in the dashboard. You don't need a finished help centre first.
Know its limits. It sees the page the customer is on, not the account records behind it. Voice is English only for now, and anyone can type instead. Keep your phone number visible next to it, because some customers will always want a person.
Two common cases get their own guides: when a customer can't find a setting and onboarding older users.