|
I'm not sure. Using a chatbot to triage support, or perhaps even actually provide first, or even second line support, is probably going to make for a net saving at scale. even if it's slightly leaky. Would be very careful about where to use it though.
You definitely wouldn't want to deploy such a product in a critical service context, without some kind of human marshal. Something comparatively trivial though. Perhaps like, a super intuitive insurance comparison widget, that takes natural language as an input. Sure, some joker will go off piste, and try to jerk the bot, but in those circumstances, customers are there for a reason. There are of course, already products that do the insurance comparison thing, but there are a few markets, with a similar dynamic, that need a little bit more than good UX to coax requirements and data out of users. Something like this could probably do it. |