The New “UC Contact Center” – More Than A “Use Case”

The New “UC Contact Center” – More Than A “Use Case”

By Art Rosenberg November 14, 2011 2 Comments
Art
The New “UC Contact Center” – More Than A “Use Case” by Art Rosenberg

It is getting very apparent that the current shifting of communications technology to software and mobile, multimodal devices (smartphones, tablets) is also driving business communications towards greater flexibility in initiating and responding to business contacts between people and with automated business process “apps.” Most importantly, with a flexible UC framework, business communications can now selectively accommodate all contact and informational access needs for individual end users both inside and outside an organization. Such flexibility will have a significant impact on the traditional, telephone-oriented “call center,” enabling its transition to a true, two-way, multi-modal “contact center” between people and business process applications.

Unified communications (UC) has been defined by the experts at UCStrategies as “Communications integrated to optimize business processes.” That definition seems to have held up well to cover both “communications” and “business processes,” but it leaves open the question of how and when UC capabilities can best be implemented.

Because voice telephony is moving to more flexible, efficient, and less expensive SIP-based IP networking, it is now being viewed as part of general UC capabilities. As such, all business telephony technologies have to be rethought in terms of UC flexibility, and one of the most important areas is the good old “call center.”

The name transitioned to “contact center” many years ago with the growth of the Web and consumer email usage, but one of the real benefits that can be offered to consumers/customers is to increase easy-to-use self-service applications for information access and basic business transactions.  Not only do self-services, if done right, increase user satisfaction with immediate access and responsiveness, but they also reduce the labor costs involved with live assistance, which may not be necessary with online and mobile applications.

Outbound vs. Inbound Calls

“Call centers” were primarily designed to handle incoming calls from customers who didn’t want to speak to a specific person, just someone who could answer their questions and perform transactions, like make an appointment, change their service information, etc. However, outbound calls were also distributed to call center agents to deliver notifications, reminders, solicit new business, etc. The problem with outbound calls is that there is no guarantee of the accessibility of the person being contacted, so automated outdialing technology was introduced to detect ring/no answer, busy lines, answering machines, etc, before assigning the live call to an agent. If the phone was answered by an answering machine, voice mail, or someone other than the specific person (callee) desired, the calling agent could only leave a message.

With the increasing use of mobile smartphones, not only can a customer be contacted for a phone connection more easily, but also personalized messages and notifications can be delivered quickly and easily in text or speech to their individual devices. This will be particularly important for time-sensitive notifications such as health care, financial services, and emergency situations.

To add further business benefits from mobile, multimodal smartphones, automated business process applications can initiate such outbound contacts, along with immediate access to self-service functions, without requiring a live agent. With UC capabilities, however, “click-to-contact” options will still allow the customer to access live assistance and expertise contextually from within the notification or self-service application. That minimizes labor costs while still enabling easy and selective access to live assistance for a better customer experience.  

The “UC Contact Center” for Internal User “Job Contacts”

When you mention the term “contact center,” the old image of dedicated agents handling calls to and from customers is triggered. However, as business users increasingly use mobile smartphones and can benefit from “dual persona” separation of “job contacts” from personal contacts, they too can benefit from timely notifications and on-demand access to live assistance within the organization.

“Job contacts” can include both traditional “person-to-person” contacts for collaborative activities, as well as contacts through Communications Enabled Business Processes (CEBP).  Again, both person contacts and timely automated notifications can be efficiently utilized when the recipients are using multimodal smartphones. So, there will be many business “use cases” that can benefit from the combination of UC and the centralized, multimodal contact center.

Bottom Line for UC Planning

For this reason, legacy call centers have to be on the top of the list for UC migration planning. There will be implications for how contact center “agents” are trained, monitored, evaluated, etc. for maximum job performance in a multimodal, virtual telecommuting environment. Customer interactions will likewise be affected by CRM issues that will change because of dynamic mobile contacts, both inbound and outbound.

Now is the time to trial self-service applications for both customers and for internal users to insure that they will be most effective when deployed for general use. Such trials can be done more quickly and less expensively by exploiting CaaS (Communications as a Service) offerings, before finalizing procurement and implementation decisions.

 

2 Responses to "The New “UC Contact Center” – More Than A “Use Case”" - Add Yours

Gravatar
Dennis Adsit 1/3/2012 11:09:24 AM

Hi Art,

You have touched on key points to consider...multi-channel, in/outbound, mobile, internal/external. These are critical considerations in "how" contacts are made.

But while we are focused on managing the how, we cant forget the contact itself. Here there is one simple question that is too often overlooked: "Was the call/contact we just handled correct or not?"

The call center industry is 40+ years old. And though it is way more productive than it was...in large part because of UC, there is one problem it has not been able to solve: between-agent variation. Some agents are fast; some are slow. Some are well-trained; some are inexperienced. Some you have no trouble understanding; some have heavy accents. Some are kind and courteous; some are tired, burned-out, and downright surly. Some follow all the proper steps and read the proper disclosures; some don’t care or skip steps to save time.

After 40 years, why is there still so much between-agent variation in process and outputs? Why do we continue to rely on monitoring and coaching to reduce between-agent variation when we have been trying those approaches for 40 years and they haven't worked yet? Do we really think they will work better next year? Or have we given up on trying to reduce the variation and get the call/contact right?

We shouldn't give up because there are solutions producing real results. https://en.wikipedia.org/wiki/Agent-assisted_automation and https://callcenterinfo.tmcnet.com/analysis/articles/57874-it-time-mass-customization-call-centers.htm

There are some signs that new companies and leaders are willing to "break set" and try new approaches: https://blogs.hbr.org/cs/2011/11/how_to_scale_without_losing_sa.html

And it may in fact take a new generation of companies and leaders to drive change, but the change is coming. Even if you can juggle a lot of channels, if the quality in each of those channels is dreadful, it is going
Gravatar
Art Rosenberg 1/7/2012 2:44:00 PM

Dennis,

Thanks for your constructive comments.

Obviously, the more you can automate the interaction process, the less problem you will have with "agent variation." In the early days of call centers (Delphi Communications, 1976), we were hoping to use speech recognition to help automate things, but that technology was too primitive to be useful.

However, we considered using the "Wizard of OZ" approach, where the agent wouldn't speak but was just listening to understand the voice input, then select appropriate pre-recorded output. So, we actually tried to simulate an IVR interaction but using speech input rather than TouchTone. With speech recognition technology now well advanced, "standard" caller issues can be handled without live assistance, and customer assistance, using well-trained agents (not just bodies), can be supplied on demand.

However, with Mobile UC and smartphones, I would expect consumers to first exploit Web portals with visual information screens and no slow TUI interface or waiting in queues, rather than request live assistance.

To Leave a Comment, Please Login or Register

UC Summit 2013 UC Alerts
UC Blogs
UC ROI Tool RSS Feeds