There's an interesting phenomenon in WiFi: many users don't want to pay, but forget to pay. The system breaks the net on the day the set comes due."Why am I out of the net?"This silence is particularly common in prepaid venues like apartments, dormitories.——The user lives for three months, the second month's suite is off the net on the day it expires. He doesn't even realize he has to pay."Cutting off the money."The state of affairs is inadequate and there is a mechanism for reaching out to the public.
Let me be clear:The notice is not harassment. It's part of the billing shut-down.The user gave the money. The system has to tell him."The bill is here. The package's in effect."The user's running out of money. The system has to warn him."We're running out of balance."The system has to tell him that the user package is almost due."Three days to go.". The notifications are not sent, and the user is black boxed between the system: the user does not know how much money it has in its account or when it expires, but the system suddenly breaks off the web at the moment of maturity, which is a very bad experience.
V7 NATHHELL_AUTH_BILLING, which is based on several channels.Text message.: Insufficient balance, mating of the package, successful charging and unusual login. These events can be sent with text message templates. The benefit of text messages is that almost all phones receive them without relying on users to install an APP; the disadvantage is to get a SMS gateway, billed, and often used as garbage text messages. So text messages are needed at key nodes, so nothing can be texted.
The more cost-effective passageway isWeds and small program announcementsV7 supports micro-credit authentication and small program payments, the user has completed a public number or sub-procedure through the micro-link process, followed by billing notices, renewal reminders, successful replenishments that can be pushed over via a micro-mail service notice at much lower cost than text messages, and opening rates. Many apartment operators now have to send out a sMS drive with key nodes (e.g., expiry of the last day) and daily alerts to take a micro-service notice, so that users are neither leaked nor wasted.
The timing of the notice is more important than the content of the notification.. The user forgets too early; it is too late to be informed, but not yet. The more reasonable rhythm is three: the first warning is three to five days before the package expires, telling the user when and where the fee link will expire; the second reminder is made on the day before the break; and the third time after the net is really off, send a single."Your network has been suspended and the click charge is restored immediately."The same is true for users with insufficient advance balance: the balance is used to 20%, and 5%, not until full arrears are paid. This rhythm is not determined by brain count, but by the constant rate of renewal in the statements——If the reminder rate is still low three days before the due date, it is advanced to seven days and if user feedback is disturbed, it is consolidated into one.
There's another kind of notice.The bill itself.. A lot of users are right."How much did you charge me this month?"The V7 user self-service system allows users to search fees, log online records, and access traffic; but the system does not automatically push bills to him. It is mature to push last month’s bill through a micromail or mail at the beginning of each month to indicate the cost of the monthly package, traffic usage, balance changes."Why am I being held back?"Such complaints——Many cost objections, which are that users never know what happened on their own books.
Here's a border:The ability to notify is not the same as a marketing bombing.Some operators use Portal pages and notice channels as advertising slots, pushing the menus daily to users, pushing events and pushing third-party advertisements, which result in users turning public numbers off, blocking text messages, and flooding out of real important renewal notices. V7 supports Portal pages using 4W+B+S strategies to push different content, but this is a business strategy at the level of system delivery.——Service announcements must be guaranteed and the marketing notices should leave a counter-subscript for users.
What's easy to ignore in the actual project is the bottom of a failure to notify.The user phone number changed and text messages were empty; the user shuts off a public number, we can't get a micro-letter; the information that the user fills out is random and not personal. These systems don't automatically know, they just take it."Sending Failed"The V7 supports the cell phone number, ID card, name and name as compared to the actual name. When opening an account, it blockes the false number, much better than when 100 notifications are returned.
And there's another reality:Notification of charges for front desk or agentThe landlord pays the tenant cash, he doesn't receive any call on his own phone, and he thinks the owner has not. This system supports: whoever charged the value, a successful notice must be sent to the user ' s own cell phone, not just to the replacement. That seems fine, actually dealing with trust issues.——Tenant trust in the system only accepts self-service contributions; if you have to ask for it yourself every time you pay"Are you in?"And this pattern won't move.
The notification layer of WiFi's system is the blood vessels that connect the system and users. The system is accurate, and users do not know, see, or receive warnings, turn into complaints and losses. The alerts for maturity, balance warning, charging back, monthly bills are matched with a reasonable rhythm, text messages and micro-mail access, service rates are regularly monitored, and leakages from the pay-in-the-hear payments can be dropped. This is not a technical difficulty, but a business detail, but it is a place where many billing items are never touched after they have been completed.