When the campus access billing system is online, the most intense source of complaints during the operation period is often not a system failure, but rather a flow pack design itself."Where's my traffic?"Right."The net is slow."More sensitive.——The cost is real silver, and when the bill is not transparent, complaints can spread in the dormitory area, where people complain, and soon they will be around. This article does not mention the technical realization of the flow packs, but simply says that the number of complaints for which design programmes are relatively low and those on line are easily problematic from the point of view of their actual operation.
There are fewer complaints of non-mortality than of zero monthly.
Students use the Internet in a highly uneven manner: there are few games, no videos and little traffic consumption before or after the examination week; on the eve of vacation or overnight weekends, traffic can be reduced by one week. If the pack is at monthly zero, a group of students will feel that every month at the end of the month"I'm not buying the traffic anymore."The system of monthly uncertainty (a cumulative roll, with a general ceiling, for example, effective over six months), the student’s initiative and control over the traffic bag is much more active, with a significantly lower rate of complaints than that of zero. From an operational point of view, cumulative flows do add some peak pressure, but this problem can be controlled in conjunction with the capping of the flow of the billing system.
The traffic is more visible in real time than the post-post.
Many systems are designed to use a threshold for text messages or micromessage. Students usually don't see any real-time residuals. This design has an obvious flaw in the user experience.——Students don't know who they are."How much is left?"It's only when we're running out of time that you get a passive notice."You're waiting for me to run out of it.". Real-time search portals (Portal pages show real time surpluses, micro-credit programs are tied and checked at any time) can significantly reduce such complaints because students have the means to be proficient and do not feel that the charges are opaque. Technically, real-time residual queries are less stressful to the back end than they are a low cost but clearly effective design point.
The package should not exceed three.
Some schools prefer to give students more options, designing five or seven-package packages, and instead of knowing which ones they buy, the number of customer calls and online consultations has increased dramatically."Select Paradox"It's also on the flow set.——The more options you have, the harder to make decisions, the more users tend to buy nothing or choose one and regret it. In practice, a diet with relatively low complaints rates is usually three-track: one basic (for light users), one main level (to cover 80% of students' daily needs), one high-level (for game parties, video parties). The price gradient between three levels is designed logically and cannot be allowed."I'd rather buy two lower ones."This algorithm appears, otherwise students will be specifically assigned to the accounting process and the conclusions derived are transmitted across the halls, raising questions about the fairness of the system.
Time strategy is public, not secret speed limits.
Many campus-based Internet billing systems have a speed-limit strategy for night or peak hours, which is itself a reasonable means of network management, but the most problematic is that students do not know about it and find the speed to be significantly slower than the mark."My package was fucked.". The time limit rules (as specified on Portal pages and purchase pages) reduce the number of complaints."Speed limit at peak hour"Far more than not."I don't know why the net is slow."It's much easier. Transparency is more important than perfection.
Refunds and balances refunds should be smooth
The refund of the balance is a centralized complaint scene when students transfer to school, drop out, and graduate. If the refund process is complicated, approval cycle is long, even if you need to run off to the Treasury, it may be small money in itself, but emotional frictions are magnified."School pit money.", fermented on social media. A smooth refund process——Online requests, clear processing time frames (e.g. 5 working days), automated reconciliations——Not only will complaints be reduced, but it will also reverse the evaluation of the entire Internet billing system. The priority of this function is underestimated in many school choices and often used as a tool for learning how to pay fees."Follow-up"Keep it, but only when it is actually operational will it be discovered that the complaints are lodged annually.
Rules on the attribution of shared equipment to traffic
In the accommodation environment, students share a network with their roommates by routers or give other people in their dormitories their own flow of accounts. The campus Internet billing system is prone to disputes if it does not provide clear rules for multiple equipment binding and traffic sharing: a person’s account is used by his roommate to run out of traffic, but the system has no warning or tie-down restrictions, and the complaint is made. Reasonable design is to specify the maximum number of terminals that can be tied per account, to alert users when they are bound, and to show in the bills how much each device is used (if technically differentiated). This rule is to inform users at the registration and purchase points rather than waiting for the terms to be taken.
You have to understand the billing format.
Many systems have these: XX MB, deductibles, balance XX. For light users, but for perception"I don't have much to use, but I'm keeping a lot of money."The bill is usually designed to show the daily use curves, display high consumption times, distinguish between the consumption of different equipment (if there are many devices)."Oh, so it's all Saturday night."——A clear bill would naturally dispel a large number of doubts and would not require manual intervention on the part of clients.
The flow pack design does not have an absolute correct answer, and schools of different sizes and nature (specialties, undergraduates, graduate studies) vary widely in terms of web-based behaviour, with specific strategies adjusted to actual use data.——Zero clarity, real-time visibility, streamlined slots, transparent rules, smooth refunds, readable bills——Repeatedly tested in practice is the most direct means of reducing the density of complaints. Writing these points as functional requirements at the system selection stage is much less costly than going back online.