| Revision History | ||
|---|---|---|
| Revision $Revision: 1.7 $ - covers QueueMetrics 1.6.1.0 | $Date: 2010/10/06 07:39:12 $ | L |
Table of Contents
Revision history:
You probably already know that by using TrixBox (TB) or AsteriskNOW 1.5.0 you can install a fully featured Asterisk-based PBX in a matter of minutes. This PBX is very good for most users as it is preconfigured to handle the most common scenarios one can find in a personal environment or in a small to medium sized office.
Still, the typical usage patterns of a small call center are quite different from the ones you are likely to find in a classical PBX, because:
In our opinion, running a successful call center is more a state of mind than a given set of telephone equipment. What makes a difference is not the number of extensions, queues or agents you have; is a mindset where you consider that the customers calling in are actually very important and you do your best to serve them well within given budget limits.
Maybe you just run a small computer-repair shop and have a couple of lines coming in. What is the cost of having people waiting or calling multiple times because they cannot talk to anybody within a reasonable time? What will your clients think about you? On the contrary, what will your clients think of your Customer Service Department if it always answers on the very first ring? And how do you know if your technicians actually answer the phone when the calls come in or wait five minutes because they are doing other things? These are the questions you should ask. If you follow the guidelines in this document, you’ll find an easy way to start answering questions like these.
Running a call-center, therefore, is not a matter of having multiple PRIs or special hardware. In most cases, you will not even need a separate box from your main PBX running TB. You will only need some software and a bit of configuration to set it up correctly.
Before we start building a small call center, we have to focus a bit on the terminology:
An agent can be working on one or more queues: whenever he is available, all calls coming in to any queue he’s working on will be routed to him.
In this tutorial, we will learn how to create both inbound queues and outgoing campaigns and the proper agent setup to handle them successfully.
To follow this guide, you will need an already-installed, reasonably modern TB or AsteriskNOW instance. It may be your home or office PBX. This tutorial was developed for TrixBox 2.8 and its derivatives, but applying it to different versions should be anyway trivial.
You can follow this guide completely while having your PBX running, so there is no need for a prolonged downtime. You will need at least a couple of telephones to test your setup, and a land line you can use.
You should be familiar with how to use TB as a basic PBX: creating extensions, connecting to external lines and so on.
The following tutorial was created using the following set of software:
or, for AsteriskNOW:
There may be minor differences caused by minor revisions of the software if you have a different version installed.
This tutorial is split into two separate parts; one for inbound and the other for outbound. They can be implemented separately, though system-wide changes are explained only for inbound, to avoid duplication.
For each queue/campaign, for both inbound and outbound, we will show how to:
In our scenario, we have a fictitious set of queues and agents that work on them. They are defined as:
| Queue code | Campaign name | Direction | Agents working on it | Extensions |
|---|---|---|---|---|
300 | Support EN | Inbound | 200 and 201 | 400 and 401 |
301 | Support ES | Inbound | 200 | 400 |
302 | Helpdesk | Inbound | 201 | 401 |
350 | Callback | Outbound | 200, 201 and 202 | 400, 401, 402 |
Each agent is defined by his/her agent code; as you can see, extension codes are now separate and linked to the physical extension being used. You can have agents logging on from different extensions and still being able to accurately track their activities.