Encouraging designs and strategies that matter to consumers

Subscribe To My Feed
 

Read More On

Read my blog on Kindle

Filter My Posts

     

My QR Code

Vodpod

Watch videos at Vodpod and more of my videos

Discover More

 

 

 

Videos


Visit Society of Digital Agencies

Great Products Tell Stories

   

Favorite Reads
What I believe



Thanks to Jessica Hagy from moo.com

Entries in SMS (2)

Tuesday
Feb022010

Hey, Verizon, My USB Modem Doesn't Receive SMS Messages. But Then You Already Know That.

I try to imagine I'm a normal consumer when I do my job and when I post on this site, because it is important to me to exercise great empathy for the average user. However, I have to admit every now and then, that because I work in technology, and I love gadgets, I am not every consumer. The difference is an important one.

By way of example, I recently bought a Verizon Wireless USB Modem. I have no Verizon phones, because I own an iPhone, Blackberry Curve and NexusOne, and I didn't need another phone. (This is when my admission I am not every consumer is relevant.) I carry different devices for different reasons and different times, which I know is not average. Switching phones keeps me from getting too familiar or biased towards any one phone, or to any particular mental model. So, in my defense, I like to believe it keeps me from getting too jaded like early adopters tend to do.

In any event, I prefer to manage my wireless bills online, which brings us back to me being pretty average. I went to the Verizon Wireless site today to create an online account so I could keep track of my data usage and set up auto-pay. Again, nothing out of the ordinary. After asking me for my phone number, and asking me to identify myself as the primary account holder with the last four digits of my social security number, the site informed me that the account would  not be accessible till I retrieved the temporary password that was being sent by SMS to my phone.  Excuse me? That's right, I just got finished telling you in the paragraph above that I am not a Verizon PHONE customer. And who should know that better than Verizon? Didn't they just look up my account to verify my social security number as the primary account holder's before they sent that SMS? That same account could have told them what devices I owned, and that none of them could receive SMS.

Sure, Verizon plans to send me a hard copy of the temporary password through the good, old USPS. But the fact remains they missed the opportunity to ensure I will use the online portal at the moment when I was actively engaged and had the time to do so. Any marketer worth their weight knows that getting someone to come back and take action is much harder than working them into action once you have their eyeballs.

My issue is not about security and authentication. It's about the original experience. Why do I have to wait at least 3 days for the temporary password to complete the transaction? Sending a temp password by snail mail as a back-up may be the best way to "close the loop" and ensure a customers' privacy. But that's really just a consequence of a more foundational problem: either Verizon don't understand CRM or they have such a bias for their voice-centric network, that their CRM system doesn't support a use case for a customer with a data-only device that can't receive an SMS.

Friday
Jan292010

Google Voice Uses HTML 5 To Work on iPhone

First published on Technorati:

I am a Google Voice user, but I have not used it much for outbound VoIP calling. My friends often ask me why I use it since its primary benefit to many users is low-cost long distance calling. I use the system primarily to route inbound calls to different phones that have better coverage or battery Courtesy of Wired.comlife than whatever handset I am carrying. Since AT&T coverage is spotty at my home, and I don’t like to carry my phone around the house, I try to route inbound calls to my landline so I can hear the ring on all the extensions.

Google Voice also lets me send SMS messages seamlessly continuing a conversation thread between my home PC and my cell phone when I go mobile. I don’t use the service to make outbound calls mainly because I don’t have challenges with my long distance bill as most of those calls are domestic and can be done within my cell plan as free mobile-to-mobile minutes.

Occasionally, I will forget to deactivate a phone number I no longer wish to route calls to when I am on the road. Since there has been no Google Voice app available for my iPhone, I put a browser shortcut on my home screen so I could quickly access the Google Voice website and change the settings when I am away from my PC. Today when I did that, I was surprised and delighted to find that my experience had completely changed.

Google Voice is now a web app. A web app differs from a website because it creates a unique experience for every session and visitor. When I interacted with the web page, Google Voice provide my device with a newly coded page which told my phone to update the icon on the home screen shortcut from a picture of the Google Voice web page to a neat, streamlined Courtesy of wired.comGoogle Voice icon.

Google developers used HTML5 to support  outbound voice calling and avoided the Apple App Store approval process, which previously led to a rejection of the downloadable version of the application. A phone number in your Google contact list that is accessed through the new web app - or entered in the web app's dialer - will connect through the standard iPhone calling function.

The call will actually use the AT&T voice network to connect the call but route through Google Voice and appear to the person you are calling as if the call came from you Google Voice phone number, hopefully avoiding some pesky international long distance charges you might incur. Oddly, though, to do that routing through Google Voice, the phone appears to dial a number with a totally different area code than the one you are actually calling.

The biggest challenge to using Google Voice on your iPhone will be the segregation of contacts between Google Voice and the native iPhone Contacts application. If you have not synced with Google contacts before, that will take some effort, especially to move the local contacts from your device to the Google Voice service. Wired has done a nice job of explaining the various alternatives to accomplish this migration or sync. You will also need a Google Voice account on top of your AT&T voice plan to place and receive calls.


One of my favorite benefits of using Google Voice is that it lets you replace your caller ID with your Google Voice number. The Google Voice web app now lets me make an outbound call from my iPhone but display my Google Voice number if I choose in the web app’s settings. I like to use the call screening features of Google Voice, which means I also like to manage what number displays when I dial different contacts.

For professional contacts, I may choose to display my Google Voice number, making it more likely callers will return the call to that number. I can then have the Google Voice service “announce” who the inbound caller is the next time they call allowing me to screen callers coming from corporate switchboards or numbers with blocked caller IDs.

What makes all of this possible now, even though Apple previously rejected the Google Voice app as a download from the App Store? The iPhone, like the Palm Pre, Palm Pixi and Google Android devices all use a browser that shares rendering technology based on Webkit, an open source web browsing engine that is one of the first on mobile phones to support this new update to HTML. Some of these devices may require an update to the device’s firmware in order to have the full Google Voice experience.