Hacker News new | ask | show | jobs
by LostJourneyman 2541 days ago
It depends build to build. The standard approach is one of 4:

1) The bot initiates the conversation and your initial message gets sent directly to an agent. This is the older model that's in most common use today.

2) The bot initiates contact and based on your responses does some simple keyword matching and delivers help article links where possible or asks for more information IVR style, then when it hits an "I don't know" point or if the agent option is selected, offloads to an agent.

3) This is my favorite style, honestly: The bot initiates the interaction, and does some machine learning backed AI chat, all the while the interaction is monitored by an agent who can take over at any time. Similar to #2, if the bot hits a sticking point, it'll just queue to an agent. This unfortunately is the least common of the implementations.

4) This is the most modern and is becoming the industry leader: Fully AI bot trained against a veritable Everest of chat conversations for that entity/industry, only offloads to a human when you shout "HUMAN" at it enough times or if it gets really stuck and confidence intervals start falling rapidly.

NOTE/DISCLAIMER: I design and implement these systems for a living, and we don't often get much say in the customer-side UX, so I'm sorry if you've gotten stuck with an arguably bad build!

(Edit: formatting)

2 comments

#3 reminds me of self-serve retail checkout kiosks: when I get stuck, or the kiosk gets stuck, a nearby live human approaches and resolves the issue (except when there's no live human nearby in which case I just get to stand there feeling awkward and useless. it's pretty humbling.)
https://xkcd.com/806/

Nobody will notice, you know you want to add it ;).

You have NO IDEA how tempted I've been to add that! I've literally had printed this out and pinned to the wall of my cubicle for years!