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.
Bots are good at routing, collecting details and pointing to help articles; people are better at nearly everything else. How to design button-based flows, hand off cleanly, avoid dead ends and measure the result.
The real question is rarely "bot or human?". It is which parts of a conversation a bot handles well, and how quickly and cleanly it gets out of the way when a person is needed. Get that split right and visitors get faster answers while your team spends its time on conversations that need judgment. Get it wrong and you build a maze that frustrates the people you most want to help.
Bots are good at short, predictable steps where the visitor knows the answer and you need it in a particular form.
Hand anything that needs judgment, empathy or an exception to a person: an upset customer, a refund outside your usual policy, a bug report that needs follow-up questions, a large sales opportunity, or a question your help center does not cover. Bots are also poor at noticing when a visitor is getting frustrated, which is exactly when a person should step in.
| Situation | Let the bot | Hand off when |
|---|---|---|
| "Which plan includes this feature?" | Suggest the plans article | The visitor asks a follow-up |
| Password reset | Point to the reset article | The reset email never arrives |
| Demo request | Collect name, email and company size | Straight after, so sales can reply |
| Problem with an order | Collect the order number and email | Always: a person needs to check it |
| Angry or urgent message | Nothing beyond routing | Immediately |
| Outside office hours | Collect email and the question | First thing next business day |
Buttons beat free text for the bot part of a conversation. They show visitors what you can help with, they cannot be misunderstood, and they make reporting simple because every answer falls into a known bucket. In TalkingDot, a chatbot flow is a series of steps: show buttons, collect an email, name, phone number or free-text answer, hand off to your team, or end the conversation.
A simple flow for a software business might look like this:
Alongside your flows, TalkingDot's answer bot suggests relevant help-center articles when a visitor asks a question, so many simple questions are answered before anyone needs to reply.
A dead end is any point where the visitor cannot move forward: a bot that repeats "Sorry, I didn't understand", a branch that stops without an answer or a handoff, or a menu with no option that fits. These rules prevent most of them:
Hand off immediately when a visitor:
In TalkingDot, the handoff step passes the conversation to your team, and routing rules take it from there. A rule can look at the message, page, country, language, device or contact, then assign a team or teammate, add a tag, set the priority, send a reply or close the conversation. A good first rule: messages that mention "refund" or "charged twice" get high priority and go to whoever handles billing.
The worst handoff is the one where the visitor has to repeat everything. Whatever the bot collected should be in front of the person who picks up the conversation. In TalkingDot, the bot's questions and the visitor's answers sit in the conversation itself, and the contact sidebar adds location, local time, current page, page history, past conversations and custom attributes. The teammate can open with a real answer instead of "How can I help?".
Keep the first human message personal and specific. "Thanks, I can see you're asking about your March invoice; let me check that now" tells the visitor the handoff worked.
To build your first flow, follow the chatbot guide, or see what else TalkingDot can automate on the automation features page. Workspaces are free, so you can try it with your own visitors.
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