{"id":50192,"date":"2024-07-08T13:21:08","date_gmt":"2024-07-08T11:21:08","guid":{"rendered":"https:\/\/enreach.es\/?p=50192"},"modified":"2024-07-08T13:26:39","modified_gmt":"2024-07-08T11:26:39","slug":"how-not-to-lose-quality-when-using-a-chatbot-to-automate-responses","status":"publish","type":"post","link":"https:\/\/enreach.es\/en\/blog\/how-not-to-lose-quality-when-using-a-chatbot-to-automate-responses\/","title":{"rendered":"How not to lose quality when using a chatbot to automate responses"},"content":{"rendered":"
Level: <\/strong>Intermediate<\/h5>\n

We had the pleasure of interviewing Jorge Garc\u00eda<\/strong>, our Product Director, for several articles on artificial intelligence. During one of those informal meetings where we were discussing potential use cases in the contact centre sector, he told us:<\/p>\n

“The philosophy behind self-service should be nothing more than automating customer service without losing the quality of experience you would get when talking to an agent.”<\/strong><\/p>\n

It’s true. The word “self-service” can have a certain negative connotation because it evokes a scenario where the customer is alone in the face of danger.<\/strong><\/p>\n

For example, we call the checkout machines in supermarkets self-service<\/strong>, but the machine does not help the consumer to scan the products, the consumer scans them alone.<\/p>\n

So when we talk about an AI-powered chatbot<\/a> that serves users who come to the website and provides answers<\/strong>to their questions or redirects them to the best available agent<\/strong>, we are talking about a system that automates responses.<\/p>\n

We have been stressing this a lot lately, but we think it is very important to remind those companies that are thinking of investing in this technology that if it is not applied with certain criteria, the bot can end up truncating the customer experience.<\/strong><\/p>\n

WHAT ARE THE KEYS TO MAINTAINING QUALITY WHEN AUTOMATING RESPONSES?<\/strong><\/h2>\n

1. PROCESS SIMPLE AND REPETITIVE ENQUIRIES<\/strong><\/h3>\n

The first thing we can start automating are FAQs. Frequently Asked Questions are those that come up all the time, either before buying a product\/service or after.<\/strong><\/p>\n

One of the questions a telecommunications company could automate would be \u201cWhy has my phone bill gone up this month?\u201d.<\/strong><\/p>\n

If we connect the AI to our customer service agent, the bot can access<\/strong> the customer’s bill, analyse<\/strong> the document and inform<\/strong> the customer of any additional charges.<\/p>\n

2. TAKING THE CUSTOMER’S EMOTIONAL STATE INTO ACCOUNT<\/strong><\/h3>\n

The AI that powers the chatbot<\/a> not only understands the user’s request, but also has the ability to extract their emotions.<\/strong> As a result, it knows from the outset the severity of the incident and the emotional state of the customer.<\/strong><\/p>\n

The bot is not a human, so no matter how much we train it to deal with serious problems, it will always lack emotional intelligence.<\/strong><\/p>\n

So if the bot is talking to a customer who has a power cut at home, for example, we need to train the AI to transfer the conversation to an agent.<\/strong><\/p>\n

3. TRANSFER THE CONVERSATION TO THE AGENT WHEN THE USER REQUESTS IT<\/strong><\/h3>\n

There is nothing more frustrating for a user than talking to a bot when they want to talk to an agent. So it’s always a good idea to give the user instructions on how to get in touch with an agent.<\/strong><\/p>\n

In addition, it will soon be illegal to offer customer service based on voicemail or bots that do not allow you to speak to an operator.<\/strong> When the new Spanish customer service law<\/a> comes into force, companies that do not comply will be fined up to \u20ac100,000.<\/strong><\/p>\n

4. AVOID BOT HALLUCINATIONS AT ALL COSTS<\/strong><\/h3>\n

We don’t want our bot to give a customer the wrong answer.<\/strong> So we need to learn how to maintain the knowledge bases properly.<\/p>\n

When we create a knowledge article, we must avoid explaining multiple processes<\/strong> in the same document.<\/p>\n

WANT TO ADD A CHATBOT<\/span> TO YOUR BUSINESS? <\/strong><\/h2>\n