FuLL_MeT4L
Expert Member
- Joined
- Oct 25, 2004
- Messages
- 1,230
- Reaction score
- 3
Actually we've setup our backend to do precisely this. The development is not that tricky, but we have to build an API on our network systems to do this. So the API is being built so that it checks overall network usage against a few parameters, does a JSON call to our usage tracker per account, and then links to our CRM system to send customised, realistic, and informative data to our customers about their current usage vs our network and how best to help us keep it in line, without having to ask customers to download less. Essentially we'd like to be able to send each customer detailed information in our daily usage emails to them, with customised information about their usage patterns, that will assist our customers in scheduling their large downloads to run off at the right time.
Oh wow. Awesome!
Actually no... I get where he is going, but I'd take it even a step further (even though the dev is not worth the effort more than likely)..
Provide an API that can be called once a day or something, that will provide suggested time frames for unthrottled connections and then users can call the API and then modify their schedules automatically to suit. It might even out the network load a bit because your high end users are also the ones who will hopefully be tech-savvy enough to implement something of that nature.
I love this, but you're right in that too few would be able to hook it up.