The WiFi network billing system has a non-recoverable function: late fee processing and offline strategy. What about the user balance under prepaid models? What about the user debt under post-payment? Is it a direct break or a buffer period? How do you recover after off? These issues look like functional configurations, actually business strategies. Poor match, user complaints surged, customer uniforms inundated; well equipped, users cannot sense surprises, and arrears can be treated with dignity.
Different logic in the treatment of prepaid and post-payment arrears
WiFi web billing system, where prepaid fee is used, has a relatively simple processing of arrears——The balance is fully utilized and services are discontinued."Processing"Actually,"Prevention arrears"——The system is expected to provide early warning when the balance approaches zero, giving users a chance to fill it. The warning strategy suggests two levels: alerting the balance to 10% and sending the balance down to 0:00 instead of directly breaking the network. Direct break-up is too abrupt for the user to feel, so that the user can be given a buffer.——The user will naturally charge it. The later payment model is more complicated than the outstanding fee processing.——The user pays the fee first, and then charges are paid at the end of the month before a bill is made.
Early warning and buffer mechanisms before the break-up are key
WiFi network billing systems must have early warning and buffer mechanisms before the breakup, regardless of whether they are prepaid or paid."Normal use"Jump to"Completely off the grid.", the user experience is extremely poor. The logical breakout process is phased: phase one (balance warning)——Remaining traffic or up to 20 per cent of the time, alert users by text message or App; phase II (speed reduction stage)——By 5 per cent, the bandwidth will be low but not completely broken and users can send micromails but cannot see videos; phase III (disconnection stage)——Completely use the network to disconnect, but keep a channel that only accesss the page for the charge. This phased strategy will lead"Disconnect"It's become..."The gradual experience is falling."Users have a response time and the number of complaints will be significantly reduced.
Recharge the line after a break in the network to remain available
The WiFi network billing system is supposed to be able to keep the user fully loaded when the user is off. That sounds bullshit, but many systems are out of order here. After the user is out of the network, all network access is blocked, including the page with a chargeable value. Users can only use mobile traffic (if any) or go to the network central counter."White List Channel"——In a network break, only the charge page and payment of the platform domain name are allowed, with all other traffic blocked. The white list channel is configured correctly to include all the payout platforms 'domain names, otherwise the user cannot load a resource during the collection process.——The white list of payment platforms for the change of domain names is not updated and users cannot be valued.
The solution to the speed reduction strategy is balanced with user experience
The WIFI network billing system's speed-down strategy is the core of a pre-disconnected buffer mechanism. How fast does it go? It's like zero, and it loses its buffer; it's too low for users to feel.——We can send text messages at this speed, but the video is basically not working."The speed's not right."But it won't be completely cut off. Speeding down strategy is about to come into effect.——The balance is immediately reduced to zero, without a few minutes ' delay, or the user will continue to use it normally during the delay period, generating excess traffic.——Tell the user what the reason is and how to solve it. Silence slows down so that users don't know what happened, and there will be more complaints.
Retention and recovery mechanisms for outstanding fee records
WiFi network billing systems keep complete records of those who owe the fees. The charges are not equivalent to a fee disappearing, and user-receipt payments under the later payment pattern are recovered. There are several levels of recovery mechanisms: minor arrears (within one month) are paid through system alerts; moderate amounts due (one to three months) limit some functions (e.g. high bandwidth applications cannot be used); heavy amounts due (more than three months) are frozen and require processing at the counter. All notification records, user response records are kept during the collection process as a basis for follow-up.——If you do not do this, the fee is bad and the income from the school network is lost.
Exemptions and extension mechanisms in exceptional circumstances
WiFi’s network billing system is subject to various special circumstances when it carries out a disconnection strategy.——The operator can temporarily restore the network to users (for example, 24 hours) or adjust the arrears. Exemptions are subject to a process that does not allow individual operators to operate at will, or may be misused. Exemptions are kept in their entirety, including reasons for exemptions, operators, approving officers, and recovery times.
The breakup strategy is to be retraced and adjusted regularly.
WiFi’s network billing system is not a breakout strategy that is set up once and for all.——The number of complaints from the offline is high, the reasons for the frequent complaints and the rate of conversion of the post-off. This indicates that the strategy is too radical or inadequate to warn. If the change rate is low, it may be problematic to clarify the list access.——For example, the early warning threshold is raised from 10 to 15 per cent, so that users know that rules change. Rules are more transparent than rules themselves, and users do not know they feel that the system is targeting themselves.