Creating a “Personal Workgroup” to help answer your phone!

One of the great attributes of a Personal Call Manager, is the multiple call appearance functionality.   When you have an active phone call  you  can actually see a new call ring in, on your screen.  I like to think of this as “priority call management”.  Given that I know the value of the call I am on, when I see the Caller ID of the new call, I can make a real time decision about putting my current call on hold to take the new call.   Sometimes, however, this is just not possible without offending someone!  What I really want to do, is let the person ringing in, know that I am aware they are there and I will be right with them as soon as I finish the call I am on.  What combination of ShoreTel features will let me do that?

I created a new Personal Workgroup and put myself in the Workgroup as the only “agent”.   I also used the administrative interface to declare myself “always logged in”.  In this way I do not need an Agent Call Manager, nor do I have  to “log in” and Log out” of the Workgroup and I save the cost of a Workgroup Agent License!   I then recorded a Workgroup Queue Message: “Hi! I see you ringing into my desktop and I just wanted you to know I will be with you in just a minute as I am wrapping up this current call”.     To fully appreciate how this works, you have to understand one of the underlying principles of a ShoreTel Workgroup!   If you are a member of Workgroup, that Workgroup will only present one call at a time.   If you are on a Workgroup call, the Workgroup will queue the caller until an Agent becomes available.

Now when I am on the phone and I see a new phone call ring in that I really want  but can not just put my current call on hold,  I can still answer the new call!   First, as the new call rings in, I right click the new call appearance with my mouse and, while still stalking to the original caller, I  Transfer the call to the extension number of my Personal WorkGroup.  The ShoreTel Workgroup, sees that I am already on the phone and queues the caller.   The caller then hears my Queue message “ please wait and I will be right with you”, followed by music on hold.  When I wrap up my current call, the ShoreTel Workgroup sees me available and takes the caller off hold and routes them directly to my extension.  This is very effective tool for managing a busy desktop and it is also easy to implement!

ShoreTel Version 10+ “Find Me/ Follow Me” Enhancements!

Mobility and Office Extensibility continue to be “must have” feature sets for success in todays hyper competitve market place.   Nobody seems to care if it is after business hours in your time zone.  When a client wants you, they want you now and if you can’t be found, they will find someone else!  ShoreTel has had a range of features to address this requirement since the early on releases.  Features like “Office Anywhere” and “External Assignment” have been the minimum daily adult requirement for ShoreTel mobility from the very early releases and they continue today and they continue with Version 10.   ShoreTel has refined the “find me” functionality in this latest release to include a number of new capabilities including “call screening” and the ability to route a call before the caller hears your Voice Mail greeting!
There is an ever increasing group of knowedge workers and professional staff that spend very little time sitting at a specific desk location.    Sales and IT professionals, for example,  are always on the move and away from their desk.   With ShoreTel 10 we can now route the caller to your “find me” locations before the caller hears a greeting.  Depending on your selected call handling mode, you can route an incoming call directly to your cell phone, with full call screening.  This is not a simple call fowarding feature, it is an intelligent process of routing calls and enabling the recipent to determine the priority of the call and then accept or reject the caller.  If the caller is rejected, they then hear your Voice Mail greeting.  (Make sure you don’t invite them to press 1 to activate “find me” as they have already gone down that path)!
Generally, you would set up your “find me follow me” locations as part of your basic Call Manager setup.    You then associate that process with one of your calling handling modes.  I for one, do not want people hitting “find me” when I am in the office and in my Standard call handlign mode.  When I am out of the office, I might want to offer the caller this option, so I associte this process with that call handling mode.   What about the professional who is never at their desk?  Version 10 has a key new option in the “find me” setup: “enable Find me for incoming calls before playing my greeting”.   Additonally you can elect to send the caller CID and even “Enable Callers Name for find me”.
This last option cause the system to prompt ” the person you are calling requests your name”.   The system records what the caller mutters and then follows the “find me” instructions to locate you at one or two locations.   When your cell phone rings you will hear “this is the ShoreTel Voice Messaging system with a call from”, at which time we will insert the recorded mutterings of the caller for your edification.   Press 1 to accept, 2 to reject or 3 to repeat the caller ID.  If you did not elect this option which many might consider obnoxious and rude, the system will speak the numeric caller ID phoen number unless it is another ShoreTel user from within your system.  In this last case, you would hear the ShoreTel play the record name of that users mailbox.
This is only one of the mobility solutions that ShoreTel offers.   Other features including Mobile Call Manager and External Assignment also prove to be powerful options to keep you intouch and availalbe, regardless of your geographic location.    The following film clip walks you through the process of setting up “find me follow me”.   Enjoy!
Mobility and Office Extensibility continue to be “must have” feature sets for success in todays hyper competitve market place.   Nobody seems to care if it is after business hours in your time zone.  When a client wants you, they want you now and if you can’t be found, they will find someone else!  ShoreTel has had a range of features to address this requirement since the early on releases.  Features like “Office Anywhere” and “External Assignment” have been the minimum daily adult requirement for ShoreTel mobility from the very early releases and they continue today and they continue with Version 10.   ShoreTel has refined the “find me” functionality in this latest release to include a number of new capabilities including “call screening” and the ability to route a call before the caller hears your Voice Mail greeting!
There is an ever increasing group of knowedge workers and professional staff that spend very little time sitting at a specific desk location.    Sales and IT professionals, for example,  are always on the move and away from their desk.   With ShoreTel 10 we can now route the caller to your “find me” locations before the caller hears a greeting.  Depending on your selected call handling mode, you can route an incoming call directly to your cell phone, with full call screening.  This is not a simple call fowarding feature, it is an intelligent process of routing calls and enabling the recipent to determine the priority of the call and then accept or reject the caller.  If the caller is rejected, they then hear your Voice Mail greeting.  (Make sure you don’t invite them to press 1 to activate “find me” as they have already gone down that path)!
Generally, you would set up your “find me follow me” locations as part of your basic Call Manager setup.    You then associate that process with one of your calling handling modes.  I for one, do not want people hitting “find me” when I am in the office and in my Standard call handlign mode.  When I am out of the office, I might want to offer the caller this option, so I associte this process with that call handling mode.   What about the professional who is never at their desk?  Version 10 has a key new option in the “find me” setup: “enable Find me for incoming calls before playing my greeting”.   Additonally you can elect to send the caller CID and even “Enable Callers Name for find me”.
This last option cause the system to prompt ” the person you are calling requests your name”.   The system records what the caller mutters and then follows the “find me” instructions to locate you at one or two locations.   When your cell phone rings you will hear “this is the ShoreTel Voice Messaging system with a call from”, at which time we will insert the recorded mutterings of the caller for your edification.   Press 1 to accept, 2 to reject or 3 to repeat the caller ID.  If you did not elect this option which many might consider obnoxious and rude, the system will speak the numeric caller ID phoen number unless it is another ShoreTel user from within your system.  In this last case, you would hear the ShoreTel play the record name of that users mailbox.
This is only one of the mobility solutions that ShoreTel offers.   Other features including Mobile Call Manager and External Assignment also prove to be powerful options to keep you intouch and availalbe, regardless of your geographic location.    The following film clip walks you through the process of setting up “find me follow me”.  It is part of a four part series on setting up Call Handling Modes.    Enjoy and email your comments and questions to DrVoIP!

ShoreTel Compatible Audio Conference Bridge on a Plug Server?

The Sheevaplug computer is an amazing appliance!  Think of the applications you could create on this 3 watt PC often confused as a wall transformer  by the uninitiated.   In fact I have a bunch of “wall warts” under foot  for a variety of electronic devices on my desk that need stepped down AC power and the Sheevaplug server is smaller than any of them!    A  Plug Computer is designed to draw so little power that it can be left on all the time.  Unlike other embedded devices, it contains a gigahertz- class processor designed to offer PC- class performance, Ethernet interface, USB port and a SD Flash Card.  OMG! Geek Heaven!

As a technical support organization,  we needed a network monitoring tool to help us diagnose WAN QOS issues for our ShoreTel and CISCO VoIP clients.  How do you get an appliance on a clients network that can connect to the mother ship, capture network performance statistics and be left on all the time with no large power consumption?  We also needed something that was “plug and play” and dirt cheap as we give them to our ShoreTel multi-site clients who are under contract as part of our normal support service!   With this little plug computer  we can put a full network monitoring appliance on the network and try to stay ahead of the QOS issues that result from bandwidth, latency and jitter fluctuations.

With the network monitoring solution solved,  we started looking for other useful VoIP applications we might stuff into this plug computer.     Sometime back we created a fully featured audio conference server in software.  The goal was to make it possible for clients to create multi  party fully managed, audio conferences without having to spend tens of thousands of dollars.   Thanks to SIP we were able to do just that and the results were exceptional.  (Click here for full specifications  http://www.siplistic.com/tutorials/setup-users-and-standing-conferences .   The marketing challenge was  the fact that the server hardware and OS cost more than the application software!

So that became the next project to take over in our wonderful world of VoIP!   We have now achieved what would have been unthinkable only a year ago!  We can now provide the same audio conference solution including the hardware at the same price we charged for the application software!  Thanks to the wonderful engineers at Marvel  we have been able to realize a fully feature, SIP based audio conference server on an appliance that draws less than 3 watts of power!  How green can you get?  Now the problem is how to keep people from stepping on it!

marvell_sheevaplug_computer2

I know it is crazy to get excited about a hunk of hardware, but next to my iPad this is a must have and I have a long list of applications that would make the world of VoIP more exciting!  How about a turn key telephone system for a remote office that cost less than an SG30 and interfaces to ShoreTel and CISCO as a SIP tie line?  Let me know your thoughts!

NOTE – March 2012-  We have had so much demand for this product that we now offer it as a SKU through our product company, http://www.Siplistic.com !  We can ship you a turn-key Audio Conference Appliance for $1995 including the Server Hardware.  Answer a few configuration questions, and you will have a 24-94 port appliance with web interface administration as fast as Fedex!  Price includes remote configuration and installation on ShoreTel, CISCO, Microsoft or Asterisk!  – DrVoIP!

Log Blog – Debugging ShoreTel Voice Mail with vmail.log

We should probably do several blogs on logs!   Logs to an engineer are like finger prints to a cop!   Both professionals need to play “detective” and gather all the hints they can in an exhaustive effort to figure out what went wrong!   Logs always have interesting information, written cryptic ally but useful none the less.  Recently we had to solve the case of the “missing message notification” and that sent us deep into Vmlogs.   The problem statement was that a message left in a voice mailbox was suppose to notify a cell phone when the message was marked urgent.  The client reported that this was not happening .  So how do you go about debugging this issue?

 ShoreTel gathers log information and stores them in a specific data folder.  The logs folder is contained in the X:\Shoreline Data folder on both your ShoreTel HQ server and your Distributed Voice Mail Servers.  This folder is a critical component in any disaster recovery plan as it contains all the information you need to recreate your system.  For example, you system automated attendant prompts are located here, so make sure you back this folder up along with the configuration database.   The Log folder contains a number of logs that can be used to trouble shoot ShoreTel system issues and you should become familiar with them.  For purposes of this blog, we are going to focus on the vmail logs.  These logs are created for a 24 hour period and are time date stamped accordingly.  You will find this folder and its parent folders, exist on each ShoreTel server.

 Poking around in the Shoreline Data folder is instructive.   These is a sub folder named VMS.  This folder contains several other folders that effectively define the Voice Mail structure of the system, or at least of the Voice Mail boxes that live on that server.  In the folder marked ShoreTel, you will find a folder for each voice mailbox on that server, named for the extension number.  Inside that folder will be the data pointer and the wav files for the mailbox name and the various call handling mode greetings.   The actual voice mail messages, however, are contained in one massive folder named Messages, also in the VMS folder.   The Message folder contains all of the voice mail messages saved as wav files with cryptic file names.   Moving through the vmail logs, not only can you associate the messages with a specific mailbox,  you can generally get the password to that mailbox as it is saved in clear text.

The vmail log is verbose and very English like in is format.   It does not take much time to get comfortable with the interpretation of this log.   Generally, when reviewing any log, you have some basic information about what you are looking for.  Often you will have a GUID or an extension number that when coupled with time can help you search the log for a specific call.   In this log we can see the incoming call answered by the voice mailbox and the caller Id captured for call back and email notification.   We can see the various key strokes that the caller entered and we can also capture the name of the WAV file that ShoreTel will write out to the Message folder.

 If any of the out dial features are activated, you can see the perform in the mail log, including  the number dialed and any digits captured by the system when the caller answers.   Generally, all of the activities associated with this phone call are recorded to this log.  Working between the log and the VMS Folder you can locate messages for a particular user.  In this example we were able to trace the incoming caller ID through to a mailbox, watch the caller interact with the mailbox by generating DTMF digits and then mark the message urgent.  The logs continue to demonstrate that the system then set up an external call to a remote phone, played the ShoreTel voice mail notification greeting, collected the acceptance of the voice mail and the user password.  The system then marks the message heard and moves it to the delete message queue.  

 All in a days work for a log file!  If you have to debug ShoreTel, Logs are your new best friend!  

ShoreTel ECC – the powerful “change call profile” scripting tool!

Call Profiles can be of two varieties in the ShoreTel Enterprise Contact Center. They are either System Mandatory or User definable. ( Actually, to be absolutely correct, we need to acknowledge that “Skill Sets” are another type of call profile, but we are including them as User definable). The system assigns a number of Call Profile parameters automatically as the call moves through the system. These profiles are variables that change with each phone call. Examples of system call profiles would be Priority, DNIS, Call Type, Agent Extension and Average Queue Time. User Definable Call Profiles are parameters that you define to enable values required to implement your specific application. If your application, for example, plays a prompt to the caller that asks the caller to enter their account number, this information needs to be saved for follow on processing. As the caller enters their account number, the digits are saved to a User defined call profile that might be named “account code”. This profile variable can be interrogated , tested and used to further define call routing.

Lets assume that the account code that is entered by the caller is used to determine if that caller requires Platinum, Gold or Silver routing. You might assign Platinum callers a higher initial “priority”, a System mandatory Call Profile, than you might assign a Silver client. Given that an Agent is eligible to receive one of many calls awaiting service you might want to set the call select strategy at to be “by priority” rather than by “longest wait” or “best skill fit”. With this option you would manipulate the Priority Call Profile to set the Platinum caller with a higher value. You might also want to change the service that that call is routed to based on the account code. The question becomes, however, how do you manipulate the Call Profile? What tools area available to do this manipulation and what other tools might work in harmony with this capability?

In the ECC Scripting tool there is a remarkable scripting Icon named “Change Call Profile”. This icon can easily become the most powerful tool in your implementation scripting arsenal! When used in conjunction with a other icons like the “logic menu” or SQL dip kit, you can solve some really amazing application requirements. The video for this blog, uses a SQL data dip to look up and account code, entered by the caller, to determine how to route the call. Once this decision is made, the Change Profile icon is used to steer the call to the appropriate service, and send along other application specific call profile parameters. We use the Account Code to index a SQL database and return the “status” (e.g. Platinum or not) and the “route” we want the call to follow. The Route information is used to index a Logic map to find a specific Agent or Group that is assigned to handle that particular client account. The video also illustrates the use of the “branch to  script” icon to further manipulate the call parameters. I often use the ” Change Call Profile” icon to flip the automated attendant scripts from on hours to off hours when implementing that function within the ShoreTel ECC. Individually, these capable scripting icons are very powerful call handling manipulators. Taken as a suite of scripting tools I have not yet found an application that we could not implement in the ShoreTel ECC!

ShoreTel Database Replication and Manipulation of MAXDBQUERIES!

It really doesn’t matter what VoIP system you installed they all generally have one architectural characteristic in common; the configuration database.  Depending on the system, you might find a database engine that ranges in complexity from an Access Database to a full blown SQL database.  The database will store configuration information, status information and often, call detail records that document phone system activities.   The characteristic of the database that is consistent across all architectures is the fact that there can only be one “read/write” copy of that database!

Some phone systems distribute the database across multiple servers.  ShoreTel, for example, distributes components of the database to application servers and distributed voice mail servers that characterize the single image architecture in a multi-site environment.   We need to better how a change to the database effects the operation of the system, the bandwidth of the WAN links and the demand on the database engine.  First, what constitutes a change to the database?   Well clearly any configuration change that is made to the system.  For example, adding or deleting a User are clearly going to cause a database update!  Lets take a more subtle example, however. Lets consider what happens to a Agent in a Workgroup, located at a remote site, behind a distributed voice mail server.  Each change that Agent makes on their Call Manager represents a database change.   Logging into the system, and Logging out of the system are database changes.  How about, accepting a call being offered to the Agent by a Workgroup?

Each of these Changes is communicated to the database.  The change is first made on the “read/write” database and then replicated to the remote database copy.   ShoreTel system processes use MS Distributed Component Object Model (DCOM) objects to share information from the configuration database among themselves and to write configuration  information to the database.  User configuration options are written to the database from Personal Call Manager, and the telephone interface.  Each ShoreTel service on a distributed server caches it own copy of the configuration database.  When a distributed server loses connection to the HQ server (read “read/write” database) any changes made are no longer received by the distributed server.   If a DVM restarts without a connection the HQ database, services are started but are not functional.  When the network connection is restored, the configuration is retrieved and again cached by each service as the services become functional.

If there is a flap in the WAN we note that the DVM will in fact reload a copy of the database.  This movement of the database between the HQ server and the DVM servers clearly uses bandwidth and also makes additional demands on the database engine.   In ShoreTel the database engine, is now MySQL.   The question becomes how many simultaneous database access (read, modify, write) transactions can the MySQL server handle at one time?  What happens if the transaction can not be completed?  Does it queue and retry?   In a large system of say 700 workgroup agents at a site, is it possible to overload the MySQL database with state change requests?   If you dig down through the Server registry you will find the MAXDBQUERIES is set by default to 100.  It has been our experience that, defending on the size of the system, it is sometimes necessary to dial this number back to eliminate overloading the database.   This adjustment should be made only on the DVM’s in the configuration and not on the HQ server.   You will need to reboot your DVM servers after making this change.  You should also note the difference between HEX and Decimal!

The following SILENT file clip demonstrates how to make this adjustment.

ShoreTel Enhanced Workgroup Services!

Historically, there were three services in the ShoreTel architecture that were no distributed to other servers.   To oversimplify, this meant that if the HQ server (read primary server) was unavailable, the services that were not distributed would not function.  The three services were Route Points, Account Codes, and Workgroups.   For example, if a user group was set to “forced” account code verification and the server was unavailable, that service would fail and the affected user would not be able to place a call.   Likewise, if the HQ server were unavailable, Workgroup services would fail.  ( The “best practice’ deployment strategy was to backup a Workgroup with a “hunt group” given that the HG ran on a switch and not a server, it would continue to function in this scenario.  Calls targeting agents in a Workgroup would fail over to a hunt group that would target the same list of agents).

ShoreTel has steadily progressed the distribution of these services out from the HQ server to either SG switches or  Distributed servers.  With the latest release of ShoreTel,  they have migrated critical services to include Workgroup services.   This is a major enhancement and any organization that makes use of the Workgroup functionality, especially in a multi-site environment,  will realize a  benefit by these enhancements.

Through the ShoreTel administration portal, we now find a drop down window that enables us to select which server should be utilized to run the Workgroup we are defining.   For example, in a multi-site environment, I might want to have the Workgroups organized by Site and run the workgroup service on the DVM at that site.   This would keep the Workgroup local and a failure of the HQ server would not dramatically affect the workgroup at the remote site.   We note that, in the absence of the HQ server, we are still unable to make database changes.  For example, Logging In/Out of a Workgroup would not be possible, but the remote Workgroup would still function.

Additionally, we note that you can continue to name a Hunt Group as a backup extension.   The key difference here is that the Hunt Group can contain extensions that are Workgroups on other servers!   This offers a degree of flexibility not previously available and is a viable alternative to a straight Hunt Group solution.   A failure of the HQ server will only effect the Workgroups that are on that server and distributed Workgroups on other servers will continue to run.  A failure of a DVM with an operating Workgroup can fail to a Hunt Group that can be used to route calls to other Workgroups.

The vocabulary might be a bit confusing, but the strategy represents a significant step forward in assuring the operation of a distributed call processing application as powerful as ShoreTel Workgroups!

WorkgroupScreen

ShoreTel CDR Format- How to find the International Calls!

Recently, while working with a third party Call Accounting vendor, we had an opportunity to revisit ShoreTel CDR records.  ShoreTel stores CDR records in two locations for two different purposes.  Historically, the first format is basically the “Legacy CDR Text Files” and they are stored in the Shoreline Data folder as log files.  The log files are written to \Shoreline Data\Call Records 2 and are written out at Midnight to a file named CDR-YYMMDD.HHMMSS.log.   This is the file that is generally accessed by third party Call Accounting software vendors.

The second format is written to a MySQL database which is used to generate call accounting reports directly from the ShoreTel server.  In version 7 ShoreTel began to migrate away from Microsoft Access to MySQL for both the CDR and the configuration database.   There is a procedure for converting the older files into the new MySQL format, but we are not going to cover that as most people have already made this transition.      The MySQL database also opens the opportunity to create custom reports using SQL queries.  Through the ShorewareDirector portal, under Reporting options, you can set the Retention Period for CDR Data as well as the Archive retention period.

CDR Options in ShorewareDirector Portal

If your third party Call Accounting software uses the 011 to detect an international CDR record, you will need to make some adjustments.  ShoreTel uses a Canonical format to collect digits.  This means that no matter what the user actually dials on the phones keypad, the system internally converts the numbers to +country-code area-code subscriber –number.   The fact that you dialed 9+011+52+3654587 will be stored in the ShoreTel CDR log file as 9+523654587 and the 011 reference will not be in the record.  The following silent film clip walks you through the format and content of the CDR.log files.

Configure ShoreTel for Redundancy, Resiliency or Business Continuity?

Of late we have seen a growing interest in building “disaster recovery” solutions for both the data and the voice applications so critical for business operation.  First, we need to make sure we understand the difference between redundancy, resiliency and other configuration options to assure business continuity.  Many more installations now include the use of a remote “collocation” facility as an key  component of the installation plan.  What is the best way to configure a ShoreTel HQ server, for example to provide for continued operation under a wide variety of options.

The subject of redundancy is almost amusing at times.  How much redundancy is reasonable and appropriate?  You can have all the redundancy your budget can fund, but at the end of the day are you able to continue the business operation in the event of a catastrophic event.    Clearly, two power supplies are better than one.  If they are both plugged into the same commercial power outlet, however, it really will not matter how many power supplies you have if you lose commercial power!  Again, we need to focus on what are we trying to protect?

Redundant servers?   Some HQ servers have been configured with “double take” enabling a hot standby server to take over in the event of a primary server failure.    Candidly, we do not see the benefit of hot standby server swaps in the ShoreTel architecture and it is a nightmare to administer, backup and restore.  The cost of the solution outweighs the benefits and there are other configurations that are more cost effective and work just as well.

For example, there is no law that says you can not install a ShoreTel Distributed Voice Mail server at the same level as the ShoreTel HQ server.   Actually, this works just fine!   Install the servers at the same physical location, or put the HQ server in the remote “collocation” facility.  If they are installed at the same “logical” level (i.e. appear on the same level in the Shoreware Director, either server can handle the load.   Generally, you would put all of the users and switches for that site under the DVM and use the HQ as your “fail up” and proxy solution.   Nothing wrong with this configuration, it is cost-effective and easy to administer.  From time to time you might hear ShoreTel say “ please wait while I connect you to the correct server” but even that can be managed.

ShoreTel HQ has three services that are not distributed: Route Points; Account Codes and Workgroups.  If you lose the HQ server, you will lose these services, but generally, that is a small price to pay for this level of resiliency!   ShoreTel Version 10 promises to distribute these services, so there is no reason not to configure this way and achieve full survivability given the building is still standing.

You don’t have to think very long about a Katrina or Haiti, especially if you live in California!  It is only prudent to not only plan for some level of “redundancy”, but also to plan for how the business would operation if we could not get into our building!  If we put the HQ server at the “collocation” facility and we provide for Trunk Lines and “dial tone”, we can balance this possibility.   The issue is, that if the building housing the people becomes unavailable, users can still log in and route their phones to cell phones or make use of RDP to access their Call Managers.

The “collocation” option often requires a trade-off between bandwidth and trunk lines.   You can put all your trunk lines at the colo, in which case every call made from the sites, will traverse a WAN.  So moving the trunk lines to the colo increases resiliency but also drives up your WAN cost.  At the end of the day, it is most likely some combination of bandwidth and trunk lines spread between the facilities.  In either case, you will work with your carrier to enable lines to be repointed in the event of an outage.  This is a bit more challenging if you are in New York and your collocation facility is in Phoenix, but it can be done.

We are experimenting with the use of SIP trunk facilities at the Collocation site.  Generally, this can be more cost effective especially if you can get an agreement for a burstable SIP pipe.  You may not want to pay for T1’s at the collocation if you are only planning to use them for a disaster situation!  SIP also enables you to be generally independent of your physical location.

It is a sign of the times that we spend so much time planning for “what if” scenarios, but being prepared is not only prudent but appropriate.   Have a comment on this blog?  Email:drvoip@drvoip.com

DisasterRecovery

Why move the Auto Attendant into the Contact Center?

Many Call Center applications have an Automated Attendant front end call tree.  Typically, you  might have an Automated Attendant that plays the familiar On-Hours recoding: “Thank you for calling our company, press 1 for technical support and 2 for sales support”.  The question asked in today’s blog is: should the Automated Attendant be located in the PBX or in the Call Center? There are very interesting ramifications for each of these options.

Generally, with out thinking this question through, the easy answer is to have the PBX do the front end Automated Attendant.  In the ShoreTel world, the On-Hours/Off-Hours scheduling of the changes to the call tree and messages played is so “brilliantly simple” that everyone will select this implementation strategy.   In our simple example above, selecting either option will direct the caller via a route-point/IRN marriage into the Contact Center to be processed by the appropriate Service, Group and Agent.

If you implement that Automated Attendant in the PBX, however simple it is, you potentially rob management of very urgent call detail information. Typically, the Off-Hours location is a general delivery mailbox in the PBX anyway, so why not just keep it all in the PBX?   If the Automated Attendant shuttles calls to the Off-Hour location, that call may never become known to the Contact Center and therefore would  not be captured in the Contact Center Historical Reports.   Call Center Management might be very interested in knowing how many calls came into the Center before or after On-Hours!  To obtain the information the Call Center, not the PBX needs to host the Automated Attendant!

What is the result of implementing the Automated Attendant in the Call Center?  If you look at the above Automated Attendant script, you can see immediately that we need to add the famous “If you know the extension number of the person you want to speak with, dial it at any time during this recording”.   Given that you have already concluded that this is an option you want to offer clients, something a Call Center manager might not recommend, how do you implement this feature using the ShoreTel Contact Center?

There are several ways to do this on the ShoreTel ECC, but all options require the creation of a “Call Profile” value.   We have put together a quick video tutorial on how to implement a multi-digit transfer in the ShoreTel Contact Center using the Graphical Scripting Tools.   Minimally, after you create the Call Profile value you will need to have a “Get Digits” and the “Transfer” Icon.    In our example, we have created a Call Profile value named “ExtensionNumber”.  This value anticipates a three digit integer and does not require a termination character.   The GetDigits Icon is normally associated with a WAV file that prompts the caller for digits.  Once the digits are collected the are deposited into the Call Profile place holder named “ExtensionNumber”.   This value is then past to the Transfer Icon and the value is dialed by this function.   Enjoy!