Tuesday, November 03, 2009

Avaya's Aura Exploits CEBP For Notification Solutions

Copyright (C) Unified-View, All Rights Reserved.

November 3, 2009

Avaya Runs With CEBP For Aura “UC Telephony” Solutions

Art Rosenberg, The Unified-View

“Collaboration” means working together, exchanging information, and communicating in a timely manner with people and processes in various ways. It usually is a term that applies to people involved in a common task or problem and often need to discuss important issues in real time.

However, "customers" were rarely treated the same as enterprise personnel in the collaborative space because they are independent of the enterprise communications and information infrastructure and can’t be easily contacted for timely collaborative interactions .

With the interoperability of the Internet, personalized multi-modal endpoint devices, business communication applications, business process applications, presence information, and mobile accessibility, "Customer UC" flexibility is enabling business contacts with customers to be treated in a more "collaborative" way. What “UC” as a concept does is to make the choice of interaction more flexible for all the people directly involved with a business process.

Process-to-Person Contacts For Work Flow Inside And Outside The Organization

UC is not just about person-to-person contacts, but also about pro-active process-to-person "notifications" that enable the recipient to dynamically use any mode of notification receipt (text, speech), as well as choose the modality of response. The latter can include interactions with automated self-service business process applications (on-line, IVR) and any mode of communication access to live assistance when necessary.

Outbound contacts with customers by automated business process applications is coming to life under the label of "Communications Enabled Business Processes" or CEBP, and will be particularly effective with the growing population of mobile users that carry "smart-phones" for flexible accessibility and increased availability and responsiveness.

CEBP, coupled with UC, is thus enabling customers to become part of the "collaborative" business landscape by providing a cost-effective means for a business process application to contact a customer whenever and wherever they may be through UC "notification and response" services. Notification alone is not enough to close the communication loop in a timely and efficient manner. Remember the pager?

Avaya Puts Aura To Work To Support Timely Business Process Flow

Avaya has just announced its first customizable automated outbound solutions for its Aura enterprise communications system that provides what I call "UC Telephony" (IP Telephony) integrations across multi-vendor, multi-location, and multi-modal business processes. One solution is called Avaya Notification Solution (ANS) designed to orchestrate and streamline the voice contacts between people involved in coordinating any real-time business process activity, but especially in responding to urgent or emergency situations.

The second solution is called Avaya Proactive Outreach for Financial Services for the mortgage market, which automatically contacts customers by phone to determine eligibility. This is an example of a proactive outbound IVR application that can also trigger delivery of text messages that contain a URL link for further self-service actions. In addition, the Outreach solution provides timely messaging notifications of ongoing mortgage processing status, as well as any need for real-time interactions, if required.

Such CEBP-based business process solutions are unlimited and, like smart-phone " apps," will proliferate swiftly with Aura system customers. Clearly, multimodal, mobile accessibility will be key to the effectiveness of many of these solutions, so we should see more mention of the role of Mobile UC in the future.

What Do You Think?

You can contact me at: artr@ix.netcom.com or (310) 395-2360.

Friday, October 23, 2009

Copyright © 2009 The Unified-View, All Rights Reserved Worldwide
October 23, 2009

“Customer UC” For Improving Collections ROI

Art Rosenberg, The Unified-View

As knowledgeable technology experts now agree, unified communications (UC) is a concept for integrating the use of various forms of communication technologies to make more flexible and efficient contact with people; such contacts can be initiated either by other people, or, even more importantly for business processes, by automating process workflows.

The “ROI” of UC technologies is expected to come from both reduced costs and more efficient and productive business processes that involve timely contact with people. The latter objective will also include reducing labor costs by exploiting automated notifications and self-service applications. More importantly, any customer-facing business process activity that can impact revenue generation will be of particular interest to business management, making contact center applications high-priority targets for UC implementation planning.

We are starting to see some contact center applications being integrated with UC capabilities to help provide the ROI that enterprises require. For example, Aspect, which has its roots in the contact center market, announced its unified communications solution, “Streamlined Collections.” By applying its long experience with traditional, telephony-based outbound customer contact and self-service applications to the increased need to make debt collection both more productive and cost efficient, Aspect is targeting a common high-value business process that suffers from the limitations of traditional, person-to-person telephone contacts.

The nature of outbound contacts for debt collection lends itself ideally to the flexible capabilities of UC, as well as the opportunity to exploit automated self-services applications, efficiently coupled with selective, on-demand live assistance when needed. This customer-facing outbound UC application fits in very well with other “Customer UC” applications, which I define as all forms of business communication services that directly involve interactions with “customers,” whether as contact initiators or recipients/respondents.

Moving Debt Collection From The Past To The Future

Debt collection letters have always been slow, with no guarantee of delivery or a convenient means of quick response. Collection phone call attempts are even more expensive, especially if you don’t know when and where to make direct contact with a particular person, and/ or debtors are avoiding such contact. The limitation of a traditional phone call to handle a data exchange has also been a major shortcoming for efficiently negotiating a collections interaction with a customer.

However, the consumer communications world has been dramatically changing in terms of personalized communications through individual email mailboxes, personalized mobile “smart-phones,” instant messaging (IM) contacts, Short Message Services (SMS) for mobile devices, social networking contacts, etc. It is really time to exploit the new web-based contact environment, not just the old telephone network, since the limitations of the Telephone User Interface (TUI) also restrict the flexibility of automated self-service applications, requiring greater use of live assistance than online Web applications. So, UC, coupled with mobile, multi-modal “smart-phones,” can expand the benefits of outbound self-service applications and reduce the need for live assistance to provide additional information.

A typical collections scenario would involve a customer contacting a customer service department for an unrelated reason and a business process application detecting the fact that a payment is overdue and automatically generate a personalized (text) “notification” message to the debtor (via email, SMS). A mobile recipient with UC capabilities will have the option to hear the message as well read it. Then, depending on the recipient’s particular situation, various response options can be offered, ranging from simple confirmation of receipt to a choice of payment methods. If there are questions or problems that require additional assistance, the response can escalate to an exchange of emails, a real-time “chat,” or a live call connection to an available and qualified collections agent.

Aspect’s Streamlined Collections integration with UC capabilities exploits “Communications Enabled Business Processes" or “CEBP”, where an automated business process can initiate an outbound communication contact to an individual person, based on personalized criteria. Customer debt collection is an ideal application for CEBP, enabling the choice of outbound contact, self-service application, and access to live assistance to be automatically optimized selectively on an individual customer basis.

“First Contact Resolution” Metrics For Outbound Customer Contact
Personalization of outbound contacts for customer collections will be very critical, because it will require differentiating the modality requirements of contact – proactive notifications coupled with self-service or live assistance options, as well as privacy concerns for the individual customer. Aspect has categorized its collection activities across different “phases” of the process, i.e.:

· “Early stage” 30- day
· “Mid-stage” 60-90-day
· “Late stage 90-day +

Each phase can have its own “message” to deliver, along with different choices for delivery and distinct self-service application options and live assistance requirements. Leveraging consumer’s increased use of ‘smart-phones” will enable faster contact accessibility, as well as customer response flexibility for both online or voice response self-service options. This will also minimize the need for live agent involvement unless requested by the customer. The self-service approach also facilitates identifying the level of live assistance required, which may or may not be immediately available and can be deferred.

Just as IVR applications have traditionally been used to screen incoming calls and determine intelligent routing to qualified call center agents, outbound contacts that connect recipients to either an online or an IVR self-service application can perform the same role for customer access to live assistance via a presence-based call connection or chat session.

Benefits for Everyone

Although important, it is simply not enough to claim that UC technologies will reduce enterprise operational costs in various ways. Unless it pays off in making a specific business process more efficient and productive for all users involved, the overall business process results will not be optimized. In the case of the Aspect Streamlined Collections contact center application. UC-based technologies exploit mobile consumer communications, email, and self-service technologies to maximize the following benefits:

For the enterprise:
· Efficient customization of interactions for different customer circumstances
· Faster revenue generation
· Minimized operational costs, especially need for staffing support
· Lower infrastructure technology costs
· Maximizing customer retention, customer experience satisfaction

For the customer:
· Greater contextual personalization of collection contacts
· Maintaining customer privacy for such interactions
· Opportunity to avoid or minimize financial penalties
· More response flexibility and information access, especially for mobile customers
· Greater flexibility for access to live assistance on demand

UC-based business process applications can be selectively implemented to improve a particular business process that will involve a specific group of end users, both inside and outside of an organization. They can integrate existing communication technologies with new capabilities to produce the benefits of cost savings, but more importantly, business process efficiencies and productivity. Aspect’s Streamlined Collections Solution is a practical example of the benefits of Customer UC in the rapidly changing world of consumer communications.

The consumer transition to universal online Internet access, UC, and multimodal “smartphones” won’t take place overnight, so there will be a requirement for enterprise organizations to continue to support traditional customer telephone contacts in addition to new UC contacts, with live assistance. For this reason, the Streamlined Collections unified communication applications for the contact center from Aspect integrates its outbound contact planning and workforce management functions to optimize “agent” and “expert” resources across all forms of customer interactions.

In addition, Aspect has its collections business process optimization solution packaged as “Optimized Collections,” which focuses on enhancing calling strategies and helps apply the right resources at the right times to improve collector productivity.

What Do You Think?
You can contact me at: artr@ix.netcom.com or (310) 395-2360.

Wednesday, October 21, 2009

Getting Enterprise Telephony Ready For UC

Copyright © 2009 The Unified-View, All Rights Reserved Worldwide

October 19, 2009

New, Combined Gateway Simplifies Migration of Enterprise Telephony To OCS UC


Art Rosenberg, The Unified-View

While business managers in enterprise organizations may just be starting to research their operational business needs to identify and prioritize their UC requirements to improve business processes, IT management must prepare to migrate existing enterprise telephone systems into the coming UC infrastructure environment.

For the many organizations that are deploying the latest version of Microsoft Office Communications Server (OCS 2007 R2) for their UC infrastructure, NET’s newest VX series gateway with Enhanced UC Features, will provide a very practical, cost-savings approach to integrating enterprise telephony with the PSTN, SIP trunking, different PBX systems, and various UC applications provided through OCS. This migration can be done selectively to support specific individual end users (e.g., mobile users) or for selected business groups as needed, rather than on an across the boards basis.

As has been stressed many times, UC is not a single communication system, but a concept of open, communication applications that are interoperable across different user interfaces. UC communication applications must also be able to integrate with a variety of enterprise business process applications to enable them to initiate contacts and to interact with people both inside (internal staff) and outside (business partners, customers) of an enterprise organization. This also means that communication access for UC applications must support network and device independence, if necessary through gateways, in order to allow for all forms of contact between people and any business process applications they interact with.

The flexibility for Microsoft’s OCS to support a variety of SIP service providers or ITSP’s is also expanded by NET’s demarcation gateway approach. As a certified Microsoft partner for OCS gateway, NET gateways increase the number of supported, approved SIP carriers from three to eleven, and also directly support a wide list of WAN interfaces.

While it will take time to plan and implement all the business process applications that can be communications enabled (CEBP), IT management doesn’t have to wait, but can safely get a head start by moving forward with integrating existing telephony capabilities with Microsoft’s OCS server and UC applications.

What Do You Think?
You can contact me at: artr@ix.netcom.com or (310) 395-2360.

Saturday, October 03, 2009

Customer UC Issue #5 - Implementing Customer UC Applications

Copyright (C) Unified-View, All Rights Reserved.

October 3, 2009

“Customer UC” – Panelists Discuss Issue #5 – Trialing and Implementing New UC Applications

Art Rosenberg, The Unified-View

More Panelist Comments on “Customer UC” Issues

I put all business communication contacts that directly involve customer facing activities into “Customer UC,” because they must ultimately all be accounted for in managing customer relationships. This topic was discussed by a panel of innovative contact center technology developers at a kickoff session, ”UC and the Contact Center,” at TMC’s last Internet Telephony conference in L.A. (9/1-3). My panelists were representatives from Altitude Software, CosmoCom, and Fonality.

In previous posts on what was happening with UC in the Contact Center space, I summarized comments by the panelists on the first four issues we discussed that face business organizations looking to exploit the benefits of UC for customer contact activities.

Here are their comments on another key issue discussed:

Issue #5. How should an organization implement new “Customer UC” applications for their customers?

As business information becomes increasingly accessible online over the public Internet, the need for an organization to provide personnel for such access is greatly reduced. Not only does this capability for direct customer online access to information reduce operational labor costs, but it expands customer service levels to 24x7 self-services and opens the door to other kinds of transactional services that would traditionally be limited to “office hours” and premise-based access. Clearly, cost-effective expanded customer service capabilities can accelerate revenue growth and profitability.

Voice-based self-service (IVR) applications, while productive, have always been limited to simple applications because anything complex would quickly require live assistance. On-line web-based applications have been better because visual screen interfaces are much more practical for information output, long menus, graphic output, links to web sites, etc., but once live assistance is required, it becomes limited to Instant Messaging facilities or email, with no simple way to switch to a real-time voice connection. However, with the rapid consumer adoption of personalized, multi-modal, mobile devices (“smart-phones”), UC can now help bridge the gap between customers, online or voice self-service applications, and various sources of live assistance. Going a step further, business process applications can now also become more pro-active in contacting customers to flexibly deliver information and services on a customized, individual end-user basis.

The challenge for implementing any new contact center communication applications will be a learning process to design and test the new user interfaces and integrations with real customers and contact center staff, before finalizing such offerings. Given the fact that UC is still evolving as a set of old and new communication applications that need to integrate and interact with each other and with business process applications, most business organizations don’t have all the technologies nor the expertise in place to develop and test the effectiveness of a UC solution to a business process problem. We have a “chicken and egg” situation - we don’t want invest too heavily in new technologies until we can demonstrate that it will work with customers and will produce the benefits for expected.

Most consultants and industry pundits therefore push the practical idea of “pilots” and “trials,” but that only raises the questions of “how?”

Panelist Comments

· Every organization will have its own business process application candidates for UC trialing. Based upon type of business, customer base and geographical locations, current use of self-service applications, and strategic operational problems that need to be addressed

· The business process application that is of high priority because of time-criticality and impact on revenues, but with relative ease of testing implementation, should be selected for trialing first

· The key operational problems associated with that application must be identified first

· The UC feature set required for that application solution and it’s operational problems must be determined

· The users involved, including, “agents,” “experts” and types of customers, must all be identified for trialing purposes

· Any existing online or IVR self-service applications must be evaluated for changes that must be made for new options for customers and impact on customer-facing staff (“agents,” “experts,” business partners)

· Performance metrics, for evaluating the pilot, need to be established, including metrics not previously used for traditional call center operations

· “Try before buy!” – Before investing in the purchase of new technologies, it would be advantageous to utilize hosted services to test the tools for designing, developing and managing the UC communication applications and for integrating them with existing process business applications

· A “phased” approach may be used for a given business process application, where not all the desired UC applications are implemented or integrated at once. For example, the first target might be online customers and a specific set of business process applications that can maximize the benefits of UC flexibility at the desktop. Alternatively, mobile customers might be the first targets because of their increased accessibility and need for both timely delivery with multi-modal flexibility

· After trialing the application solution for its effectiveness with the users involved, a next step will be to test the approach for scalability with increased volumes.

· Prepare both your “pilot” customers and “agents” for the expected changes they will experience from legacy technologies in both self-service options and in accessing live assistance. Based on the actual user results, the user preparation for the full rollout can be finalized.

Bottom line, every organization should be prepared to learn how to benefit from UC in the contact center environment, even though the technology is still evolving and experience is lacking. Trialing and piloting self-service applications with hosted and “cloud”-based software services are rapidly becoming a cost-effective, practical alternative to quickly finding out what you don’t yet really know about your customized, UC-based, self-service application needs.

What Do You Think?

You can contact me at: artr@ix.netcom.com or (310) 395-2360.

Sunday, September 27, 2009

UC and Contact Center Panel Issue #4 - Where Does CEBP Fit In?

Copyright © 2009 Unified-View, All Rights Reserved Worldwide

September 26, 2009

“Customer UC” – Panelists Discuss Impact of CEBP on Business Applications

Art Rosenberg, The Unified-View

More Panelist Comments on “Customer UC”

In previous posts on what was happening with UC in the Contact Center space at TMC’s Internet Telephony show in L.A., I summarized comments by my panelists on the first three issues we discussed that face business organizations looking to exploit UC for customer contact activities.

I have labeled all customer-facing UC communication activities as “Customer UC,” which was then discussed by a panel of innovative contact center technology developers at a kickoff session, ”UC and the Contact Center,” at TMC’s last Internet Telephony conference in L.A. (9/1-3). My panelists were representatives from leading innovative contact center technology developers Altitude Software, CosmoCom, and Fonality, Here are their comments on another key issue discussed:

Issue #4. How will business process applications be affected by “CEBP” in a Customer UC environment?


With UC, different forms of business communication contact may be activated, depending upon who (or what) is initiating the contact with a person, which may be person-to-person or process-to-person. The type of contact will also depend upon the current real-time accessibility and availability of the contact recipient. As more elements of a business process become automated, e.g., monitoring sensitive status conditions, the role of real-time process-to-person “notifications” will increase, including what is commonly referred to as “Communications Enabled Business Communications” (CEBP).

CEBP commonly stands for “Communications Enabled Business Process,” which means that an automated) business process application can initiate a communications contact to a specific person, instead of it being done manually by another person. Needless to say, this kind of capability is particularly useful for contacting mobile recipients and for what some people call “outbound IVR” to exploit self-service transactions initiated by a business process application. Another term for such a capability is a “Communications enabled application” or CEA, which can apply to non-business applications as well, e.g., entertainment, social contacts, games, etc.

Like everything new that is falling under the umbrella of UC, the definitions for “CEBP” can be confusing. Microsoft’s OCS enables it’s online users to “click-to-call” contextually from information within any online software application. And, of course, there is competition for the term itself from the likes of “all-in-one” enterprise communications provider, Interactive Intelligence, with its communications-based workflow platform it describes as providing “CBPA” (Communications-Based Process Automation). The difference claimed there is that CBPA consolidates work flow activity on a communications-based platform, making contacts with people at any point in the process flow readily accessible, while CEBP doesn’t go beyond enabling individual applications within a work flow process to contact people.

The business application contact target could be any end user, including people within a business organization or external users such as business partners and consumer/customers. The contact initiator can also be any type of end user who may be using a CEBP application, or it could be initiated pro-actively and directly by a CEBP application itself to send personalized information or a notification to a specific person.

Process-to-person forms of contact initiation will require the business application involved to interoperate with various communication applications (telephony, messaging, presence management, routing information, etc.) just as a person would, providing specific contact information (name, “addressing”, etc.). However, an automated application that can make contact with a customer’s phone (mobile or desktop), will obviously not be expected to carry on a voice conversation that people do.

Panelist Comments

· The technology for enabling business process applications to exploit UC capabilities at the recipient end, particularly customers using mobile “smart-phones, is complex and still evolving.

· Today, CEBP is still very much the exception and not the rule, when you consider the fact that 75% of businesses in the US are under 20 employees.

· CEBP needs to complement existing business process applications enabling different forms of contact and interaction between the contact initiator (application process, person) and the recipient (person).

· In a contact center environment, CEBP must support the basic objectives to align a customer need with available types of company support resources -i.e., self-service, live assistance or a combination of both. This can be done on the traditional contact center “on-demand” response basis, or pro-actively by automated business process applications that monitor and respond to dynamic status information.

· UC flexibility improves contact accessibility and thus flexibility when person-to-person contacts are required. Increased accessibility through both mobility and UC flexibility will make CEBP applications more useful and productive.

· Unified Messaging will be a key UC application that enables a business process application to efficiently deliver a time-sensitive notification to an accessible (mobile) customer for information delivery. Coupled with “click-to-interact” with an online or IVR self-service application, or “click-to-talk/chat” for live assistance, the customer can immediately execute time-sensitive transactions that require attention.

· If CEBP is deployed correctly, it will be perceived positively by customers and will also reduce traditional on-demand contact needs.

Example: Proactive flight status notifications that advise a passenger of gate changes and departure time changes can proactively provide timely updates to a mobile customer. Customer will rely on such timely and up-to-date notifications to avoid, minimize and correct their travel problems.

· The impact of such timely access to personalized information will be greater customer satisfaction and loyalty and reduced labor costs for handling unnecessary on-demand contacts.

· CEBP is, by its nature, a highly customized business application development and almost always requires an integration and/or professional services design and development effort. However, off-the-shelf CEBP applications that apply to horizontal industries can be useful in minimizing the costs and effort in developing customized versions.

· The growing adoption of mobile “smart-phones” by consumers and business users will be a major driver for implementing CEBP for both customers and customer-facing staff.

· Such use of mobile devices will also enable CEBP to tie in comfortably with personalized, self-service options on a proactive, rather than just on an “on demand” basis. This will minimize the need for staffing customer assistance and associated costs, in order to maximize customer satisfaction.

What Do You Think?
You can contact me at: artr@ix.netcom.com or (310) 395-2360.

Wednesday, September 23, 2009

UC Escalations in Customer Contacts

Copyright © 2009 Unified-View, All Rights Reserved Worldwide

September 23, 2009

Drilling Down Into Contact Center “Escalations” With UC

Art Rosenberg, The Unified-View

UC is starting to get increasingly focused on customer contacts because that is where both business costs can be reduced and revenues improved. A recent post on the subject at www.UCStrategies.com by Michael Barbagallo drills down into how subject matter experts (SMEs) should be efficiently brought into contact center operations and whether their involvement should be tracked and reported.

Here is my comment to that perspective.

Michael,

I am glad to see you drilling down into call center procedures, as they will apply to customer contact operations and “agent”-“expert” escalations.

While I agree with your views on including "experts" in workflow management reporting for business process performance tracking, we have to include the role of the customer in “escalating to assistance” as well. Accordingly, UC will be disruptive for customers too, since they will be increasingly "escalating" to live assistance from self-service applications (online, IVR), using multi-modal devices (PCs, smartphones). That also means it can be their choice to contextually "click-to-call," "click-to-chat," or, if there is no real rush, "click-to-message" (text, voice) for live assistance from their multi-modal endpoint devices.

Note: “Contextually” means that information about the self-service application they were using will be passed on to the person providing assistance (“screen pop”).

That also means new, UC-based "contact centers" must move away from the metric of just First “Call” Resolution to First “Contact” Resolution and apply it to both "customer" and "agent" escalation procedures. In many cases, the need for assistance and escalation requires further informational research or approval authorization, so there is no point in keeping a caller connected to wait for such resolution. Furthermore, with consumers becoming increasingly accessible and available because of personal Mobile UC, keeping them on a voice connection or transferring them unnecessarily becomes questionable from an “experience” perspective. With mobility and UC, we can always get back to them easily and quickly!

Which brings us to the next point of what I call "Customer UC," pro-active process-to-person contacts using CEBP (Communications Enabled Business Processes). With UC, we don't need to always have people deliver real-time information to people. Automated business process applications can now do that using Mobile UC tools for media flexibility and faster notification/delivery, coupled with "click-for-assistance" if necessary. That will take labor costs, as well as the "human latency," out of many business processes.

Needless to say, Mobile UC won't happen overnight and won't always be available to all customers, so the old call center "agent”/”expert” game will continue being played but on a “virtual” basis. However, on the enterprise side, “agents” and “experts” will not only NOT be collocated geographically, but will be selected for "escalation" based upon their "availability” and contextual qualifications, not by "agent" choice. This will apply to all involved customer-facing staff, who may belong to different business organizations.


What Do You Think?
You can contact me at: artr@ix.netcom.com or (310) 395-2360.

Friday, September 18, 2009

Issue #3 UC and Contact Centers

Copyright (C) Unified-View, All Rights Reserved.

September 18, 2009

“Customer UC” – Panelists Discuss UC and the Contact Center - Issue # 3

Art Rosenberg, The Unified-View

More Panelist Comments on Implementing “Customer UC”

In my previous post on what was happening with UC in the Contact Center space at TMC’s Internet Telephony show in L.A., I summarized comments by my panelists on the first two issues we discussed that face business organizations looking to exploit UC for customer contact activities.

From a business results perspective, UC ROI performance must include metrics like customer satisfaction (soft) and revenue generation (hard), not just cost savings and Total Cost of Ownership (hard). Customer contact activities are therefore increasingly being evaluated as high-value applications for overall UC implementation planning.

I have labeled all customer-facing UC communication activities as “Customer UC.” These kinds of challenges were discussed by a panel of innovative contact center technology developers on the subject of ”UC and the Contact Center” at TMC’s Internet Telephony conference in L.A. at the beginning of this month (9/1-3).
My panelists were representatives from leading innovative contact center technology developers Altitude Software, CosmoCom, and Fonality, Here are their comments on another key issue discussed:

Issue #3. What are the key considerations for presence in a Customer UC environment?

· “Agent” availability, once they have been logged on to their desktops and set their status to being ready to take a call assignment (inbound or outbound), has always been a part of ACD technologies in traditional telephone call centers. Being “available” for a phone call means that they are not on another phone call, but can be doing other tasks that are interruptible or can be multi-tasked.

· Agent assignment to non-voice tasks can be made to a “busy” agent, especially, when such tasks are not “real-time” and can be done “as soon as possible,” e.g., outbound calls (“call blending”), messaging responses, etc. Even several customer real-time IM assignments can be multi-tasked by a single agent.

· Real-time access to non-“agents,” i.e., (”Subject Matter Experts” or SMEs) is becoming a key concern for customer contact operations and is dependent on (1) their accessibility and (2) their availability. For the most part, SMEs are not directly accessible to customer callers, but could be assigned to handle appropriate customer messages. However, “first line agents” who need assistance from an SME, must themselves be guided by presence and availability to whichever live assistance resource is available at the moment, like an “ACD for SMEs.”

· Wireless mobility and the use of multi-modal endpoint devices (notebooks, “smart-phones”), will increase accessibility to SMEs, and thus SME availability.

· However, SMEs are very dynamically “available” and “accessible,” and only they know whether they can provide real-time assistance to an “agent,” based on the SME’s current situation and other task priorities. A panel recommendation was NOT to make specific “agent” assignments to SMEs or to let an “agent” select the SME of their choice, but to broadcast a “priority alert” message (Dispatch) to all qualified and accessible SMEs and let the “first responder” SME be connected by IM with the requesting “agent” in queue.

· SMEs can also respond to tasks that are not real-time, e.g., responding to an email or SMS message request sent in directly by a customer, field sales/support personnel, or as a result of an automated business process application that is monitoring a customer-related situation (CEBP). Again, making automatic assignments to individual SMEs may not work as well as broadcasting the request to qualified and available “first responders.”

· In real world worst-case situations, where no real-time live assistance is available to resolve a customer problem, customers need to be able to leave information about their needs (trouble tickets, messaging, online or IVR application input, etc.) and given written (text) confirmation of the request, with a time projection for follow up. In many cases, there is no possibility or even need for an immediate fix of a problem; it’s just the customer reporting and acknowledgment that is “real-time.”

· Performance management issues still remain for tracking “agent” vs. “SME” availability. While “agents” have to “punch in” for call handling accountability for their time on the job, SMEs don’t have the same requirements. On the other hand, from a customer perspective, all contact activities involved with a given customer should be tracked, regardless of format and source.

· “Customer presence” is another facet for the contact center in terms of outbound contacts. This is becoming particularly important as consumers become more accessible and therefore more “available” for real-time notifications and connections with mobile smart-phones. This will make “First Call Resolution” and voice conversations less critical than “First Contact Resolution” and message notification and delivery, coupled with “click-to-call” capabilities.

What Do You Think?
You can contact me at: artr@ix.netcom.com or (310) 395-2360.