While most people on this forum understand the concept of being throttled after reaching their cap (as opposed to being hard capped, like most other providers), there are many, many iBurst subscribers who don't understand this at all.
They just see a 'slow network' (capped to 64kb/s) and then promptly call the help desk and complain about slow speeds. This is not good, they're peeved and it puts extra load on the help desk.
To try and resolve this, we introduced the redirect page. Initially it was only going to be the first time you log on (and you're already capped), you'd be redirected.
But we found that many people never disconnect. My own 2M modem only disconnected twice (both times due to network upgrades we do around midnight) in the last 3 months. For the rest of the time, my PC stays on and the modem stays connected.
So, here's the dilemma:
1) We give a feature everyone likes (uncapped accounts).
2) It causes false calls to the help desk.
3) We introduce a landing page to remind people about it but we need to strike a compromise between being irritating and reminding people they're throttled and it's not a slow network problem.
4) We get blasted for it.
So, currently it's at logon and at every hundred clicks.
We can do a few things to resolve this:
1) Stop the throttled service. It's pretty much unique to iBurst to provide uncapped access. Then if you reach your cap, we cut you off like the other operators do and you must first top up. (Someone I suspect this will go down like a lead zeppelin

. But it will resolve the problem.)
2) Remove the 100-click re-direct and just do it on logon. But then the calls will start coming in again.
3) Make it more than a 100, re-direct on every 100MB downloaded, etc. This will just push the reminder out.
4) Do it once per hour / day, etc.
5) Drop your connection every time interval. (Once per day for example. did Telkom not do this at some point?

) Or maybe after every 100MB. Then you only get one 'logon' reminder per session.
6) Introduce an opt-out option. I like this idea, but it'll require development so I need to check the impact. But it's a good option. Potential issues include that you move the config from the network (where it is a single configuration for everyone) to a system (where it is now a complex system with an entry per user.) And this is a classic chance for something to break.
I must say, I'm (pleasantly) surprised that you guys still browse after being capped. I thought it would mostly be used for torrents, etc. I did not think 100 clicks would come up so quickly. You fingers must suffer from Repetitive Stress Syndrome.
If we can't do the opt-out, I'd suggest one re-direct per day (if do-able). Feels like a good compromise.
Your thoughts?