Speaking Engagements & Private Workshops - Get Dean Bubley to present or chair your event

Need an experienced, provocative & influential telecoms keynote speaker, moderator/chair or workshop facilitator?
To see recent presentations, and discuss Dean Bubley's appearance at a specific event, click here

Wednesday, January 02, 2013

There really needs to be a "User tariff API" for developers

Generally speaking, app developers and website owners know what device you've got, what OS, and what browser. Furthermore, they know what country you're in, and a ton of other information from cookies or that you've filled in through registration. The more sophisticated companies can also work out how fast your connection is, and also already know if it's WiFi or cellular.

Using all this information, they can tailor their software or site to give a good experience - as well as using it to manage their own operational costs and resources.

But what they currently don't know is what all this is costing you, and how that might drive your preferences and behaviour:

  • What data plan do you have? Unlimited or capped?
  • How much data do you have left? When does the new month start? Are you in any danger of getting close to overage fees?
  • What policies are in place? Bandwidth limits, peak/off-peak differences, certain things being blocked or charged extra?
  • Are you a postpaid contract user, or a prepay user either with infrequent top-ups, or US-style monthly plans?
  • Do you get unlimited telephony & SMS? Or do you get a "big bucket" you never use?
  • Are you roaming (and do you roam often, and how much does it cost?)
  • What international call destinations are included in the user's plan?
If developers had access to this information in a better (and ideally consistent) way, they could design an app's experience to work better for individual customers. They could suggest using WiFi for large downloads, or double-check that the user really wants to spend 30% of their monthly data use by streaming a movie. They could know if the user is happy to send SMS's via the app, rather than using alternative messaging options. They could potentially know if "carrier billing" for in-app payments was realistic, or whether it would use too much of the user's outstanding prepay balance.

They could work out whether it was better for person A to call person B - or vice versa, with the app setting up a dial-in. Or if the data connection was good (or cheap enough), use a VoIP app instead, or WebRTC if browsers or gateways support it.

In other words, they could make their apps or websites better, by personalising them to their users' network tariffs and spending preferences.

There are however a couple of obvious problems here. Firstly, there is a huge diversity of plans, with increasingly clever variables involved (time, date, location etc). Some of those will become dynamic over time, eg giving notifications of "happy hours" as a promotional tool. Secondly, customers often don't know or can't remember accurately what plan they've got. Lastly, telcos are going to be very hesitant to give a clean and convenient API that essentially enables better and smoother arbitrage plays, or allows customers to get "as close as they dare" to thresholds but not cross them.

For these reasons, I'm not expecting to see "official" tariff APIs from many operators. But it wouldn't surprise me at all if we didn't see intermediaries or third parties spring up, who have at least *some* of this data available - especially basic information about data plans and voice minutes.

There's probably a great two-sided business model here in fact - if you collected details about millions of users' plans and usage (and kept it updated), you could supply both developers with an API, and you could advertise better/cheaper/more suitable plans back to the users themselves.

I already know about several apps that monitor / help users control their data usage (Onavo, My Data Manager etc) but I'm not aware if any of them have developer APIs, or also watch voice/SMS plans too.

Ultimately, something like this might even help telcos' own efforts to sell things like "sender pays" - if a content company knew for certain that you didn't have enough data-allowance to download a movie (or were getting close to your quota), it might be more inclined to subsidise it for you. On the other hand, if it knew that you've got plenty to spare, it could also let you know not to worry.

Someone will get this right, I suspect - although possibly it would make most sense to bake into iOS, Android and other OS's, particularly for the telephony aspect. However, billing/OSS players like Amdocs or Ericsson or Convergys should give it some serious thought. It could also be a fascinating Telco-OTT play, with great synergies for whatever operator developed and hosted it - how much would you like to know what plans all your competitors' customers have?

1 comment:

/\/\arekg said...

Actually I'm planning to start arrange part of what you call as tariffs API.
It will be more a database, simplified: only three rates per minute considered - lowest, middle, highest for both postpaid and prepaid.
And there will be all international and roaming rates.

This will be prepared (huuge effort of much more than 100 people across the world) by crawling through tariffs - and furterly kept in the way possible for automatic updates.

The purpose of this database is to show - as hard evidence - based on basket of predefined (different quantities for different user profiles)various services (incoming/outgoing local/international calls/SMSs/MMSs and MBs of data) to be used while roaming: our service vs. native MNO and other user-selected services (like e.g. Skype or TruFone).