Monthly Archives: September 2009

Dial2Do Handy Reference

Turned out my post about Dial2Do was a teeny bit out of date. One of our developers let me know that :

  • The commands and DTMFs we’ve added got a final rev before release – so they’d been updated
  • We have  handy reference card to summarise the commands and keys (DTMFs)

So without further ado…here it is!



Broadband World Forum Panel


We were invited to be on a panel last week at the Broadband World Forum conference, which was held in Paris. I’ve never been at this conference before, and was pleasantly surprised. Very well attended, with plenty of “serious” players in attendance and some pretty interesting sessions, with lots of Q&A and also networking opportunities. Despite the “Broadband” title (which initially put me off) it was really choc-tastic with Telco players both mobile, fixed and converged. Lots of topics of interest and relevance to Dial2Do, including many sessions about Web 2.x and Mobile, and also various sessions on developers and developer communities.

Our panael was called “Stimulating Service Innovation through the Application Developer Community: Open Innovation“. Alan Quayle was chairing the session. Unlike some chairs or facilitators at things like these, Alan is “into” the topics he hosts, and so brings both knowledge, research and his own passion and opinions to bear on the topic. i think this makes for a richer and more engaging panel experience for audience and panel members, as Alan helps really drive the discussion and tease out the core issues. In our case, we ran for an hour and a half and could easily have gone on twice that length!!

At the core of the discussions were the following topics:

  • How should these new App Stores work?
  • What can the mobile industry learn from the TV industry wrt Web 2.x standards and widgets, and vice versa?
  • And of course, fragmentation of platforms, and the overshadowing presence of Apple and iPhone.

Alan has a good lowdown of the whole thing here.

A few thoughts, in no particular order, from the session:

  • It’s hard to underestimate how fundamentally Apple affected the mobile and wireless industry when they launched the iPhone. In every one of these conferences I attend, it typically takes 20 seconds before someone is asking telecom panellists or luminaries to explain how they’re going to “deal” with the Apple App Store, or the iPhone, or the iPhone OS. It has the whole industry spooked (in a good way, imho). It’s taken me a while to realise how profound a kick in the gut it was for Telecom Industry that a Computer/Internet player has really set the agenda and fundamentally shifted expectations for users, developers, and most of the ecosystem.
  • The operators are really struggling to balance competing pressures on them as they roll out their App Stores. Their bosses (the operator) wants revenue and hit apps. Developers want short time to market, loads of revenue share, and promotion in the store. Users want Apple-like simplicity, clear pricing and click-to-download. Guess what – it’s not possible! In Apple’s case, the store is not a revenue-earner, it’s an ecosystem driver that helps Apple sell iPods and iPhones. Operators don’t have an equivalent (maybe the nearest they have is the need to reduce churn and maintain subscriptions?). Anyway these stores look to me like they’re on a hiding to nothing. Everyone’s going to be just a “little bit” disappointed. And in to that disappointment gap will ride Apple, Google and to some extent Nokia if they make Ovi work.
  • Most of the operators have to battle significant internal issues in order to get any new innovation in this area (developer APIs, tools, App Stores) out the door. Among the key issues include how to support apps, and how to authorise them for the usage (quickly). Many would be wise to consider  some form of “wild west” – create a separate brand that runs on the network, and allow a “promiscuous” development of apps to be available on that brand, with zero or only developer-support available there. Use this separate entity or brand to bypass your own internal antibodies that prevent innovation.
  • And lastly – on a separate note; I attended many Web 2.0 meets Telco style presentations at the event. It’s time to stop explaining what Web 2.0 is and get with the programme. Facebook has 65M monthly mobile users now and is a threat to many ingrained services that Telcos think of as being “theirs”. There is a huge potential for operators to embrace and benefit from Web 20 and mobile web 2.0 trends. Right now though there’s very little evidence of understanding how they might tap the potential here. The Social Phone is being developed largely by the internet players.

Anyway – a very interesting conference overall – I’d recommend it to anyone trying to take an industry “temperature” without wanting to slog around MWC for three days 🙂

Dial2Do – new release

Howdy – and long time no see! We’ve been busy working to improve Dial2Do and last week we rolled out a pretty major release. Many of the new features we’ve put in are “partner-centric” and so won’t change the look and feel of the service too much for our end users. So there have been changes “front of house” and in the “backoffice” if you like 🙂

Front of House

We have improved some of the user interface and in particular the Listen to Email service. It works even better now on speakerphones and over hands-free car kits so if you use Dial2Do in the car, we think you’ll like the improvements!

Here’s the low-down on the basics:

  • We have added standard DTMFs for Email, Text, Reminder (see below for an example of how it works with email)
  • You can say “Main Menu” at any point to return to the main menu
  • Say “help” at main menu to get list of commands

We’ve improved “listen to email”. After you say “Listen to Email”, Dial2Do will read the date, sender and subject, then go on to read the body of the email. At any time, you can say “Next” to move to the next email, or “Options” to hear a list of commands

On the options menu, you can say the following (or, if you’re in a noisy environment, use the keys listed beside them):

  • “Next” (6) or “Previous” (4) to navigate (6 and 4 being the keys you press)
  • “Repeat” (5) to go back to the start of this email
  • “Reply” (2) to record a reply to the current email
  • “Block” (1) – this is a new command that tells Dial2Do you don’t want to hear emails from that sender again. This is useful for emails from mailing lists that are not fun to listen to over the phone.

For other information and helpful hints please visit our helpdesk portal here.

As always, we would love to get your feedback so please do not hesitate to contact us on or just say “suggestion” when you call Dial2Do and leave us a message 🙂


Well – since you’re curious if you’ve read this far. Here are some of the main things we’ve been building in the engine room:

  • We’ve done some OAuth work to ensure we can “play nice” with as broad a range of OAuth-supporting partners as possible. This will let us pull in a range of OAuth-powered services downstream. Look for these to appear in later releases.
  • Partner Portal and customisation: we’ve done a lot of work under the hood to support our new partners (coming on stream soon!). We can now create custom-branded partner sites “powered by Dial2Do” – partner selects the look and feel, their own logo and styling, the services they want and even the charging model they want to use. This is a key plank in our plans to enable our partners to get up and running quickly, and so self-service themselves post-launch.

powered by dial2do

  • Speed and efficiency: across some of the services, we’ve done behind-the-scenes work to make the service work smarter and more efficiently.