Is it complicated to install an internal chatbot?
It seems that launching an internal chatbot is complicated…
Or is it just a myth?
"In the past, it was indeed complicated
And reserved for large companies.
Let me take you on a journey through contemporary history…
Chatbots burst into our lives during the 2010 decade. The GAFA are betting on this technology and successively launch their virtual assistants(Siri for Apple, Google Now for Google, Cortana for Microsoft (those who geeked out on the “Halo” license, then Alexa for Amazon…). On the Asian continent, it is the giant WeChat (more than 700 million users per month at the time) that is pushing the rise of chatbots by making it possible in 2013 to create bots evolving in its messaging by third-party developers.
On the corporate side, large international groups are equipping themselves with complex chatbots for the time, based on artificial intelligence technologies such as IBM’s famous Watson, with the help of consulting firms and IT services companies. Budgets are often above 200k€ for a single bot, and projects are carried out over relatively long periods of 1 to 3 years.
The chatbot hype probably reaches its peak around the years 2016-2017. Many customer services departments are equipping themselves to handle the ever-increasing volume of online solicitations.
In the early 2020s, the sector reached a certain maturity. Organizations working on operational excellence in their various divisions are increasingly integrating internal bot to assist their teams. In the first place, this type of project focuses on the processing of repetitive tasks with an obvious automation potential, but sometimes also covers complex use cases involving powerful workflows.
The chatbot hype probably reaches its peak around peak around the years 2016-2017 . Many customer services departments are equipping themselves to handle the ever-increasing volume of online solicitations.
In the early 2020s, the sector reached a certain maturity. Organizations working on operational excellence in their various divisions are increasingly integrating internal bot to assist their teams. In the first place, this type of project focuses on the processing of repetitive tasks with an obvious automation potential, but sometimes also covers complex use cases involving powerful workflows.
But today, it's pretty simple!
At the time of publishing this article, bots are not only more powerful technically, more ergonomic, but also simpler to set up. At least, among publishers who offer a intuitive “no-code” creation dashboard, and a monitoring interface with performance indicators .
This little robotics history lesson had only one goal, as you’ll understand: Deconstructing the myth of the complexity of chatbot projects among IT managers.
Un mythe fondé et rationnel, je vous le condère, puisqu’il s’explique par des croyances légitimes liées au souvenir des premiers années de la technologie.
Cependant, on espère vous convaincre que, si lancer un chatbot était certes relativement complexe et couteux il n’y a pas si longtemps de ça (au milieu des années 2010)… l’écosystème a largement évolué.
Aujourd’hui, les chatbots déployés par un acteur comme Vizir aboutissent aux mêmes prouesses que ceux développés par plusieurs développeurs à temps plein sur 1 à 2 ans en 2015, pour une phase de pré-production qui s’étend rarement au-delà de 2 mois, à un coût maîtrisé (voir notre page tarifs).
Ainsi, de plus en plus de directions passent à l’action et déploient en quelques semaines des chatbots internes, destinés à faciliter l’expérience de leurs collaborateurs tout en libérant les équipes supports des tâches récurrentes et rébarbatives.
Alors, la prochaine fois qu’on vous demande de réinitialiser un mot de passe à 19h… pensez-y 😉
