MobileVikings adopts Qelp app

Wednesday, October 14th, 2009

Belgian MVNO MobileVikings started using our customer self care application today. The app is available to MobileVikings’ customers in three languages and features embedded Twitter, Facebook, Hyves and Tell-a-friend support. Here’s the English version of the application. MobileVikings is an initiative of MVNE CityLive.

Google beats mobile operators at the customer care game

Monday, June 1st, 2009

Mind the gap! Are mobile operators allowing Google to take over territory in customer (self) care? What is the present situation and what can mobile operators do to regain lost territory? At the request of Andreas Constantinou, research director of Vision Mobile,  I delivered this article for their blog.

Google support

You might not have noticed, but behind the scenes mobile operators are quickly losing territory in customer (self) care to Google. Operators consider customer ownership one of their primary assets, and make great strides in reinforcing their brand at each and every customer touchpoint, from logos on the handset plastic, to on-device portals, branded retail stores and exclusive handsets. Such marketing moves are very visible and make industry news headlines. Yet, mobile operators don’t seem to be aware that Google is staking out territory in the field of customer self care.

Traditionally, customer support was provided by operators through call centers. But with costs of on average 10-15 EUR per phone call (source: Mobile Handset Analyst, November 2007) and decreasing ARPU levels, operators have been reducing call center resources in favour of web based customer self care. But most end-users don’t bother visiting the website of their mobile provider for support, let alone dialing its call center. Finding relevant information on a mobile operator website is is challenge, despite significant investments in staffing, content management systems and good looking website designs.

In response, consumers just apply the survival strategy they learned when dealing with a crashing program on their computer: just Google! So what is today’s situation, how are mobile operators faring when it comes to customer (self) care? Qelp conducted a small, simple test for six of the UK’s largest mobile operators.

Suppose you’d like to get email working on your Nokia N96. More and more consumers just Google the error message or for example “Nokia N96 email set-up”. The table below summarizes your experience when you are based in the UK: searching the operator’s website versus a search with Google.

Option A: Search operator website for “Nokia N96 email setup”
Website results Help section results
O2 Generic email instructions Generic email instructions
Vodafone Commercial product offers “We couldn’t find any pages etc.”
Orange Commercial product offers Generic email instructions
T-Mobile Mostly commercial offers Mostly commercial offers
3 No results Blackberry and generic email
Virgin Mobile No results No results
Option B: Search with Google for “Nokia N96 email setup” + operator name. What are the results on Page 1?
O2 No results for o2.co.uk
Vodafone Result nr. 3, vodafone.co.uk forum: “Go to Nokia.com for internet settings”
Orange No results for orange.co.uk
T-Mobile Result nr. 1: product offer for Nokia N96 from t-mobile.co.uk
3 No results for three.co.uk
Virgin Mobile No results for virgin.co.uk

The above results speak for themselves. For an end-user seeking help to get a service up and running on his mobile phone the answer is not just a few clicks away. Also the mobile operator seems ‘invisible’ for Google, unless it comes to commercial offers. If one looks somewhat closer at the Google results, result nr. 1 at page 1, lists a site called ‘Know Your Mobile’ with detailed instructions for email setup on a Nokia N96, almost exactly what we are looking for. (however the instructions are still generic and we still need to find the correct settings to access the mobile network).

Vodafone and O2 use forums, apparently in an attempt to let customers sort out their issues among themselves, facilitated by a moderator. But, is it good marketing for a mobile operator if a customer is overloaded with the frustrations of other customers while he is trying to hook up his shiny new smartphone to the network?

The stats behind the chaos

To appreciate why customer service is such a complex issue for mobile operators, it is worth looking at the following stats:

- For the first time in mobile history the handset market is shrinking. Yet smartphones, abundant with complex functionality, are still a growing segment which now represents 13.5% of the global market.

- A study by Mformation revealed that “Set-up issues prevented 45% of people from upgrading to new, more sophisticated phones” while “61% said phone set-up is as frustrating as changing a bank account.”

- The complexity of mobile internet set-up on a new mobile phone is illustrated by this top-10 device management challenges which Qelp put together based on experience with multiple operators.

- “Only 20% of a phone’s services and features are used regularly” found a study by WDS Global in September 2008.

- Already in 2005 a study by Olista reported that only “2% of end-users would seek assistance from their mobile provider” to get mobile internet working.

Recently Google has been rolling out a new search feature called Options, allowing users to filter results more quickly. Our test for the search “Nokia N96 email setup” now shows “Forums”, “Reviews” and “Videos” as filters. These options do not bring us any closer to a meaningful answer for our issue today, but one can expect web shops, forums and blogs to act upon this change and ensure that they rank even higher when applying these filters.

Can operators get their act together?

Is there anything mobile operators can do to stop Google’s invasion of their territory? Shouldn’t operators have the ambition to help customers get any service up and running at first attempt within 3 minutes? Smartphones represent only 13.5% of the market, what if this number grows to 20 or 30%? How are mobile operators going to stay “in touch” with customers and deal with the growing complexity of their questions?

There are still options, but operators will have to get their act together. Here’s a few suggestions:

1. Significantly improve the user experience of their websites. For example, by using better site search and helping visualise complex user instructions. End-users love YouTube, Maps, Streetview, Flickr and know a how picture tells a thousand words. Operators already use such tools in marketing, so why not in customer self care as well?

2. Ensure that mobile operator websites are discoverable for Google by applying search engine optimization (SEO) techniques. Mobile operator KPN has been optimizing parts of their website for Google indexing. A recent experiment of KPN showed that some 30% of end-users try Google first to get their phone problems sorted out. (disclosure: KPN is a Qelp customer).

3. Be present in social networks, forums, blogs, even on an experimental basis – this would give give operators bonus points with early adopters. See for example how Comcast is using Twitter.

4. Provide on-device, mobile phone based, customer self care. Voice search and device based solutions are becoming available from companies like Nuance (SnapIn), Ydilo/Movidilo as well as Qelp. But also Google is entering the game with voice search for iPhone and of course Android phones.

Some of the above would even help operators obtain a first mover advantage rather than remaining in a defensive mode. A mobile operator is in the best position to know the user’s phone number, their device, voice/data usage and their location. Who would be in a better position to address the user’s need for support?

Design for user experience

Wednesday, April 15th, 2009

User experience is a continuously moving target. If we compare the first application we inaugurated with our launching customer Telfort three years ago, a lot has changed. Telfort applicationOur first approach was a 1, 2, 3 concept (see screenshot). Select your device, select your question and get a resolution for your problem. However, moving back and forth between topics with that interface appeared less intuitive for end-users than we thought. Hence, we switched to a more traditional “menu” design where end-users can jump directly to the topic of their choice. In addition, we moved from dynamic HTML, to static HTML and introduced Flash in parallel such as this example for KPN brand Hi. Each of our customers now has a “unique” application with a user interface customized to their needs. For the latest example of user experience in Flash, take a look at the application we recently released for T-Mobile.

Top 10 device management challenges

Sunday, January 18th, 2009

In October last year at the Device Management Conference in London, I delivered a presentation together with Blyk, one of our customers, about the day-yo-day difficulties in device management. During the conference, the consensus emerged that a best in class mobile provider cannot achieve an OTA success rate higher than 60%. In other words: at least 40% of all OTA settings attempts fail! We think this is clearly very poor performance, for all good reasons, but still. Based on that discussion at the conference, our customers’ experience and our own experience, we have put together a Top 10 of device management challenges. Or, device management headaches if you will.
Top 10 device management challenges:
1. Over-the-air settings require user acceptance
2. Some devices do not support OTA, require manual configuration
3. New handsets coming to the market through different channels
4. Remote access to a device requires mobile internet
5. End-users are confused when settings arrive
6. Each handset has a different user interface
7. Call centre support is too costly
8. Second hand devices are preconfigured incorrectly
9. Network operator settings get preference over MVNO settings
10. New IMEI ranges and handsets without an IMEI number
More details about this Top 10 can be found here.

The good news if of course that with Qelp’s web based application, most of these issues can be addressed. As Harri Väyrynen from Blyk stated at the Device Management Conference: “Qelp self service application helps us close the gap of those 40% of end-users struggling with settings on their mobile phone.”

“60% is best-in-class mobile device management success rate”

Tuesday, October 28th, 2008

The cryptic title for this post is a summary of the consensus coming out of Monday’s Device Management Forum in London. At the conference in London, I delivered a presentation together with Blyk, one of our clients. We shared with the audience our lessons learned in how to increase the OTA success rate up to 100%, which in fact is a requirement for Blyk. Their members must have internet and MMS working on a mobile phone to be able to receive these multimedia advertisements (see example) and get free texting and minutes in return. It makes the Blyk lessons learned unique, in a sense that they have really tuned the over-the-air (OTA) settings provisioning systems to the max. The remaining 40% of unsuccessful settings deliveries is caused by end-user confusion and handset issues (e.g. “settings memory full!”). Issues that can be resolved only manually by the end-user, which is where our self service product comes in. Achieving a success rate of only 60% is of course pretty disappointing. And this is best-in-class according to the industry players gathered at the conference. Here’s our Top 10 challenges for providers to get the settings right. To resolve these problems structurally, handset vendors and mobile providers need to work much more closely on standards. But in fact, there have been Open Mobile Alliance committees talking about this already for quite some time… Alternatively, I could imagine a “gorilla” like Google comes with a quicker fix, packaged within their growing list of mobile internet initiatives.
If you are interested in a copy of the Blyk-Qelp presentation (title “Mobile internet is not plug and play”), please send us a message using this form.

Reblog this post [with Zemanta]