Technology

Does anyone like writing down processes?

Contact centers are process driven environments, yet frequently, documenting processes is one of those jobs that has to be done, no-one wants to do it and everyone has an opinion about it when someone else does it. It’s also a job that needs to be done slowly and carefully, but is usually requested at the last minute. So what is the fastest way to document a process at a fairly high level while retaining enough information to make it useful?

One approach is called the SIPOC chart. This is an acronym that translates into “Supplier, Input, Process, Output, Customer.” The basic principle is to create a chart with each of these five headings.

Sample SIPOC

Sample SIPOC chart showing inbound call process

It’s best to start with the process itself, which can be expressed as a series of events in bullet points (a maximum of 10 for very high level overview). On the left hand side, we then complete the inputs column. This contains everything that the process requires to run. To the left of this column, we complete the suppliers column. This contains the names of the people and organizations that supply these inputs. On the right hand side of the process column, we fill in the outputs which the process produces. This should include not only the final product, but any documentation or data produced and also any by products. To the right of this, we have the customer column. here we fill in the names of the people and organizations that receive these products.

In one document, you will not only have a simplified account of the steps of the process itself, but you will have identified many of the drivers and products of the process and the people who affect and will be affected by the process.

This is a very high level approach. Engineers, analysts and computer programmers will need something that is a lot more detailed. In this case, the SIPOC chart would be a starting point to generate the questions and discussions needed to describe a process in more detail.

One mistake many people make in documenting processes is to mix what the boss would like to happen with what really happens. If you are planning to improve an existing process, it is essential that you document the process “as is”, talking to the people who are the closest to the process as it happens. Doing anything else is like treating a sick person in hospital without knowing what he is suffering from.

Any document is only as good as the information it contains, so consider your sources carefully, and you will write a more accurate and therefore more useful document.

Bookmark and Share

ZOOM & Sipera Partnership and Case Study

ZOOM and Sipera have teamed to create a flexible and secure call recording solution for a U.S. Children’s Hospital.

all-childrens-architecture

Reference Architecture Sipera - ZOOM

A specialty licensed Children’s Hospital based in Florida, with multiple outreach centers and facilities located throughout the state required a solution that would provide secure communications for both on campus and remote home users. This included call recording requirements for Operator Services, Internal Helpdesk and the Nurse Triage unit with the additional feature of using extension mobility to provide the same extension both on campus and as a secure remote home user.

Thanks to a partnership and close collaboration with Sipera Systems, ZOOM and Sipera together delivered a solution with the flexibility of “Borderless UC,” extending their Unified Communications applications to any location while maintaining the mission-critical compliance and security posture that is needed to protect these communications.

sipera-logoSipera Systems, the leader in real-time Unified Communications (UC) security, is the choice of enterprises and service providers around the world to support their mission critical UC deployments. Sipera offers groundbreaking, production proven solutions that secure voice, video, messaging, collaboration and real-time communications in converged IP networks, boosting compliance with information security requirements

Brian Shore – President, North America : “Recording encrypted calls has been an industry dilemma for some time. To eliminate this challenge, ZOOM is very proud to partner with Sipera to provide a tested reference architecture for secure and flexible call recording. Sipera’s depth of knowledge in the security arena matched with ZOOM’s IP telephony expertise is a powerful combination.”

Read the ZOOM – Sipera Case Study on this Childrens Hospital.

Bookmark and Share

ZOOM QM Suite 4.6 Released

Scaling up.

ZOOM QM Suite Scaling up.

Probably the heat has caused that we almost forgot to break the news that  ZOOM QM Suite version 4.6 has been released and is made available for download…

Enterprise, enterprise,enterprise, enterprise !!!

It is safe to say that this release is all about improved Enterprise Support. Supporting enterprises with their large or complex installations requires the best performance, scalability and high availability options and these are exactly those areas that have been addressed with this release.

Truly supporting  large contact centers and large  Genesys deployments  has raised the bar for ZOOM  to deliver a top-performing and enterprise class product suite and ZOOM is proud to say that with release 4.6 it has successfully delivered a true Enterprise Class product for both Genesys and Cisco environments.

This release brings you:

  • Major Database Performance Improvements
  • Improved Scalability options
  • Support for Genesys High Availability Architecture
  • JTAPI Enhancements supporting more and more complex network scenario’s

You could say that all key products from the ZOOM QM Suite have received a big  enterprise ‘power-boost’  to better support large, demanding and complex installations.

As ‘cherry on the pie’, this release also delivers new functionality and a more unified experience. Enjoy new ScoreCARD features to get your quality management program started faster, get more value for money and flexibility using ScreenREC, make your choice in OS platform and integrate ZOOM’s powerful media life-cycle management tools with IBM Tivoli. In more detail…

CallREC and ScoreCARD Unified
Enjoy an unified experience in installing and running CallREC and ScoreCARD. These two flagship products are one step closer to 100% integration.

ScoreCARD Questionaires export and import
ZOOM ScoreCARD now makes it a lot easier to get your Quality Management Program started with it’s Questionnaire Export and Import functionality.

Optimize your ScreenREC usage
ZOOM ScreenREC has undergone significant changes to support the capturing of more screens in higher resolution and allowing for flexible recording rules.

Red Hat Support
Enjoy the freedom of choice in operating system. Next to CenOS you can now choose for Red Hat Enterprise Linux to runs ZOOM products.

IBM Tivoli Support
Use provided scripts to integrate ZOOM Media Lifecycle Management with IBM Tivoli Storage Manager (TSM) to seamlessly backup, archive and restore using TSM.

Read more details in the ZOOM QM Suite 4.6 Release Bulletin. The distribution of this release plus documentation is available for download via the ZOOM Partner Portal.

We’ll have a glass of champagne and then we’ll start work on the 4.7 release. Stay tuned for more product unification and a long list of new CallREC, ScreenREC and ScoreCARD features.

Bookmark and Share

ZOOM CallREC release 4.4.1 – What's new there

It has been a few days since we released the next version of our flagship product – ZOOM CallREC, version 4.4.1.paper plane
It’s a minor release; however there are some important new features and improvements.

Let me briefly describe what has been achieved and how it helps to improve usability, and make CallREC a more robust product.

Multi-Server Setup
Multi-Server deployment was already supported by CallREC; however we have improved the setup process itself. Version 4.4.0 already introduced a new installer, but it didn’t specifically support multi-server deployments and you had to do a lot of changes manually. Now during installation you can easily choose what the server role will be, where the other servers are and prepare almost all the required configuration steps. The only step missing now is NFS file sharing; this must still be done manually.

Full Implementation of IPP Libraries
This one is really technical, so what does it mean for “ordinary people”? IPP stands for “Integrated Performance Primitives” and is an Intel software product. Intel defines it as “an extensive library of multicore-ready, highly optimized software functions for digital media and data-processing applications”. Wow!
Basically, Intel provides optimized software libraries for media processing, which we’ve decided to use instead of our existing media processing tools (these libraries were already present in the recently released 4.3 version).
We have replaced the decoding libraries that handle all the G.whatever codecs (G.711, G.722 and G.729). This first step brought us a significant performance boost and  now we have made another step—we have replaced the encoding part (the libraries that are responsible for mp3 encoding). We were previously using open source libraries that had occasional issues, which had already caused us long-term pain. Now with IPP we have a much more stable and reliable media encoding part.
The side effect is that we can no longer support the Speex codec for recorded calls. Speex was officially discontinued in version 4.3 (although it was still available) and has now finally been removed. We believe this will not be an issue, since only a few CallREC users ever tried to use it and no one has been using Speex in a production environment.

Genesys Integration Module Improvements
The Genesys Integration Module went through a substantial redesign last year. The vast majority of changes were implemented in the latest 4.3.2 release. Now all of them (and a couple of new ones) have been ported to the 4.4.1 release as well.
Among the changes, such as improved reliability and efficiency in attaching the related call data, there is a really interesting feature—you can choose what external data will be attached and saved in the database (regardless of T-Server properties, attached data or configuration information). Some customers use tens of different attached data, so in some cases we were saving 70-80 different key-value pairs for every call, even if they used just a few.
The database performance impact is obvious. Now we can precisely set up what information will be stored and what will not.

Improved GUI Search Performance for Large Databases
The database and its associated parts are now one of the most closely monitored components and is the focus of a lot of development work. Changes in database structure and related components are planned for the next major releases, but we wanted to improve performance sooner—and on top of the current structure.
Fortunately we were able to implement some tweaks that have a big impact, boosting the database and GUI search performance significantly for external data. The tradeoff is that you need to stick to the recommendations and there are a few small limitations, but it flies!

Bug Fixes
No software is perfect and CallREC is no exception. There are several bug fixes in the Multimedia Management Tools (MLM), the Migration Tool (a Swiss army knife for upgrading data from one version to another) and in the setup scripts.
Last (but not least), CallREC version 4.4.1 includes Apache Tomcat application server version 6, which itself solves some issues encountered when running GWT based applications—such as ZOOM ScoreCARD.
There’s still a lot of work to do to make CallREC the “best solution in the world”. It’s a challenge for us and we’re working hard to deliver the best we can. Stay tuned—there are loads of exciting new features to come. And of course, we’ll be only too happy to share them with you…

Bookmark and Share