3 ms·
> Why not just present your users with your FAQ and a search box prior to them chatting with an agent? Because e.g. the user asked the question on Facebook Mes
by sorich87 10y ago
> Why not just present your users with your FAQ and a search box prior to them chatting with an agent?
Because e.g. the user asked the question on Facebook Messenger. And you don't want to send them to your website when you can reply instantly, right there.
> You don't need a bot for that, and it's just more load on a customer to try and understand the interface to the bot.
I'm actually advocating for bots with no interface, no IRC-like commands. The customer sends the question via chat. If the bot understands it replies instantly, if not a support person replies. Simple. No "type X for whatever" or "sorry I didn't understand your request".
> I feel like a lot of bots are being built to try and replace the human connection between customer and the business, which I think is the wrong approach.
We're definitely on the same page. :)
- intoverflow2 10y ago> Because e.g. the user asked the question on Facebook Messenger. And you don't want to send them to your website when you can reply instantly, right there. You're defending the use of a bot for a scenario that only occurs because the bot exists.
- sorich87 10y agoNo, please read the full thread. The scenario is the following: There are currently hundreds of thousands of Facebook pages which receive dozens of customer support questions every day via Messenger. My point is that a bot can be used reply instantly to frequently asked questions and leave more sophisticated questions to humans. I'm not defending any fancy use of bots. Just simple use cases like this.