It has become a standard: A robot took my job. This mantra should be familiar to everyone as mechanization in the workplace has been an issue for at least one hundred years. In 1913, Henry Ford’s automated assembly line turned a whole company and its people into a giant cyborg; half human and half robot. We could further trace robot outsourcing back through mid 19th century British industrialists, scientists and free thinkers who spent their time developing machines that “replaced” people. If we consider Archimedes screw that “laid-off” people who were moving water with buckets it reaches the edge of written history.
We spend half our time vilifying people like Henry Ford and the other half celebrating them. However, we should probably take a few moments every Friday afternoon to thank Ford for inventing the weekend and an 8 hour work day. Who really knows if his motives were altruistic or motivated purely by greed in optimizing his manufacturing plant. We do know he created a car that anyone could afford when only rich people could afford cars. We also know he was the first to institutionalize the concept of a life-work balance.
Thinking through this, there is reason to believe that robots are all-good for people. Consider the possibility that jobs we are “losing” to robots are really just parts of jobs that are too tedious or back breaking to do for 8 or 10 hours every day. Let’s face it, the good parts of any job are the parts that require some imagination or intuitive thinking. Why not think of any job or task as part that a robot can do and part that needs real thought and flexibility?
If we start to draw this out we can see how a robot taking part of a job may benefit the employer, the worker and the client or end user. Since this is a chatbot blog let’s consider a product support chat room that services 100 calls a day with 4 people on the team. Each product specialist handles an average of 25 calls a day. It doesn’t really matter what the numbers are. We just want to be able to see the effects of automation.
A pie chart will be good to handle this:
Maybe it would be better to add some humanity. People don’t work 100% of the time so let’s add a simple buffer that may include getting a quick snack, adjusting the work station, maintenance, going to the toilet or taking a deep breath once in a while. In a way, this number is a constant for any amount of humans. Every person needs humanity in their job and there will be a fitful price to be paid if it is not applied. We’ll use 10%. It is probably more like 30% but let’s use 10% to avoid arguments at this point.
Now let’s add a robot into the mix. Consider how many calls the product specialists will receive that have existing answers. They are either in the frequently asked questions (FAQ’s) for the given product or a chat has produced a question and answer that can be used in the FAQ’s. Assuming these FAQ’s and their answers are not changing, we can give them to a chatbot. The chatbot can filter incoming requests and hand-off the customer when it can’t find a solution. It is important to note that the chatbot has to handle this gracefully or it will just be giving annoyed customers to the specialists. We’ll use 15% as the percentage of requests a chatbot may handle.
This is the part where a lean thinking manager might say “Aha! Now I can get rid of one of my support agents if that chatbot will just handle a few more calls.” This could be a good idea. It is entirely possible a chatbot could buffer 80-90% of increased support calls during an upsurge from product deployments or failures. Conversely, this might not be a good idea. What if there is a growth spurt in the company or a new feature or product is launched…and fails? A chatbot can easily handle repeat questions such as “How do I return this?” or “Where’s the manual?” but a good support tech may do better at leveraging nuances in the conversation to endear good faith from the customer. In this case, a chatbot combined with the company’s loyal support people may outperform an outsourced team dedicated to events such as recalls.
A key point is: the chatbot is “in-sourced.” An in-house chatbot has the advantage of taking input from the sales team along with support or engineering. The well mannered chatbot can appease the customer while offering references to new products and public relations based media. We could give the support team a script produced by the sales team along with some training to solve the problem. On the other hand, that would take the support team out of their element while creating more administrative and training work. Arguably, a well tuned chatbot with a good script will cost less and perform better than outsourced or overworked support teams.
Business owners and managers will want to know about the bottom line. The US Bureau of Labor Statistics lists the annual mean salary for office and administrative support occupations at $36,000 per year. Considering costs for administration such as payroll and HR, fees, insurance and taxes, the total cost to hire support people is around twice their salary: $72,000 per year. A manager may be looking at this when increasing the size of the support team. To the manager a chatbot might be looking pretty good right now.
At this point we may have the managers ear but the “robot took my job” argument has come to the forefront. Let’s see if we can make everybody happy…
First, the manager since the ball is already rolling. Looking at the pie chart with the chatbot we can see the chatbot’s job portion is very close to the human worker’s part. If the given chatbot was optimized a bit more it could effectively “replace” the fifth human on the team. Also, remember the chatbot’s ability to simultaneously handle multiple calls and work all three shifts. If we can ensure the chatbot won’t mishandle customers, the manager is happy.
The support team may balk at implementing a chatbot that could take their job. A suitable device will be needed to convince them. Let’s use a carrot! The key to any job is growth. We need to get a raise once in a while to keep up with inflation or a growing family. We may also get bored with a given post and want a way up…or out. A training program that involves learning about and tuning the chatbot may provide a perfect opportunity for the worker to gain knowledge and skills and for the company to improve employee retention.
One support person might find chatbot programming interesting and take night classes to get a better job in the company. Another might go off to school and return with diploma in hand, thankful for the company’s encouragement and ready to make a positive difference. Still another may be sad at loosing the easy questions to the chatbot but somewhat satisfied the manager kicked down a few bucks at his last review. It was all possible because of the improvements in service created by the chatbot and training program. The team is mostly happy. The two new members are very happy because they found jobs when one member was promoted and the other went to college.
And finally, the customer. Why last? Because customer satisfaction and conversion is the bottom line in any business. How we treat the customer with courtesy and respect while we are cajoling, coaxing and coercing them to like our products and buy more will advance our chances for success in business. The customer may not always be right but customers must be listened to and the knowledge gained must be employed effectively. By using chatbots to courteously interact with our customers we have an opportunity to streamline support issues, increase leads and sales, and mine for data. The customer gets treated carefully and fairly; gets the product they are looking for; and enjoys time spent on your website. The customer is happy.