|
|
|
 |
|
|
|
|
|
|
 |
| |
Inbound/Outbound
Blending |
|
|
| |
Timed Blending |
| |
Typically, production
lags during inbound
projects while agents
await incoming calls.
Those agents are often
instructed to manually
call from outbound lists
during these slow
periods. This results in
few outbound calls being
placed at inopportune
times (to the prospect).
eTelescript can blend
inbound and outbound
calls using ‘timed
blending’, which
automatically switches
the agent from an
inbound project to an
outbound call if no
activity occurs within
preset intervals and
then back again. |
| |
Call Volume Blending |
| |
Depending on the phone
system being used,
eTelescript can also
base inbound/outbound
switching on call
volume. When inbound
call volume decreases,
eTelescript can switch
the agent from inbound
to outbound,
automatically dialling
the most appropriate
number at the designated
time. Similarly,
eTelescript can check
for increased inbound
call volume, and
automatically switch
back from outbound to
inbound - maximising
efficiencies and keeping
staffing levels to a
minimum |
| |
Database Integration |
| |
An inbound telemarketing
project can utilise any
corporate database.
eTelescript can both
read and write directly
from dBase, FoxPro,
Paradox, Access, SQL
Server, Oracle and any
ODBC compliant database.
This enables you to
directly integrate
eTelescript within your
corporate information
system without
conversions, exports and
imports. |
| |
All information gathered
in the agent’s script
can then be exported
directly to your
database or CRM, thus
avoiding costly
duplication and double
entry. Selected fields
from the database or CRM
can be imported to the
scripts making sure that
the agents have the most
up-to-date information
to hand at all times. |
| |
>> Scripting |
| |
|
|
|
|
|
|
 |
 |
|
|
|
|