TalkingDot 1.29: two-way WHMCS ticket sync
Tickets opened in WHMCS show in your TalkingDot inbox, and tickets opened in TalkingDot show in WHMCS, with replies, notes and status copied both ways.
Most help centers are written from the product's point of view. Start from real conversations, write the way customers search, and put articles where people already ask: inside the chat window.
A help center is supposed to answer questions before they become conversations. Many never do, because they are written from the product's point of view (a tour of every settings screen) rather than the customer's (I'm trying to do this, and it isn't working). The fix is not more articles. It is the right articles, written the way customers search, placed where customers already ask.
"Deflection" sounds like keeping customers away. It should mean the opposite: the customer gets a complete answer immediately, at any hour, without waiting for a reply, and your team gains time for the conversations that need a person. If an article leaves people more confused, it has not deflected anything. It has delayed a conversation and made it harder.
So the goal is not fewer chats at any cost. It is fewer repeat questions, and better conversations about everything else.
Do not start from a blank outline. Start from what people already ask.
Collections are the top-level groups in your help center. Organise them by what customers are trying to do, not by how your product's menus are laid out. Four to eight collections is plenty to start with, for example:
Put each article in the collection a customer would check first, and link related articles to each other so a reader who lands in the wrong place can still find the right one.
Most help-center readers arrive from a search box, either yours or a search engine's. Write for that.
A help center only deflects questions if people find it. The best place to surface it is the chat window, at the moment someone is about to ask.
TalkingDot records view counts and "Was this helpful?" votes for every article. Read them together:
| Signal | What it usually means | What to do |
|---|---|---|
| Many views, mostly helpful | The article works | Leave it, and link to it from saved replies |
| Many views, many "not helpful" votes | Popular topic, weak answer | Rewrite it, starting with the first two sentences and the steps |
| Few views, topic still common in chat | People cannot find it | Retitle it in customers' words and link it from related articles |
| Few views, few chats about it | Low demand | Leave it alone and spend your time elsewhere |
Also watch your conversation tags after publishing. If a topic's share of conversations drops after you publish or rewrite its article, that is your best evidence the article is working.
An out-of-date article is worse than none, because it gives a confident wrong answer. A few habits keep a help center accurate:
Every TalkingDot workspace gets a public, search-engine-friendly help site. That matters beyond support. People search for things like "how to connect X to Y" or "why does Z happen" long before they contact you, and a clear article can be the first time they meet your business. Help articles answer the specific, long-tail questions that marketing pages never cover.
To get the most from it, keep titles in plain customer language, link to the help center from your site's navigation and footer, and link related articles to each other. Keep anything private, such as internal procedures or customer details, out of public articles.
Start small. Five excellent articles on your most common questions will do more than fifty written to fill out the collections.
The help center guide shows how to set up collections and publish your first article in TalkingDot. If you do not have a workspace yet, create one free and start with the five questions you answered most often this week.
Tickets opened in WHMCS show in your TalkingDot inbox, and tickets opened in TalkingDot show in WHMCS, with replies, notes and status copied both ways.
Turn any chat or email into a ticket with a number, type, status and priority. Customers follow their tickets in the messenger and by email.
Live chat software puts a chat box on your website and gives your team one inbox to answer it. How it works, the main features, what it costs and how to add it.
Create a free account, paste one line of code and start talking to your visitors.
Free plan foreverNo credit cardUnlimited teammates