How to deal with customer loyalty using the website
To get the subway, little tram into the ground to bury. To get an effective Internet site, it is not enough to make a set of scripts and dump it into the network. Internet service is not just a “if-then” digital logic, it’s also a lot of work to integrate the system, check its reliability and carefully select the formulations that are used to communicate with the user. Let's see how it is when people think about it not enough.
I returned from Krasnoyarsk, where I spoke at the Second Krasnoyarsk Conference on Internet Technologies (By the way, greet the Web Alliance and thank you for the excellent atmosphere of the event!).
Flew back and forth from the former Siberia, now S7 Airlines. Departure from Moscow in the morning, getting to the airport for a long time, given the reserve for registration, will have to get up very early. Naturally - laziness. And then - about a miracle, service! The airline's website says that you can register online, starting a day before departure. Great news!
')
And now we open the site, enter the e-ticket number, select the airport of departure, see our last name, register. The next step is to print the boarding pass. And here the connection with the site breaks. We update the page, re-enter the ticket number - the site thinks for a long time:
And then suddenly he is stunned:
We repeat several times, but the result does not change. We do not lose courage, we call in support. The support report that “apparently, some work is being done on the site now,” so the site is unavailable and they cannot go there either to send me a file with the boarding pass. But that's okay - you need to arrive at the airport in advance and complete the registration there.
In total, it took me about three hours to various attempts to register online, including several support calls, since after long inquiries and attempts to log in, the operators recommended “to call back later, it may work”. Plus that time, which in the end did not manage to save money at the airport. As a result, the declared service turned into something opposite.
However, this whole article is not at all for the sake of complaining. We have didactic tasks, and let's move on to them.
So, what problems can we point out in organizing this online registration service?
The first is that for some reason it was not possible to achieve stable operation of the service. Either the bug was “by itself”, which was a disaster, or, as the operators said, “work was being done”, that in general no door would climb, because white day and quite a lot of visitors.
Therefore, we note that if we launch a project that provides service to our clients, it should work “in any weather.” In other words, always, and always well and steadily. Problems with the operation of such a project should be considered a critical event, and not to treat it calmly and relaxed (lie down, lie down, and get up ...). Accordingly, the operator, faced with a problem, had to report it to the “rapid response team”, and that, within the shortest possible time, the problem was resolved. At the same time, all other operators had to receive notification of the problem and a forecast for the restoration of working capacity in order to promptly orient customers.
In the above example, the service was not operational for at least 14 hours, specially checked late in the evening.
The second . Of all the possible ways to report an error, the most probably unsuccessful one was chosen. Look again:
They notify us in intelligible human language that they cannot process the request. However, there are no explanations or assumptions about the causes. Just "well, not shmogla." What can the user think? For example - that his electronic ticket "flew" from the base. Why not? Will this thought add peace to the client?
It's funny that any unreadable technical message in this situation would be better - it would immediately indicate a technical problem.
We write : Informational messages of the service should be as specific as possible and not force the user to guess and invent various horror stories. In this case, the first part of this phrase could sound, for example, like this: “Your request could not be processed due to technical reasons.” But this is not the whole phrase, so next is the third.
Third . User left alone with this message. What should he do next? "We could not process" - and what should I do? The wording used sounds even somehow apocalyptic - we could not, and no one can. And never. The user is offered the only possible option - to leave (the “Exit” button) and no longer load “us” with their exorbitant requests.
We fix : The error message must necessarily contain instructions for further action. For example: “Your request could not be processed due to technical reasons, try to repeat it after a while. If the problem persists, contact our support team. ”And the buttons -“ Repeat ”, returning to the initial form,“ Support ”, leading to the contact page, and“ Exit ”, since there is no way without it.
Fourth . In the above situation, both parties - the client and the operator of technical support, had a common tool, a web-based application, which, having blocked, prevented the first opportunity to use the service, and the second - to help in this matter. It seems that when organizing such a service, separate tools should be provided, duplicating each other, allowing “in manual mode” to bring the problem to a resolution.
So, the summary.
The title is not by chance the word "loyalty". It is such “trifles” as buggy, unreasoned services, in theory designed to make the life of the client easier, but in practice they create unnecessary problems and difficulties that affect the subsequent attitude.
A client who has broken off in his expectations becomes negatively biased and begins to interpret all the manifestations of the company in this sense. And broadcast your displeasure further - in conversations, in a blog, on forums. Or in the didactic articles on marketing :)
Therefore, remember that, declaring a certain service, you are not just doing a cool thing. You are creating a new type of relationship, taking on new obligations, creating a new loyalty management tool. Users satisfied with your service will become more loyal. And recommend to others. And vice versa - the opposite.
I returned from Krasnoyarsk, where I spoke at the Second Krasnoyarsk Conference on Internet Technologies (By the way, greet the Web Alliance and thank you for the excellent atmosphere of the event!).
Flew back and forth from the former Siberia, now S7 Airlines. Departure from Moscow in the morning, getting to the airport for a long time, given the reserve for registration, will have to get up very early. Naturally - laziness. And then - about a miracle, service! The airline's website says that you can register online, starting a day before departure. Great news!
')
And now we open the site, enter the e-ticket number, select the airport of departure, see our last name, register. The next step is to print the boarding pass. And here the connection with the site breaks. We update the page, re-enter the ticket number - the site thinks for a long time:
And then suddenly he is stunned:
We repeat several times, but the result does not change. We do not lose courage, we call in support. The support report that “apparently, some work is being done on the site now,” so the site is unavailable and they cannot go there either to send me a file with the boarding pass. But that's okay - you need to arrive at the airport in advance and complete the registration there.
In total, it took me about three hours to various attempts to register online, including several support calls, since after long inquiries and attempts to log in, the operators recommended “to call back later, it may work”. Plus that time, which in the end did not manage to save money at the airport. As a result, the declared service turned into something opposite.
However, this whole article is not at all for the sake of complaining. We have didactic tasks, and let's move on to them.
So, what problems can we point out in organizing this online registration service?
The first is that for some reason it was not possible to achieve stable operation of the service. Either the bug was “by itself”, which was a disaster, or, as the operators said, “work was being done”, that in general no door would climb, because white day and quite a lot of visitors.
Therefore, we note that if we launch a project that provides service to our clients, it should work “in any weather.” In other words, always, and always well and steadily. Problems with the operation of such a project should be considered a critical event, and not to treat it calmly and relaxed (lie down, lie down, and get up ...). Accordingly, the operator, faced with a problem, had to report it to the “rapid response team”, and that, within the shortest possible time, the problem was resolved. At the same time, all other operators had to receive notification of the problem and a forecast for the restoration of working capacity in order to promptly orient customers.
In the above example, the service was not operational for at least 14 hours, specially checked late in the evening.
The second . Of all the possible ways to report an error, the most probably unsuccessful one was chosen. Look again:
They notify us in intelligible human language that they cannot process the request. However, there are no explanations or assumptions about the causes. Just "well, not shmogla." What can the user think? For example - that his electronic ticket "flew" from the base. Why not? Will this thought add peace to the client?
It's funny that any unreadable technical message in this situation would be better - it would immediately indicate a technical problem.
We write : Informational messages of the service should be as specific as possible and not force the user to guess and invent various horror stories. In this case, the first part of this phrase could sound, for example, like this: “Your request could not be processed due to technical reasons.” But this is not the whole phrase, so next is the third.
Third . User left alone with this message. What should he do next? "We could not process" - and what should I do? The wording used sounds even somehow apocalyptic - we could not, and no one can. And never. The user is offered the only possible option - to leave (the “Exit” button) and no longer load “us” with their exorbitant requests.
We fix : The error message must necessarily contain instructions for further action. For example: “Your request could not be processed due to technical reasons, try to repeat it after a while. If the problem persists, contact our support team. ”And the buttons -“ Repeat ”, returning to the initial form,“ Support ”, leading to the contact page, and“ Exit ”, since there is no way without it.
Fourth . In the above situation, both parties - the client and the operator of technical support, had a common tool, a web-based application, which, having blocked, prevented the first opportunity to use the service, and the second - to help in this matter. It seems that when organizing such a service, separate tools should be provided, duplicating each other, allowing “in manual mode” to bring the problem to a resolution.
So, the summary.
The title is not by chance the word "loyalty". It is such “trifles” as buggy, unreasoned services, in theory designed to make the life of the client easier, but in practice they create unnecessary problems and difficulties that affect the subsequent attitude.
A client who has broken off in his expectations becomes negatively biased and begins to interpret all the manifestations of the company in this sense. And broadcast your displeasure further - in conversations, in a blog, on forums. Or in the didactic articles on marketing :)
Therefore, remember that, declaring a certain service, you are not just doing a cool thing. You are creating a new type of relationship, taking on new obligations, creating a new loyalty management tool. Users satisfied with your service will become more loyal. And recommend to others. And vice versa - the opposite.
Source: https://habr.com/ru/post/106139/
All Articles