Why would you text a picture to your Amazon Connect call center?

If you have ever worked in a help desk technical support role in a call center environment, you have always wished you could “see” what your caller was stressing about!  How many times, if you could have seen that device, you could tell them specifically which cable to move.    Insurance adjusters also have that same challenge.   It would really be helpful if you could text me a picture of that crumpled fender!

Being able to send a TEXT message to your call center could be a major time saver!   Yet how many call centers can route an incoming TEXT message like a voice call, sending it on to the next available Agent?  The Dextr Dashboard now enables incoming TEXT messages to be sent to the next available AWS Connect agent. Messages can be TEXT (SMS) or PICTURES (MMS)! Dextr also enables “sticky SMS” which assures that an “in progress” text message exchange stays with the agent that originally handled the text request. If a message is assigned to an agent who is not currently logged in to AWS Connect, the entire text conversation is moved to the next available agent!

“TEXT” becomes a “skill” or permission that is added to an Agent profile nominating them to participate on inbound text messages sent by callers.  Dextr has a variety of interfaces that support Voice, Text, Email, Chat and Social Media messaging and an inbound message will pop the correct TAB enabling an Agent to handle multiple channels if they have the correct skill or permissions.

If you are using an AWS Connect call center, head over to http://go.dextr.cloud and onboard you instance and give the Dextr dashboard a try!  If you are not using AWS Connect, but are thinking about it, we would build you a proof of concept and you can still try it!  No cost to you, so give us a call!

Amazon Connect Forced Release Behavior Option

Sometimes it is better to give folks what they want, rather than what they need! Over the years of working with call centers you develop a sense of what is a best practice and what is something that will be nothing but a problem! You do your best to educate folks on the issues and make recommendations that you know are in their best interest. However, “if you have the peso, you have the say so” and ultimately we do what the client wants to do, right or wrong.

Such is the issue of the “forced release” status that results from an unanswered call presented to an “available” login agent. Most if not all call centers, will attempt to present a call to the next available agent based on the routing plan, generally “longest idle”, “round robin” or “top down”. The issue is what do you do if the agent does not answer the presented call?

Most all call centers will set the agent to “forced release” which does two things. First, it assures that we do not waste the callers time presenting another call to an agent that may not be present. Secondly, an agent in “forced release” alerts a supervisor to a potential staff management problem.

Recently we had a client who did not want agents put into “forced release”. Well if we do not put them in forced release what is the desired behavior? Take an CSQ with one agent for discussion purposes. If we present the call to that agent and the caller is not answered within the system Ring No Answer time, we would normally queue the caller for the next “available”agent and put this agent in “forced release”. if we do not put the agent into forced release, the call will be ping ponging back and forth between the queue and the same agent!

Ultimately it was decided that we would create a global option that would allow the administrator to set the default behavior for the call center. The default behavior is either “forced release” or, thanks to Dextr, “follow Wrap Time behavior”. In this way a call presented to an agent and not answered, would optionally be put in “wrap time” or “after work”.   The Dextr application also enables the global setting of a “name” for the wrap behavior to distinguish that mode from a normal wrap period.  This seemed like the best solution.  This would enable the agent to return to “available” status when the wrap time or after work time expires.

Comments are welcome!  DrVoIP@DrVoIP.com

Amazon Connect Custom Integration tools!

If you have taken the time to experiment with AWS Connect and the creation of a cloud call center instance, you know that the basic setup is achievable by a business analyst and no implementation engineer is required. This is good news for very simple, inbound call centers but if you are planning to connect with the rest of the enterprise, you will need some folks skilled in full stake web service development.

No Call Center is an Island!

Call Center as a business process and customer experience management, require that the call center be able to communicate with other information resources throughout the enterprise. The interface between the AWS Connect call center instance and the rest of your organization will must certainly require both middleware and API’s that make use of advanced software development tools within AWS!

Common integration requests that dominate the call center technology space include:

  • Customer Routing Database Integration;
  • Work Force Management
  • Voice and Screen Recording and Playback
  • Voice Analytics
  • Salesforce.com
  • Electronic Health Record
  • Website Integration (think MyChart or CoBrowsing)
  • Microsoft CRM
  • Microsoft Skype for Business
  • Custom Agent dashboards
  • Real Time Metric display boards

These are just a few of the common requests we see on a daily basis. There are also unusual requests for custom solutions that are unique to the business enterprise the call center is deployed in!are also unusual requests for custom solutions that are unique to the business enterprise the call center is deployed in!

Common AWS Connect Integration Tools!

There are a few tools that are essential for developing integrations in AWS Connect. Generally, you will always require Lambda a “function as a service” to unite the call center to any other service. Lambda is “serverless” so you do not need to worry about setting up a server and you can write your function in any of the popular programming languages including Node.js our particular favorite!  Unless you are interfacing with a CRM, you will need a database and we would choose a noSQL solution like AWS DynamoDB, another server less solution.  Lets assume you want to route calls based on the callers area code, so that east coast calls go to the Agent group in your hierarchy that is optimized for east coast callers.  Maybe you want to greet your callers by name. This would require you to pass the Caller ID on an incoming phone call to a function in Lambda that would look up the customer and find the name, then pass the name back to the call center and activate Poly, the AWS text to speech service, so that you can prompt the caller with “Hi <customerName> before continuing to route the call to an agent!  Maybe you want to display the callers name to the Agent when they answer the call, which would again require both Lambda and DynamoDB in addition to some custom code!

Custom Agent Display?

Sometimes it is necessary to create an entire Agent dashboard to handle information displays, team collaboration, key metric broadcast, recording retrieval and playback.   We created the Dextr.Cloud dashboard to provide such an interface.  This is an example of the type of integration that is possible with AWS Connect and the many services that exist in the AWS Cloud.    We are interested in learning more about your own call center integration requirement and invite you to give Dextr.Cloud a try and also to contact us with your integration “’wish list’.   We have seen a lot of requests and nothing suprises us anymore!  So please feel free to play ‘STUMP THE VENDOR” and we will see if we can help you or at least direct you in the right direction!

 

 

 

Amazon Connect Arrange a Call Back from Queue?

Setting up options for Callers waiting in Queue for “the next available representative” often include offering a call back option. Generally, it is a best practice to not offer this option immediately but queue the caller for some time before offering this option. They have already called in and you have answered the call, so let them wait a few minutes before offering bail out options.

Common Call Flow Errors!

One of the most common errors in call center call flow planning is allowing a customer caller to queue for an Agent when no agents are logged in! The second biggest error, is leaving folks in the call back queue, at 5PM when all the agents log out and go home! So how do you do make sure this situation does not happen?

As it relates to the first issue, we always check to make sure that Agents are logged in BEFORE we queue a caller! This is a very simple step to do and it saves a lot of aggravation for callers who will never forget how long you left them rotting away in an empty queue!

Now as it relates to ‘call back’ without losing your place in queue, we have the same issue. Let’s assume that you offer callers this option. It is now 15 minutes before closing, what happens if all the agents log out before the call back is next in queue?

Call Back without losing your place?

In AWS Connect, Call Backs will follow the On-hours schedule. So if someone left a request for call back at closing time, that option will not trigger until the next day when the queue is open per On-hours. Lets see if we can improve this, but NOT offering that option late in the day!

We can setup a new schedule that only offers the call back between certain hours, so that if it is near closing, we do not offer the caller this option. This can be easily scripted in AWS Connect Contact Flows by adding a “check on-hours” step that eliminates this option when callers enter the queue and hour before closing time. This assures that Agents can log out at the appointed time and not leave anybody in queue!

AWS Connect is written around “contact flows” of different types. A “contact flow” handles inbound calls and routes them to Agents in queue. A “customer queue” contact flow deals with how to treat a caller while they are awaiting for the “next available representative”. You will learn this the hard way the first time you try to add a block to a contact flow and find that, though the block was there earlier, it is not there now! Why, the contact flow you are working on, does not support this type of block.

Free Call Back Script just for Asking

In this example we use a “Main Greeting” that is triggered by a call to the DNIS number associated with this path. We start the contact flow off by setting up all the variables like what voice to use, are we logging, what queue hold to use, which queue we are using etc. The flow goes on to check operating hours – routing ON- hours to the Queue and Off-hours to the Voice Message center.

If it is “On-hours” we send the call to the Queue flow. If an Agent is available, we connect them to the caller. If all agents are engaged with other callers, we queue the call. We play our “poor mans” Estimated wait time and then queue them with a “care message” followed by Music. 60 seconds later, we offer the option to continue to hold for an agent, or press 1 to receive a call back without losing your place in queue’.

Before we offer this option, we check another schedule that determines if we should offer the call back option. If the caller hits the center during the call back hours, the call proceeds as described above. If it is an hour before closing time, we do not offer the option.

So hit us up with a request and we will send you three “Quick Start” scripts that enable you to get this working as quickly as you can import the scripts into your AWS Connect call center instance.

Better yet – Give us a call and we will set this up for you!

Amazon Connect replaces ShoreTel Workgroups with the Dextr Dashboard!

Replace ShoreTel Workgroups with AWS Connect1

Recently we had a client with a very specific set of requirements and DrVoIP was able to satisfy with Dextr dashboard!   The client had a ShoreTel deployment that used ShoreTel Workgroups. ShoreTel Workgroups are often called a ‘poor man’s’ call center.  The client had made a decision too they were migrating away from ShoreTel to Skype for Business, they needed a new Call Center solution.  Workgroups act like traditional hunt groups but they enable customer queueing and both historical and real time reporting in a manner that is very similar to a formal call center.

The client wanted to replicate ShoreTel Workgroups along with the same ‘look and feel’ as ShoreTel Workgroup agent dashboard.   This dashboard enabled queue monitoring and also enabled a supervisor to change an agent state from Forced release to available or move an agent between queues.   We had no doubt that AWS Connect was the ideal solution, but we knew the Connect Control Panel or CCP as AWS calls the webRTC soft phone, would need a lot of work if it was going to provide the same functionality as ShoreTel.

 

We created the basic Dextr Agent dashboard to have the same features and functionality as the ShoreTel Workgroup Agent interface with several new and advanced features.  We needed to create a solution that would enable Supervisors to create an ‘ad hoc’ meeting and to close the call center and even create a new ‘CLOSED’ greeting.   Additionally it would be desirable if the Supervisor could send a broadcast message to all the agents in the queue.  This broadcast message would scroll across the agents screen, alerting all to a situation that the Supervisor wanted to bring to the attention of all Agent.

AWS Connect Holiday Schedule.

The first requirement was to setup a holiday schedule and also to allow the supervisor to create a ‘CLOSED FOR MEETING’ date and time.  AWS Connect does not have this ability out of the box, but it does have the API’s available to create such a solution.  So our team added this functionality!  Dextr enables a user with Admin privileges to open a window and create both HOLIDAYS AND AD HOC closings.   The instance is initially stocked with all US Federal holidays already listed.  The Admin can modify, add or delete these dates.  They can also specify, via the drop down window, which queues they are closing.  There is also a Text to Speech window in which the supervisor can enter the text of a prompt that will be played to a caller should they call during that time slot.

Dextr uses AWS Lambda to test for a holiday or ad hoc closing as step one in the opening contact flow.   The Lambda function brings back open or closed, a reason code and the text to speech prompt.   In this way the caller might hear ‘ You have reached us at a time we are closed for <insert reason from Lambda>, please hold while we transfer you to the message center’.   The entire message is created by the supervisor as the TTS or text block that will be returned by Lambda.

Dextr also enables the Supervisor to send out a broadcast message that scrolls for all queues or just a selected queue!  This is a list of all the features of the Dextr Dashboard basic version;

  • Nothing to install! Instant Access via https://go.dextr.com which has video instructions for on boarding;
  • Customizable Logo;
  • Role based Login (supervisor, agent, administrator)
  • SAML support;
  • Agent Team Status Display;
  • Agent Call Activity with (click to return call);
  • Directory System with Click to call;
  • Help Button – Alert Supervisor;
  • Queue Monitor – including calls in queue, max waiting time; optional red, yellow tags)
  • Personal Recording; (permission option);
  • Supervisor Permissions add: Login/Logout (change agent state) Monitor, coach and Barge in;
  • All Recording search and play (see note 1 below);
  • Real Time Metric review Report Generation
  • Ability to set Holiday Schedules and “ad hoc” closings with new close prompt (think team meeting).
  • Push Announcement String out to Agent Dashboard for alerts and other notices.

Dextr augments the basic AWS Connect CCP softphone to enable advanced features that we find most call centers demand!  See Dextr.Cloud or DrVoiP.COM for additional details!

 

 

 

 

Dextr a Customized Agent Dashboard for #Amazon Connect Call Center!

AWS Connect CCP

Building out call centers on AWS, you learn a lot about opportunities for productivity enhancements!   One of the first issues that we noted was that the standard Contact Control Panel or CCP, which is basically a WebRTC soft phone client, though very useful has many opportunities for improving the Agent experience.   The list of request features is growing and as a result, we have taken on the development of  a customizable AWS Connect Agent Dashboard!

 

Call DrVoIP for AWS Call Center migration assistance.

If your only introduction to AWS is Connect, their cloud based call center product, you have successfully created your first call center instance and you are now taking inbound phone calls!   It was remarkably easy and with no real ‘geek” training, most call center professionals were able to log in, setup an instance, organize a call flows, create agents and voice prompts, obtain a phone number an in a few hours, you were taking phone calls!  Wow!

AWS Demo API’s

Did you know that the Agent CCP is completely customizable?  AWS provides a number of API’s and Connect Streams that a software engineer can access toward the goal of building an Agent Dashboard with a set of features and tools that are unique to your call center environment.  There is even a site you can log into and test some of the available API’s.   If you go to http://connectdemo.com and click on the “demo sites” you can see some examples of customized CCP, Click to Call, Screen Pops and other tasty code bits.

Agent Streams

We note that there are many “connect streams” that a developer can tap to create their own version of CCP.   The supervisor side, however is not as fully formed and there are not as many streams and API’s available to support Supervisor requirements like real time queue and agent metrics.   In fact we had to develop our own socket layer communication strategy to implement the features we envisioned in our dashboard.

Recently we have discovered new and not readily available API for other AWS streams.  Some are only available depending on your support contract status.

Agent Dashboard Feature Set

The list of functions and features that we have added to our CCP is still growing but we set a goal of making the dashboard painless!   For example there is nothing to install.  Our application needs to be added by your instance administrator as an application end point in the Connect dashboard.  Once that is complete, the user just points at our portal and enters their instance name (you can even upload your own logo).   The traditional AWS Connect CCP shows up and you login as normal.   Once your credentials are established, you are then presented with the revised Agent Dashboard as shown below.

AWS Connect Dextr Agent Dashboard feature set

Most folks have asked for a “team status” display.  As an Agent I want to see the status of the other agents on my team.  So the first attribute we added was just that, a team status display.    Each agent has their own Activity List showing all of their calls both inbound and outbound.   Next to each call is a link to hear the recording of that call. Supervisors can select all calls, but agents only see their own call recordings.

Each Agent has a personal contact list with contacts that they have entered for their own use.  This augments the “quick connects” that they system administrator had created.  Here is the feature list:

  • Nothing to install! Instant Access via https://go.dextr.com which has video instructions for on-boarding;
  • Customizable Logo and YourCompany custom log-in URL;
  • Role based Login (supervisor, agent, administrator)
  • SAML support;
  • Agent Team Status Display;
  • Agent to Agent Chat
  • Agent Call Activity with (click to return call);
  • Directory System with Click to call;
  • Help Button – Alert Supervisor;
  • Queue Monitor – including calls in queue, max waiting time; optional red, yellow tags)
  • Personal Recording; (permission option);
  • Supervisor Permissions add: Login/Logout (change agent state) Monitor, coach and Barge in;
  • All Recording search and play (see note 1 below);
  • Real Time Metric review Report Generation
  • Ability to set Holiday Schedules and “ad hoc” closings with new close prompt (think team meeting).
  • Push Announcement String out to Agent Dashboard for alerts and other notices.
  • Omni-Channel SMS/MMS enables test and pics to the next available agent
  • Omni-Channel email routing to the next available agent
  • “no headset” audible alert options for softphone

We are also planning to integrate or Click2WebChat functionality as an advanced feature option.  This would bring website co-browsing, video chat, SMS and keyboard chat into the call center!  The Dextr screen shows the Agent interface including the Video and Chat links.

How do you set a Holiday Schedule in Amazon Connect?

Dextr enables a user with Admin privileges to open a window and create both HOLIDAYS AND AD HOC closings.   The instance is initially stocked with all US Federal holidays already listed.  The Admin can modify, add or delete these dates.  They can also specify, via the drop down window, which queues they are closing.  There is also a Text to Speech window in which the supervisor can enter the text of a prompt that will be played to a caller should they call during that time slot.

We named the dashboard Dextr!  There is nothing to install.  Follow the video instruction below and have your Amazon Connect Administrator add us as a trusted application, then head over to our portal, log in and put Dextr to work for your team!

If you have a requirement for the CCP we would also like to know more about your requirements, so let us know.   If  you do not have an AWS Connect instance, DrVoIP will build you a “proof of concept” portal for no charge!  Remember, the American Business Communications landscape will be littered with the bleaching bones of those companies that do not adopt Amazon Connect as the enterprise call center that manages customer engagements!

 

 

 

 

 

 

 

 

 

 

 

 

Front End your Call Center with Twilio Appointment Reminder!

Send a Text or add more Telephone lines?

We have long been a proponent of using more text solutions in the call center.  From our perspective it makes more sense to let clients text you customer service team than it does to add more telephone lines, to hold more clients in queue waiting for the next available agent!   With the dramatic growth of smart phones, it makes sense to engage your clients with an understanding that they are (a) very mobile; and (b) very text savvy!   We are willing to bet, you text message more than you actually talk on your smart phone!

Call Trees

Anyone who has had to write routing scripts to figure out which group of agents to send an inbound caller to, will tell you that having a DNIS number per route is the best way to go.  Why prompt the user to press 1 for Spanish, if you could just market a number that expects Spanish callers!   A separate number for Customer Service and Tech support also saves having to have the caller self navigate through an elaborate call tree just to end up waiting in queue.   Generally, the call center will end up publishing a single inbound phone number and then prompt the caller with “Press 1 for Customer Service, Press 2 for Technical Support” as adding and managing DNIS numbers gets to be a costly head ache!

Estimated Wait Time

So we keep adding more inbound telephone lines, to the same number of Agents, causing more folks to remain in queue waiting for the “next available agent” and growing more frustrated with each passing minute!   Most call centers now attempt to reduce frustration by “Press 1 to receive a call back without losing your place in queue”.     This is a helpful option in reducing customer frustration, but does nothing to reducing costs.  Actually it increases costs as you are now calling folks back on your dime!

Reduce call center cost and improve customer satisfaction by letting callers contact by text message!

Enabling your clients to TEXT a “keyword” inbound could accomplish the same result as having them self navigate through a call tree.  In fact, you could get the call routed and also provide a call back based on the estimated wait time!   Inbound text messages also facilitate more accurate data dips as the caller ID can be used to index a database to bring back relevant  customer information.   For example, if the customer were to  text the keyword “appointment” you might be able to return the following text message”

” Mr. Merkin,  we see that you have an appointment scheduled with our hygienist for Tuesday at 10AM.  Are you calling to confirm or reschedule this appointment?  Please REPLY with CONFIRM, CHANGE or CALL ME”.

Logic can be applied to the inbound text and if the REPLY returns “Call me”  the following text might be sent back by the call center:

“Please standby and we will get you connected with a scheduling assistant”  or “We estimated that we can call you in 5 minutes”

The dialog can become very customized based on the call centers CRM integration, but simplification of the inbound request and customer  contact can be significantly enhanced using TEXT.  Appointment reminders are an excellent application for text based call center integrations.    You can create a Proactive or Reactive model to remind folks of a scheduled appointment.   A Proactive model would process a list of appointments, sending a reminder text to each client and asking them to REPLY with CONFIRM, or RESCHEDULE.   A reschedule would set up a call back from the call center.   The Reactive model would function similarly but would be triggered by an incoming text request from the client.

TWILIO to the rescue!

In the following video tutorial we build out a generic TEXT and voice  based “automated attendant” that can be used to front end you customer service organization, sales team or technical support group.   We use Twilio to create a cloud based front end with the ability to transfer the call to a specific number or agent group in a call center.    Normally we would write our text applications in Twilio using Nodejs and Twilio’s Twiml but Studio, as a graphical scripting tool,  is a very useful rapid deployment strategy.

In this tutorial, though we are focused on TEXT we will also setup a solution that can answer VOICE calls or TEXT messages.  We will use speech recognition in addition to the normal “Press” instructions to get calls routed to the proper recipient.   Once the call flow is designed, we will add a number and test out our solution!     Twilio is a powerful tool and we have been able to script out customized text, voice and video solutions in days or hours rather than weeks and months!   Generally we also make liberal use of AWS for API Gateway access to AWS MySQL or DynamboDB database information using AWS Lambda functions.

The DrVoIP demo Challange!

We can build out a prototype AWS Connect Call Center with a Twilio Text front end for your company in less than a day!  So just ask us by sending a message to our Text Based Auto Attendant at 929-292-8100 and we will get you setup in no time!

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Estimated Wait Time

 

Why your call center needs “TEXT” solutions!

21st Century Call Centers still operate with 1980 business models!

I have been working with inbound call center for some 40+ years and despite all the”omni” channel technology the inbound call center model has not changed very much.   Those of us who have call centers that support a for profit business are focused on improving the customer or patient experience.   We all want lower caller holding times, faster response times and lower costs.   I have never heard anyone say, lets add more agents!   The usual answer is lets add more telephone lines!   This strikes me as more than ridiculous!   Basically, increasing the size of the catchers mitt by adding more telephone lines,  enables the call center to increase the number of people on hold awaiting service by the same number of agents.  Now how can that make sense?   If you think about it, the only reason you have more inbound telephone lines than you have agents, is so folks do not get a busy signal.  Over the years call centers have learned that it is better to capture the call and then hold the caller than it is to generate a busy signal.

One of the major differences between a call center in the 21st century and earlier call centers, is the availability of “smart phones”!   As it relates to the American Business Landscape you are on safe ground if you just assume that every man, woman and child in America has a smart phone.   In fact, it is safe to assume that smart phones have long ago out paced wireline connections.   So why not use this resource to change the call center model?   Why have more incoming telephone lines than your call center has trained agents or customer service representatives?  Additionally, nobody is sitting at home or the office holding a phone handset while waiting for the “next available agent”.  They are driving the kids to school, or running around the market place in an ever increasingly more mobile environment.

“Now that cell phones are owned by 90% of American adults, many are ditching their landlines and going completely wireless in their households. The CDC recently reported that 39.4% of homes in the U.S. indicated having no landline phone and at least one wireless device. This trend is now being adopted by more and more households as many find it unnecessary to have both a landline and one or more mobile devices” – Green Mountain Communications 

Enable two way TEXT in your call center!

TEXT notifications are ubiquitous—from doctor appointment reminders to credit card fraud notifications, they are commonly used to send messages, alerts, and reminders. All too often, however, the message only goes one-way and the customer cannot reply with a question or text back anything other than a confirmation code or a request to stop receiving such messages. Or, the customer is provided a phone number to dial for further assistance.  Enabling two way TEXT applications in your Call Center could be a disruptive game changer!

Imagine a call center in which folks just send a ‘text’ to the call center.   The call center could respond with a useful message that estimates the wait time for a return call if an agent can not immediately call you back.  A very simple change in strategy, but the improvement in customer service and reduced operating expense should be obvious:

  • Customer Sends TEXT – “Please call me”
  • Call Center  returns either a voice call from an available agent or;
  • Call Center returns a TEXT message “We will return a call to you at this number in 5 minutes.   Is that a good time to speak with you”
  • No more IVR “call trees” or extended hold times.  The customer knows exactly what to expect and when to expect it!  Options to call another number of call at another time can be easily worked into the TEXT conversation.   NO need to have more than one telephone line per agent!

The Deep Data Integration options are enormous:

  • Customer Sends TEXT – “Please call me”
  • Call Center returns a TEXT message “Hi Peter, we see you have an appointment on the calendar for Monday, is this what you are calling about”?
  • Customer Sends TEXT – “I need to change my appointment”

The fact of the matter is it may not be necessary to speak with an Agent at all!    The application of Artificial Intelligence and “bot” technology to TEXT based information is significantly more achievable than that required of speech recognition.  It is also much less costly to implement!

No more Abandoned Calls!

A TEXT based Call Centers would drop the abandoned call statistics to zero!  Given that all calls are now scheduled and there is no caller waiting in queue on an incoming telephone line that your call center pays for, there are no abandoned calls!  This would decrease holding times and increase service levels across the board.   It is also self documenting, secure

4 Reasons Your Call Center Needs SMS

Many of the benefits SMS affords companies are specific, but there are also some big picture advantages worth exploring. Here are the top reasons why your call center needs SMS.

  1. Customers Want SMS

SMS is the new email. Customers are comfortable with texting and prefer SMS for the flexibility and convenience. While it was easy to ignore in the past (when only a small fraction of consumers used text messaging), you can no longer ignore SMS without some negative consequences.  According to industry research, call center wait times are one of the biggest turnoffs for customers. The vast majority of customers – 95 percent to be exact – feel like five minutes is the longest you should ever have to wait to speak with someone. Unfortunately, the majority of businesses force customers to wait much longer than this. Enabling SMS not only relieves call center congestion, but it also gives customers the option to ask for a callback, as opposed to waiting on the line.

  1. Self-Service Options

As you know, many of the calls your customer service department fields are simple. However, they still tie up your time, energy, and resources. What if you could automate these simple, yet time-consuming calls and free up your resources for the bigger picture issues? Well, you can.  Ultimately these self-service options benefit businesses in multiple ways. To quote our article, “consumers will often take the path of least resistance, so offering a text in service will save them having to call in, while avoiding having complaints aired in public on social media.” In the end, this leads to more satisfied customers, better brand image, and fewer wasted call center resources.

  1. Superior Service

The bottom line is that phone lines simply don’t cut it anymore. The modern consumer expects businesses to offer multiple channels of engagement and doesn’t want to be forced into placing a phone call. SMS is seen as much more convenient and service-oriented.  This is why text-enabled concierge services like GoButler have seen tremendous success. Customers feel like they’re getting more value from a company or service provider when the company is willing to communicate in comfortable and convenient ways.

Consider a cable and internet provider. Instead of needing to place a phone call and wait on hold for 10, 20, or 30 minutes, a customer could send a simple text message to the company that reads, “Hey, my internet is down. Can you help?” The provider can then respond with some simple questions about the situation and set up an appointment time without further disrupting the customer’s day.

  1. Customers Answer Texts

From the enterprise side of things, it’s sometimes necessary to contact customers. Well, the problem with contacting customers is that they’re often hard to get in touch with. Many users won’t answer numbers they don’t recognize and others rarely check their voicemails after missing a call.   SMS is an entirely different story. The Pew Research Center says 67 percent of cell phone users check their phone for messages even when they don’t notice it vibrating or ringing. Roughly 44 percent sleep with their phones next to their beds in case they receive a message or notification while sleeping.

Both of these statistics prove that customers are highly connected to mobile messaging. This rapid response makes SMS the quickest way to connect with customers, especially when the issue at hand is timely in nature.

Give TEXT a chance now!

The benefits of enabling TEXT in your call center will increase customer satisfaction, enhance the service experience and significantly increase productivity in your call center while reducing over all costs!   If you would like to experiment with TEXT in your call center, send the keyword DEMO to 424-348-4000 and we can get you setup in short order.   You might also check out www.Click2WebChat.com for some additional thinking on this subject.

The Achilles Heel of all Cloud Based Call Centers!

The Cloud Call Center Problem Statement!

A very common call center requirement is the ability to route a call based on the DNIS number dialed.  This is simple enough when you have only a few DNIS numbers to manage, but consider this application:   Consider a central call center that provides centralized appointment scheduling for some 600+ medical offices.    The call center agents are required to answer an inbound call with a custom answer greeting that is based on the medical office that cares for that patient.   The solution in place today requires the cloud platform to have a unique DNIS for each of 600 medical offices.  When a medical office wants to take advantage of services offered by the call center, they call forward their phone to the unique DNIS number on the call center platform assigned to their medical office.   On an incoming ring,  the call center grabs the DNIS and uses that number to index a connected database to retrieve the  name of the medical office and then display it to the agents on call presentation so they can provide the custom answer prompt.

As you might imagine, maintaining and updating both the relative campaign and a database of DNIS numbers is not only a nuisance with many opportunities for an error, it is also not very scalable.  The simplest solution is the ability to normalize or change SIP Headers or obtain the RDNIS in a PRI connection.   Neither of these is an option in any of the many cloud based solutions we have worked with.

The CPE solution!

In a CPE based solution we can touch the boarder controller of the incoming SIP trunk and see the various headers.   In a PRI trunk you could also see not only the CID/ANI  but the DNIS and the RDNIS.   RDNIS is commonly used in a voice mail system for example, to know the correct mailbox to open so the caller does not hear a main greeting but a custom greeting for the mailbox owner.   In either the SIP or PRI environment, we would NOT need 600 DNIS numbers to solve this application.   We could see the RDNIS or the FROM SIP header and use that field to look up the correct answer prompt or medical office name in the database.  We did a complete tutorial on this SIP header manipulation to achieve this same solution though the application was a bit different.

One for all and all for one?

Another major shortfall with cloud based call centers is that you will find it very hard to make modifications that are unique to your call center.  Keep in mind that all the cloud based call centers, with the possible exception of AWS Connect, are solutions that encompass many different clients.   The cloud provider can not make a modification for your call center unless it is applicable to all their other clients.  Likewise, when they upgrade or add a new feature, you are getting the new feature and the upgrade regardless of your desire to participate!

Summary

The Cloud is an amazing resource but it is not a one size fits all.  You will need to understand your requirements and how they match to what is generally available from your provider.  You should also understand that you will be increasing your WAN connectivity requirements to include advanced options like Software Defined Networks and MPLS, BGP along with bandwidth increases and new firewall challenges that you would not have on a CPE deployment.   You will still have phone and video end points, power over ethernet switches, network access credentials, intrusion protection and all of the IT resources you would still have with the Call Center located on site.  There are many advantages to the cloud, but make sure you know what you are hitching enterprise with!