The first impression of the hotel WIFI is often created in a matter of 10 seconds after it was connected to the Internet. The certification process is well designed and its customers are almost unconscious; it's poorly designed, and guests take several steps and lose a lot of information before they get online. Real name certification is mandatory, but how to do the process as light as possible while fulfilling it is a test of design power. This is a special discussion on how to balance compliance with experience by applying the actual system WIFI certification.
The guest is better off with a real no-sense certification.
For guests, the ideal experience is that they can be connected to WIFI because they have been registered in the front desk and the identity of the Internet is already available. If the authentication system and PMS are used, the guest will be certified by a room number plus a name or mobile tail number 1, even if the first connection to the equipment automatically carries registration information. So the client hardly needs extra action. The condition for non-sensor certification is that PMS has access to the position, data real time, and the docking hole described earlier, which is not repeated here.
The authentication page is automatically ejected after the WIFI is connected.
Many clients do not know that the browser is needed to trigger the authentication page, and even if it is found unusable on board the WIFI. The good design is that the certificate page automatically pops up as soon as the customer comes in, as many public WIFIs do. This relies on the system to re-direct the uncertified terminal's HTTP request correctly. It also needs to process the window mechanism of all types of mobile systems. Apple and Andre are triggered slightly differently."Why aren't you online?"The phone.
As few information as possible on the authentication page
If a customer needs manual authentication, such as when a visitor or PMS is not connected, the less things to fill in on the certificate page are needed. The mobile phone number plus the certification code are a more balanced way of filling out a real name and familiar with the guest. To avoid having customers fill up a lot of irrelevant information, companies, jobs, mailboxes, these fields that have nothing to do with Internet access, etc. For every one fill-in, the number of guests will be dropped midway.
Clear feedback after certification is successful
The client is certified and has access to the Internet. Some systems have a blank page, or stop at the certification page, and the customer does not know it's done, but has ordered several times. There should be a clear indication of success after the certification process, or jump directly into the hotel ' s welcome page, official website headline, so that the guest knows that it can work. This little detail will reduce confusion and duplication among many guests.
Multiple equipment processing should take into account
The experience is bad if every device has to be re-certified completely. It is better that the number of devices can be tied up in a reasonable amount, and other equipment used in the same room after a customer certification is more easily accessible. Of course, the number cannot be unlimited or could be abused.
The certification process is fast. Don't keep the guests waiting.
The client points to authentication to real access, and the waiting time in the middle directly affects the experience. If the authentication server responds slowly, PMS queries data slow, text message-codes less than half a day, the customer is upset. Each step of the certification process takes time, the authentication code comes second, data search fast, and authentication judgement is instantaneous. Behind this is a combination of server performance, chain quality, and SMS channel stability. The question of simultaneous distribution was raised earlier on web check, with certification often at a peak and pressure high. Process design is designed to allow speed to move away, allow for distance, provide a buffer and pressurize the guest ' s wait to the shortest possible.
Authentication failed to give a clear indication.
When the authentication failed, the room number was wrong, the name was not right, and the code expired. The clue to failure is specific, understandable, telling the guests what they were wrong about, what to do, not a saying."Authentication failed"It's hard to think."Please check the card or contact the front desk."A clear hint of failure will enable clients to solve most problems themselves and reduce the number of calls to front desk. This is also a part of process design that can be easily ignored but very influential in its experience.
The core of the authentication process design is to keep the physical name as a hard line, and to keep the client's operation and waiting minimum. The guest is as insensitive as possible, the visitor is as clear as possible, feedback is clear, failure is fast enough, and there are guidelines for this. This is done so that the hotel WIFI authenticated access system can be both compliant and non-attendant.