
If enabled, the guest login page will ask for Room-Number & GuestName/Reservation-ID/PIN-Number as set by PMS. Though this is a fully automatic mode, but may not be totally secured because such guest-details are shared to other departments also in the hotel.

If enabled, the guest login page will ask for Room-Number & GuestName/Reservation-ID/PIN-Number as set by Receptionist (during when there is no PMS integration). The receptionist has to enter such details using 'Receptionist Console' manually during every check-in. Similar intervention is necessary during check-out also.

If enabled, the guest login page will ask for Room-Number & PIN Number. The hotspot server will SMS a PIN Number (suggested by PMS / generated by hotspot-server) to the RoomGuest immediately during check-in. This is the most secured mode because the PIN Number is known ONLY to the room-guest.

If enabled, the guest login page will ask for Room-Number & PIN Number (during when there is no PMS integration). The receptionist has to use 'Receptionist Console' to enter guest's room-number & mobile-number to SMS him a random PIN-Number, manually during every check-in. Similar intervention is necessary during check-out also.

If enabled, the guest login page will ask for username & password (of the WiFi voucher, sent through SMS). The receptionist has to enter Room-Number & Mobile-Number using 'Receptionist Console' to SMS a voucher. Because, the voucher is delivered through SMS, this method is relatively secured and meets legal criteria.

If enabled, the guest login page will ask for username & password (of the printed WiFi voucher, handed-out by receptionist). The receptionist has to enter Room-Number & voucher-Number in the 'Receptionist Console' while issuing each voucher. Any manual error by the receptionist, may lead even unrelated innocent room guest to legal risk, imagine receptionist typing wrong room number.

If enabled, the guest login page will ask for username & password (of the WiFi voucher, sent through SMS). The receptionist has to manually enter visitor's Mobile-Number using 'Receptionist Console' to SMS a voucher. Because, the voucher is delivered through SMS, this method is relatively secured and meets legal criteria.

If enabled, the guest login page will ask for username & password (of the printed WiFi voucher, handed-out by receptionist). The receptionist has to manually enter voucher-Number & Visitor-Details (to meet the legal criteria) in the 'Receptionist Console' while issuing each voucher. This method is laborious and also prone to receptionist's human error.

If enabled, the guest login page will ask for mobile number & password. Any New User can use BLANK password to get his random password through SMS. These users will be limited as per a Top-Listed-Plan in Self-Signup-Plans-List. It is suggested to set per-day-limit for this plan, to avoid neighbours exploiting your bandwidth. This login method will be useful for Airport/Corporate/Mall scenario to allow free access for the visitors after SMS authentication. When expired, the users can always purchase TopUp-vouchers either manually/online for further access.

If enabled, the guest login page will ask for mobile-number & activation-code. Any New User has to get the Activation-Code manually (from the receptionist) or online, and enter, and get OTP (one time password, through his mobile) and use the OTP to login. This is useful when the cafe decides to distribute vouchers only for specific users (example, who at least comes inside the cafe to get the voucher). This can be used in combination with Option-4 also, wherein Option-4 can be useful for a mall, and this Option-5 can be useful for a cafe inside the SAME mall.
Enable / Disable SMS Settings
Enable / Disable SMS Settings
Enable / Disable SMS Settings
Enable / Disable SMS Settings
Enable / Disable SMS Settings
Enable / Disable PMS Settings
Random Password Settings
Reboot/Shutdown
Backup/Restore