By Edwin Margulies
(Part I of III)
Sadly, the majority of Smartphone apps were built quickly to fulfill the “cool” mandate. Versions 1.0 rarely scratch the surface of customer care and provide only the fundamentals like checking balances or looking up credits. So what’s the problem? Well the fact that most enterprise Smartphone apps are built in a silo creates channel confusion (phone vs. web vs. chat vs. SMS) and can create more problems than they solve.
Do You Know What Your App Is Doing?
I often ask customer care practitioners if they really know what their Smartphone app is doing. For example, is there a likelihood that chances for cross-sell are getting blocked? Or chances for retention of an angry customer falling away? How about the “contact us” page? Is it nothing more than a speed dial? Can customers communicate with you without having to dump out of the app and go to a discrete communication channel? All of these questions and more are often answered with a knowing nod: “Yes it’s a mess and we have to figure out how to make it better.” Continue reading

On the other hand, the enterprise is able to more evenly spread its demand throughout the day. Agent productivity and service levels are improved by shifting calls from busy periods to the slowest periods. Idle time in the call center is reduced. Callbacks also reduce the number of abandoned calls which can increase sales and revenue.
I don’t know too many people that enjoy “taking a survey” at the end of a call center transaction or even in a pop-up window on a web site. Yet more and more, people nonetheless want to broadcast their sentiment. Take all the tweets and Facebook posts on brands and products. Those are “democratic” or at least “free market” forms of feedback. And social feedback is on your customers’ terms.