Setting the Stage

In most legacy contact centre interaction scenario's there is a heavy element of Identification and Verification (ID&V) required between the interacting parties. Overwhelmingly the onus of obligation to confirm ID is placed up the customer.

Do you ever receive a call from a contact centre, where the dialogue goes something like;

"Hello, this is Acme Bank calling, for security purposes can you please confirm you full name"
     "David Tidwell, what's this about?"
"Thanks, I'll explain why in a moment or two! Can you please confirm the last part of your postcode starting BS16?"
     "1FX"
"Just a couple more questions…."
     "AAAAAAAHHHHGGGG !!!" CLICK – hang up

As a customer, this experience is infuriating! The Call Centre CALLED ME, and now I have to go through 100 hoops; and they are already inconveniencing me right when I need it the least! The natural and easiest reaction for the customer is to simply hang up! I know; because I do it a lot on unsolicited calls made to me from contact centres.

What about scenario's where the customer has asked for a callback? I suggest in these scenario's the customer is EXPECTING the call/contact, but still may have concerns that they are actually talking to their bank. It is incredibly easy for PHISHING to occur even in voice interactions. How? I block my Calling Line Identity, and phone my TARGET consumer pretending to be their bank. I can FREELY challenge this customer for their full name, date of birth, address, zip (postcode), telephone number and even confirmation of account details by simply pretending to be their Bank.  It only requires minor levels of 'professionalism' and a practiced approach to PHISH in voice channels with some success.

Think about how easy this is to do! So, our line of argument for this concept of reversing the role of Identification and Verification is two-fold;

• It should make it easier for the customer to identify and authenticate themselves to the contact centre
• It should make it easier for the contact centre to identify and authenticate themselves to the customer

With Mobile solutions for Customer Service we have a new instrument that may make for an effective instrument to present SECRETS or TOKENS that are used in a variety of use cases for interactions driven by the CUSTOMER or interactions driven by the ENTERPRISE

Using Mobile Applications to present TOKENS or SECRETS to the Customer Services Team

The Anana Mobile Applications Solution for Customer Service now features the capability for the Customer to provide a secret or token as part of their CONTACT Request.  In the use case presented below, our Customer, Dave Tidwell requests a callback from Customer Service 

Step One – Booking the Callback and setting SECRET Token

Start the dedicated Customer Service application on the iPhone and go to the CALLBACK option.

Dave has selected the CREATE CALLBACK option on his Mobile Application.  In doing so he has provided all the appropriate details and has added a SECRET.  In this case that token is "anana". Dave's expectation is that when the Customer Services Representative calls him back that this token will be 'read-back' to him so that he has a tangible confirmation that the organisation is who they are purporting to be.  Dave presses on CREATE button and the callback request; including the appropriate token is transmitted to the Contact Centre. In this case, we transmit this information into Genesys 8.1 through the Genesys Mobile Solution and Anana's Composite and Atomic Services Solution for Mobile. (A RESTful interaction stack; more on this later!)

Step Two – Confirming CallBack Request is Active

Dave now confirms on his listed CallBacks that the callback is booked.

Step 3 – Confirming details of Callback

Dave has the choice to click on the scheduled Callback item and see the details (we could of course add lots of options for rescheduling, cancellation, changing tokens or means of callback from Voice, to SMS, to eMail to Twitter, to Facebook and so on)

You can see in the graphic above that we have APPENDED the SECRET TOKEN to the Subject of the CALLBACK.  It doesn't have to go here; but it makes presentation for the Customer Services interface in the Genesys Interaction Workspace slighly more intuitive.

Dave goes back to his HOME SCREEN in the Application and can see his pending CALLBACK request.  We can send NOTIFICATIONS in email, or directly to the Application to confirm 5WH (Who, What, Why, When and Where) so that Dave is kept up to date with the STATUS of his interaction request in real-time.

Step Four – Callback active and pending (The work item is being targetted in the Contact Centre)

Step five – Targetting a Customer Services Team Member to conduct the Callback

Meanwhile, depending on the business logic in the underlying routing strategy (either in Genesys Orchestration Server – ORS) in SC-XML or via alternatives such as the automation of injection into Outbound Contact Server (OCS) an agent is targetted based on the NATURE of the enquiry, customer segment, context and state of conversation (via Genesys Rules Engine – GRE), Context Server and Conversation Management and a ringing event occurs in the Contact Centre.

The screengrab above shows that we have configured our Genesys Contact Centre system to RING with a TOAST popup event for this media type.  The Customer Services Representative can see immediately that this is a CallBack interaction, from a Customer called Dave Tidwell, with a Subject of "Help" and the associated TOKEN or SECRET of "anana".  A quick click on "Accept" spawns the interaction proper on the Genesys Desktop in Interaction Workspace.  The agent will of course confirm the Contact Details and importantly the Interaction History to support context and the overall Customer Journey and Customer Experience.

Step Six – Customer Services conducts the Customer Requested Callback

Again, we present this key or token as attached data, and show it clearly in the associated interaction CASE INFORMATION.

Step Seven – the Customer Interaction Dialogue

"Hi Dave, this is John at the ABC Company calling you back as requested.  Your secret is "ANANA", how may I help you?" says the Customer Services Representative
     "Okay, Hi John, thanks for calling back, I have a question about my….." says our customer

Conclusion

The subtle injection of interaction TOKENS, KEYS or SECRETS can help both parties in the conversation.  It adds an additional layer of explicit security with is tangible, is dynamic, and may be easily injected by either party.  The Mobile device is the instrument that allows for the customer injection of ATTACHED DATA and context that "changes the conversation" and helps both parties enjoy a healthier, faster and more effective conversation.

Other Idea's that immediately come to mind

PCI Compliance

Payment Card Industry Compliance – when a customer needs to make a payment via the Customer Services Representative, for example, to pay a current bill, the Customer may easily do so privately on their own Application and on their own Device.  We can transport the attached data for AUTHENTICATION, Transaction ID and Verification Code via the application layer back to the contact centre.  At NO TIME does the CSR see, interact with or request the Credit Card Number, CVV – Card Verification Value or CVV2 (Card Verification Value Code).

Customer Alerting with TOKENS

The Enterprise needs to reach the customer.  In most environments today this is accomplished via OUTBOUND campaigns (dialers) against distinct groups of customer service agents that may even be external to the Enterprise (offshore or otherwise outsourced).  It may be far more effective for this requirement to reach the customer to be handled slightly less confrontationally and to improve the customer experience by sending a NOTIFICATION to the Customer Services Application indicating that the company needs to speak to the customer about their latest bill.  The customer can then acknowledge this request by suggesting the date, time, media and context of that planned conversation.  The results of the application level negotiation for the conversation may be easily pumped into Workforce Management and Schedules to that it is effective for both the contact centre and the customer.  Tokens may be used in this use-case in a similar way.

"Hello Dave, this is John at the ABC Company. Your secret is"anana". Thanks for making time to talk to us" Says John in the Contact Centre
     "Hi John, no problem, it was handy being able to tell you when I'd be free! What seems to be the problem? Why do you need to talk to me?" says Dave our Customer
"Dave, we noticed that your last payment didn't go through……" and so on

Dynamic Use of existing SMART Tokens for AUTHENTICATION mid-interactions

It is easily possible to transport the results of a smart TOKEN via the Application into these scenario's too.  Where Banks issue their customers with smart-fobs that allocate digit based authentication tokens these may be included in the application to provide short lifecycle authentication for high value transactions.  A Customer Service Representive may be able to ask the customer to enter their smart-pin in mid transaction for high risk transactions, for example;

"Yes, Dave, I can help you do the balance transfer. Because its over £1000 can you please activate our BANK Smart PIN and enter the digits in the mobile application now?"
     "Yes, no problem" Says Dave as he enters the 6 digits into his dedicated Banking Application
[We send this key via the application to the Bank Back end systems, and provide a validation token to the Agent and we update the Interaction Workspace Data to show this new state]
"Great, thanks for confirming that for me Dave, so you wanted to transfer £5000 from Savings to your Current Account?"

Tweet Originate is a custom Anana development for Genesyslab Interaction Workspace 8.1.200.16 on Genesys 8.1 with Social Messaging Server. It is a functional addition to the main shipping capabilities of Twitter as a media type for Social Media Customer Service. It allows Customer Services Representatives to conduct 3 typical additional functions in the following typical use cases;

1 – It allows the CSR to post an outbound tweet to the underlying Brand Twitter Account that doesn’t specifically target an individual customer
2 – It allows the CSR to initiate an outbound tweet to a new customer which has not yet interacted with Customer Services on the inbound side
3 – It allows the CSR to initiate an outbound tweet to a known existing customer

Use Case One
We have found our existing Genesys based customer deployments of Twitter required the ability for the Customer Services team to send a “Good Morning” or end of the shift tweet to their followers. Another use case could be a tweet to the timeline that recognises an event that touches a significant number of followers; for example, an Operating System Update available for their phones; or an outage or similar regional or national event.

Use Case Two
Could be triggered by a scenario where someone in another part of the business is very keen that someone in Customer Services reaches out to a customer who is talking about the Brand; but not directly at them. This form of escalation is quite common; where Customer Services may get an urgent request from Marketing or the Brand team to reach out to a Customer and offer assistance. “Could you please get one of the Customer Services team to reach out to Dave Tidwell @dave_t_pilot and assist him with the problem on his iPhone?”. In this case Dave may have been complaining bitterly about the device and/or the brand but not mentioned the brand directly. This is common too where your Genesys deployment is configured to pick up MENTIONS and Direct Messages but not to listen for keywords.

Use Case Three
Is typically triggered by a customer who might say “Okay, when you’ve got the answer from engineering can you please tweet me with the update?” The time lag between the original interaction and the subsequent response from the back-office could be minutes, hours, days or even weeks. Without Tweet Originate it is impossible for the agent to initiate a response to the customer as the previous interaction will have been closed.

The following video explores these 3 use cases in detail, completely narrated and described step by step.

All of the custom features included in this module are designed to fully harmonise and replicate usage of the Interaction Workspace by Agents on the inbound side. Some are subtle; for example, the lookup of the target customers KLOUT social influence score when the outbound tweet is initiated. This activity is conducted asynchronously so that a failure of score to return from KLOUT will not prevent the agent from doing the response; and will appear after the interaction has already been started. You’ll notice that perhaps in the video.

Anana has been quite busy over the summer deploying and realising Social Media solutions on Genesys. During the course of these projects we have enjoyed working closely with our customers on use cases, and scenario’s in which they would like to use the technology.  A more recent development is the concept of treating social media interactions as conversations rather than transactions in the form of individual interactions.

What we have certainly noted with some of our clients is that their customers actually treat Twitter differently than originally intended.  Rather than sending in a single request, that recognises the limited real-estate (character count) in a standard tweet, a user may type 3 tweets in rapid succession that target the Enterprise in rapid succession.  In order for these tweets to arrive into Customer Operations in a meaningful way we had to think of ways to deal with the scenario.

The standard, out of the box capability in Genesys (as of Genesys 8.1.1)  is ‘interaction based’. In other words, each tweet is treated distinctly, and is routed and targetted to a skilled agent distinctly.  This is fine in any use case where the customer does not Power Tweet, or indeed, use a Twitter LONG web-service that turns a long utterance into a series of tweets.

If a user sends, say, 3 tweets in rapid succession (or a longtweet that is turned into 3 of appropriate length), and these 3 tweets are picked up by the social media server in the next POLL interval, then Tweet 1 may go to Agent 1, Tweet 2 may go to Agent 3, and Tweet 3 may go to Agent 2.  As a whole, the ‘conversation’ could still be reviewed by any of these targeted agents by using the ‘interaction history’. At best though, this may result in the FIRST tweet in thread being the owned tweet, and the other two agents having to go through consultation with each other to FORWARD the other tweets that formed part of that conversation directly to the now, newly owning interaction Agent.  Sound complex?  It can be!  In simple terms, why target 3 agents with a single LONG Tweet that spans 3 interactions, when it could be easier to simply target all 3 of them at the same time to a single agent, in the right order.  That consideration gave us time to think about, what will happen if a few seconds later the subscriber tweets again?  Where should that tweet go?  A new agent, or take the first agent as the preferred agent and send it straight into that interaction?  Sounds a bit like Web Chat does it not?

Genesys has done an incredible job of offering the maturity in social engagement that is evident in the 8.1 release and we are working closely on the types of use cases cited above with Genesys Product Management, Engineering across eServices and the Interaction Workspace on identifying and documenting these new use cases so that they can be captured and become part of the roadmap where approved.

To test out the use case scenario we are discussing, our Platform Practice Team went ahead and built a new Social Media driver for Genesys based on the STREAMING API, which allows us to listen in real-time for any activity on our ABC Company Wall (in the Anana Briefing Centre) and immediately target that to an agent.  Once targetted, any subsequent tweets from that subcriber in timeframe X would be targetted to the same agent; effectively treating the interaction the same way the use-cases for Web Chat have already proven themselves against.

The video below shows the Anana manipulation of a new Driver for the Social Media Server, with Real Time Streaming API, targetted to the Genesys Strategy as a Web-Chat.  This is a basic proof of concept and would require a lot more work.  For now, it shows how useful it could be in certain use-case scenario’s where your customers want to treat social media streams of communication as near real time channels.  Please turn on the CC (Closed Captions) option, and go full screen for best viewing.  Best viewed in HD format of course if your bandwidth will allow it.

Do you think a conversational mode for interaction management in social engagement has a role to play in Customer Services?  Our clients currently think so!

Further to our recent post describing the development of the first concept Customer Services application on the iPhone we are pleased to continue our exploration of this theme with a video of the application in action.

Anana will be showcasing a version of this application at the premier Call Centre Expo in London next week. Please pop by and ask to see it in action in real-time. We’ll be able to show both Customer Services Representative as well as the Customer Experience from the same place at the show.

For best results make the player below fullscreen and select the HD Mode On format for the video.

Exciting times appear to be ahead. Over the last 4 months or so my team has been very busy delivering on customer projects to bring Genesys Social-Engagement into the enterprise Call Center. Change that; into the enterprise Contact Center!

Social Engagement as a strategy for the Enterprise makes a lot of sense for many reasons. Now we see our customers begin the process of moving Social Engagement from the control of the Marketing Department into the operational front-line in the Contact Center.

That process too, though, adds more questions for the Enterprise. Should I segregate my agent pools and teams so that the large proportion stay on the original inbound voice channel, answering telephone calls? Should I create new agent teams that are trained specifically in written communications rather than verbal communication skills? If I create a team of agents that are now familiar with a text based interaction method (Facebook and Twitter in the Contact Center for example) then it is an easy step, is it not, to add other textual channels to their tasking too? Channels of Communication with Customers like SMS, eMail, Web-Chat and Instant Messaging?

With these questions Anana spends a lot of time thinking about the impact of this sudden and rather remarkable swing of interest from inbound (and outbound) voice in the Contact Centre to one of “Blending” across channels and interactions.  One of our most recent technical additions has been a mobile framework that brings the power of Genesys as a solution itself to the Customer! How can the customer themselves become part of the Customer Services paradigm?  How may Anana effectively explore this new “Voice of the Customer”?  What meaningful ways could be explore that help our customers and clients begin the process of thinking about Customer Enablement?  How can we also reduce the Customers actual (and perceived) effort score (Customer Effort Score) in reaching out to their contact center?

An excellent vehicle to explore these questions has been the creation of a series of ATOMIC and COMPOSITE web services that act as a bridge between any HTTP enabled device and the software that powers the call center itself from Genesys Labs.  When I think of any HTTP enabled device, in our current modern context that could be as simple as a smartphone, an Internet Ready TV, a Sony Playstation, or even in the case of some manufacturers In Car Entertainment (ICE) systems.  We started with the obvious paradigm; the smart mobile phone. As telephones are still the prevailing method to access Customer Care Services that are multi-channel ready the smart-phone is a great place to begin exploring.  Smart Phones are everywhere!  This market includes other devices that aren’t typically associated with Telephony; like Tablets.

To help our clients and customers begin the process of understanding how to enable Customer Care over these types of devices we have built an iPhone application which runs on any HTTP enabled iOS (Apple) device; this includes iPhone3, the iPhone4 and iPad (even some versions of iPODs). This application is an ALPHA (brand new initial exploration) and only just begins to scratch the surface of customer care solutions on smarter devices. Please see my earlier post on this subject for the technical details.

What are the details of this first iPhone customer services application for Genesys?

For all pictures in the post; please click on the picture and it will open full size for easier viewing. The application sits resident on the device itself and is started by touching the associated icon. In the picture on the left of your screen this is the ABC Company application logo. Prior to first use of the application the customer would configure their own Customer Services account details in the iOS settings application; declaring their name, contact details and associated customer record number.

Once the customer has opened the application we immediately publish ALERTS for them that have been generated by their activity with the Enterprise. If they have orders open and the status of those orders has changed we can show them here for example. We also show a list of any open ‘interactions’ and their status.  We also list any customer requested callbacks that are pending so that they don’t forget the callbacks that they have already requested.  From this simple home screen we would obviously have enormous opportunity to offer cross-sell and up-sell, advertising etc for and on behalf of the enterprise. If we know what products and services the Customer has purchased in the past; and there’s a better offer on the table then we can show them here. Indeed, the very nature of these types of smart-phone applications makes it incredibly easy to solicit location information, and presence information.  There is absolutely no reason why the consumer wouldn’t have this application open by default if it was adding significant value to the progress of their day (in any form!).  This presence can be reflected back into customer operations in cool ways; for example; If we know how many Customer Services Representatives are currently available AND we know how many customers are currently logged in to the Customer Services Application then we can take this information to use our excess CSR pool to do outbound call campaigns to subscribers that are ALREADY known to be available.  This could even be geo-fenced into “Add subscriber to the campaign if they are within X metres of one of our retail outlets”….and then target them with GEOFENCED offers when they break this border.  An obvious example is an airline customer on the loyalty scheme that happens to be within 2 miles of the airport. Back office systems confirm they are booked in for a flight that leaves in an hour and a half; so why not offer immediate concierge based curbside check-in?

From this home screen the Customer has fast access to common Customer Services functions.  They can view their HISTORY for example.  The interaction histories are interesting to me for one very profound reason. As a consumer, when I have to phone in, or email into a Contact Center I feel an overwhelming burden of ‘effort’ due to the fact that I have to verbally reiterate the entire reason set for calling in; specifically so when following up on an existing customer services activity. Knowing that my interaction history is clearly understood relieves me of this assumed requirement. Publication of the interaction history for the customer also shows a full commitment to transparency and a 360 degree view of the customer ‘journey’.  Telephony (inbound voice) call centres have typically focussed on First Call Resolution (FCR); often in defiance of the actual ability to resolve the issue in one swoop of the agent script. With the Genesys solution we focus more on managing an interaction, that itself forms part of a dialogue or in other words as part of the overall “conversation”. This reduces the relevance of first call resolution, and puts more focus on the actual current need cited by the consumer and relieves the CSR from the shackles and constraints of the published script.

From the Home Screen the consumer can also select to open a chat session. In keeping with the familiarity of SMS chat, web-based chat, instant messaging chat and other chat mechanisms the Chat function works exactly the same way. If the consumer starts a chat, we take this chat request, and target it to an underlying Genesys Strategy that will find an appropriate agent in the pool of current resources. The Customer Services Representative desktop uses the prevailing ‘out-of-the-box’ web-chat capability already shipping in the Genesys Agent Desktop and the Genesys Interaction Workspace.  The CSR see’s absolutely no differentiation between web initiated chat or a chat that starts from the iPhone application.

Once a chat is initiated the Customer can interact with Agent freely. The agent is able to send URL’s, and to dip in and out of Content Analysis, FAQ and knowledgebase at the desktop level to offer immediate customer assistance that is timely, appropriate and accurate. <<USER ACTION>> is very much a work in progress. This is a placeholder in this alpha version of the application that will offer status updates, for example, Agent is Typing and notifications of other parties joining; “ABC Agent 1 has joined the chat”. These are useful updates to the consumer about who’s on the chat, who’s currently typing, and who’s been added to the conference, transfer to other agent updates; or the simple fact that the Agent has invited a subject matter expert to join in the chat (conference). It is also remarkably easy for the Customer Services Representative to nest other interactions whilst in a chat; for example, sending an email to the customer that is recorded as part of the chat interaction and have it reported on for full cross-channel transparency purposes.

What happens if the customer would like a call-back at some point later on? Using the call-back web-service we can add a callback request into the Genesys Customer Interaction Management Platform so that the callback request is targetted to an available Customer Services Representative at the requested time.  A customer may have hit a busy period in the call center. They may have remembered whilst in a meeting that they need to speak to the Call Center but right now is inconvenient or inappropriate. It may be convenient for that call to take place some hours later, say, on their way home from work in the commute.  Anana could even extend these callback bookings into ‘campaigns’ mapping agent availability, workforce management and the Genesys Dynamic Contact Center capability to only offer callback times that coincide with planned operational performance. There’s a lot that we can do with this I’m sure.

Summary

My view is that this is a great place to start a journey of exploration, discovery, learning and innovation around Mobility Enabled Customer Care. We have already showcased this application to our existing customers and all are extremely excited by it. We’ll maintain a keen and steady pace on improving the interface; do some more work on graphics, layout and functionality and continue exploring how we can use the Anana Atomic Services Bridge into Genesys technology in innovative ways.  We have already built out a series of use-case scenario’s to effectively demonstrate this application as part of the already extensive Anana Briefing Centre experience.