CLL is not a solution - it is a problem. The line being locked effectively bricks a smartphone - I haven't tested it but I imagine with CLL in place a Red Unlimited (or whatever it is called) customer could find themselves unable to make phone calls because their account went OOB and hit the ceiling.
The bottom line is that to use the prepaid billing approach - and thereby avoid OOBSharkey - requires (a) that you sacrifice postpaid contract benefits such as Night Owl and (b) that you data driven SIMs are on a different device to you postpaid contract
The current setup does not encourage users to comfortably and conveniently sign up for a postpaid cellular contract and take up high data usage and I know at least two people who have smartphones that don't even have email set to the device because of the fear of the OOBShark and it is the height of corporate stupidity to sell people expensive devices on contracts that they then don't use the features because to do so carries a risk that the company can prevent.
As for a solution within the existing system: one has been put forward on this forum that works using the reforms on the billing system. If your engineers can't build on what has already been set out, make an offer. The OOBShark can be sorted out once and for all it is simply a refusal to recognize the actual problem and provide a solution.
The bottom line is that to use the prepaid billing approach - and thereby avoid OOBSharkey - requires (a) that you sacrifice postpaid contract benefits such as Night Owl and (b) that you data driven SIMs are on a different device to you postpaid contract
The current setup does not encourage users to comfortably and conveniently sign up for a postpaid cellular contract and take up high data usage and I know at least two people who have smartphones that don't even have email set to the device because of the fear of the OOBShark and it is the height of corporate stupidity to sell people expensive devices on contracts that they then don't use the features because to do so carries a risk that the company can prevent.
As for a solution within the existing system: one has been put forward on this forum that works using the reforms on the billing system. If your engineers can't build on what has already been set out, make an offer. The OOBShark can be sorted out once and for all it is simply a refusal to recognize the actual problem and provide a solution.