Amazon Tech Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Friday, 11 May 2012

Phone number as OTT identifier - a problem in the making?

Posted on 01:21 by Unknown
I got an SMS this morning from a business contact - actually a client from an operator who came to the Telco-OTT workshop a couple of weeks ago. It was an invitation to download TU Me, the new Telefonica VoIP and messaging app, sent from within the app itself.

But as it happens, I've already got the app on my phone. But what I don't have on my phone is this person's phone number. So I can't connect to them. And so TU Me didn't realise we already knew each other.

This got me thinking. A lot of the more successful recent OTT apps (whether Telco-OTT or Internet-OTT) have used the contact list and people's phone numbers as easy ways to make connections. Viber and WhatsApp both do this. There's been a bit of a privacy outcry about such apps uploading your contacts to the cloud, but newer ones like TU Me seem to have smoothed peoples' fears and claim that they only use the data to find other contacts.

In many ways, this is a good thing. It helps automate the process of "virality", by seeing which other app users have your phone number, and vice-versa, in their phone books. Using the number gets around random spellings and nicknames - if you have 07111 222333 down as "Johnny Boy" it doesn't matter, as long as Jonathon / John / Jack / Jon has your number in his phonebook too. It also avoids the complexity of issuing and managing a separate ID and login (eg I'm @disruptivedean on Twitter, although I use my real name on LinkedIn and Quora).

But phonebook-driven virality only gets you so far. Traditionally, I would have had all my contacts replicated in my handset, including the client I mentioned at the start. But I don't. I only have people that I actually want to phone or SMS on a regular basis. I don't "add contact" in my Outlook and sync everyone to my phone. I don't use vCard. I only have about 50% of my Facebook friends, maybe 10% of my LinkedIn contacts and 1% of my Twitter followers' phone numbers on my phone.

I don't want 1000+ people in my handset phonebook. In my head, the phonebook is for certain use-cases - eg chats with friends and family, arranging meetings with regular clients and business contacts (often via SMS), some businesses I need to call frequently (accountants, bank etc) and a bunch of "legacy" numbers I ought to delete. I don't want to scroll past dozens of acquaintances that I'll never actually contact "by phone". I also want to reduce the risk of embarrassing mistakes, like accidentally mis-keying and sending personal texts to work contacts.

I've got plenty of good business and personal contacts I have no intention of saving in my phonebook, because I know I'll likely never phone them. In particular, I don't bother with most international numbers as usually I'll only call at specific times - and then I'll use Skype from my PC (or occasionally my handset). Or if I do suddenly need to call for some reason, I'll probably use Outlook to find an old email from them, and just dial the number in the footer. And then not save the number afterwards.

Now some people are probably different. They'll use various forms of syncing, and have a single contact list. Good for them, but not for me. I guess my client has my number in my phone for this reason - or perhaps he put it in his contact-list pre-emptively in case he got lost or delayed on the way to the Telco-OTT workshop. I prefer maintaining multiple independent lists - especially keeping work & personal contacts about 80% separate. I also use different names / pseudonyms, and avoid things like Android because I don't want everything converged.

Which brings me back to OTT apps like TUMe and WhatsApp and Viber. There may well be instances where I do want to connect with people like my client on these tools. They might evolve to have certain use-cases that go beyond my normal use of telephony and SMS, for example being good for occasional contacts, IM chats or image-sharing.

But if I'm forced to use a phone number as an identifier - and enter it in my main "master" phonebook" - then I simply won't do that.

I think that using the number is a neat way to get early "virality" - Viber proves this. But it runs into a ceiling after a while. Not only that, but many PC/tablet-based users don't want to associate a phone number with a given messaging or social account. No matter how many times Facebook and Google try to take my mobile number "for backup purposes", I tell them to get lost.

This is true for things like RCSe as well - I remember a Middle Eastern operator ask a question at a conference a few months ago, wondering if it was possible to have a separate ID (eg an email address or a BBM-style PIN) for the account, as users in his region are wary of sharing phone numbers but may still want to IM. There's a ton of social, cultural and psychological factors at play here around phone numbers.

I think there's a reason that the most successful OTT services such as Facebook, Skype, BBM, Twitter and others have managed to scale so well - unique IDs. They have also been able to use third-party directories - phone contact lists, Gmail and Yahoo and AOL accounts etc - to help find contacts, and selectively invite people to become friends/contacts on the new system.

As our use of telephony and SMS diminishes, one of the side-effects will be a parallel fall in the value and usefulness of the phone number. Add in multiple numbers, churn, portability, "temporary numbers" and other factors and it gets worse still. OTT players (Internet or Telco) who use the directory & E164 identifiers will get a short-term quick win, but face an uncertain future if they depend on a source of identity that is sliding gradually into irrelevance.
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Mobile social networking - how I'll know when it's going mainstream....
    This falls into the category of "amusing personal anecdotes" rather than "rigorous industry analysis". But it also refle...
  • Forget lobbyists, this is how Net Neutrality gets enacted in law....
    I've long held that the Internet will always find ways around any blocking/filtering mechanisms for certain types of application, especi...
  • UK ISPs Code of Practice on Traffic Management - OK as a start, but major flaws
    A group of the UK's largest fixed and mobile ISPs have published a "Code of Practice" about managing traffic on their broadban...
  • The danger of "cutting the cord" - where's the femtocell going to go?
    I see many references to people wanting to "cut the cord", and have an all-mobile home. This is particularly the case in the US, w...
  • The "Social web" - does anyone actually want it?
    Is this another example of The Emperor's New Clothes? I've lost count of the number of pitches I've heard recently along the lin...
  • The mobile industry buzzword of 2009 will be......
    OFFLOAD This year has been all about mobile broadband revenue and traffic growth. Dongles, iPhones, embedded PCs, Android, consumer BlackBer...
  • What's the story with the Phonejack 'femtocell"?
    I'm now trying to catch up with events and analysis over the past few weeks, as I've been on vacation. One of the more bewildering t...
  • The Novatel MiFi - possibilities for new mobile broadband business models
    OK, I realise that I've been a bit grumpy and critical of some things recently. But before everyone assumes I'm getting more cantank...
  • The risks of ignorance-based pricing strategies for telecoms
    Almost exactly 5 years ago, I wrote a blog post cutting through the myth of "value-based pricing" in the telecoms industry. It fo...
  • Android - the retail experience
    I just stopped off at my local branch of Carphone Warehouse on a whim, to have a quick look at what's being sold and how. (By coincidenc...

Blog Archive

  • ►  2013 (31)
    • ►  October (2)
    • ►  September (3)
    • ►  August (1)
    • ►  July (2)
    • ►  June (6)
    • ►  May (5)
    • ►  April (1)
    • ►  March (3)
    • ►  February (3)
    • ►  January (5)
  • ▼  2012 (46)
    • ►  December (5)
    • ►  November (4)
    • ►  October (3)
    • ►  September (2)
    • ►  August (4)
    • ►  July (3)
    • ►  June (1)
    • ▼  May (6)
      • Updates on VoLTE - secondary not primary voice?
      • The telecoms industry and a dual-dilemma problem
      • Phone number as OTT identifier - a problem in the ...
      • Telefonica TU Me - first salvo in full-scale inter...
      • Summary slides on Telco-OTT rationale
      • Upcoming Events: Open Mobile Summit, NGMN, Small C...
    • ►  April (4)
    • ►  March (1)
    • ►  February (9)
    • ►  January (4)
  • ►  2011 (73)
    • ►  December (4)
    • ►  November (10)
    • ►  October (8)
    • ►  September (6)
    • ►  August (3)
    • ►  July (5)
    • ►  June (7)
    • ►  May (9)
    • ►  April (4)
    • ►  March (7)
    • ►  February (6)
    • ►  January (4)
  • ►  2010 (130)
    • ►  December (4)
    • ►  November (10)
    • ►  October (10)
    • ►  September (6)
    • ►  August (9)
    • ►  July (7)
    • ►  June (19)
    • ►  May (19)
    • ►  April (11)
    • ►  March (18)
    • ►  February (7)
    • ►  January (10)
  • ►  2009 (126)
    • ►  December (4)
    • ►  November (14)
    • ►  October (9)
    • ►  September (8)
    • ►  August (9)
    • ►  July (10)
    • ►  June (21)
    • ►  May (14)
    • ►  April (2)
    • ►  March (11)
    • ►  February (15)
    • ►  January (9)
  • ►  2008 (94)
    • ►  December (24)
    • ►  November (26)
    • ►  October (25)
    • ►  September (19)
Powered by Blogger.

About Me

Unknown
View my complete profile