Free WiFi in public places, with users certified at intervals from the top to the bottom of the Internet. This process is designed to determine whether the user stays or turns around. We do a rough count, just like the commercial WiFi, where certification steps are more than 30% lower than the actual completion of the access. Users are not patient."It's for your own good."They only care about one thing: a few more points to get online. It's much more important than a stack of functions to use process design as a product experience.
The number of steps is the hardest indicator of loss
Each step of the operation, a user is sifted. The ideal public WiFi certification is"I want you to connect the automatic page, fill in your cell phone number and access one key."Three steps within. But there are many systems that have agreed to take it."Reading clause""Select the package""Watch the public."The user is bored with the process. We have seen a viewing area, WiFi, where the certification page was advertised, then a questionnaire and finally a certificate code, and half of the visitors gave up, and backstage data showed less than 40% completion.
The authentication code waits to determine the first impression.
Users fill out the cell phone to obtain the code, and if they get five seconds of confiscation, most people do not wait, but simply break the reconnect or switch the network. The stability of the authentication code channel, the speed of its arrival on SMS gateways, is the most easily underestimated part of the authentication process. Once a project was lined with an unknown text message route cheaply, the peak period code delayed by more than ten seconds, and the complaint telephone was blown off.
Balance of one key login and secondary decertification
The user's first authentication is a bit complicated, but every time you have to re-do the process, it's bad. A good system does it."Remember Device"Or..."Exemption from authentication during active life", keeping users in a less operational position to the extent that compliance permits. Here you have to be sure of the degree of confidence: the length of the release cannot be unlimited, because otherwise it would amount to a disguised abandonment of the real name; too short and unexamining. We suggest that the day-to-day location of the malls is set as a scenario, that hotels are available for check-out, and that office space can be trusted over time with the work number. This level is not a technical parameter, but an operational judgement.
The loading speed of the authentication page itself
The authentication page itself, Caden, is more lethal than the back end, because users can see it. Some manufacturers have a certified page with video background, rotation plans, a bunch of JS effects that cannot be opened for half a minute in a cell phone network environment and which users think is not connected to. The authentication page should be as light as a plain text, first screen seconds open, functional restraint. When we optimize our clients, the first thing is to delete all non-essential images and scripts on the certification page, leave only titles, input boxes, buttons and necessary legal tips, drop loading time from three seconds to zero points, and the rate of abandonment improves immediately.
The guide is more important when you fail than when you succeed.
Authentication failures are inevitable, but failure tips determine whether the user should retry or abandon."System error. Please try again later.", the user cannot read or try. A good hint should tell the user about the reasons and next steps, for example"Could not close temporary folder: %s"Or..."The network is busy and you can click below to try again."We have encountered a case where failure reminders are changed from generic reporting errors to specific guidance, and the certification success rate is mentioned several points. User loss often is not due to failure but because it is not known what to do after failure.
Multilinguality and accessibility do not wait for trouble to come.
The WiFi of the ports, scene zones and international hotels, which have only Chinese pages to keep some foreign users out of the door. Not everyone can cut words or see small words. It is recommended that the authentication page provide at least a switch in Chinese and English with a key button number that is large and comparable. This seems a minor matter, but it is a direct manifestation of professionalism for a high-level guest service. When we do this for an airport ' s hotel around the airport, the head of operations is especially interested because there are former guests who complain about not being connected to the Internet.
Optimize with data reverse process
The process is not always good, but it depends on how many. The authentication system usually records the rate of transformation at each step: how many people pop out the page, how many have filled their cell number, how many have their code and how many end up online. Pulling this number out, the loss is clear to which point it occurred."I filled out the cell number and didn't get a code.", the explanation is that the buttons are not clear enough or the user does not trust. It is much more useful to look at data and change processes than to shoot head plus functionality. The authentication process is a continuous process of improving performance without being online.