Micontact Center Business
Micontact Center Business
Release 9.5
Document Version 1.0
May 2023
Notices
Trademarks
The trademarks, service marks, logos and graphics (collectively “Trademarks”)
appearing on Mitel's Internet sites or in its publications are registered and
unregistered trademarks of Mitel Networks Corporation (MNC) or its subsidiaries
(collectively "Mitel") or others. Use of the Trademarks is prohibited without the
express consent from Mitel. Please contact our legal department at [email protected]
for additional information. For a list of the worldwide Mitel Networks Corporation
registered trademarks, please refer to the website:http://www.mitel.com/trademarks.
Mitel Multimedia Contact Center enables contact centers to handle email, chat, SMS, and open media
interactions from customers. Agents handle voice, email, chat, SMS, and open media interactions
using Ignite.
center activity and interactively manage interactions. Supervisors can monitor and interact with
contacts and employees using Contact Center Client, Interactive Contact Center, and Interactive
Visual Queue.
Multimedia interactions are routed using workflows, created using a visual, intuitive interface. Also
included in Multimedia Contact Center is a Contact Us page that can be used by contact center
website administrators to add live wait time statistics to their corporate website page, enabling
customers to select their preferred communication method based on media type availability.
Multimedia reports and charts provide valuable information by summarizing agent, employee, queue,
and contact center performance.
To know more about how to manage a multimedia Contact Center, see Multimedia Contact Center
Installation and Deployment Guide.
Voice-enabled contact centers will benefit from referring also to the MiContact Center Business
User Guide and the MiContact Center Business Installation and Administration Guide.
• MiContact Center Business User Guide: provides information on the basics of contact
center management, and descriptions for use of all agent and supervisor desktop
applications within the MiContact Center Business suite. This guide focuses on voice
media.
• MiContact Center Business Installation and Administration Guide : provides instructions
for:
Mitel MiContact Center Business integrates with MiVoice Business platform to provide contact centers
with the tools they need to efficiently and effectively measure and manage contact center operations.
Interactions are routed intelligently across all media types (voice, email, chat, SMS, and open media),
increasing customer satisfaction and streamlining agent calls. Contact center efficiency and agent
performance can be monitored both historically and in real time and can be measured using a wide
variety of reports. Flexible licensing packages provide access to specific features and applications and
enable you to build a contact center package that best suits your business needs.
Contact Center is the licensing level of choice for businesses with more than 100 concurrent
agents, who want resiliency, and require, requiring a maximum of 10 IVR endpoints more than 10
IVR ports.
Workgroup is geared toward contact centers with fewer than 100 concurrent agents, requiring a
maximum of 10 IVR endpointsports, with no need for resiliency. Workgroup supports single-node
ACD environments only.
Both licensing bundles offer general business and contact center reporting and real-time
monitoring, client desktops, and IVR Routing capabilities, and support voice, email, chat,
SMS, and open media communication. They include feature-rich, web-based applications for
streamlining contact center management and enabling agent productivity. There are several
options available to further customize your contact center solution.
For detailed licensing information, see the MiContact Center Business System Engineering
GuideMiContact Center Business and MiVoice Analytics System Engineering Guide .
MiContact Center Business Microsoft Skype for Business includes the following applications,
depending on your licensing bundle:
• CCMWeb
• Contact Center Client
• Interactive Contact Center
• Interactive Visual Queue
2.2 Licensing
An employee is a physical person you track in your contact center. In the YourSite database, you
must create an employee ID for each employee who works in your contact center. Employees
can have multiple agent IDs, but only one employee ID. You can run reports on licensed
employees only. The number of employees you license in YourSite Configuration must be
consistent with your software license.
Contact centers process a high volume of contacts to meet marketing, sales, customer service,
technical support, and other business objectives. A fine-tuned contact center distributes contacts
efficiently and optimizes the use of agents and other resources. This section describes the inbound
contact center environment and how resources interact to process voice contacts.
Call Accounting ensures businesses have a true picture of how and where their telecommunication
budgets are spent. This chapter discusses how Call Accounting can be used to track phone use,
reconcile carrier bills, and bill back departments, and how it costs calls and detects toll fraud.
You can use Call Accounting to track phone use and to determine
Generate the Employee Group Accounting Summary report. This report provides the average
duration and cost of calls made by each employee of an employee group.
Where most of your long-distance budget is spent, and which employees make the most and
longest calls.
Generate the Employee Accounting by Phone number/Location report. If you have added these
phone numbers and names to your database (YourSite ExplorerPhone numbers), they will also
appear in the report. This report also provides you with a list of the 100 most often dialed phone
numbers by employee, and the 100 longest calls by employee.
Monitor call costs and other call statistics by extension in real time. You can set alarms, for any
or all extensions, for all call statistics, including caller ID information (such as caller name and
number). You can also set alarms based on call cost thresholds and toll fraud parameters. Alarm
notifications alert you when event thresholds are reached. You can choose to be notified by
visual changes in the monitor, sound prompts, pop ups, or email. By setting alarms based on the
thresholds you define, you can monitor telephone system abuse and stop it as it occurs.
You can set up Call Accounting to detect billing errors. When you configure Call Accounting to
mimic your phone carrier charges, you might notice discrepancies between your amounts and your
carrier amounts.
• Billing back departments
To bill back departments, your call costing information must be accurate. If your call costing
information is inaccurate, and you charge your subscribers less than you yourself are charged by
the phone company, then you are losing money. Of course, you do not have to assign the same
rates to subscriber calls that the phone company charges you for your calls. You can modify the
rate to include a markup or intentionally provide a discount.
• Monitor telephone system use in real time
You can set alarms, for any or all extensions, for all call statistics, including caller ID information
(such as caller name and number). You can also set alarms based on call cost thresholds and toll
fraud parameters. Alarm notifications alert you when event thresholds are reached. You can choose
to be notified by visual changes in the monitor, sound prompts, pop ups, or email. By setting alarms
based on the thresholds you define, you can monitor telephone system abuse and stop it as it
occurs.
To optimize the use of agents, you cross-train them so they can handle a variety of inquiries.
Rather than distributing calls to a number of small, specialized agent or extension groups, ACD
distributes them efficiently among the entire pool of available agents. When you consolidate
resources (use the Pooling Principle), the same number of contact center agents handle more
calls while maintaining Service Levels.
Typically, you program ACD to ensure the first call to arrive reaches the first available agent or
the agent who has been idle the longest. However, you can vary the order of calls and agents to
provide superior service to preferred customers, and skills-based routing.
When a trunk picks up a call, it forwards it through to a group of agents handling calls, or to
some other answering point. The call arrives at the ACD queue of an agent group. The queue
delays the call rather than blocking the call from entering the system. The length of time the caller
waits in queue is the queue time. While waiting in queue, the caller listens to product features,
announcements, or other messages provided by a Recorded Announcement Device (RAD). The
caller can wait patiently in queue for an available agent, leave a voice mail message, or hang up
(abandon) the call. (See the following figure.)
An agent handles the call. The time the caller spends talking to the agent is the ACD Handling
Time (including the hold time). If the agent calls the supervisor in search of more information
(while the caller is on hold) and/or transfers or conferences the call, these times are added to the
ACD Handling Time value.
For example, an agent speaks to a caller for two minutes and then puts the caller on hold for
three minutes and tries to solve the problem. This may include a call to the supervisor. The agent
then initiates a conference call with the caller and a third party and they speak for three minutes
and resolve the issue. Therefore, the ACD Handling Time for the agent is 2 + 3 + 3 = 8 minutes.
When the call is completed, the agent might need to perform additional work associated with the
call. The time taken to perform this work is the Wrap Up Time.
data on the agent and trunk involved in the call. The ACD management reporting application
produces reports on agent and trunk activity.
to distribute calls to a pool of specific extensions. Users can configure Ring Groups within
YourSite Explorer, monitor them in Contact Center Client, and report on them.
When an incoming call rings the Ring Group, the member extensions configured in the Ring
Group are rung until one extension answers. Ring Groups can be programmed to offer calls to
extensions using five different algorithms:
• Ring All: Rings all available extensions in the Ring Group simultaneously.
• Terminal: Starting from the first extension in the member list, rings the first available
extension.
• Terminal Cascade: Starting from the first extension in the member list, rings the first
available extension for the duration of the Cascade Ring Timer before calling the next
available extension in the member list.
• Circular: Starting from the last member to handle a call, rings the next available
extension in the members list
• Circular Cascade: Starting from the last member to handle a call, rings the next
available extension in the member list for the duration of the Cascade Ring Time
before calling the next available extension in the member list.
Ring Groups enable a business to ensure that in settings where employees may not have a set
physical location or mobile device, such as a warehouse or back office, calls can be effectively
distributed to an answering extension. Calls to Ring Groups can be ACD or Non ACD in Mi
Contact Center Business real-time and reporting.
Incoming calls are handled differently than ACD path queues as well. If a call comes in, it will be
queued if any one of the Ring Group’s extensions are available. Available extensions are those
that are:
• Idle
• Busy (ACD, Non ACD, or Out)
If the Ring Group’s extensions are not available, the call is overflowed immediately (if an overflow
point has been configured) or receives no answer. Extensions in the following states are not
available:
• Do Not Disturb
• Out of Service
• Not Present
• Reseize Timer
Calls arrive randomly to contact centers. You cannot predict the minute-to-minute arrival of calls.
This results in unanticipated increases in workload, and impacts staffing calculations and the load
carried by system and network resources.
You can predict the pattern of call arrivals for 15-minute or longer intervals. For example, you
can predict that next Monday between 1:00 P.M. and 1:30 P.M. you will receive 60 phone calls.
However, you cannot predict how many calls will arrive in the first five minutes, the second five
minutes, and so on.
Effective contact center management involves having the right resources in place at the right times to
handle an accurately fore casted workload at the desired level of service. Commitment to a systematic
planning and management strategy is essential. The strategy is based on corporate objectives that
you continually assess and refine. Whether you are managing a start-up contact center or refining the
performance of an existing operation, the process illustrated in the following figure applies. It is the
basic framework for achieving and maintaining your service objectives.
The objective of contact center management is to find the right balance between the agents scheduled
and the service provided to customers. This involves assessing and re-assessing trade-offs between
the Service Level, agents scheduled, and average call duration for a known Call Load for each 15-
minute or half-hour interval of the day. Collecting, properly interpreting, and applying ACD and other
information allows you to accurately forecast the workload and schedule sufficient agents to meet your
service objectives.
Defining and adequately funding a service objective should be closely tied to your corporate
mission. The service objective identifies the average length of time a caller who has obtained
a trunk waits for an available agent. It is the basis for planning and budgeting and links the
resources you require to your service objectives. Choosing a service objective is the first step in a
comprehensive planning and management solution. Once you set a service objective, you should
routinely access it to see how consistently you are meeting it, on a 15-minute or half-hour basis.
Contact centers in different industries use different criteria for measuring service. Your service
objective should reflect the type of service being provided and the expectations of callers seeking
the service. For example, a company that sells magazine subscriptions has less to lose in the
outcome of any one call than a car dealership does. A caller to a credit card 'lost or stolen' line
might expect different service than a caller to a customer service department at a bank. Contact
center metrics across industries are designed to reflect this.
Performance targets must suit the primary function of a contact center. In revenue-based contact
centers where agents sell products or services, the net revenue per call is considered when
defining a service objective. Revenue-based contact centers strive to provide a high level of
service with minimal blocking and delays.
The Service Level is expressed as X percent of calls handled in Y seconds or less, such as
80 percent of calls handled in less than 20 seconds. Why is Service Level the standard
measurement of service? Service Level provides the most accurate representation of the callers’
experience. It is ultimately the caller who decides what constitutes good service, and whether or
not to end a call. It applies to inbound transactions that must be addressed as they arrive.
When a caller enters a queue, the call is processed in one of three ways:
For detailed information on Calls Offered, Calls Handled, Calls Abandoned, Calls Interflowed,
and other Service Level parameters see "Choosing a Service level goal".
of receiving a busy signal. Since trunk costs are insignificant compared to agent costs contact
centers are well advised to schedule sufficient trunks, abandons should be minimal.
A delayed call is a call placed in the ACD queue because it cannot be answered immediately by
an agent. The probability of delay statistic relates the number of agents or extensions to the level
of traffic carried by the trunks and indicates the likelihood and amount of delay experienced. The
GOS, probability of delay, and Quality of Service rendered by agents provide vital information
about the callers’ experience. (See the following figure.)
The GOS and probability of delay contribute to our understanding of what happens to the calls
not answered in Y seconds, and give meaning to Service Level. Service Level is the primary
statistic used in planning and budgeting because it is the most stable measurement of queue
activity.
ASA
The Average Speed of Answer (ASA) is an ACD statistic that measures how long the average
caller waits on hold before the call is picked up by an agent. ASA is a valuable measure of
service quality, but is often misinterpreted. The average does not represent what is typically
experienced by individual callers. Most calls are answered by agents more quickly than the
average, but a small percentage of callers wait several minutes in queue. ASA is a useful
parameter, but Service Level is a more reliable indicator of what callers experience.
Abandonment
ACDs collect statistics on how long callers wait before abandoning calls, and what percentage of
calls are abandoned. Unfortunately, abandonment is difficult to forecast because it is impossible
to predict caller behavior with any reliability. Sometimes when the Service Level is high more
callers abandon than expected. There are no industry standards for abandonment. It is a
somewhat unreliable measure of contact center performance. However, abandonment statistics
assist in planning Service Levels, and provide valuable information used to create in-queue and
message-on-hold announcements.
Setting an appropriate Service Level goal for your contact center is not easy. The motivation
and expectations of your customers, the availability of similar goods or services, the Service
Level targets of same-industry companies, and the value of calls are things to consider. It may
be useful to run some calculations to determine the trade-offs in Service Level associated with
adding or removing an agent, and implement customer satisfaction surveys. When defining your
corporate Service Level, consider several factors and rate their relative importance.
Consider this modest objective. For a Service Level of 80 percent of calls answered in less than
20 seconds, callers receive the following service:
Service Level alone does not ensure customer satisfaction. The quality of the interaction between
the caller and agent leaves a lasting impression. Quality of Service reflects an agent’s ability
to provide excellent service to each customer. The knowledge of the agent, the accuracy and
completeness of the information provided, and the courtesy extended to the caller contribute to
the caller’s experience.
Silent monitoring takes the bias out of performance evaluation. Silent monitoring provides
a systematic process for monitoring and grading agent calls. You can schedule sessions
across different times of the day, days of the week, and evaluators promoting fairness and
consistency. Showing agents where improvement is needed is more effective than just telling
them. Silent monitoring can contribute to a reduction in call time, a reduction in monitoring time
and personnel, and increased training efficiency.
You can use pre-recorded interactions between agents and customers to train agents and for
ongoing evaluation.
The parameters used to evaluate how well agents handle calls are based on the purpose
of the calls. Goals vary across calls for inbound and outbound services. For example, in an
outbound sales environment quality may be based on whether or not the agent made the sale,
took advantage of cross-sell opportunities, and adhered to a pre-defined script. In an inbound
environment quality may be based on the completeness and accuracy of the information and
whether or not the caller’s questions were answered satisfactorily. Agents are also evaluated
on 'soft skills', such as voice quality, pausing at regular intervals, rate of speech, use of positive
language, and other listening and communication skills.
Once you determine appropriate scoring parameters, you define standards for exceptional
and acceptable levels of performance. Assessment standards are based on consensus and
must be clearly defined and communicated to monitors and agents. Collaborate with agents
in setting performance goals and clearly define exceptional service and interim performance
steps. Determine a baseline of current performance and set performance steps for an agent
group. Provide agents in the group who meet or exceed the interim target with rewards and
recognition commensurate with their performance. When systematically used in training and
coaching recorded sessions positively impact productivity. Fair assessment is good for moral and
motivation, and contributes to an environment in which agents can learn and grow.
Monitoring frequency
The frequency of monitoring sessions is determined by individual companies and ranges from
once a month to 15 or 20 sessions a month. Implementing five to 10 monitoring sessions per
month is common practice. Trainees and agents with consistently low scores are monitored more
frequently than other agents. Resource limitations typically influence the frequency of monitoring.
Silent monitoring systems range from tape recorders to client/server based recording systems.
Advanced systems schedule, record, and store voice files in a compressed digital format using
a real-time link to your telephone system. They capture any data tables accessed by the agent
in addition to voice data. Silences are eliminated to optimize monitoring efficiency. Recording
sessions can be played back from any telephone, anywhere, at any time. You can customize
agent evaluation forms and define parameters for quality with advanced systems. They provide
activity, status, and management reports for evaluating agents and observation practices.
IT support systems
Information Technology(IT) support systems are commonplace in contact centers. Contact center
agents divide their time between listening to customer requests, entering and updating customer
information and other entries, searching for required information, and providing feedback to
customers. In order to provide prompt and complete information, agents must have immediate
online access to information including customer records and case histories, products and
services, and company policies and procedures.
The push to increase agent efficiency and customer service has placed new demands on
computer information systems and information technology. Information products that enhance
agent productivity are continually being developed. Contact center systems are designed to
incorporate some, or all of the following specialized support functions.
CTI
Computer telephony integration (CTI) is the merging of computers and telephone systems.
Today’s computer-based telephone systems deliver synchronized voice and data, voice and
data conferencing, automatic information retrieval for calls, caller-based messaging and routing,
and desktop productivity tools. You can use customer databases in call handling to enhance
customer service and agent productivity. When databases are shared between contact center
departments each agent can access a caller’s contact information, purchasing records, call
history, and preferences by a caller ID number.
ANI
Automatic Number Identification (ANI) identifies the telephone numbers of callers to your contact
center, so agents can receive screen pops with calls. You can connect a database to your
telephone system to simultaneously send calls and caller information. The telephone system
forwards the caller’s telephone number to a software application that relays database records on
the caller to the agent. Alternately, the caller enters an ID number that the database associates
with a set of records for the caller and the agent is sent the information.
ANI saves agents time since they do not have to ask for and enter a name for a caller, and wait
for the database to respond. This time savings significantly impacts staffing requirements and
telephone service charges. ANI also identifies telephone numbers of callers who abandon calls
so they can be contacted later for potential business.
Reports can identify the volume of usage and costs of internal line numbers, and help you track
the long distance distribution per line number and maximize long distance efficiency.
DNIS
Dialed Number Identification Service (DNIS) is a feature of toll-free lines that identifies the
telephone number the caller dials. This assists agents who handle calls for more than one
business or product line. Each business or product line has its own toll-free number. When a
caller dials a toll-free number, the telephone system forwards information to the agent so the
agent can identify who the caller dialed. For example, a caller dials a toll-free number for a
cruise line. The telephone system sends a script to the agent along with the call. The agent then
knows to answer 'Good morning. Thank you for calling Southern Cruises', instead of the name of
another cruise line serviced by the center.
External applications, help desk operators, or end users (in web-based applications) generate
tickets. The system generates them manually, or in some cases automatically, in response to
system events. It can correlate multiple incidents with single tickets, and multiple problems with a
single call.
Automated help desk workflow systems track each step taken in answering a call, with automatic
time stamping of all of the referrals, escalations, reminders, alerts, and email notifications. Calls
are prioritized and referred to other departments without reassignment, reassigned (escalated) to
other technicians or specialized staff, and placed in an alert condition when they are not resolved
promptly. Activities are date and time stamped automatically. Most help desks offer outgoing
email notification and paging. Some help desks offer automated logging of incoming emails, and
automated call acknowledgment emails to clients.
Telephone systems provide detailed report data on every aspect of call transactions. You can
program computer-based telephone systems connected to a Local Area Network (LAN). Users
on the LAN can view or print real-time and historical reports. Using web-enabled telephone
systems, you can view and generate reports in a Web browser. You can monitor contact center
activities remotely, and distribute reports to people on different networks.
You can use historical data in forecasting and in assessing the performance of your resources.
Historical reports provide vital information on load activity, resource activity, and queue activity.
Workforce management systems use telephone system data to forecast and schedule agents.
Some packages monitor the real-time adherence of agents to scheduled activities, so you know
the number of agents currently logged on and available to handle calls. Workforce management
systems collect and store real-time adherence data. This data provides a historical account of
adherence used in agent assessment.
As the economy moves towards individual, personalized services, new ways of handing calls
continue to emerge. These new features add to the complexity of collecting and measuring
information. It is vital you establish an integrated, reliable system for measuring the key indicators
of performance: the efficiency of call handling, the service that callers experience, and their
perceptions of that service.
Forecasting impacts contact center operations and performance in the following ways:
The range of forecast dates you specify depends on the purpose of the forecast. Using long-term
forecasts, you can estimate future budgets and expansion opportunities, and establish corporate
objectives. Using short-term forecasts (of one to three months) you can determine seasonal
staffing requirements, plan for short-term sales campaigns, and assess upcoming hiring needs.
You can use weekly, daily, hourly and half-hour forecasts to tweak agent schedules and adjust for
absenteeism.
You may need to consider the following issues: hardware or software system changes, expected
callers, advertising and media, changes to your products, services, or pricing, new products,
product performance, competitors' actions, and international, national, and corporate events.
It is vital to have a systematic forecasting process in place that all of the departments support.
For detailed information on Call Load, ACD Handling time, Wrap Up Time parameters, see
"Forecasting terms".
The Erlang C formula uses your historical Call Load and Average Talk Time data to predict the
agent requirement for the time interval and date range in the forecast. The resultant spreadsheet
displays the Call Load and agents required across time intervals.
You can predict the agent requirement for your Service Level Percentage and Service Level Time
targets by applying the Erlang C equation to the estimated Call Load and Average Talk Time.
The industry standard Erlang C equation operates on these principals. Most contact center
reporting packages use Erlang C. An Erlang measures telephone traffic, or the flow of calls and
call attempts to your contact center during a given period. One Erlang equals one hour or 60 x 60
= 3,600 seconds of telephone interaction. This could be one call lasting one hour, six calls lasting
10 minutes, or any combination of calls and call durations that equal 60 minutes. The Erlang
formulas provide a mathematical basis for making predictions about randomly arriving workloads.
Agent and delay calculations use the Erlang C equation. It predicts the resources required to
keep delay times within your Service Level objective. Three variables influence the delay time:
the number of agents, the number of waiting callers, and the average time it takes to handle each
call.
Limitations of Erlang C
Erlang C has fundamental principles that do not reflect real-world circumstances. It assumes
all of the calls reach the contact center and all of the callers wait indefinitely to reach agents.
Because Erlang C assumes no blocking or abandons, it may overestimate the agents you need.
Erlang C requires accurate information on call flow where voice messaging and call overflow are
employed, assumes your Call Load prediction is extremely accurate, and assumes you have the
same number of agents handling calls the entire half hour.
Although Erlang C has its limitations, it is the preferred planning tool as it provides reasonable
traffic estimates for contact centers that maintain good service-and few abandons.
• The contact center blocks a certain proportion of calls and some callers abandon their
calls.
• Talk time is unpredictable, and although most calls may last two to three minutes, a
few calls can last upwards of an hour.
• Agents in training may require more time to process calls.
• Agents may use wrap up (after-call paperwork) time inconsistently during busy
periods.
• Not all of the agents within an agent group are available at all times to handle calls
offered to the agent group.
Erlang C predicts staffing needs fairly accurately. However, contact centers that use skills-based
routing, overflow, interflow, and advanced routing options need to use intuition and experience in
adjusting the final numbers.
The Erlang C formula uses your historical Call Load and Average Talk Time data to predict the
agent requirement for the time interval and date range in the forecast. The resultant spreadsheet
displays the Call Load and agents required across time intervals.
The following definitions are essential to understanding the relationship between agents and
trunks.
Delay
Trunk calculations assume no queueing. For trunk calculations, the delay includes the time from
when a trunk picks up a call until an agent answers it.
Agent Load
The Agent Load includes the ACD Handling Time and Wrap Up Time.
Trunk Load
The Trunk Load includes the time from when a trunk picks up a call until the agent finishes
speaking to the caller and disconnects. The Trunk Load does not include Wrap Up Time.
Callers expect to have a 95 percent or better chance of obtaining a free trunk in to your contact
center, and expect to connect to an agent within a reasonable amount of time. There must be
sufficient trunks available to pick up calls, and sufficient agents available to handle the level of
traffic carried by the trunks. The more agents handling a given Call Load, the less delay callers’
experience. Callers experience a delay if there are insufficient agents available. If the delay is
considerable, calls back up and some calls do not reach the contact center.
Traffic engineering involves estimating the number of trunks and amount of communications
equipment needed to service an anticipated number of callers. It revolves around basic questions
concerning the relationships between service parameters and trunk and agent resources. How
much traffic can a particular number of trunks handle for a particular GOS? What is the GOS
for a particular number of trunks and traffic level? How many trunks are required to handle a
particular traffic level and GOS? What is the probability of delay and length of delay experienced
for a particular traffic level and number of agents? How many agents are required to handle a
particular traffic level for a given set of delay characteristics?
BHT
The Busy Hour Traffic (BHT) statistic, measured in Erlangs, is the number of hours of call traffic
(or trunk traffic) you experience during the busiest hour of operation. It is important that your busy
hour figure represent the busiest Call Load your trunks will ever receive, and not just today’s
peak traffic. BHT is the (average call duration+ average delay) x calls per hour ÷ 3600. This value
represents the highest Trunk Load (occupancy) in hours.
The call center traffic is the average number of trunks busy during the hour in question. One
Erlang equals one hour, or 60 x 60 = 3,600 seconds of telephone interaction. If a contact center
experiences 6.12 erlangs (or 6.12 hours of telephone interaction) during an hour, an average of
six trunks were busy.
GOS
The Grade of Service (GOS) value is a decimal fraction. A GOS of P.02 means a caller has a two
percent chance of receiving a busy signal. Contact centers use GOS in calculating the number
of trunks required. It is important to specify a GOS that is right for you in order for the trunk
calculation to be realistic.
Traffic calculators used to predict contact center resource requirements are available on the Web
from companies such as erlang.com. You can obtain basic calculators at no cost. Calculators that
display and print results or calculations made during the previous week are available at a modest
cost.
To calculate the trunks required you simply input two of the figures and calculate the third. For
example, if you know that your Busy Hour Traffic is 10 erlangs and you want to determine how
many trunks are required when two calls are blocked in every 100 call attempts, you input the
busy hour time (10) and your target rate of blocking (0.02). The calculator displays a value for the
trunks required (17).
The following figure illustrates the trunks required across a spectrum of GOS values. Whether
you chose a GOS of 0.01, 0.05, or somewhere in between these values reflects how may calls
per 100 call attempts you can afford to lose. In revenue-based contact centers minimal blocking
and delay is a priority.
Although some contact centers base the trunk requirement on a staff-to-trunk ratio, such as 1.5
trunks per agent, many use the Erlang B equation. Whatever ratio results will be the right one for
you.
It is better to slightly overestimate than slightly underestimate the number of trunks required:
trunks are inexpensive, compared to agent costs. You can always cancel a trunk if periodic Trunk
Load calculations show low occupancy on the trunk.
No staffing approach is absolute. You need to acknowledge the assumptions implicit in your
calculations and use common sense when estimating your resource requirements. When you
schedule resources, they must be closely monitored to ensure you are making full use of them.
periods, repeating work patterns, holidays, and on call work. You can categorize agents by pay
level, overtime eligibility, skill level, employment status (part time or full time), and scheduling
preferences. Matching these shift and agent variables to the anticipated workload, and re-
allocating agents in response to employee absenteeism can be a daunting task.
Accurately forecasting and building schedules that reflect the workload as it changes across
intervals for days of the week, weeks of the month, and seasons of the year is essential in
meeting your service objectives. You need a schedule that accurately matches agents to the
anticipated workload and agents who aspire to adhere to the activities scheduled.
You can track the availability and activities of agents throughout the day and verify agents are
performing the duties for which they are scheduled. Not adhering to the schedule, such as
forgetting to log out for a break, or performing Non ACD work when scheduled to perform ACD
work adversely affects your Service Level and the moral of other agents who must compensate
for the unavailable agent.
Agents scheduled for ACD work can be involved in some of the following activities:
• On a bathroom break
• Making or receiving personal calls
• Conferring with the supervisor or another agent
• On the phone with other departments
• Sending emails
• Involved in a lengthy, difficult call
• Prolonged in after-call work
• Absent due to illness or compassionate leave
To account for short-term or daily unscheduled absences, you can calculate the rostered staff
factor (Shrinkage Factor). The Shrinkage Factor is a numerical value that defines the percentage
of time agents are scheduled to work but are unavailable to handle calls. It tells you the number
of agents you must schedule in addition to the base number of agents required to meet your
Service Level.
1. Determine the base staff forecasted by hour or half hour for the day.
2. Make a list of activities that prevent ACD agents from handling calls.
3. Add the base staff to the number of agents who are unavailable to handle calls
because they are absent, on break, at an unanticipated meeting, etcetera.
4. Calculate the Shrinkage Factor for each time interval by dividing the scheduled staff by
the base staff required to handle telephones.
The result is a set of Shrinkage Factors that represent the expected shrinkage by half hour.
You multiply shrinkage values against the base staff required on telephones when setting future
schedules. If your agent requirements vary considerably on certain days of the week, you can
calculate a separate set of Shrinkage Factors for these days. You must use your good judgment
in identifying absences that are relevant to include in your Shrinkage Factor calculations.
Anticipating higher absenteeism on Fridays and Mondays is a safe bet while factoring in daily
compassionate leave is not. As with all of the steps in contact center planning, routinely assess
the accuracy of your shrinkage predictions and adjust them as required.
The following examples illustrate ways to adequately staff a contact center without having agents
sit idle during slower periods.
Although not everyone likes to take a long break in the middle of a shift, for some agents split
shifts fit well with priorities outside of work. For contact centers that experience heavy call traffic
in the morning and evening, split shifts prevent overstaffing during these periods.
Staggering shifts
Staggering shifts allows you to maintain staffing levels over busy periods or periods when agents
are on breaks. For example, one set of agents could start at 8:00 A.M., a second group at 9:00
A.M., and a third group at 10:00 A.M. so the contact center is fully staffed when it starts getting
busy mid-morning. Alternately, you could schedule morning and afternoon shifts that overlap
from noon until 1:00 P.M. to enable the morning shift to break for lunch while the afternoon shift
handles calls.
Staggering breaks
Making slight adjustments to the timing of morning, lunch, and afternoon breaks has a
tremendous effect on call handling. The Erlang C equation predicts 28 agents can handle 300
calls, each lasting 280 seconds and delayed 20 seconds. (See the following figure.)
The following figure illustrates that changing the availability by one agent decreases the average
delay time by five seconds, and allows the contact center to handle 16 additional calls.
Not all of the Non ACD work must be performed immediately. For example, call-backs to clients,
emails, and discussions with staff and supervisors can sometimes wait until less busy periods.
Forecast and schedule Non ACD work for slow times to ensure sufficient agents are available
during peak periods. Set availability priorities and regularly communicate them to agents.
When practical, scheduling part-time agents and agents on call can be an effective strategy for
topping up your pool of available agents. Scheduling agents on call is particularly useful for days
of the week and seasons when absenteeism is noticeably higher.
You can overflow calls from busy agent groups to less busy agent groups during peak periods.
You can route calls to agents who primarily perform Non ACD work but act as reinforcements
during busy periods, and to supervisors.
You can program the ACD to forward calls to voice mail so callers can leave messages instead of
waiting for live agents. Call-back messaging helps to balance agent workloads between peak call
periods and slow periods.
Contracting calls is a growing industry. During peak periods, you can route simple, routine calls
externally to customer care bureaus. Service bureaus collaborate with contact centers to set up
scheduling and monitoring practices, and train agents to handle calls that vary in complexity.
Contact centers that provide extended, or around-the-clock service, can interflow calls to other
sites. For example, you can interflow mid-day calls received by a busy center in San Francisco
to agents working the late-afternoon shift at a center in Philadelphia. This optimizes call handling
without scheduling additional agents.
Producing long-term schedules is less efficient than producing monthly schedules, as contact
center conditions and agent availability are continually changing. Short-term scheduling is more
accurate, but less popular with agents. It is important to find a good balance.
You can measure the effectiveness of your scheduling process. Create a line graph of the
Service Level for each half-hour interval for each day over the past week. Draw a horizontal
line across the graph to indicate your service objective. Look for inconsistencies in the service
provided for different time intervals across days, and how far you stray from your service
objective.
If the Service Level is erratic, you may have enough resources in place, but they may not be
consistently available to handle calls. If the Service Level is inconsistent at certain time intervals
across the week, or you are not meeting your Service Level objective, investigate to see if you
are adequately staffed at these times and are making the best use of resources. Try to assess
how consistently the agents are responding to real-time information displays. Determine if they
are restricting Non ACD activities to slow periods and adhering to the schedule.
Workforce management tools assist you in scheduling agents for work and holiday periods.
Many packages offer an integrated forecasting component that uses historical data to partially
automate the scheduling process for established agents. Scheduling is not entirely automated:
you must tweak agent schedules and enter shift and agent variables for agents manually.
You need to provide a clear indication of how the money is being spent, what you are doing
to reduce or curb spending, and what equipment is required to meet service objectives and
expected growth over the next year. Budgeting is on-going process that needs continuous
refinement.
Loaded labor costs include wages, fringe benefits, and facilities, and account for over 60
percent of contact center costs. This is a significant cost and underlines the importance of
accurate forecasting and scheduling.
Equipment and automation costs include the cost of the telephone system, computer systems,
and furniture, and account for about five percent of total expenses.
• Transmission costs
Transmission costs include costs incurred for voice (telephone lines) and data transmission,
and account for 25 to 30 percent of contact center costs. Transmission costs have decreased
considerably in the past few years and are continuing to drop. In revenue-based contact
centers, toll-free lines cost approximately 15 cents per minute, or nine dollars per hour, per
line.
The following statistics help you breakdown and analyze your contact center costs:
• Cost of Delay
When insufficient agents are available to handle a given Call Load, the delay increases as
does the Trunk Load. Calls are queued. For toll-free services each call delayed in queue is a
cost to the organization. You are charged for the toll-free service from the time a trunk picks
up a call until an agent completes the call and hangs up. The expense of queueing callers is
known as the Cost of Delay. Staffing affects toll-free service costs: if insufficient agents are
available and the Service Level is continually low, network costs will be high. You need to
consider the Cost of Delay when estimating the agent requirement, and closely monitor it.
• Cost per Call
You use a cost-per-call analysis to measure contact center profitability and performance.
The cost per call measures labor, communication, and equipment costs against the revenue
generated. You calculate it by dividing the total cost by the total calls for a particular period of
time.
• Average Call Value
You use the Average Call Value in revenue-based contact centers. You calculate it by dividing
the total revenue by the number of calls received for a given period. Sales and reservations
environments use the Average Call Value. The value of each call is balanced against the
service provided to customers.
System Administrators are responsible for upgrading their contact center to the latest release and for
configuring all devices to ensure the business can run smoothly and efficiently.
MiContact Center version 7.0 introduced a new multimedia contact center product that eases
configuration. Routing of contacts is optimized through the use of visual workflows. Visual workflow
configuration presents contact routing elements in an intuitive user interface. Using a drag and drop
process, workflows can be customized to suit the individual needs of your contact center.
Note:
• As a best practice, system administrators should always apply the latest Windows
component updates are to all servers and client machines. For more information on
updating Windows products, consult Microsoft documentation.
• Version 9.3.x
• Version 9.3
• Version 8.1.x
• Version 8.0.x
• Version 7.1.3.3
When upgrading from MiContact Center version 7.x or 8.x or 9.x to MiContact Center Business
version 9.4.1 cases are automatically created for emails (beginning with the most recent email
and ending with the oldest email). Emails that are associated to a particular customer interaction
are grouped within a single case to consolidate information.
In addition, contact information based on historic emails is added to the MiContact Center
Business database. For MiContact Center version 8.1 customers who implemented the Omni
Channel Tech Preview cases are also created for SMS and Chat during an upgrade to MiContact
Center Business version 9.4.1.
Simplified Configuration reduces Multimedia Contact Center setup time significantly but requires
that the voice only portion of the system be configured first. The voice organization is used by
Simplified Configuration as a template for enabling multimedia functionality.
The Simplified Configuration process creates Unified Queue Groups, which are used to organize
queue and agent groups by the service for which they answer contacts. For example, a Unified
Queue Group for the Sales department would contain only those queue and agent groups that
handle Sales related contacts, either by email, chat, SMS, or open media. Unified Queue Groups
are based on a service group, not on the media type handled. Unified Queue Groups can contain
queues of any supported media type. Agent groups can contain agents of any supported media
type.
Note:
The Simplified Configuration feature is not available in the Version 8.0+ installer. Using this
feature decreases the time spent upgrading and simplifies multimedia device configuration by
auto-creating devices based on the current setup for voice. Upgrading from Version 6.0.3.0 to
Version 7.1 before upgrading to Version 8.0+ enables you to take advantage of the Simplified
Configuration option in the Version 7.1 installer.
Due to the significant architectural changes introduced in Version 7.0, we strongly recommend
using a side by side migration method when upgrading from Version 6.0.3.0 to Version 7.1. This
will help ensure a smooth transition as well as reducing setup time and minimizing downtime
during and following the upgrade.
If you choose to upgrade on top of an existing Version 6.0.3.0 server, please note the following:
In a direct upgrade, Version 7.1 is installed onto your existing Version 6.0.3.0 server. This method
In a direct upgrade, there are post-upgrade steps that must be completed before you will regain
full Multimedia Contact Center functionality. Multimedia Contact Center functionality is lost while
you configure your new email settings. See "Creating mail servers" and "Configuring the email
media server" for more information. If your contact center hosted chat configuration files on
your corporate web server, you must enable chat to use them. See "Hosting chat files on your
corporate web server" for more information.
If you currently use Multimedia Contact Center and choose to upgrade using your existing
Version 6.0.3.0 server, you will be given the choice during the upgrade to either migrate your
existing multimedia configuration or program the new multimedia portion of the software
manually. Programming the multimedia software manually enables you to take advantage of the
configuration options included with Version 7.1.
A side by side migration carries the lowest level of risk in upgrading but may require purchasing
additional hardware depending on your current configuration.
Additional licensing is not required when running a second Enterprise Server for the purposes
of migration or to create a sandbox environment. To mitigate risk, consult a certified technician
before configuring a second server. Once a license has been migrated, support will be provided
for the latest release only. Support will not be provided for the older server with the previous
release or the sandbox server.
A side by side migration is strongly recommended when upgrading an environment that currently
uses voice and other media types. With a direct upgrade, Multimedia Contact Center functionality
is lost while you configure your new email settings. In a side by side migration, where you install
the new version on a new server, this situation is mitigated. There is only a temporary loss of
functionality when you move your live data from the old system to the new system.
In a side by side upgrade, contact centers must implement a new version 8.1 Chat or Contact
Us configuration using the new files in version 8.1 and add their previous chat and Contact Us
settings to the 8.1 files. For information on Chat and Contact Us configuration, see "Enabling
chat" and "Enabling Contact Us".
After restoring the configuration backup to the new server, data collection, synchronization, and
voice contact control on the production PBXs begins. This ensures a minimal gap in reporting
data. If the data directory is copied and the database restored outside of business hours, there is
no reporting data gap.
Synchronization is enabled and changes to the telephone system will be reflected in both
the new and production servers after the maintenance cycle or upon completion of a manual
summarization. If write back is enabled, settings take effect on the other server only after
synchronization is complete.
We recommend testing your new configuration by creating a test email queue, a test chat queue,
a test SMS queue, and a test agent on the new server and validating that email, chat, SMS, and
open media are being correctly routed to queues and agents. Run reports to verify accuracy.
Confirm that email aliases or distribution groups and URL redirects for chat have been correctly
implemented.
In a side by side migration, once the new server is installed and all of the devices configured
we recommend you then proceed to upgrade one client and ensure the system is functioning
correctly before upgrading all other clients. If you choose to upgrade on top of your current
system, the clients are automatically updated during the upgrade process.
• By default, MiVoice Business supports three ACD and three SMDR connections
to the same PBX. The existing system and the new system use one ACD and
one SMDR connection each. When migrating servers, data collection will resume
on the new server upon restoration of the configuration backup. As a result, two
connections to the SMDR and ACD ports will be used until one of the servers has
been decommissioned. Ensure the number of connected devices to these ports does
not exceed three per IP port.
Note:
MiVoice Business supports 3 ICP connections by default, but the number of
supported ICP connections can be increased. Exceeding the number of supported
connections will impact the collection of data on the server.
• When using voice contact control through MiContact Center Business for business
hours queues may be closed by the new server if business hours are reconfigured.
To ensure no voice contact control is performed until testing or migration, stop the
MiContact Center Business MiTAI Proxy Server service on the Enterprise Server.
• You must ensure queue schedules are identical on both systems.
• Reporting discrepancies can occur due to differences between software versions or if
data collection is interrupted.
• IVR Routing services must be shut off on the new server until you are ready to switch
over or assign new ports.
Note:
We strongly recommend storing backup files in a location outside of the Enterprise Server in
order to maintain essential data in the case of a hardware failure or catastrophic event.
• YourSite Database configuration data files – These files contain all device
configuration for your contact center (including IVR Routing and Multimedia Contact
Center workflows and prompts) and are backed up automatically during nightly
maintenance. They are located in the SQL Server database as part of the CCMData
files. During nightly maintenance, the data is backed up as an .xml file and retained
for the last 30 days, enabling you to restore a previous configuration if necessary. You
can also backup configuration data manually using the Backup and Restore Wizard in
Contact Center Client.
• Raw data files – These files contain all raw data from the media servers,including
ACD and SMDR historical data and a flat file multimedia repository for all media,
excluding voice. The multimedia repository stores multimedia messages and SMS and
chat transcripts. These files are not backed up during nightly maintenance and must
be backed up manually using your corporate backup solution.
• Reply template data files – These files include the packaged responses for email,
chat, SMS, and open media. The reply template data files from the default folder and
all user-specified folders are backed up automatically during nightly maintenance.
Reply template data files are also included in manual backups using the Backup and
Restore Wizard in Contact Center Client.
• SQL Server data files (CCMData and CCMStatisticalData) – The data that is
stored in the SQL Server database is not automatically backed up during nightly
maintenance. Consult Microsoft documentation for more information regarding backup
and restore processes.
Following is a list of folders and locations for data that should be backed up using your corporate
backup solution. Suggested backup tools include Symantec Backup Exec and Microsoft System
Center Data Protection Manager:
This folder contains the nightly .xml backups of configuration data and IVR Routing
and Multimedia Contact Center workflows and prompts that are created during nightly
maintenance.
• Raw data: <drive>:\Program Files (x86)\Mitel\MiContact Center Business
\DataDirectory
This folder stores all raw data from the media servers. Using this data you can re-summarize
your raw data to enable reporting. This folder also contains the multimedia repository for all
media, excluding voice.
To restore your system with the backed up data, you must stop the MiContact Center Business
services and use the backup tools to restore the folders that you previously backed up. After
these folders have been restored, restart the MiContact Center Business services. For more
information, see "Restoring telephone system and configuration data".
Some manual device configuration is required for those devices that were introduced in version
7.0 and version 8.1. We recommend you gather the following information before beginning the
upgrade process:
CRM 2007 is not supported with version 9.1. If workflows contain Execute activities that point
to CRM 2007, the preinstall checker will stop the upgrade. Microsoft CRM 2011 and 2013 are
supported for use with Mi Contact Center Business version 9.1.
• Choose the corporate web pages on which you want the Contact Us page to display
Employees handling inbound interactions for each service organization can be enabled to handle
email, chat, SMS, and open media. Agent groups handling interactions for a service organization
can be expanded to handle email, chat, SMS, and open media for the same service. Each
voice queue representing a service organization will be contained within a Unified Queue Group
to which email, chat, SMS, and open media queues are added. The Unified Queue Groups
represent each service organization and route any media inbound interaction intended for that
particular service.
Note:
Unified Queue Groups are optional. You can alternatively use standard queue groups,
depending on your business organization and needs.
See the MiContact Center Business and MiVoice Analytics System Engineering Guide for
specification details.
3. Migrate SQL databases. (Side by side migration method only)
Migrating the SQL databases enables you to preserve your previous reporting data. If you do not
migrate the SQL databases, a new database will be created to which you can copy over the raw
data, restore the database from the backup files, and, then, re-summarize the data. However, the
data you will be re-summarizing will be for the current configuration so the reporting data may not
match that of your previous system.
The two most common methods for migrating SQL databases are:
• Dropping the database files from the SQL instance and making a physical copy of
the .mdf and .ldf files
• Using SQL Server Management tools to generate backup files or scripts
See the applicable Microsoft documentation for more information on migrating SQL databases.
1. Copy the SQL database .mdf and .ldf files or use MS SQL Server Management tools
to make backup files or scripts.
2. Provision a new SQL server or new instance of SQL server.
3. Restore the SQL databases to the new SQL server or instance of SQL server.
The Enterprise Server configuration backup includes configuration items such as employees,
agents, agent groups, queues, and security roles.
Note:
A .zip file is created that contains an XML file with the entire configuration. The file size
will vary depending on the amount of data that needs to be backed up, but will typically be
between 1 and 20 MB. This .zip file name contains the date on which the file was created. For
example, a backup file created on June 24, 2015 will contain ‘20150624’.
Note:
After restoring a backup, check the IP addresses configured in YourSite Explorer and the
computer names associated to all media servers to ensure the local media servers are set to the
local server name and remote collectors are also set correctly.
After creating a mail server, we recommend using the test button to verify both the SMTP and
mail server are connected.
For more information and configuration details, see "Integrating Multimedia Contact Center with
mail".
For media server configuration details, see "Adding email to Multimedia Contact Center".
Chat media servers require the chat server URL and auto-response username to be specified.
The chat server URL is the public URL invoked when a customer requests a chat. When a chat
server URL is configured, the system performs an auto test to determine if the URL redirect is
properly configured.
For more information and configuration details, see "Adding chat to Multimedia Contact Center".
To send and receive SMS interactions, SMS media servers require an SMS Gateway Provider.
Multimedia Contact Center supports Twilio as an SMS Gateway Provider. You must have a Twilio
account to add SMS handling capabilities to Multimedia Contact Center.
For more information on integrating with an SMS Gateway Provider, see "Integrating Multimedia
Contact Center with an SMS Gateway Provider". For information on configuring an SMS media
server, see "Adding SMS to Multimedia Contact Center".
For media server configuration details, see "Adding Open Media to Multimedia Contact Center".
For additional information and configuration details, see "Adding multimedia capabilities to
employees".
1. Use the multi-select method to select the employees who will be upgraded to
Multimedia Contact Center licensing.
2. Click the General tab and enable employees for the media their agents will support.
Additional agents are created for the media specified. The agent uses the same name and
reporting number as the employee.
Agents that are newly created in the Employee device page will only be added to the
employee's agent group if the employee's agent groups are enabled for the relevant media
type and the Unified Queue Group Wizard is used.
3. Click Save.
During the upgrade, default Workloads are created and assigned to existing employees who
are licensed for Multimedia Contact Center. Newly created employees must have Workloads
manually assigned to them. You can also choose to create customized Workloads and assign
them to employees, rather than using the included, default Workloads.
For information on defining employee Workload, see "Managing Employee Workload". For
information on configuring Workloads, see "Configuring Workload".
If you have agents who handle non-voice media interactions only, you will need to add agent
groups accordingly.
You add agent groups and then associate employees to these groups.
Agent group presence, previously only available to voice agents, is now also available for
multimedia agents. Agents and supervisors can adjust a member’s presence in an agent group.
By default, on login, agents are present in all of their agent groups. You can adjust this setting
in the Agent group device page of YourSite Explorer. See "Managing agent group membership,
presence, and skill level".
For more information and configuration details, see "Adding agent groups" in the 'Configuring
your multimedia contact center' section of this guide.
If you use the Unified Queue Group Wizard, you do not need to add multimedia queues. Voice
queues will be used by the Unified Queue Group Wizard as the basis for creating Unified queue
groups that will handle all inbound interactions for a service group.
For more information and configuration details, see "Adding multimedia queues" in the
'Configuring your multimedia contact center' section of this guide.
Unified Queue Groups are used to enable the media queues for a service organization to be
grouped together. They are called ‘Unified’ Queue Groups because they unify a group of media
queues, for example, email, chat, SMS, and open media, that handle interactions for a service
group (i.e., Sales or Customer Support) within a business.
The Unified Queue Group wizard uses current voice queues to represent the service groups
that will be expanded to handle multimedia. The System Administrator is asked to select voice
queues and the media types that are to be enabled in the organization. The wizard then uses the
voice queue name and reporting ID to create media queues, with the same name and reporting
ID, and groups them into a Unified Queue Group. Each media queue is assigned a default
Inqueue workflow.
Note:
• Unified Queue Groups are restricted to one media queue for each type of media.
• Individual queue priorities are used to specify the priority for media and queue
routing. The default priority assigned is 64.
• Default Inqueue workflows have four levels of offer to agent group activities (to
support multiple overflow conditions). The wizard populates the default Inqueue
workflows with the same agent group order used by the voice queue member of
the Unified Queue Group.
• Unified Queue Groups are optional. If you choose not to use them, then you must
create individual email, chat, SMS, and open media queues and enable agent
groups for multimedia.
For more information and configuration details, see "Adding queue groups".
Note:
During the upgrade, a default response workflow is assigned to relevant media servers. Default
Inqueue workflows are assigned to each media queue. You can choose whether to enable default
Inbound workflows on the Media Server configuration page in YourSite Explorer.
The first step in converting to visual workflow routing is enabling inbound routing for your media
servers. Enabling inbound routing associates the appropriate default Inbound workflow to the
server. Administrators can modify these default workflows to suit the contact center’s needs.
The following explains how to convert to visual workflow routing by enabling the Inbound Routing
tab on YourSite Explorer’s Media Servers page. For more information on working with visual
workflows and applying routing rules to interactions, see:
Note:
If version 6.0.3.0 customers upgrading to a version 7.1 system do not convert to visual
workflow routing via the following procedure, multimedia interactions will continue to route
directly to queues without routing rules applied through Inbound workflows. In cases where
inbound interactions have multiple addresses in the To and/or CC fields, the interaction will
only be routed by the first address in the To field.
1. Select Multimedia > Media servers and select the media server.
2. Click the Inbound tab.
Note:
If you do not want to convert to visual workflow routing, do not save the media server.
Note:
This section is only applicable if you are upgrading from Version 6.0.3.0.
Create a test email queue, a test chat queue, a test SMS;queue, and a test agent on the new
server and validate that email, chat, SMS, and open media are being correctly routed to queues
and agents. Run reports to verify accuracy. Confirm that email aliases or distribution groups and
URL redirects for chat have been correctly implemented.
Before moving to the new system, advise agents to complete all outstanding items on the old
system. Advise agents to empty their public folders.
When moving email addresses from your old server to the new server, we recommend you
enable email addresses one at a time, beginning with those that experience the lowest traffic.
Mail-disable the email address from the existing public folder. Add the address as an alias or
distribution group to the generic email address inbox that your mail server is pulling from in the
Version 8.1 environment. Continue with this process until all email addresses have been enabled
in the new system.
Note:
When you mail-disable the email address in the public folder, mails will not be delivered and
mail senders will receive an undeliverable message until the email address has been created
in the new system as an alias or distribution group.
Optionally, you can similarly migrate the chat items. We recommend you do so in a staggered
fashion by only exposing the request to chat from the corporate Web page for a specific service
group. We also recommend that, during migration, you add a maintenance message that
explains chat is temporarily unavailable.
Deploy the updated corporate Web pages with the Contact Us page on the corporate website.
Remove the chat temporary unavailable page.
Disable the old system and instruct agents to log onto the new system.
Note:
This section is only applicable if you are upgrading from Version 6.0.3.0.
Support is provided for migrating the Exchange repository to the new flat file repository. This
migration is expected to take a significant amount of time and is dependent on the amount of
data to be migrated. This migration can occur after the new system is operational. After migrating
to the flat file repository, stopping and restarting the Storage Service is required and will tag new
entries for the search tool.
Note:
Due to Windows' limitations, you will be unable to migrate emails whose file names exceed
260 characters.
Migrating data will break the link with real-time data and preferred agent status for any contacts
from before the upgrade will be lost. The migrated data will be fully indexed and searchable. To
associate an agent to a reply will require a manual search of SMDR records.
There are several possible, existing Exchange Server deployment scenarios to consider when
upgrading. The high level upgrade steps are similar regardless of the version of Exchange
currently being used. See the following table for a description of four possible migration
scenarios.
Note:
For minimum downtime, we recommend migrating email addresses after all installation and
configuration is complete. In that way, when you mail-disable the public folders and add
email addresses, as aliases or distribution groups, agents will be already be configured and
prepared to answer emails in the new system.
Exchange is installed on its own Leave the Leave the Exchange Server intact
server and is not collocated with Exchange Server for corporate use.
MiContact Center Business. This intact.
Exchange Server is used for
corporate and Multimedia Contact
Center data.
of the rollback
plan.
• Stop and disable the Mi Contact Center Business Services on the Exchange Server
(Setup and Objects service).
• Create a new mailbox on the mail server that is going to host the new Multimedia
Contact Center mailboxes.
• Use a primary SMTP address that does not match any of the queue’s SMTP
addresses.
• Using the Exchange Public Folder Management Tool, mail-disable all of the Queue
Public Folders.
Note:
When you mail-disable email addresses in the public folder, mails will not be delivered and
mail senders will receive an undeliverable message until the email addresses have been
created in the new system as an alias or distribution group. We recommend you disable
email addresses one at a time to minimize disruption.
Distribution Groups are recommended in order to associate multiple email addresses to a single
mailbox. It may take up to 15 minutes before the email addresses are available.
Enable the IMAP service and set it to automatic startup on the CAS server that is servicing the
new mailbox.
At the beginning of the upgrade from Version 6.0.3.0 to Version 7.1, the install wizard offers
the option of the recommended normal upgrade or manually creating your Multimedia Contact
Center Version 7.1 configuration from scratch. Read further to learn about the advantages of
each choice.
If you select the recommended normal upgrade option, the installation wizard will not attempt
to create new agent IDs, agent groups, and queues. Such configuration must be done
following the upgrade. The advantage of choosing manual configuration is that it enables
you to use the Simplified Configuration tool. Simplified Configuration eases the configuration
process by creating blended queues and agent groups around each service group. It uses the
already existing voice system as a base from which to enable multimedia. After the Simplified
Configuration process is complete, each service group in the organization will have a Unified
Queue Group that contains the media queues supporting the service group and a blended agent
group(s) containing all of the employees who provide support for the service group. If another
media type is required for a service group, another media queue can be added to the Unified
Queue Group and the employees who are members of the agent group can be enabled for the
additional media type.
CAUTION:
If you select to manually configure your Multimedia Contact Center, all of your existing devices
will be designated as historical. New agent devices, agent groups, and queues will be auto-
created to align as well as possible with your pre-existing configuration settings and routing
behavior. After the upgrade it may be necessary to adjust device configuration, for example,
you may want to consolidate agent groups or create Unified Queue Groups, to better align with
the new model of Multimedia Contact Center. The advantage of choosing auto-upgrade is that
it is faster than the manual upgrade. If you want to re-enable your system quickly to minimize
downtime and do more refined configuration later, then this may be the best choice for you.
Note:
The Simplified Configuration feature is only applicable to upgrades from Version 6.0.3.0.
The Summarize process has been modified to regenerate data for historical agents if the
employee associated to the agents remains licensed for Multimedia Contact Center. This ensures
all pertinent historical agent records continue to be accessible.
• During the upgrade, device reporting numbers may change. For example, if you
choose the auto-upgrade option, similar groups will be automatically aligned,
potentially altering their reporting numbers. This will affect your report data
interpretation.
• After upgrading to Version 7.1, all multimedia reports will be generated from the
new devices on the active media servers. If you want to run pre-upgrade multimedia
reports, their data must be generated from the historical media servers. You cannot
consolidate historical and new data into a single report.
Note:
This section is only applicable if you are upgrading from Version 6.0.3.0.
Migrating the email repository can be quite time consuming. Depending on the number of items
being moved, this process may take several hours. Migration must take place after the upgrade
is finished as the C:\Program Files (x86)\Mitel and SearchStorage folders must be created before
the migration can occur. You will be able to run Multimedia Contact Center while migrating the
email repository. Any historical data that resides in Exchange will not be accessible from Ignite for
searching purposes until the migration is complete.
Migrating the email repository breaks the link with real-time data. If you use preferred agent
settings to route email, any contacts from before the upgrade will not retain their preferred agent
history. To associate an agent with a reply, a manual search of SMDR records will be required.
2. Ensure all hardware and software specifications are met for the server and clients.
See the MiContact Center Business and MiVoice Analytics System Engineering Guide for
specification details.
3. Migrate SQL databases. (Side by side migration method only)
Note:
interactions, at a rate of approximately 8000 items per hour. The processing rate depends on
your processor, available system resources, and number of historical multimedia interactions to
be migrated.
Migration speed can be decreased if the server is under high load and you want to prioritize
production operations. Migration speed should only be decreased if the system is in a high
performance production environment and there is no immediate need to search older archived
items. Default settings should provide appropriate performance for the majority of multimedia
implementations. For information regarding modifying migration speed, see the following Mitel
Knowledge Base article: https://mitel.custhelp.com/app/answers/answer_view/a_id/1002083/loc/
en_US.
Before upgrading, we recommend migrating the SQL database to the new server. By doing so,
the installation configuration wizard will update the database schema when the new version of
software is installed.
Migrating the SQL databases enables you to preserve your previous reporting data. If you do not
migrate the SQL databases, a new database will be created to which you can copy over the raw
data, restore the database from the backup files, and, then, re-summarize the data. However, the
data you will be re-summarizing will be for the current configuration so the reporting data may not
match that of your previous system.
The two most common methods for migrating SQL databases are:
• Dropping the database files from the SQL instance and making a physical copy of
the .mdf and .ldf files
• Using SQL Server Management tools to generate backup files or scripts
See the applicable Microsoft documentation for more information on migrating SQL databases.
1. Copy the SQL database .mdf and .ldf files or use MS SQL Server Management tools
to make backup files or scripts.
The Enterprise Server configuration backup includes configuration items such as employees,
agents, agent groups, queues, and security roles.
Note:
A .zip file is created within which is an XML file that contains the entire configuration. The file
size will vary depending on the amount of data that needs to be backed up, but will typically be
between 1 and 20 MB. This .zip file name contains the date on which the file was created. For
example, a backup file created on June 24, 2015 will contain ‘20150624’.
Note:
After restoring a backup, check the IP addresses configured in YourSite Explorer and the
computer names associated to all media servers to ensure the local media servers are set to the
local server name and remote collectors are also set correctly.
Note:
Whether you need to perform each of the following procedures depends on the version of
MiContact Center Business software you are upgrading from and your multimedia settings
prior to upgrade. All procedures are included here but may not all apply to your specific
upgrade.
After creating a mail server, we recommend using the test button to verify both the incoming and
outgoing connections are functioning as expected.
When email servers are copied over during the upgrade, they retain the SMTP information for
outbound mails, if it was configured in the previous system.
For more information and configuration details, see "Integrating Multimedia Contact Center with
mail servers".
If you are upgrading from pre-version 8.0, you must add a new SMS media server, add SMS
handling capabilities to employee and agent groups, and add new SMS queues. In version 8.0+,
SMS media servers require an SMS Gateway Provider. As of version 8.0, Multimedia Contact
Center supports Twilio as an SMS Gateway Provider. You must have a Twilio account to add
SMS handling capabilities to Multimedia Contact Center.
For more information on integrating with an SMS Gateway Provider, see "Integrating Multimedia
Contact Center with an SMS Gateway Provider". For information on configuring an SMS media
server, see "Adding SMS to Multimedia Contact Center".
Note:
Historical multimedia agents associated with employees can only be seen and deleted from
YourSite > Agents.
For information and configuration details, see "Adding multimedia capabilities to employees".
For more information and configuration details, see "Adding multimedia queues".
Unified Queue Groups are optional but are beneficial in organizing media types for each service
organization within your business and are a preferred method of multimedia queue configuration.
For more information and configuration details, see "Adding queue groups".
Note:
During the upgrade, a default response workflow is assigned to relevant media servers. Default
Inqueue workflows are assigned to each media queue. You can choose whether to enable default
Inbound workflows on the email media server device configuration page in YourSite Explorer.
Default upgrade settings use an Offer to Agent activity to select the next available agent. If you
require preferred agent support, then you must replace the Offer to Agent activity with an Offer to
Preferred Agent activity in the Inqueue workflow.
Note:
• Only one set of pending configuration changes can be saved at any time. If
another user saves changes to the same element of YourSite Explorer that you are
updating, you receive an error message when attempting to save your changes. In
these instances you must refresh YourSite Explorer after the other user’s changes
have been saved. You may then re-enter and save your changes. We recommend
you save your configuration changes frequently, in order to avoid losing work.
• YourSite Explorer enables you to have multiple device tabs open simultaneously.
As a best practice, we recommend you only have the device tabs open that you
are currently using.
• When you configure numbers for groups in YourSite Explorer, use numerical
characters only, such as 1 (for Queue Group 1). Do not insert symbols, such as a
star [*] or pound sign [#], in the number.
• If you attempt to add a device or device group to YourSite Explorer that is already
in the database, the system notifies you that the device or device group is already
present. When you add a series of devices or device groups to YourSite, such as
Queues 5001 to 5005, if the system detects you have already added Queue 5002,
then it will not add Queue 5002 or any subsequent queues in the series (that is,
Queues 5003 to 5005) to the database.
Note:
Only information common across devices of the same type can be changed in one action.
4. Click Save.
Multiple filters can be applied at a time, enabling administrators to selectively view devices by
multiple categories or types. For example, administrators can view only Email, Chat, SMS, or
Open Media variables by applying these filters to the Variables page.
• Queues
• Subroutines
• Variables
• Workflows
2. After Filter, select a device category or type from the drop-down list.
Note:
Filters remain in place until a category is deselected. Selecting ‘None’ removes all filters.
In Multimedia Contact Center, administrators can organize the following devices by criteria
• Agents
• Employees
• Media servers
Note:
Additional grouping criteria are nested under the original criterion selected.
Note:
To remove all grouping criteria, ensure no criteria remain selected under Group by.
For multimedia queues, interflow is conducted by the Interflow activity in Inqueue workflows.
See "Routing interactions with the Interflow activity".
• Customized auto-acknowledgment messages
For more information concerning non-multimedia enterprise settings, see the MiContact Center
Business Installation and Administration Guide MiContact Center Business for Microsoft Skype for
Business User Guide "Configuring enterprise settings".
Note:
Notifications of critical alarms are sent immediately after the issue is detected.
6. After Send Enterprise Server alarms to the following address(es), type the email
address of the employee(s) who will receive the email notification.
Your site structure determines how you view statistics and reports. When you set up your site
structure, you specify site and media server information. When you add a site, you add the name
of the site and the time zone. By making each site distinct, you can restrict user access to sites.
For more information on restricting user access, see "Configuring security roles". The site’s
language determines the default language setting for employees associated to it. Changing the
site’s language will change the language setting for employee’s associated to it.
Administrators can limit whether or not the Make Busy and Do Not Disturb reason codes used
by employees are visible in communication tools such as MiCollab and Microsoft Skype for
Business.
Administrators can also enable agent greeting and whisper announcement functionality for all
agents in the site. Agents record messages from Ignite (DESKTOP) and assign them to specific
queues, so that they are played on each incoming ACD call. For more information, see the "The
Agent Greeting feature enables agents to record messages (as .wav files) that play automatically
to callers when the agent answers an inbound ACD call. The greeting can provide a consistent
experience for each caller and free the agent from having to repeat the same introductory phrase
for every call.". For information on configuring agent greeting workflows, see "Configuring the
Record Agent Greeting workflow" and "Configuring agent workflow settings" MiContact Center
Business Installation and Administration Guide and the MiContact Center Business User Guide .
Administrators can also restrict the site’s use of Contact Center Client’s Chat Integration, which
enables employees to chat with each other in Contact Center Client. Prior to version 7.0, there
was an option to use Microsoft Skype for Business as the default chat client instead of Contact
Center Chat. In version 7.0 and greater, YourSite Explorer automatically detects if you have
Microsoft Skype for Business Server and enables it as the default chat client. If your contact
center is a mixed environment where some users have Skype for Business and others do
not, you may want to use Contact Center Chat to ensure all employees can communicate.
For information on using Contact Center Chat in an environment with Skype for Business
on some systems, see the following Mitel Knowledge Base article: http://micc.mitel.com/kb/
KnowledgebaseArticle52084.aspx
To add a site
The system displays an information message advising you to ensure that the appropriate
Class of Service options are configured for agents on the MiVoice Business PBX.
10. To disable Contact Center Client Chat Integration, clear Chat Enabled.
11. Click Save.
\<SiteKey>\<Year>\<Month>\
Year and Month folders are named numerically to correspond to the year and month of the stored
messages and transcripts. If you used the default storage path, the folder structure is <drive>:
\Program Files (x86)\Mitel\MiContact Center\DataDirectory\SearchStorage\<SiteKey>\ <Year>
\<Month>\.
Note:
• Chat and SMS transcripts are stored in the Elasticsearch index, at <drive>:
\Program Files (x86)\Mitel\MiContact Center\Database\Elasticsearch\. For more
information on Elasticsearch, see the MiContact Center Business and MiVoice
Analytics System Engineering Guide.
• The \<SiteKey>\<Year>\<Month> folders are only added the first time an email is
indexed during the corresponding year and month.
The multimedia storage path can be changed to store new messages in a different location. Old
files must be copied to the new location manually. For instructions on changing the multimedia
storage path, see the following Mitel Knowledge Base article: https://mitel.custhelp.com/app/
answers/answer_view/a_id/1000794/loc/en_US.
Certain email .msg files can be deleted from the email storage location to free up disk space.
While Ignite will return deleted .msg files in search results, attachment viewing will be limited
and embedded images will not display. For information, see the following Mitel Knowledge Base
article: https://mitel.custhelp.com/app/answers/answer_view/a_id/1013096/loc/en_US.
Mail servers will need to be created for your email media server. They are used to receive and
send mails to the corporate mail server. It is recommended that email aliases or distribution
groups, depending on your mail server type, be used to map multiple email accounts to a
single email account as this will reduce the number of mail servers that need to be configured.
Media servers will need to be created for each media supported by the contact center. Email
media servers require one or more mail servers to be specified. Chat media servers require
the chat server URL. SMS media servers require an integration with Twilio, a third-party SMS
gateway service provider.
See "Adding email to Multimedia Contact Center" and "Adding Chat to Multimedia Contact
Center" and "Adding SMS to Multimedia Contact Center".
The order for configuring your multimedia devices depends on whether or not the administrator
is creating multimedia queues using the Unified Queue Group wizard. The Unified Queue Group
wizard enables rapid configuration of new multimedia queues linked with existing voice queues.
If a contact center does not intend to have their multimedia queues mirror voice queues, they can
be added manually. For detailed information on configuring individual Multimedia Contact Center
devices, see "Multimedia Contact Center device configuration".
If you are creating your multimedia queues using the Unified Queue Group wizard, configure your
devices in the following order:
1. Create Workloads.
Workloads determine the number and type of media interactions that can be pushed to an
agent at any one time.
The default workflows included with Multimedia Contact Center require additional
configuration to customize them for your contact center.
If you are not using the Unified Queue Group wizard to create your multimedia queues, configure
your devices in the following order:
1. Create Workloads.
The default workflows included with Multimedia Contact Center require additional
configuration to customize them for your contact center.
Note:
Multimedia Contact Center integrates with mail servers using SMTP and IMAP or EWS
connections.
Note:
SMTP, IMAP or EWS connections through web proxies are not supported.
The following servers are considered to be supported infrastructures for Multimedia Contact
Center routing:
• Exchange Server
• Exchange Online (Office 365)
• Google Apps for Business
• IBM Domino
• BlueHost
Verified versions for mail servers are described in the MiContact Center Business and MiVoice
Analytics System Engineering Guide MiContact Center Business System Engineering Guide :
Multimedia Contact Center supports IMAP providers that use non-empty Namespace as
mail servers. For information on the general requirements for mail servers, see "Mail server
requirements".
We recommend configuring a single mail server connection with outgoing and incoming
connections.
On the mail server, administrators must first configure a master email account to receive the
email messages that Multimedia Contact Center copies. For these configuration procedures,
please consult the appropriate third-party documentation. See also the Knowledge Base article
appropriate to the server, listed below.
Note:
Using aliases or distribution groups ensures that emails sent to multiple addresses in the
contact center generate a single case number. If, instead of using aliases or distribution
groups, email addresses are associated to different mail servers, a single email sent to these
addresses will have different case numbers.
We recommend that the master account’s address is discrete from email aliases and distribution
groups, and is not associated to any queues. For information on configuring your mail server with
an email account and aliases or distribution groups, consult the following Mitel Knowledge Base
article appropriate to the server.
Note:
For Exchange Server users, Multimedia Contact Center requires that the master account
has Send As permissions to the distribution groups. See "Specifying Send As permissions in
Active Directory".
For information on configuring email workflows to route based on specific addresses, see
"Default Email Inbound workflow" and "Routing contacts with the To activity".
Once the contact center’s email client is connected to a supported server and an email account
for the contact center is created, administrators can configure the mail server’s outgoing and
incoming settings in YourSite Explorer.
Note:
Multimedia Contact Center supports the Exchange Web Services (EWS) protocol. The
EWS protocol is supported only on Microsoft Exchange and Microsoft Office 365 and on the
following servers:
Note:
Mitel is not responsible for any folder size restrictions on mail servers. If there are file size
restrictions on your mail server, it is strongly recommended that the Processed folder
created during Multimedia Contact Center mail server configuration be exempted from those
restrictions or else routing functionality may be affected.
Note that, occasionally, mail servers incorrectly mark valid emails as spam. We recommend
that administrators periodically check their mail servers’ spam folder to avoid losing important
contacts.
For information on migrating from one mail server to a new mail server, see the following Mitel
Knowledge Base article: http://micc.mitel.com/kb/KnowledgebaseArticle52085.aspx.
Note:
Integrating Multimedia Contact Center with mail servers requires SMTP and IMAP or EWS
server names and port information. Administrators must retrieve and enable this information
before configuring SMTP and IMAP or EWS connections to Multimedia Contact Center. See
the Knowledge Base article, listed above, appropriate to the server.
After adding the mail server, you must configure SMTP and IMAP or EWS connections.
a. In the From Name text box, enter the name of the sender.
b. In the From Email Address text box, enter the email address of the user.
c. In the Aliase text box, enter the secondary name of the user.
Note:
Note: Client ID, Tenant ID, Client Secret, Server, and Username, are details
provisioned by the customer.
Note:
a. The Test Outgoing Mail button is enabled only if all the mandatory fields are
entered.
b. Ensure that the Enable Incoming and Outgoing Diagnostic Connection Logs
checkbox is selected, so that is the test connection fails the diagnostic logs are
generated for debugging.
7. (Optional) Select the Enable Incoming and Outgoing Diagnostic Connection Logs
check box and click the Test Incoming Connection button. This will generate a log in
"StorageService – Office365 OAuth Connection - <From Name>.log".
Note:
• The Test Incoming Connection button is enabled only if all the mandatory
fields are entered.
• Ensure that the Enable Diagnostic Connection Logs checkbox is selected, so
that if the test connection fails the diagnostic logs are generated for debugging
a. In the From Name text box, enter the name of the sender.
b. In the From Email Address text box, enter the email address of the user.
c. In the Aliase text box, enter the secondary name of the user.
4. In the Server Information section, enter the following details.
Note:
Service Account Key is the windows file path to the private key file for your
service account that you download during service account creation.
Note:
a. The Test Outgoing Mail button is enabled only if all the mandatory fields are
entered.
b. Ensure that the Enable Incoming and Outgoing Diagnostic Connection Logs
checkbox is selected, so that is the test connection fails the diagnostic logs are
generated for debugging.
7. (Optional) Select the Enable Incoming and Outgoing Diagnostic Connection Logs
check box and click the Test Incoming Connection button. This will generate a log in
"StorageService – GmailOAuth Connection - <From Name>.log".
Note:
• The Test Incoming Connection button is enabled only if all the mandatory
fields are entered.
• Ensure that the Enable Diagnostic Connection Logs checkbox is selected, so
that if the test connection fails the diagnostic logs are generated for debugging
Configuring an SMTP connection enables Multimedia Contact Center to send outgoing mail
through a contact center’s email server. The following explains how to configure an SMTP
connection between Multimedia Contact Center and email servers. The outgoing settings you
configure are applied to any email your system sends, such as server alarms, reports, and
outgoing email interactions to customers.
For information on locating the required information from the contact center’s email server,
consult the following Mitel Knowledge Base article appropriate to the server.
If the mail server has not already been added, see "Adding mail servers".
• Specify the server information for outgoing emails
Note:
To test the connection, administrators must have an email address configured for them
in the Employees page. This email address receives notification of whether the test was
successful.
Note:
5. After Connection Timeout, type how many seconds the system has to connect to the
server before timing out.
1. After From Name, type the name that appears on outgoing mail.
Note:
This must be a valid email address. Add a queue email address that agents will select
as the ‘From’ address in email responses and outbound emails, if this queue is not
configured as an ‘Alias’ for the mail server.
Note:
• Include all queue email addresses that agents will select as the ‘From’ address
in email responses and outbound emails, if these queues are not configured as
the ‘From Email Address’ for the mail server.
• Failure to include all aliases will impact the ability of the Transfer activity to route
inbound emails to all queues when using the <<DestinationQueues>> variable.
For more information, see "Routing contacts with the Transfer activity".
Note:
3. If you want to associate additional aliases for the mail server, for each additional alias,
type the alias and click Add.
4. Click Ok
Note:
If you use Google’s 2-step verification, enter the password specific to Multimedia Contact
Center.
3. Click Save.
• Click Test Outgoing Mail. If an error message is received, verify that the Outgoing
Server, User, and Logon information is entered accurately. To troubleshoot, the default
installation location for verbose logs is C:\Users\<current user>\Documents\CCMLogs
\YourSiteExplorer.txt.
IMAP connections enable Multimedia Contact Center to retrieve messages from a specified
account on a mail server and define the folder from which Multimedia Contact Center retrieves
messages. The following explains how to configure an IMAP connection between Multimedia
Contact Center and a mail server.
For information on locating the required information from the contact center’s email server,
consult the following Mitel Knowledge Base article appropriate to the server.
Note:
• If you have not added a mail server in YourSite Explorer or configured its SMTP
settings, see "Adding mail servers", and "Configuring SMTP connections to
Multimedia Contact Center".
• If you are editing information for an existing server, select the media server and
click the ‘Incoming’ tab.
1. Select the Use TLS check box if the server uses Transport Layer Security.
2. After Incoming Server, type the server’s IP address or name.
3. After Incoming Port, type the server’s IMAP port number.
4. After Connection Timeout, type how many seconds the system has to connect to the
server before timing out.
5. After Incoming Folder, specify the email account folder from which Multimedia
Contact Center retrieves email.
Note:
If the system should retrieve email from the Inbox, leave this setting as the default. If
the system should retrieve email from a subfolder of the Inbox, specify the folder name.
Multimedia Contact Center can retrieve email from a single folder only. Ensure emails to
aliases and distribution groups are also routed to this folder.
Note:
Specifying the email account’s username and password authenticates Multimedia Contact
Center to the mail server
1. Select the Same as Outgoing Server check box if the email account logon
information is shared between the SMTP and incoming server.
2. If the logon information for the email account is discrete, enter the Username,
Password, and Domain information required to receive mail.
3. Click Save.
• Click Test Incoming Connection. If an error message is received, verify that the
Incoming Server and Logon information is entered accurately. To troubleshoot, the
default installation location for verbose logs is C:\Users\<current user>\Documents
\CCMLogs\YourSite Explorer.txt.
to retrieve messages from a specified account on a mail server and define the folder from which
Multimedia Contact Center retrieves messages.
Note:
The following explains how to configure an EWS connection between Multimedia Contact Center
and an exchange mail server.
For information on locating the required information from the contact center’s email server, see
the following Mitel Knowledge Base articles appropriate to the server.
General
Note:
• If you have not added a mail server in YourSite Explorer or configured its SMTP
settings, see "Adding Mail servers", and "Configuring SMTP connections to
Multimedia Contact Center".
• If you are editing information for an existing server, select the media server and
click the Incoming tab.
1. Select the Use TLS check box if the server uses Transport Layer Security
2. Select EWS for the Server Protocol
3. After Incoming Server, type the server’s IP address or name.
4. After Incoming Port, type the server’s EWS port number (most likely 443 if TLS is on)
5. After Connection Timeout, type how many seconds the system has to connect to the
server before timing out.
6. After Incoming Folder, specify the email account folder from which Multimedia
Contact Center retrieves email.
Note:
If the system should retrieve email from the Inbox, leave this setting as the default. If
the system should retrieve email from a subfolder of the Inbox, specify the folder name.
Multimedia Contact Center can retrieve email from a single folder only. Ensure emails to
aliases and distribution groups are also routed to this folder.
Note:
Specifying the email account’s username and password authenticates Multimedia Contact
Center to the mail server
1. Select the Same as Outgoing Server check box if the email account logon
information is shared between the SMTP and incoming server.
2. If the logon information for the email account is discrete, enter the Username,
Password, and Domain information required to receive mail.
3. Click Save.
• Click Test Incoming Connection. If an error message is received, verify that the
Incoming Server and Logon information is entered accurately. To troubleshoot, the
default installation location for verbose logs is C:\Users\<current user>\Documents
\CCMLogs\YourSiteExplorer.log.
CAUTION:
Deleting a mail server prevents emails dependent on the server from routing, including
Before deleting the mail server, we recommend first disassociating it from the email media server
several days in advance. This allows pending emails to clear the system before the mail server is
deleted. See "Disassociating mail servers from email media servers" for more information.
4. Click Save.
• A master account has been created in Exchange. This is the account from which
Multimedia Contact Center will retrieve emails
• SMTP and IMAP or EWS connections to Multimedia Contact Center are configured
• Distribution groups are created for the contact center’s service groups
Note:
If the Security tab does not display, go to View and select Advanced features.
• A master account has been created in Exchange Online. This is the account from
which Multimedia Contact Center will retrieve emails.
• SMTP and IMAP or EWS connections to Multimedia Contact Center are configured.
• Distribution groups are created for the contact center’s service groups.
$LiveCred = Get-Credential
Import-PSSession $Session
3. Enter the credentials for the Exchange Online administrator.
4. To add the Send As permission to the list
Note:
• The mail account from which Multimedia Contact Center retrieves emails supports
aliases.
Note:
Multimedia Contact Center supports non-empty Namespace IMAP providers. For information
on configuring a mail server, other than Exchange Online, Google Apps for Business, or
Exchange Server, consult the following Mitel Knowledge Base article: http://micc.mitel.com/kb/
KnowledgebaseArticle51977.aspx.
Note:
For a list of supported Exchange versions, see the MiContact Center Business and MiVoice
Analytics System Engineering Guide MiContact Center Business System Engineering Guide.
To ensure SMS interactions route to the Enterprise Server, for each SMS number associated with
your Twilio account, you must set the Request URL to the following: http://twimlets.com/. Consult
your SMS gateway service provider documentation for information on configuring your account.
SMS gateway provider SMS phone numbers are added to Multimedia Contact Center as a part of
configuring SMS media servers.
Multiple SMS numbers from an SMS gateway service provider can be added to your SMS media
server. Do the following to add Multiple SMS numbers:
When adding Twilio SMS phone numbers to your SMS media server, you require, in addition to
the SMS phone number, the Twilio Account SID and the Account Authentication Token. For more
information, see "Adding SMS to Multimedia Contact Center".
A single SMS number can be used with multiple queues, provided the SMS Inbound workflow is
modified to route SMS messages through a method other than by the <<DestinationQueues>>
variable, such as with an Ask activity. For more information on the default SMS workflow, see
"Default SMS Inbound workflow".
Administrators add media types to Multimedia Contact Center by adding and configuring media
servers in YourSite Explorer. Media servers are accessed via the Multimedia tab. Multimedia
Contact Center supports one media server for each type of multimedia. When a multimedia
media server is added to YourSite Explorer, that media type becomes unavailable in the Add
drop-down list in the Media Server tab. If you want to add a new media server of that type, you
must either delete the current media server of that type or make it historical.
Note:
When adding media servers, administrators must indicate if the contact center operates over
midnight. If not, reporting over midnight may not be accurate, and agent shifts are closed
after the last agent events before midnight. For more information, see "Extending reporting
over midnight".
New media servers are associated to the appropriate default workflows. For example, when an
administrator adds an email media server, the system automatically associates the Default Email
Inbound workflow to it. Administrators can customize these default workflows to suit the contact
center’s needs. The workflow displaying on a media server's Inbound Routing tab is associated
to that media server.
For more information on working with visual workflows and applying routing rules to interactions,
see
Response routing is configured via Response workflows, located on the Response Routing tab of
the media server.
New chat media servers are associated to a default Response workflow. Administrators can
customize this workflow to suit the contact center’s needs. For more information on the Default
Chat Response workflow, see "Default Chat Response workflow".
Default Response workflows are not provided for email or SMS media servers. Administrators
must create these workflows.
Note:
For more information on working with visual workflows and applying routing rules to interactions,
see
Note:
For information on configuring advanced options specific to email, chat, SMS, or open media
media servers, see "Configuring Advanced options for email media servers", "Configuring
Advanced options for chat media servers", and "Configuring Advanced options for SMS
media servers"
Note:
This option determines, for real-time purposes, how frequently the system generates a queue
statistics record.
Note:
The option enables administrators to control whether agents can preview interactions that are
in queue or ringing in the Inbox.
If this option is selected, the system automatically closes and re-opens agent shifts at midnight.
All agents remain logged into the system. Agent shift reporting is uninterrupted over this period.
If this option is not selected, the system closes agent shifts after the last agent event before
midnight. The system re-opens agent shifts after the first agent event after midnight. All agents
remain logged into the system. Agent shift reporting is not extended between the time agent
shifts close and the time they re-open.
Note:
Contact centers operating over midnight and rebooting their servers overnight should consult
the following Mitel Knowledge Base article, to enable agents to retain their states post-
reboot: http://micc.mitel.com/kb/KnowledgebaseArticle52046.aspx
Administrators can set the MKB and DND timers to begin as soon as the agent enters MKB or
DND.
Note:
Personal reply templates are not Global reply templates.
If your looking personal reply templates see Configuring reply templates for email, chat, sms, and
open media.
Email templates must be in .msg or .txt format, and .msg email templates may contain images.
Do not copy content containing images in .msg files directly from Outlook. Save this content
as .msg files in the Reply Templates folder and leverage from there. Chat and SMS;templates
must be in .txt format. Chat and SMS share templates.
Administrators store templates in either the default template folder created during installation, or
in a folder on a network share. A network share is required if agents are permitted to create and
modify templates and therefore must access them.
The default Reply Templates folder created during installation is located at <installation drive>:
\<installation folder>\Templates\ReplyTemplates. This folder contains the subfolders Email, Chat,
and SMS in which there are sample templates for the corresponding media type.
If agents are permitted to create and modify templates, administrators must create a folder in
network share to house the sample templates. We recommend that you create a folder structure
to organize the templates by media type and area of business. By default, the server points to
the default Reply Template folder created during installation. The administrator must ensure that
media servers point to the folder that they created on network share instead of the default Reply
template folder.
To point the media server to a folder on a network share, complete the following procedure.
Note:
Everyone' and/or 'Users' permissions are required for the folder in which the reply templates
are stored. If the you have permissions for the reply template files, but do not have
permissions to folder in which the reply templates are stored, YourSite Explorer displays an
error.
If templates are housed on a network share, you must perform the following:
• Configure identity settings for the CCMWa, MCCWa, and MiCCSDK web applications
• Configure security permissions for CCMWa, MCCWa, and MiCCSDK
• Point the media server to a network share folder
To configure identity settings for the CCMWa, MCCWa, and MiCCSDK web applications
Note:
7. Click OK.
8. In the Advanced Settings window, under Process Model, set the value for Load
User Profile to True.
9. Click OK.
10. Repeat the above steps for MCCWa, and MiccSDK.
Alternatively, enter the path in the Location field and click the Browse button. This redirects
the Browse dialog to the specified path.
3. Navigate to the network folder housing the templates and click OK. Alternatively, type
the network share folder path in the Location field.
Note:
• Only network share folder paths are supported. For example, the folder path
should look like \\ServerName\SharedFolderName. Standard paths are not
supported.
• To point the server back towards the default folder, delete the network share
path.
4. Click Save.
Global Reply Templates may be managed by supervisors depending if the May see all queues
check box is selected in the advanced tab of the Supervisor's Employee record in YSE
• If May see all queues check box is not selected, supervisors can see only templates
that are not associated to any queue or templates that are associated to queues that
the supervisors are allowed to see.
• If May see all queues check box is selected, supervisors can see all templates.
Note:
Agents cannot like or add warnings for templates, Supervisors cannot dislike
templates.
Supervisor can Search, Add, Edit, or Delete Global Reply Templates in Web Ignite.
Note:
During a system upgrade, old templates present in the system (in the form of txt or msg files)
are migrated to the new format. When that happens, the path of the old template is used to
created tags. For example, if an old template was found under the “English\Support” directory
structure, the tags will be “English > Support”.
If there is more than one listed template, by default it shows in descending order based on date
modified. You can display results by the date, question/concern, Media, and Tags. If there are
more than 10 templates listed, then click Show more button to see more templates.
The Search textbox allows you to search for templates (matching keywords found in either the
Question/Concern, template, or tags). The results are displayed in the paged list.
Do the following:
1.
Click icon to add new templates.
2. Optionally, add tags and select a media.
3. Optionally, click Associate to associate queues to new templates.
Note:
Templates that are associated with queues can be seen only by agents who are
assigned to these queues.
6. Click Save.
Note:
If you enter a search keyword before creating a new template, and that search
keyword doesn't match the Question/Concern, template or tags in the new
template you're creating, After you save, you will not find that template in the list
(you must first remove the search string before you see that new template in the
list).
If you select a template to edit, you will see two tabs as described below:
• Details tab - Allows you to add tags, media, question/concern, and the template
content with text.
• Queues tab – Displays the queues associated with that template. Click Disassociate
button to dissociate a queue if needed, and Click “Associate" button to associate new
queues.
Note:
• If queues are specified, only agents associated with those queues will be able
to see those templates in their inbox.
• You can see only queues that you are associated with if the new May see
all queues check box is not selected in the advanced tab of the supervisor's
Employee record in YSE.
If there were no associated queues or if you disassociate all the queues a warning "No queues
are associated with this global reply template: all agents will have access to it" is displayed
and if you associate at least one queue, the warning displayed above disappears.
Click the "Delete" icon to delete the reply template. You will see a warning message to
confirm or cancel the delete action.
• If the deleted template was linked to an interaction, you can convert the interaction
again to a template. This interaction does not remain in a disliked state.
• If the deleted template was linked to a case, you can convert the case again without
seeing a warning about the fact that a template already exists. This case remains in a
disliked state because the case could have been disliked using the dislike button.
Click this icon to save your changes to the template. You can save your changes to the
template for the following actions:
• adding/removing tags
• updating the "Question/Concern" text
• updating the template text
• updating the media
• associating or dissociating any queue
Note:
Supervisor can convert a multimedia interaction into a Global Template. This is allowed for
Handled Chats or SMS and for Sent emails but not for Handled Emails.
1.
Go to Web Ignite > History section, select a valid interaction, then click icon in the
Chat, SMS or Email tab.
• For Email Interaction: You will see Customer Question/Concerns and Response.
• For Chat and SMS: You will see Customer Question/Concerns and Response with
a check box to include each section in Final Template.
2. Click Next.
Note:
You must select at least one Question/Concern and one response, else you will
not be able to click Next.
Supervisor can convert Notes into a Global Reply Template, if the case has at least one user note
set. If the "Customer Questions/Concerns" field is not set the Notes cannot be converted to Reply
Template.
1.
Go to Cases, select a case and in the Notes tab, click icon.
2. Select one Question/Concern and a Note, Click Next.
3. Preview the entered content.
4.
Optionally, you can add Tags, click icon and enter required tags.
5. Click Save and click OK.
Note:
• Conversation Detail reporting is available for email, chat, SMS, and open media
only. Multimedia Trace reports provide commensurate data on voice, email, chat,
SMS, and open media.
• After enabling Conversation;Detail reporting, data must be summarized for the
applicable date ranges.
Conversation Detail reports illustrate, by device, how interactions transition through your system
and provide a high-level view of how customer interactions were handled. For more information
on Conversation Detail reporting, see the reports guide appropriate to your MiContact Center
BusinessMicrosoft Skype for Business licensing level.
To populate Conversation Detail reports with data, you must enable Conversation Detail reporting
for the media server.
Administrators can add only a single email media server to YourSite Explorer. Before deleting an
existing media server, see "Deleting multimedia media servers" for important information.
Note:
See below for the corresponding procedures. To disassociate mail servers from the email media
server, see "Disassociating mail servers from email media servers".
• Click the Multimedia tab and select Media servers > Add > Email.
1. Select the email media server and click the General tab.
2. Type a Name to identify the server for management and reporting purposes.
Note:
The Media Server ID;field is populated with a unique number after the media server is
saved.
3. After Site, click the Browse button and select the media server’s location.
To apply inbound routing rules to contacts retrieved from the email server
1. On the General tab, after Mail Server(s), click the Browse button.
2. Select any email accounts to associate to Multimedia Contact Center and click OK.
Note:
All outgoing email is sent through these accounts, and the system retrieves emails from
the accounts' associated Inboxes.
3. Click Save.
Note:
Using aliases or distribution groups ensures that an email sent to two contact center
addresses will share the same case number. A single email sent to addresses on different
mail servers will generate different case numbers. For more information, see "Integrating
Multimedia Contact Center with mail servers".
Note:
• This option must be enabled for preferred agent routing to function. See "Routing
contacts with the Offer to Preferred Agent activity".
• This option must be enabled to search contact history by case in Ignite.
1. Click YourSite > Media servers and select the email media server.
2. On the General tab, after Mail Server(s), click the Browse button.
3. Select the check boxes beside the mail servers to be disassociated from the email
media server.
4. Click OK.
5. Click Save.
Note:
If you are using Contact Center Messenger Chat, for more information see "Adding Contact
Center Messenger to Multimedia Contact Center"
Adding chat enables Multimedia Contact Center to route chat sessions to the appropriate queues
and agents. The chat media server resides as a service within the CCMWa web application,
which is used to manage chat sessions and is automatically installed on the Enterprise Server at
http://<Enterprise Server>/CCMWa (visible in a chat server’s ‘Internal URL for chat root’ field).
To offer chat, the chat media server requires that a reverse proxy be set up to offer CCMWa from
the Enterprise Server to the contact center’s web server. A chat media server can be added and
configured and be tested internally without a reverse proxy by using the Internal URL for chat root
as the External URL for chat root, but it will not be available for a contact center’s customers. For
information on offering chat, setting up reverse proxies, and configuring chat request and chat
session settings, see "Enabling chat". For information on setting up CCMWa with a reverse proxy,
see "Publishing Chat and Contact Us to the Internet using reverse proxies".
CCMWa is made available from the Enterprise Server to the contact center’s web server through
a reverse proxy. Before adding the chat media server to Multimedia Contact Center, you must
have first set up the reverse proxy for http://<enterprise server>/CCMWa. This external-facing
URL must be entered in the ‘External URL for chat root’ field, which validates the URL and
confirms that the reverse proxy has been applied correctly. Valid URLs are confirmed with a
green checkmark icon. Invalid URLs are indicated with a red X icon. URLs that the system cannot
confirm are marked with a question mark icon.
See "Extending reporting and agent shifts over midnight" and "Specifying when Make Busy
and Do Not Disturb timers begin".
• Specify advanced configuration options for chat servers, such as enabling alarms and
configuring reporting intervals for queues
• Click the Multimedia tab and select Media servers > Add > Chat.
Note:
Default Inbound and Response Chat workflows are assigned to the server. Modify these
workflows to specify routing rules for the contact center. See "Default Chat Inbound
workflow" and "Default Chat Response workflow".
To specify the chat media server’s name, site, external URL for chat root, Auto Response
Username, and configure default workflow email activities
Note:
To distinguish between the various types of media for management and reporting
purposes, you must give each media server a unique name when setting up your site.
2. After Site, click the Browse button to select the site where the chat server resides.
The External URL for chat root is the URL used with the reverse proxy to make chat externally
available. Valid URLs are confirmed with a green checkmark icon. Invalid URLs are indicated
with a red X icon. URLs that the system cannot confirm are marked with a question mark icon.
Note:
The Invalid URL icon may display until a complete and valid URL is entered.
4. After Auto Response Username, enter the name to be used for sending automated
messages to contacts.
5. Click the Inbound Routing tab and add an SMTP and To: email address destination for
all email activities in the workflow.
Note:
By default, employees are identified by their first name (as configured in the Employee
device page in YourSite Explorer) in chat sessions. If employees have nicknames
associated with them in their Employees entry, these can be used instead.
• Set the amount of time a closed chat session can remain idle before being terminated
Note:
If customers accidentally exit the browser or close the chat window, this configuration
determines how long they have to return to the live chat session. Customers can re-
access the session by returning to the business site and re-entering the chat request.
For more information on reply templates, see "Configuring response templates for email and
chat".
1. Select the chat media server and click the Advanced tab.
2. Select the Use agent nickname for public interaction check box.
Employee nicknames are configured in Multimedia > Employees in the Profile tab.
3. Click Save.
To configure how long closed chat sessions remain idle before being terminated
Note:
If customers accidentally exit the browser or close the chat window, this configuration
determines how long they have to return to the live chat session. Customers can re-access
the session by returning to the business site and re-entering the chat request
1. Select the chat media server and click the Advanced tab.
2. After Terminate closed chat sessions that are idle for longer than the specified
minutes, set the number of minutes.
Note:
For Contact Center Messenger Chat media server, you can set the number of minutes to
0 which specifies the session is disabled or to 10 minutes or higher.
3. Click Save.
1. Select the chat media server and click the Advanced tab.
2. After Location, click the Browse button.
3. Select the folder and click OK.
Note:
The reply template folder must be located on a UNC (Universal Naming Convention) path,
also known as a shared network path.
Amongst the various Unified Communication (UC) features, the MiContact Center Business
Chat feature (which includes sync across devices, file transfer, group chat) will be available to
existing MiContact Center Business chat users through CloudLink. This feature will be referred to
in MiContact Center Business as Contact Center Messenger.
With the introduction of Contact Center Messenger, two modes of UC chat are available for all
existing MiContact Center Business users: the legacy MiContact Center Business Chat and the
CloudLink Chat Customers need to adapt to whichever, legacy MiCC-B Chat or CloudLink Chat,
is configured on their system.
Note:
Once the legacy chat media server is converted to CloudLink- based Contact Center
Messenger, you cannot revert to the legacy chat media server.
Contact Center Messenger simplifies the deployment of chat support in Contact Center's
websites.
The Contact Center Messenger UI is powered by the custom chat component. The UI supports
several new features for sending, receiving, and displaying messages.
Note:
At a time, either Legacy MiContact Center Business chat or Contact Center Messenger chat
will be enabled.
MiCC-B has developed an internal web app called CloudLinkProxy. This app helps MiCC-B to
communicate with CloudLink. CloudLinkProxy is installed by the MiCC-B installer during fresh
installations or upgrades. If you uninstall MiCC, the MiCC installer removes CloudLinkProxy.
MiCC-B installer will install CloudLinkProxy only if the multimedia feature is enabled.
Note:
When you use Contact Center Messenger, all traffic is initiated as outbound. If you are
locking out Internet access from the server and\or clients, you may need to enable the
following connections.
• Configuration Prerequisites
• Network View
• CloudLink Chat Integration
For more information about CloudLink, see CloudLink Gateway User Guide.
On the CloudLink Accounts Console, the Mitel partner or counterparts can create customer
accounts for the MiCC-B users and specify administrators for these accounts. An account
administrator can add, delete, or edit users’ information in the customer account. For enabling the
chat integration, a MiContact Center Business administrator must have administrator rights on a
CloudLink account.
Following is a brief description of the procedure that a Mitel channel partner follows to create
CloudLink accounts and account administrators.
Note:
If you do not see the CloudLink Accounts Console, please contact
[email protected].
Important:
You must enable Delegated Authentication, Allow Guest Access, Enable MiCC
settings while creating the customer account on CloudLink, this will integrate CloudLink
with MiCC-B.
3. Select the user, click the Account Admin button to create an account administrator
for the customer account. Multiple administrators can be created for the same
account.
Note:
4. A welcome email, with the account administrator’s log-in credentials is sent to each
account administrator. Account administrators must verify their name and set a
password by clicking Finish building your account link in the email body.
5. The MiCC-B administrator must use the credentials provided in the welcome email to
access MiCC-B Auth Portal and to activate the Cloudlink integration.
Note:
You can either create a new Embedded Chat by clicking the Create button or clone an existing
Embedded Chat by clicking the Clone icon.
Note:
Chat overlay fields do not accept any size values that are out of range; that is, zero
or negative values. Chat sizes are only considered for Overlay chats and not for
Popup chats (see Step 11)
Note:
Chat options labeled with (popup) will not consider the Overlay sizes configured in
Step 8.
12. (Optional) Recaptcha. This is a free service that uses advanced risk analysis
techniques to tell humans and bots apart. This option is enabled by default when
creating a new embedded chat.
13. (Optional) Chat Options. By default, the below settings are not enabled.
• Enabling chat debug logging: This setting is to turn on debug logging on the
customer browser when accessing the embedded chat.
• Allowing file transfers on the customer side: When Enabled, this allows
customers to upload files into the chat conversation.
14. To set chats based on MiCCB availability or Queue Presence; select MiCC Options,
toggle Check MiCC server availability and Check queue availability button to on or
off based on your choice
By default, they are disabled for new chats and enabled for existing chats. For chats outside
the queue's schedule and if the same option is checked in CC-Admin, then you can start live
chats by clicking Start Live Chat and entering the queue details in the Edit Queue options.
15. (Optional) Chat Pre-Route Greeting. This is an optional message which will inject
a message into the chat stream immediately before the chat is routed to the MiCC
Business enterprise server. It will appear as a System message.
16. Enter a value for the Message for MiCC overloaded field. This is the message that
will be displayed when the CloudLinkProxy is down or if we have hit the maximum
capacity of concurrent chats the system can handle.
17. (Optional) Click Add on the Contact Us Options and enter details of Phone, Email
and SMS.
18. (Optional) Click the Add on the Chat Overlay fields and enter the fields that you would
want to reflect on the Live Chat Page. You can set the following fields.
• Visible or Hidden
• Required or Not Required
For phone number predefined phone number field is added to facilitate the customer with a
built in phone number form fields that will help ensure a valid phone number is entered.
19. (Optional) Click Queue Options and enter the required queue information.
Note:
If the default queue field is not provided or the user is not allowed to pick a queue, then
the inbound chat workflow on MiCC needs to be configured to route to a specific queue
as using <Default Queue> which doesn't work if no queue information is passed from the
chat overlay.
Note:
The Start Live Chat button appears if at least one visible field is configured in Chat
Overlay script
Before you configure Embedded Chat with Google AI enabled, you must configure a GCP
account and enable Dialogflow. You must configure the Dialogflow bot to interact with the
customer.
Following is the complete procedure for configuring Embedded chats with Google AI.
• Enabling Agent Assist allows the suggestions panel to be displayed on the Ignite
screen.
Note:
Before enabling the Google AI, you must ensure that your Mitel Channel partner
has an authorized partner agreement signed which states that the mandatory
services engagement for onboarding/activation has been followed and the
customer has signed a subscription for virtual Agent/Agent Assist capabilities. For
more information, you must contact your Mitel contact center sales specialist.
6. Enter the Google project details that you have created while configuring the GCP
account for the customer. Enter the google project ID and service account name and
click Create Project.
7. Enter a name for the Google Bot and click Assign bot name button. The Google Bot
name will be displayed when the Google Bot interacts with the customer in the chat.
8. If Agent Assist is enabled.
• If you enable the display suggestions for agent messages option, it will display
suggestions for messages typed by the agent (also, for the customer).
• In the Setup Conversation Profile section, you can configure whether the Article
source, FAQ source, or both will be displayed in the suggestions panel in Ignite.
• To add an Article source:
Confidence threshold allows you to control which suggested articles are displayed for
a conversation depending on the scores Agent assist has assigned for the articles. The
articles for which the score is equal to greater than the value you select will be displayed
and the other articles will be dropped.
Note:
If you do not turn on the Specify Confidence Threshold option, none of the suggested
articles will be dropped.
Note:
If you select a type of Knowledge base that has a combination of FAQ and Article
suggestions type documents in it, then only the article suggestions will be considered.
Note:
If you select a type of Knowledge base that has a combination of FAQ and Article
suggestions type documents in it, then only the FAQs will be considered.
Note:
Chat overlay fields do not accept any size values that are out of range; that is, zero
or negative values. Chat sizes are only considered for Overlay chats and not for
Popup chats (see Step 14)
Note:
Chat options labeled with (popup) will not consider the Overlay sizes configured in
Step 11.
15. (Optional) Recaptcha. This is a free service that uses advanced risk analysis
techniques to tell humans and bots apart. This option is enabled by default when
creating a new embedded chat.
16. (Optional) Chat Options. By default, the below settings are not enabled.
a. Enabling chat debug logging: This setting is to turn on debug logging on the
customer browser when accessing the embedded chat.
b. Allowing file transfers on the customer side: When Enabled, this allows
customers to upload files into the chat conversation
17. To set chats based on MiCCB availability or Queue Presence; select MiCC Options,
toggle Check MiCC server availability and Check queue availability button to on or
off based on your choice.
By default, they are disabled for new chat and enabled for existing chats. For chats outside
the queue's schedule and if the same option is checked in CC-Admin, then you can start live
chats by clicking Start Live Chat and entering the queue details in theEdit Queue options.
18. (Optional) Chat Pre-Route Greeting. This is an optional message which will inject
a message into the chat stream immediately before the chat is routed to the MiCC
Business enterprise server. It will appear as a System message.
19. Enter a value for the Message for MiCC overloaded field. This is the message that
will be displayed when the CloudLinkProxy is down or if we have hit the maximum
capacity of concurrent chats the system can handle.
20. (Optional) Click Add on the Contact Us options and enter details of Phone, Email,
and SMS.
21. (Optional) Click Add on the Chat Overlay fields and enter the fields that you would
want to reflect on the Live Chat page. You can set the following fields.
• Visible or Hidden
• Required or Not Required
For phone number predefined phone number field is added to facilitate the customer with a
built-in phone number form fields that will help ensure a valid phone number is entered.
22. Click Queue Options and enter the required queue information.
23. Click Save.
24. On the Embedded Pages, the new Chat is listed.
25. Click on Copy to Clipboard icon to copy the script.
26. Paste the script inside script tag under the head section of the webpage.
Note:
The Start Live Chat page appears if at least one visible field is configured in Chat Overlay
script.
4. Enter the username and password and click the log in button.
Note:
5. On successful log in, the YourSite Explorer displays the Disconnect button.
Note:
Note:
Users must have a valid email address before enabling the Contact Center Messenger Media
Server.
1. In YourSite Explorer, go to Media servers and create a new chat media server.
For more information on adding a chat media server, see MultimediaContactCenter Installation
and Deployment Guide.
2. Select the Enabled for CloudLink check box to enable chat media for CloudLink.
After the Enabled for CloudLink check box is selected, the External URL for Chat root and
Internal URL for chat root fields are not displayed. These fields are displayed only when the
Enabled for CloudLink check box is cleared.
Note:
• The Enabled for CloudLink check box is grayed out after you save the chat
media server configuration.
• Once the Contact Center Messenger is enabled, the existing CCMWa chat media
server stops functioning.
The administrator can enable CloudLink for an existing CCMWa chat media server. The
administrator can use the Enable For CloudLink button, which is available when MiCC-B is
connected to CloudLink to convert the existing CCMWa chat media server to CloudLink chat
media server.
Following is the procedure for an administrator to convert CCMWa Chat media server to
Cloudlink Chat media server:
Note:
The Enable For Cloudlink button is available only if MiCC-B is connected to Cloudlink.
3. Click OK to confirm.
YourSite Explorer checks the CCMWa for active chats in the IVR, and chats in queue, in an
inbox, or on hold.
YourSite Explorer terminates the process if there are any active chats in the IVR, or chats in
a queue, in an inbox, or on hold. The administrator is notified that the active chats must be
cleared before the conversion can be processed.
After the chats are cleared, YSE converts the media server, queues associated with the media
server, and the employees who have active real time agents associated with the media server.
After completion of the process, a pop-up dialog opens confirming that the existing CCMWa
chat media server is converted to Cloudlink chat media server.
Click the Disconnect from CloudLink button to terminate the connection between the CloudLink
platform and the MiCC-B. The CloudLink Client is logged out and CloudLink features are disabled
for all the users.
After CloudLink is successfully disconnected, the CloudLink tab again displays Connect from
CloudLink button.
Administrators may add only a single SMS media server to YourSite Explorer. Before deleting an
existing media server, see "Deleting multimedia media servers" for important information.
Optionally, SMS handling for agents in Ignite can be modified through editing JavaScript files.
See "Configuring the agent configuration JavaScript file".
Note:
SMS media servers must use a single Twilio account. For more information, see "Integrating
Multimedia Contact Center with an SMS Gateway Provider".
See "Configuring Advanced options for media servers" and see "Configuring Advanced
options for SMS media servers".
• Specify Data Summary options, such as indicating that the contact center operates 24
hours a day.
See "Extending reporting and agent shifts over midnight","Specifying when Make Busy and Do
Not Disturb timers begin", and "Enabling Conversation Detail reporting".
Note:
Default Inbound are assigned to the server. Modify these workflows to specify routing
rules for the contact center. See "Default SMS Inbound workflow".
Note:
The media server ID field is populated with a unique number after the media server is
saved.
2. After Site, click the Browse button to select the site where the SMS server resides.
3. Click Save.
1. In the General tab, after SMS Provider, click the Browse icon.
2. Click Add.
3. Enter a Name for the SMS Provider.
4. Enter the PhoneNumber (including country code) for the Twilio SMS phone number.
Note:
5. If this SMS number handles inbound SMS interactions, set Retrieve incoming SMS
messages to True.
6. If this SMS number only sends outbound SMS messages, set Retrieve incoming
SMS messages to False.
7. Enter your Twilio AccountSid.
8. Enter your Twilio Authentication Token,
9. After Days to Search, set how many days back Twilio will check for new SMS
interactions.
1. In the General tab, after SMS Provider, click the Browse icon.
2. Select the SMS Provider and click Edit.
3. Modify the settings.
4. Click Save.
5. Click OK.
6. Click Save.
1. In the General tab, after SMS Provider, click the Browse button.
2. Clear the checkbox beside the SMS Provider.
3. Click OK.
4. Click Save.
• Set the amount of time an SMS session can remain idle before being terminated.
Note:
This configuration determines how long a customer or agent cannot participate in an SMS
session before the system ends the SMS session. Customers can continue their SMS
interactions with an agent by sending a new SMS interaction to the contact center.
For more information on reply templates, see "Configuring response templates for".
To set the amount of time an SMS session can remain idle before being terminated
1. Select the SMS media server and click the Advanced tab.
2. After Terminate SMS sessions idle for longer than the specified minutes, set the
amount of time an SMS session can remain idle.
3. Click Save.
1. Select the SMS media server and click the Advanced tab.
2. After Location, click the Browse button.
3. Select the folder and click OK.
Note:
The reply template folder must be located on a UNC (Universal Naming Convention) path,
also known as a shared network path
4. Click Save.
Administrators can only add a single open media media server to YourSite Explorer. Before
deleting an existing media server, see "Deleting multimedia media servers" for important
information.
Note:
The media server ID field is populated with a unique number after the media server is
saved.
2. Beside Site, click the Browse button to select the site where the Open Media media
server resides.
3. Click Save.
Note:
You can also access the API Documentation at any time by entering the following into
your browser: <ServerIP>/miccSdk/help.
When an employee reaches their maximum Workload for a media type, their agent is put into
Make Busy with the Overloaded reason code. When an employee is Overloaded, the employee
will not be offered inbound interactions for that media type. This state is automatically removed
when they are no longer at their maximum Workload. Employees in Ignite who have reached
their maximum concurrent interactions in one type of media are still able to pick interactions from
the corresponding media’s queues and receive transfers from other agents.
A default Workload is provided with Multimedia Contact Center. The default Workload can be
modified, but not deleted. The followinf figure shows the default Workload.
Administrators can create Workloads and assign them to employees as necessary. There are two
areas of configuration required for Workloads for each media type:
Note:
• Agents can still pick and receive transferred interactions of the disallowed media
type.
• If you do not want agents to receive multiple ringing interactions of different
media types, configure this option
Note:
1. Click Add.
2. Type a Name for the Workload.
3. To apply the Workload to outgoing voice calls, select Apply rule to outgoing voice
calls.
4. For each media type, under Concurrent contacts, select the maximum number of
connections of that media type that can be handled concurrently.
5. For each media type, click the icons of the media you do not want employees to
concurrently handle when handling that type of media.
6. Click Save.
1. Select a Workload
2. When you are done modifying the Workload, click Save.
To delete a Workload
For more information on employee licensing or for instructions on creating new employees in
YourSite Explorer, consult the "Adding employees".
Voice
Chat
SMS
Open Media
Note:
Employees must be licensed to handle non-voice media. See "Licensing requirements for
employee multimedia capabilities".
When you remove the employee's ability to handle non-voice media, the employee's agents are
made historical. Historical agents are disabled for real-time monitoring and data collection. If
the employee is re-enabled to handle that non-voice media, then their agent will be made active
again. Multimedia agents can be deleted to be removed entirely from the system.
Note:
Failover media servers for voice agents must be configured on your telephone system and
synchronized into YourSite Explorer. Workgroup does not support Contact Center resiliency.
You cannot program failover media servers for ACD agents and extensions.
A voice agent and extension are automatically created for the employee.
By default, the extension type is voice softphone, which emulates a 5020 IP set.
By default, the extension reporting number/dialable is populated with the employee’s business
phone.
3. Optionally, change the agent’s First name.
4. Optionally, change the agent’s Last name.
5. Optionally, after Agent login ID, enter the reporting number for the voice agent.
6. After Media server, click the Browse button.
7. Select a media server and click OK.
8. If you want to disable real-time monitoring and data collection for this agent, select
Disable real-time monitoring and data collection on this device.
9. If a 3300 media server was selected, after COS, select a Class of Service from the list.
10. If a 3300 media server was selected, optionally, after COR, select a Class of
Restriction from the list.
• Make the device historical—sets the agent as historical, but leaves it associated
to this employee
• Disassociate the device—disassociates the agent so it can be used with another
employee
• Remove the device from the system—deletes the agent
4. Click OK.
5. Click Save.
1. Select an employee.
2. Under Devices, click the media button to select which media this employee can
handle.
3. Click Save.
1. Select an employee.
2. Under Devices, click the enabled media button.
3. Click Save.
1. Select an employee.
2. Click the down arrow beside the media button and click Delete.
3. Click Save.
Note:
Alternatively, if you want to create a new Workload to associate to the employee, click Add.
4. Click OK.
5. Click Save.
Note:
If you do not want agents to receive multiple ringing interactions of different media types,
configure this option.
8. Click Save.
To delete a Workload
Note:
Note:
• If the May see all queues check box is not selected for a supervisor, then in Web
Ignite, the supervisor can view only the queued interactions, historical interactions,
and cases that the supervisor is associated with.
• It is strongly recommended to program at least one supervisor who can see all
queues so that outbound interactions that could not be sent or have bounced will
be detected when the agent is not available to handle.
3. On the Membership tab, under Available members, select an employee and click >
to move the employee to the Selected members list.
4. Click Save.
Voice and multimedia agent IDs are added in the Employee section of Multimedia Contact
Center. To add different media agent IDs to an employee, see "Managing the media types an
employee can handle". Voice agents can be created in the Agent section of Multimedia Contact
Center, but it is recommended to create agents within the Employee section. The Agent section
also enables administrators to delete agent IDs. Deleting an active multimedia agent removes an
employee's capabilities to handle the corresponding media. Historical multimedia IDs can only be
deleted in the Agent section.
3. If you want to associate the new voice agent ID to an employee, click the Browse
button after Employee.
Selecting an employee will automatically fill in the First name and Last name fields with the
employee’s name.
4. Type the voice agent ID's First name.
5. Type the voice agent ID's Last name.
6. After Agent login ID, enter the reporting number for the voice agent ID.
7. After Media Server, click the browse button.
8. Select a media server and click OK.
9. Click Save.
Note:
The Disable real-time monitoring and data collection on this device check box is
automatically selected if the employee that is associated to this agent has their licensing
attribute set to 'None'.
Workgroup does not support Contact Center resiliency. You cannot program failover media
servers for ACD agents and extensions.
7. Click Save.
5. After External dialing number, type the dialing number for the device to which calls
will be routed.
6. Click Save.
To delete an agent ID
When agent groups are created, an employee’s agents are assigned a default group presence,
either Present or Absent. An additional default group presence option (Last Known) is available
for the voice agents on MiVoice Business platform. Employees whose agents’ default presence
is Absent will not be present in the agent group after logging in their agents. To handle that media
type, the employee must change their agent state manually in Contact Center Client or Ignite.
Employees whose agents’ default presence is Present will be present in the agent group when
they log in.
Note:
• If you attempt to add a group to YourSite that is already in the database the system
notifies you that the group is already present. When you add a series of groups
to YourSite, such as Agent Groups 1 to 5, if the system detects you have already
added Agent Group 3, then it will not add Agent Group 3 or any subsequent agent
groups in the series (that is, Agent Group 4 or 5) to the database.
• Deleting an agent group that is currently the last member of a voice or multimedia
queue will invalidate that queue. Deleting an agent group that is associated to an
activity in an Inqueue workflow will create a validation error. The queue will not be
able to be saved until another agent group is associated to it. It is recommended
that you disassociate agent groups from queues and their associated Inqueue
workflows before deleting the agent group.
• If you want to remove Voice handling from an agent group previously enabled to
handle Voice, you must delete the agent group, writeback the deletion to the voice
media server, and then recreate the agent group.
1. Click Add.
2. Type a Name for the agent group.
3. Type a Reporting number for the agent group.
Voice
Chat
SMS
Open Media
5. If you select voice media and have multiple voice media servers, select the voice
media server and click OK.
Note:
If this agent group is not handling voice interactions, then this option will not be available.
6. Click Save.
Some employees may have multiple voice agents associated to them. When these are added to
an agent group, they are highlighted in yellow. Administrators can select which of an employee’s
voice agents are in the agent group. It is recommended that an employee only have one voice
agent associated to an agent group.
3. Select the employees to add to the agent group and click OK.
4. Click Save.
• Absent—the employee’s agent ID will be put into the Logged in Not Present agent
state when they join the agent group.
• Present— the employee’s agent ID will be put into Idle when they join the agent
group.
3. Repeat Step 2 for each media type the member can handle in the agent group.
4. Click Save.
For information on configuring employees, see the MiContact Center Business Installation and
Administration Guide MiContact Center Business for Microsoft Skype for Business User Guide
"Adding employees".
3. When you are done editing the employee, click Save.
To remove a member
Workgroup does not support Contact Center resiliency. You cannot program failover media
servers for ACD agents and extensions.
4. Specify if the agent group uses skills and if calls are to be queued to the agent group
when no agents are logged in.
5. Click Save.
It is recommended that new queues be configured in this order. New queues cannot be saved
until after the primary agent group and overflow agent groups have been assigned in the Inqueue
workflow. See Configuring multimedia queue membership and routing.
Note:
Note:
For email queues not automatically requeuing interactions on agent logout, emails are put
on hold until the agent logs back in and removes hold. Once the hold requeue time expires,
interactions are requeued whether the agent is logged in or not.
Note:
For Unified queue groups, when the reporting number is the same for all queues in the
group, the queue ID must be entered in this field instead of the queue reporting number.
4. The Members field is auto-populated after an agent group has been added as a
destination to the Inqueue workflow. Clicking the link opens the applicable agent group
page, enabling you to make changes or view the configuration.
5. For Email queues, after Email address, click the Browse button.
6. Type the queue's email address and click Add.
The Email queue’s email address identifies the queue to which the system will route the email.
The email address can correspond to an email address included in a mail server distribution
list or it can be internal to the Multimedia Contact Center. For information on configuring mail
servers, see "Integrating Multimedia Contact Center with mail servers".
Note:
information about adding aliases to the mail server, see "Configuring SMTP
connections to Multimedia Contact Center".
7. If you want to associate additional email addresses to the email queue, for each
additional email address, type the address and click Add.
Alternatively, to import all of the email addresses and aliases associated to the mail servers
associated to your enterprise, click Pull From Mail Server(s).
The first email address in the list is always considered the primary email address for the
queue that is used as the From address when an agent responds to an email address in this
queue. Each subsequent email address is considered an alternative email address.
You can adjust the order of the email addresses by selecting an address and clicking the Up
and Down buttons.
8. Click Ok.
9. For Chat queues, type a Username.
The Chat queue’s auto response username is used with workflow activities that provide
automated responses to interactions in queue.
10. For SMS queues, type a Phone number.
SMS numbers must not use dashes or parentheses and must include both a country and
area code. SMS queues can only have one SMS phone number associated to them. An
SMS;number can be used for multiple queues, with some restrictions. For more information,
see "Integrating Multimedia Contact Center with an SMS Gateway Provider".
11. If you do not want the queue to be viewed in Contact Center Client and Ignite, select
Disable real-time monitoring and data collection on this device.
12. Click Save.
If your default Inqueue workflow uses Email activities as auto responses, you will need to specify
the SMTP servers as well. The default email messages assigned to Email activities in the
Inqueue workflow should be reviewed and customized as required. After assigning agent groups
in the Inqueue workflow, administrators can review them in the General tab. Agent groups are
listed, in the order from the Inqueue workflow, in the Members field. Administrators can click the
name of the agent group to open that agent group’s page in YourSite Explorer.
Once you have configured your Inqueue workflow, you must enable validation for the workflow.
Validation prevents workflows with invalid or incomplete configuration from being used.
If you have an existing Inqueue workflow you would like to use for routing, you can assign
it to the queue from Workflows. For information on assigning Inqueue workflows to queues,
"Associating workflows to queues".
For more information about the Default Inqueue workflows, see "Multimedia Contact Center
default workflows".
To apply the business hours to all queues on the same media server
1. Select a queue and in the ribbon, click the Queue Tools tab.
2. Select Apply business hours to all.
Note:
When 'Include queue work timer as part of handling time' is enabled, the ACD handling
time durations for reporting purposes span from ACD pick up to the end of the Work Timer
time.
When this option is disabled, the ACD handling time duration spans from ACD pick up to hang
up.
3. To enable the queue for Work Timer, select Use Queue Work Timer and set the
duration of Queue Work Timer.
4. Click Save.
For example, type 3 to define a short handle call as one that lasts less than 3 seconds. Short
talk calls are included in call statistics.
3. After Short abandon less than, type the duration that will define an abandoned call
as ‘Abandoned (Short)’.
For example, type 5 to define a short abandon call as one that is abandoned in less than 5
seconds.
Note:
4. Click Save
Note:
This applies not only for the initial ACD call handling, if the call is transferred to
another employee (Supervised or Blind), the Auto Answer also applies to the
transferred employee.
3. Click Save.
Note:
• If the Agent Auto Answer check box is selected, the Accept button is not
displayed in Web Ignite because the incoming conversation is auto answered.
• The Agent Auto Answer option can be enabled for voice, chat, email, sms, and,
open media queue types, but not for the Ring Groups.
To apply queue spectrum settings to all queues on the same media server
1. Select a queue and in the ribbon, click the Queue Tools tab.
2. Select Apply queue spectrum to all.
Note:
For email queues not automatically requeuing interactions on agent logout, emails are put
on hold until the agent logs back in and removes hold. Once the hold requeue time expires,
interactions are requeued whether the agent is logged in or not.
To set how long an interaction can remain on hold or in the Inbox after logout before being
requeued
Note:
When the 'Minutes an interaction can be on hold before being requeued' timer expires, the
interaction is returned to the queue as the longest waiting interaction and the employee (if
logged into Ignite) is put into System Make Busy. For emails, any text the agent entered is
visible to the agent who handles the requeued interaction.
Note:
Once the 'Minutes an interaction can be on hold before being requeued' timer expires,
interactions are requeued whether the agent is logged in or not.
3. Click Save.
To use the mail server email address to reply to an email from a queue that does not have an
email programmed.
To force the agent to pick a From address to reply to an email from a queue that does not have
an email programmed.
2. Deselect Use Mail Server From Address When Queue Address Is Not Defined
checkbox.
Note:
If you deselect Use Mail Server From Address When Queue Address Is Not
Defined checkbox then the Allow Pick From Address is automatically selected.
3. Click Save.
Note:
• Do not copy signatures containing images in .msg files directly from Outlook. Save
these signatures as .msg files in the Reply Templates folder and leverage from
there.
• The size of email signatures contributes to email file size. By default, the maximum
file size for emails, including attachments, signatures, and images, is 25 MB.
• Email queue signatures are limited to 150 000 characters. To increase this
number, consult the following Knowledge Base article: https://mitel.custhelp.com/
app/answers/answer_view/a_id/1000752/loc/en_US.
• Email queue signatures are not inserted in workflow automatic email responses.
Administrators can apply signatures to email queues. These signatures are automatically inserted
into agent email responses. Signatures are configured and applied on a queue-by-queue basis.
Queue signatures enable custom signatures to be deployed uniformly across the responses of
agents answering for the queue.
Email signatures must be in .msg or .txt format. .msg signatures can contain images.
Unsupported file types cannot be saved to the queue.
Administrators can either store signature files in the default Reply Template folder location
created on the server during installation, or they can move the Reply Templates folder to a
network share. Using the Reply Templates folder ensures that signature files are included in
database backups. A network share is required for signatures to be created and modified on
client computersor remote servers. If the network drive is unavailable to the server, the queue
signature is not automatically inserted in agent replies. However, agents can manually insert
signatures in their responses from the Reply Templates folder.
Administrators must ensure that media servers are pointed to the Reply Templates folder and that
queues are pointed to the signature file in that folder. By default, media servers point to the Reply
Templates folder. To point the media server to a Reply Templates folder housed on a network
share, see "Configuring Reply templates for email, chat, SMS, and open media".
If agents are permitted to use personalized signatures, they must use response templates
configured for that purpose. Administrators must configure the templates for agents to apply as
signatures. See "Configuring Reply templates for email, chat, SMS, and open media".
Note:
This folder must the same folder to which the media server points.
Note:
Reply templates only in .msg and .txt files can be inserted into the Email Signature field.
5. Click Save.
Note:
Once the hold requeue time expires, interactions are requeued whether the agent is
logged in or not
The chat options tab for chat queues enables you to email chat transcripts to interactions as a
part of the Chat Response workflow and view the internal and external URL for that specific chat
queue.
A queue’s internal URL has the queue’s GUID built into the URL, removing the potential need for
customers to select the queue they want from the chat request page and, if the Inbound workflow
is configured to route based on queue IDs, automatically identify the destination queue so that
customers are routed directly to the appropriate queue. There are two fields for chat URLs, the
external URL for Queue and the internal URL for Queue. The internal URL for Queue is the
Public URL used internally by the system <Enterprise Server>/chat/GUID. The external URL for
Queue is the Public URL used externally with the reverse proxy applied and is the URL to link
interactions to specific queues.
Note:
Once the hold requeue time expires, interactions are requeued whether the agent is
logged in or not
3. Click Save.
Note:
The email address must be your SMTP server’s main address or an alias. For more
information on SMTP servers, see "Configuring SMTP connections to Multimedia Contact
Center".
4. Click Save.
To delete a queue
• Reporting—groups queues together for reporting and viewing their activities in real-
time
• Mitel Virtual—groups queues across telephone switches that load balance ACD calls
between multiple queues
• Unified Queue Group—groups queues of different media types that handle
interactions for the same service group in a contact center. For mor e informtion. See
Multimedia Contact Center Installation and Deployment Guide.
• PBX 1: Queue 7000: reporting number P700, dialable 7000 on PBX1, queue 700, 701,
702 assigned
• PBX 2: Queue 7001: reporting number P700, dialable 7001 on PBX2, queue 700, 701,
702 Assigned
Virtual queue groups provide the ability to merge multiple queues into a single visual
representation in Interactive Visual Queue and provide callers with an accurate position in queue
through the Updated Position in Queue service.
Note:
Although Virtual queue groups are added and configured under Queue Groups in YourSite
Explorer, a virtual queue group is treated as a singular entity.
Repeat as necessary.
4. Click Save.
Repeat as necessary.
4. Click Save.
Unified queue groups can be created using a wizard or may be created manually. The Unified
Queue Group wizard takes an existing voice queue and then uses its configuration settings
to input information into new multimedia queues. The wizard also enables all agent groups
associated with the voice queue to support the multimedia type selected during queue creation.
Note:
• The Unified Queue Group Wizard does not create new agents for employees
belonging to the associated agent groups. Employees must be enabled to handle
new media types manually. See "Managing the media types an employee can
handle".
• Employees already enabled to handle the new queues’ media types will be set as
Present in their agent groups for those media types. For information on changing
the default presence, see "Managing agent group membership, presence, and skill
level".
• A default queue priority of 64 is assigned to queues created by the Unified Queue
Group Wizard. These may be altered after the wizard has finished.
• Business hours are copied over from the business hours configured for the
voice queue. Default automated responses for business hours are provided for
multimedia.
• The wizard will populate the Offer to Agent Groups activities in the default Inqueue
workflows with the same agent group order used by the voice queue member of
the Unified queue group.
When manually creating a Unified queue group, administrators can create new queues
to associate with the Unified queue group. When you create these new queues, they are
automatically assigned the name and reporting number of the existing Unified queue group.
Users manually creating a Unified queue group can also associate existing queues to a Unified
queue group. Virtual queue groups may be associated to the voice media of a Unified queue
group. If an administrator disables a media type for a Unified queue group, the associated queue
will become historical.
• Add a Unified queue group using the Unified Queue Group Wizard
• Add a Unified queue group
• Associate new queues to the Unified queue group
• Associate an existing queue to the Unified queue group
• Associating an existing virtual queue group to the Unified queue group
• Replace an associated queue with a new queue
• Replace an associated queue with an existing queue
• Remove a media type from a Unified queue group and set the associated queue as
historical
To add a Unified queue group using the Unified Queue Group Wizard
Chat
SMS
Open Media
5. If you want to create a corresponding reporting queue group, select Create reporting
queue group and type a Reporting number.
6. Click Create.
7. Click Save.
1. Click Multimedia > Queue groups and select a Unified queue group.
2. Click on the media type icons to select which media types the queue group can
handle.
For instructions on configuring an email, chat, SMS, or open media queue, see "Adding
multimedia queues".
Note:
Voice
Chat
SMS
Open Media
3. When you are done configuring the new queue, click Save.
4. Repeat steps 2 and 3 for each media type you want the Unified queue group to
handle.
5. Click Save.
1. Click Multimedia > Queue groups and select a Unified queue group.
2. Click the down arrow button beside the media type icon and click Associate existing
<media type> queue.
3. Select a queue and click OK.
4. Click Save.
1. Click Multimedia > Queue groups and select a Unified queue group.
2. Click the down arrow button beside the voice media icon and click Associate existing
Virtual queue group.
3. Select a virtual queue group and click OK.
4. Click Save.
1. Click Multimedia > Queue groups and select a Unified queue group.
2. Click the down arrow button beside the media type icon and click Replace with new
<media type> queue, click on the media type icons to select which media types the
queue group can handle.
For instructions on configuring an email, chat, SMS, or open media queue, see "Adding
multimedia queues".
Note:
3. When you are done configuring the new queue, click Save.
4. Click Save.
1. Click Multimedia > Queue groups and select a Unified queue group.
2. Click the down arrow button beside the media type icon and click Replace with
existing <media type> queue.
3. Select a queue and click OK.
4. Click Save.
To remove a media type from a Unified queue group and set the associated queue as historical
1. Click Multimedia > Queue groups and select a Unified queue group.
2. Click on a selected media type icon.
3. Click Save.
the Schedule activity". Multimedia Contact Center includes default holidays for the USA, UK, and
Canada.
• If the holiday always falls on the same day of the month, select Every and specify
the month and date the holiday falls on.
• If the holiday has a pattern of falling on a certain day, week, and month, select The
and specify the pattern, day of week, and month.
• If the holiday is a calculated holiday, such as Good Friday or Easter Monday, select
Calculated holiday and specify the holiday.
6. Click Save.
To delete a holiday
1. Select the holiday you want to delete from the holidays list.
2. Click Delete.
3. Click OK.
Multimedia Contact Center ships with a default 24/7 business hour schedule and a default
Monday to Friday 9:00 AM to 5:00 PM business hour schedule. Administrators can
Note:
To create a schedule exclusion list, or to edit an existing schedule exclusion list, see
"Managing schedule exclusion lists".
4. Specify the business day Start time and End time for each day of the week.
5. Select the Disable for day check box for each day the business is closed.
6. Click Save.
3. To apply a Schedule exclusion list, click the Browse button, select an exclusion list
and click OK.
Note:
To create a schedule exclusion list, or to edit an existing schedule exclusion list, see
"Managing schedule exclusion lists".
4. Specify the business day Start time and End time for each day of the week.
5. Select the Disable for day check box for each day the business is closed.
6. Click Save.
Managing schedule exclusion lists enables administrators to omit days from business hour
schedules. For example, administrators can use a schedule exclusion list to omit national
holidays from a business’ yearly schedule.
Note:
To create a new list for a schedule with an exclusion list already applied to it, click Add
and follow step 2 onward.
3. Select the dates to exclude from the schedule and click Save.
4. To apply the exclusion list to the selected schedule, click Apply. Otherwise, close the
schedule exclusion list designer window.
5. On the ribbon, click Save.
1. Select the schedule and, after Schedule exclusion list, click Browse.
2. Select a schedule exclusion list and click OK
3. Click Save.
1. Select a schedule with an exclusion list applied to it and click Manage Schedule
exclusion list.
2. Click Edit.
3. To add new dates, select them from the calendar.
4. To remove dates, select the dates from the list and click Remove.
5. To remove all dates, click Clear.
6. Click Save.
7. To apply these changes to the schedule, click Apply.
8. On the ribbon, click Save.
1. Select a schedule that has the exclusion list to be deleted and click Manage Schedule
exclusion list.
Note:
If deleting exclusion lists as part of clean-up, select any schedule with an exclusion list
applied to it and follow these steps.
2. From the drop-down list, select the exclusion list you want to delete and click Delete.
3. Close the schedule exclusion list designer and, on the ribbon, click Save.
For example, an administrator applies a Monday to Friday, 7:00 AM to 7:00 PM business hour
to a Schedule activity in a Chat Inqueue workflow. Chat messages arriving after hours follow
the ‘After Hours’ branch. This branch is configured to send an automatic response informing
customers of the contact center’s business hours and to expect a reply during that time.
To apply business hour schedules to workflows, see "Routing interactions with the schedule
activity".
Note:
In order for you to assign security roles, your account must be associated with a security role
that has ‘May manage security’ enabled.
MiContact Center Business has two default security settings, Local administrator and Enterprise
administrator. These settings provide employees full access to all MiContact Center Business
applications (to which the contact center and employees are licensed) and devices, and allow
Write Back for synchronization.
Employee access to applications is limited by their security role and their licensing. An
employee’s security role defines the application areas an employee can access and licensing
limits what applications an employee can access. For example, an employee with the Enterprise
administrator security role but no supervisor license would not be able to access YourSite
Explorer.
When you install MiContact Center Business, a default user is created. This ensures there is at
least one account with which you can access YourSite Explorer.
• Username: _admin
• Password: _password
Basic—Basic security controls user access to specific areas of Mi Contact Center Business, and
Flexible Reporting, and to Workforce Scheduling and Schedule Adherence.
For detailed information regarding creating and applying security roles and creating security lists,
see the MiContact Center Business Installation and Administration Guide MiContact Center Business
for Microsoft Skype for Business User Guide "Security roles".
Security roles can be applied to restrict which devices agent can view in Ignite, so that they are
limited to both handling and viewing only the queues associated to their agent group. Employees
can be restricted from controlling their Agent Group Presence, so their presence in agent groups
can be entirely controlled by the system. Employees can be restricted from picking interactions
out of queue. Employees can be restricted from transferring interactions from the queue and their
Inbox. Employees can be restricted from marking interactions as Junk. Employees can also be
restricted from accessing Ignite.
Note:
Users currently logged on are not affected by changes to their associated role until the next
time they log on.
To restrict the devices an employee can view in Ignite, enable the following Advanced security
options:
• May view real-time information on devices contained in this list only <device list>.
• All the queue groups that contain queues the employee handles
• All the agent groups to which the employee has agents
• Employee groups that mirror the composition of the agent groups’ employee
membership
To restrict control of presence in Ignite, such as Join and Leave, disable the following Advanced
security option:
To restrict the ability to pick interactions out of queue, disable the following Basic security option
To restrict the ability to transfer interactions from the queue and Inbox, disable the following Basic
security option
To restrict the ability to mark interactions as Junk, disable the following Basic security option
• Chat
For information on offering chat through your corporate website, see "Enabling chat".
• Contact Us
For information on offering Contact Us through your corporate website, see "Enabling Contact
Us".
The following is the suggested order of configuration for Multimedia Contact Center web features.
See "Publishing Chat and Contact Us to the Internet using reverse proxies".
4. Add SSL (optional)
For information on troubleshooting the deployment of Multimedia Contact Center web features,
see "Troubleshooting Multimedia Contact Center web features".
Note:
These are the minimum proficiencies required. More complicated integrations will
require more enhanced skills.
Chat and Contact Us both use CCMWa, a web application installed on the Enterprise Server
at http://<Enterprise Server IP Address>/CCMWa to route interactions to your queues. Using a
reverse proxy enables requests to your corporate website to be served from CCMWa through
your corporate website, proxying requests through the web server to CCMWa on the Enterprise
Server.
Setting up a reverse proxy requires setting up Inbound and Outbound routing rules on your web
server. The Inbound rule configures the directory on the web server that routes the requests to
the Enterprise Server. The Outbound rule modifies the responses from the Enterprise Server to
match the corporate website URL format.
The method for configuring a reverse proxy depends on if your organizational web server is an
Apache or an IIS web server. The Mitel MiContact Center Knowledge Base contains guidelines
for reverse proxy deployment:
Note:
We do not support WebDav Publishing feature in Windows.
During the installation of Multimedia Contact Center, the chat server CCMWa (Internal URL
http://<enterprise server>/ccmwa) and the customer-facing chat request form (default URL http://
<enterprise server>/ccmwa/chat) are installed on the Enterprise Server. Individual queues include
an Internal URL for direct access to them: http://<enterprise server>/CCMWa/chat/<queue
GUID>. The configuration and customization of your chat request forms are handled in a single
JavaScript file, chat.public.config.js.
Note:
As of version 9.2, it is recommended to use the chat files on the Enterprise Server rather
than hosting them on your corporate web server. For more information, see "Hosting chat
files on your corporate web server".
Multimedia contacts to select a queue to which their chat will be submitted, through a queue-
specific chat request form, through activities in an Inbound workflow, or through a user-made
chat request page.
For more information, see "Publishing Chat to the internet using a reverse proxy".
3. Customize your chat request forms.
For more information on customizing your chat request forms, see "Customizing chat".
4. (Optional) Customize Ignite chat and SMS agent options.
Agent options for handling chat and SMS messages can be configured to change Ignite
handling options and display avatars in chat sessions. For more information on customizing
your agent chat and SMS session in Ignite, see "Customizing Ignite chat and SMS agent
options".
5. Integrating chat with your website.
You must determine how chat is offered through your website so that your contacts can
access it. For suggestions on how to integrate chat with your corporate website, see "Offering
chat through your corporate website".
• chat.public.config.js
• Chat.ui.public.config.DEFAULT.js
• Chat.ui.agent.config.DEFAULT.js
• Chat.ui.supervisor.config.DEFAULT.js
During upgrades, these default files update the chat customization files with any new fields and
populates them with the default values. On every start/restart of the CCMWa application on the
Enterprise Server, if the customization files are not found, they are recreated automatically from
the default files.
CAUTION:
Note:
• If you are hosting your chat configuration files on your corporate web server,
they will not be automatically updated during an upgrade and must be manually
upgraded.
• Chat configuration must be consistent for the fields shared between the different
JavaScript files used to customize chat. If you want to use a default public
Gravatar image for a queue, for example, you must ensure that the same image is
set in both chat.public.config.js and chat.agent.config.js.
Public customizations add options to the chat request form as well as providing avatar options for
contacts chatting with contact center agents. For information on customizing contact-facing chat
options, see "Customizing chat request forms and chat sessions".
Agent-facing customizations modify chat and SMS handling options in Ignite and provide avatar
options for agents handling chat and SMS options. For information on customizing agent-facing
chat options, see "Customizing Ignite chat and SMS agent options".
Note:
Chat configuration must be consistent for the fields shared between the different JavaScript
files used to customize chat. If you want to use a default public Gravatar image for a queue,
for example, you must ensure that the same image is set in both chat.public.config.js and
chat.agent.config.js.
You can make the following customizations to your chat request forms and chat sessions:
• Show or hide Estimated Wait Time, Number of Available Agents, Number of Idle
Agents, Number of Chats Waiting, and Business Hours queue statistics
• Enable chats to be submitted after hours
• Enable chat requests to be submitted when the queue is closed or unavailable
• Enable chats to be submitted when there are no available agents
• Enable Gravatar avatars
• Add a corporate logo and customize its placement on the chat request form
• Provide a description for the queue that appears both on the chat request form and in
the browser title bar
• Change both the background color and if it displays as a solid color or a gradient
• Show or hide the topic field, make topics mandatory, and set specific topic choices
• Set up Gravatar avatars for contacts
• Configure queue closed messages
• Configure the LumaThreshold for light or dark icons
Note:
If you customized your chat request form in version 7.0, your customizations will not
be retained after an upgrade to version 8.1. For more information, see "Updating chat
customization from Version 7.0 to Version ".
You can make the following customizations to chat and SMS sessions in Ignite:
Note:
If you modify the default handling, it is your responsibility to inform agents of changed
handling behavior.
• chat.agent.config.js
• chat.supervisor.config.js
• Global settings—control agent handling behavior of chat and SMS in Ignite. These
settings are applied universally or are required to enable features at a queue level.
The following table outlines the global fields.
• Queue settings—are controlled in DefaultConfig and ChatQueues. These two
sections share the same fields. DefaultConfig fields apply the default settings for
queues while ChatQueues fields are applied to individual specific queues. Table 7
outlines DefaultConfig and ChatQueues settings.
• Logging and connection settings—provide troubleshooting options as well as
enable connection limits for devices. Table 8 outlines the logging and connection
settings.
When adding field values based on the following tables, ensure that they use correct JavaScript
formatting and punctuation.
Note:
Note:
Note:
QueueId (ChatQueues only) The queue’s GUID, The GUID for the chat
such as ‘26F1A5C3- queue to which you want
DD2C-45FFBE75- the associated settings
2BC7B85012 D0’ to apply. You can use
YourSite Explorer to obtain
a queue’s GUID. See
"Obtaining Queue GUIDs".
• It must be publicly
available
• It must be accessible
via HTTP or HTTPS
on ports 80 and 443
• It must be
a .jpg, .jpeg, .gif,
or .png image file
• It must not include a
querystring.
• It must be publicly
available
• It must be accessible
via HTTP or HTTPS
on ports 80 and 443
• It must be
a .jpg, .jpeg, .gif,
or .png image file
• It must not include a
querystring.
UseDefaultSupervisorGravatarForAllSupervisors
True or False This field is used to set
whether or not all users will
UseDefaultPublicGravatarForAllPublicUsers
True or False This field is used to
set whether or not all
contacts will use the default
Gravatar image.
Note:
Note:
Note:
Note:
After customizing your agent chat and SMS sessions, your changes will be applied to Ignite.
For a description of the settings and their fields, see Table 6, Table 7, and Table 8.
4. Save and close the editor.
1. In YourSite Explorer, obtain the queue IDs of the chat queues for which you want to
customize settings.
Enabled: true,
QueueId: ‘’,
DefaultAgentGravatarURL:
encodeURIComponent(window.ccmwa.shared.getCCMWaBaseUrl() + '/content/images/
gravatar/defaultagent.png'),
UseDefaultAgentGravatarForAllAgents: false,
GravatarSize: 32,
PeekModeAllowed: true,
IconTheme: 'Dark'
},
For a description of the settings and their fields, see Table 6, Table 7, and Table 8.
4. Save and close the editor.
1. In YourSite Explorer, obtain the queue IDs of the chat queues for which you want to
customize settings.
3. Locate ChatQueues:[ ] and copy and paste the following fields within ChatQueues’s
brackets.
Enabled: true,
QueueId: ‘’,
DefaultSupervisorGravatarURL:'',
DefaultPublicGravatarURL: '',
UseDefaultSupervisorGravatarForAllSupervisors: false,
UseDefaultPublicGravatarForAllPublicUsers: false,
GravatarSize: 32,
PeekModeAllowed: true,
IconTheme: 'Dark'
},
Multimedia Contact Center includes sample files demonstrating these suggested methods.
Samples can be found in <drive>:\Program Files (x86)\Mitel\MiContact Center\Support
\BasicSamples.
Note:
The following HTML is an example of offering chat to a specific queue via a basic hyperlink in a
page in your own website.
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Basic Chat</title>
</head>
<body>
<a href="http://localhost:8082/ccmwa/en-CA/chat/26F1A5C3-DD2C-45FF-
BE75-2BC7B85012D0">chat now</a>
</body>
</html>
For an example of chat embedded within the body of a webpage, with usable HTML and
JavaScript, see chat.basic.embedAsPage.html in <drive>:\Program Files (x86)\Mitel\MiContact
Center\Support\BasicSamples. Adjust as needed to match your storage of scripts and chat queue
GUIDs.
For an example of chat embedded within the body of a webpage as a widget, with usable HTML
and JavaScript, see chat.basic.embedAsWidget.html in the Samples folder at <drive>:\Program
Files (x86)\Mitel\MiContact Center\Support\BasicSamples. Adjust as needed to match your
storage of scripts and chat queue GUIDs.
Note:
If you use these HTML, do not modify the variable names for queueId or targetContainer. Do
not modify the name or value of the hdr variable. Doing so will cause issues for rendering the
chat session.
Language Designators
Dutch nl-NL
German de-DE
Italian it-IT
Norwegian nb-NO
Russian ru-RU
Swedish sv-SE
Language Designators
Welsh cy-GB
The WickedTix sample website included with Multimedia Contact Center showcases an
integration of Contact Us within a corporate website. For more information, see "Corporate
Website Example: WickedTix". There is also a basic sample website included called
BasicSamples, focusing on basic Chat and Contact Us integrations, available in the Samples
folder at <drive>:\Program Files (x86)\Mitel\MiContact Center\Support\BasicSamples.
The following figure displays Contact Us. By default, all the business lines display as collapsed,
showing only the business line name and hours. The footer of Contact Us contains a link that can
be configured to send customers to relevant information concerning the contact center.
When clicked, a business line expands to display the queues configured with it. You can
configure the specific contact information for each queue so that customers can contact the
business line by that media type. (See the following figure.)
Contact Us can also be configured to use a horizontal display of business lines and their queues.
(See the following figure.)
In Contact Us, each queue media icon can be configured to launch a contact session. Icons
can be disabled and greyed out or hidden if that media type is not applicable to a business line.
Clicking the phone icon will make a call if the device is able to make calls. Clicking an email icon
will either launch an email form (see the following figure) or, if the customer is using a mobile
device, it will open the phone’s email application with the icon’s configured email address in the
To: field.
Clicking a chat icon launches a chat session with the configured chat queue. Clicking an SMS
icon launches an SMS form (see the following figure) or, if the customer is using a mobile device,
it will open the phone’s SMS application with the icon’s configured SMS number. When the
customer clicks Send on the form, an SMS will be send to the queue by Contact Us with the
customer’s number.
If the contact center is licensed for IVR, the web callback icon can be configured to submit
callback requests for customers. When clicked, a web callback request form is opened for
customers to fill in callback details and submit a callback request. See the following figure shows
the options in the web callback form. For more information on web callbacks, see the MiContact
Center Business Installation and Administration Guide .
Contact Us has several samples available to help guide decisions on how to offer Contact
Us. For basic deployments, see the files available within <drive>:\Program Files (x86)\Mitel
\MiContact Center\Support\BasicSamples. These include a sample file showing Contact Us as
a standalone webpage and a file showing Contact Us embedded as a slider. For an example
of a more integrated deployment of Contact Us, Multimedia Contact Center includes a sample
website, WickedTix, which provides an example implementation of Contact Us. WickedTix files
are available in <drive>:\Program Files (x86)\Mitel\MiContact Center\Support\WickedTix. For
more information on WickedTix, see "Corporate Website Example: WickedTix".
The main WickedTix landing page shows Contact Us integrated in the horizontal mode within
a targeted container within the page. Other pages in the site integrate Contact Us using the
vertical layout, auto-centering it within the viewable area of the page. The following figure shows
WickedTix with Contact Us expanded.
To implement Contact Us
Contact Us uses a JavaScript file, contactus.config.js, to manage business line and queue
information.
Configurations can be reused if you want to show the same contact options on multiple pages
(or a single configuration referenced in a header/footer, for example). A separate configuration
file is required for any alternate configurations you want to render, where the contact options
are different.
See "Configuring your business lines and queues for Contact Us".
2. Configure Contact Us style.
Contact Us uses CSS to implement its styling. All of the visual components are set by
ContactUs.css in <drive>:\Program Files (x86)\Mitel\MiContact Center\WebSites\Ccmwa
\Content. You can copy this file and host it in your own website with any style modifications.
For the Contact Us email from, the information captured is sent as an email to a queue for
routing. Therefore, the From address must not be same as the To address submitted in the
form; otherwise, the message is flagged as a no-reply and is not routed. To prevent this, in
YourSite Explorer application, configure an alias email address that is valid for the SMTP
server to send an email.
Note:
Do not set as this email address as the dial-to address for any queue in the system.
Edit the CCMWa web.config file using any text or XML editor. The file location is: C:
\Program Files (x86)\Mitel\MiContact Center\WebSites\Ccmwa\. In the appSettings section
of Web.config, set the value to the email address that you configured. Save and close the
file.
Note:
Editing the CCMWa web.config file causes the CCMWa process to restart. Hence we
recommend that you configure this setting during a downtime.
These settings do not affect mobile clients because they use the native email client instead
of the web form.
• Configure the email form with Exchange
If you are using multiple configuration files for Contact Us, you must host them externally on
your corporate web server and then enable Contact Us to use the external files.
Add the necessary files to your corporate website’s web directory on the web server and add
the JavaScript references to add Contact Us as either a standalone webpage or embedded
within an existing corporate webpage.
If you intend to offer multiple instances of Contact Us on your corporate website with different
business line and queue information, you will require multiple copies of contactus.config.js.
Copies of contactus.config.js can be renamed and stored in different locations, but script
references to Contact Us must be updated to renamed file in the script reference’s parameters.
For more information, see "Adding Contact Us to your corporate website".
Business line or service group sections can be added or removed and the available media types
for each of these sections can be modified. The media type layout is fluid so that if one media
type icon is removed, the others flow together.
See the following figure for a labeled diagram of what fields correspond to which elements in
Contact Us.
3. Under MediaTypes, configure the MediaTypes fields to correspond to the queues for
your own service groups or business lines.
See the following figure for a labeled diagram of what fields correspond to which elements in
Contact Us.
• Voice: lobMediaTypePhone
• Chat: lobMediaTypeChat
• Email: lobMediaTypeEmail
• Callback: lobMediaTypeCallback
• SMS: lobMediaTypeSms
• Phone
• Chat
• Email
• SMS
• Callback
Note:
• Call
• Chat
• Email
• SMS
• Callback
Note:
Voice:
2. If the media type is email, chat, or SMS, locate the service group or business line’s
section in contactus.config.js and add the following under MediaType:
Enabled: true,
OnMouseHoverMessage: "",
CssClass: "",
Caption: "",
ContactDisplayInfo: "",
Icon: "",
QueueIdOrNameOrReporting: "",
ClickToContactInfo: "",
Handler: ""
EwtPrefix: ""
},
3. If the media type is callback, locate the service group or business line’s section in the
contactus.config.js and add the following under MediaType:
Enabled: true,
OnMouseHoverMessage: "",
CssClass: "lobMediaTypeCallback",
Caption: "Callback",
ContactDisplayInfo: "Callback",
Icon: "Callback",
QueueIdOrNameOrReporting: "",
ClickToContactInfo: "Callback",
Handler: "Callback",
EwtPrefix: "ewt_wcb",
OutboundWorkflowId: ""
},
4. If the media type is voice, locate the service group or business line’s section in
contactus.config.js and add the following under MediaType:
Enabled: true,
OnMouseHoverMessage
Caption: "",
ContactDisplayInfo: "",
Icon: "",
QueueIdOrNameOrReporting: "",
ClickToContactInfo: "",
SupportedProtocols "tel",
Handler: "Call"
EwtPrefix: "ewt"
},
To remove media types from a service group or business line in an instance of contactus.config.js
2. To remove a media type, delete that media type’s lines from under MediaTypes,
To delete chat, for example, you would delete the following lines:
Enabled: true,
CssClass: "lobMediaTypeChat",
Caption: "Chat",
ContactDisplayInfo: "",
Icon: "Chat",
QueueIdOrNameOrReporting: "d596e70f-526d-4c94-aa86-faa0e8bdb9db",
ClickToContactInfo: "http://localhost/ccmwa/chat/
d596e70f-526d-4c94-aa86-faa0e8bdb9db",
SupportedProtocols: "",
Handler: "Chat",
EwtPrefix: "ewt"
},
2. After ClientSidelogging, type True if you want to enable a log for Contact Us to be
available in the client’s browser.
3. After ConnectionRetryLimit, set the number of times a desktop device can attempt to
connect to Contact Us.
4. After MobileDeviceConnectionRetryLimit, set the number of times a mobile device
can attempt to connect to Contact Us.
5. After ConnectionRetryIterationCount, set the number of times a device can attempt
to connect before prompting the user that it is unable to connect and that a refresh will
occur.
6. Save and close the text editor.
Note:
For information, see "Adding Contact Us to a webpage" and "Adding Contact Us with the
default slider".
For instructions on the specific Exchange configuration, see the following Mitel Knowledge Base
article: https://mitel.custhelp.com/app/answers/answer_view/a_id/1001226/loc/en_US.
Note:
For Office365 user accounts created in October 2020 and later, Basic Authentication
is disabled by default. Currently, MiContact Center Business supports only
Basic Authentication. Therefore, if Office365 is used as an email server, Basic
Authentication must be manually enabled.
You can store Contact Us JavaScript and CSS files on your corporate web server within the
corporate website’s directory. Files stored within your website’s directory on your corporate web
server can be located anywhere within the directory at your discretion. If you store Contact Us
files on your corporate web server, you must manually update your files with any new fields and
settings after every upgrade.
Multimedia Contact Center includes a preconfigured JavaScript file that renders Contact Us in
the specified container on a webpage. This can be used to render Contact Us as a standalone
webpage, embed Contact Us within a page, or render Contact Us in a pop-up or slider. For more
information, see "Adding Contact Us to a webpage".
For integrations with existing webpages, Multimedia Contact Center includes a preconfigured
JavaScript slider containing Contact Us that can be added to your webpages. For more
information, see "Adding Contact Us with the default slider".
For either resource, you must decide whether you want to host Contact Us’s JavaScript files
and CSS files on your corporate web server within the corporate website’s directory or store the
files within CCMWa on the Enterprise Server. Files stored within your website’s directory on your
corporate web server can be located anywhere within the directory at your discretion.
Note:
Optionally, you can store Contact Us JavaScript and CSS files on your corporate web server
within the corporate website’s directory. Files stored within your website’s directory on your
corporate web server can be located anywhere within the directory at your discretion. If you
store Contact Us files on your corporate web server, you must manually add new fields to the
files after every upgrade.
Ensure that you specify the locations in the script reference parameters discussed in "Adding
Contact Us to a webpage" and "Adding Contact Us with the default slider".
Contact Us can be offered using a script reference. Multimedia Contact Center includes a
JavaScript file, MiccContactUs.js, to render Contact Us within an optional target on a webpage.
If you want to render Contact Us as a stand-alone webpage, create an empty HTML file and add
a reference to this script. For an example of this implementation, see contact.basic.stacked.html
or contact.basic.horizontal.html in <drive>:\Program Files (x86)\Mitel\MiContact Center\Support
\BasicSamples.
By default, this script uses the default contactus.config.js and ContactUs.css. To use different
business lines’ contactus.config.js files or CSS files with MiccContactUs.js, different parameters
can be added to the script reference. The following is an example of a MiccContactUs script with
all parameters applied to the script reference.
<script
src="ccmwa/scripts/micccontactus.js?
embedded=false&target=contactus&vmode=false&csspath=assets/css/&jspath=assets/js/
&config= contactus.config "></script>
Note:
vmode overrides
the value set in
UseVerticalBusinessLinesFirst
in contactus.config.js.
There are various other integration options based on a combination of the parameters used and
what kind of container is targeted. For more information, see the basic samples website located
in <drive>:\Program Files (x86)\Mitel\MiContact Center\Support\BasicSamples. The following
procedure details how to configure Contact Us as a standalone webpage. It assumes that you
have:
1. Open the webpage in which you want to render standalone Contact Us with an editor.
2. Add the following script reference to the Body:
<script src="ccmwa/scripts/micccontactus.js"></script>
3. If you are using JavaScript and CSS files other than the defaults, update the script
reference with parameters indicating the file locations.
<script src="ccmwa/scripts/miccsideslider.js"></script>
To use different business lines’ contactus.config.js files or CSS files with MiccSideSlider, different
parameters can be added to the script reference. The following is an example of a MiccSideSlider
with all parameters applied to the script reference as guidance for formatting:
<script src="ccmwa/scripts/miccsideslider.js?
embedded=false&target=contactslider&vmode=false&csspath=assets/css/&imgpath=images/
&imgmod=_wt&jspath=assets/js/&config=contactus.config&promptafter=30000"></script>
Note:
vmode overrides
the setting of
UseVerticalBusinessLinesFirst
in contactus.config.js
The following procedure assumes you have already added your business lines and queues to
a copy of contactus.config.js, optionally updated the style in ContactUs.css, and placed your
JavaScript and CSS files in the desired location.
1. Open the webpage you are adding the slider to in an HTML editor.
2. Add the following script reference in the body of the webpage:
<script src="ccmwa/scripts/miccsideslider.js"></script>
3. If you are using JavaScript and CSS files other than the default, update the script
references with parameters indicating the file locations.
MiccSideSlider can use custom images, either through replacing the default images on the
Enterprise Server or by using parameters on the JavaScript call to MiccSideSlider.js to instruct us
different images. The following images can be customize with MiccSideSlider.js:
• Contact_Us_Slider_Expand.png
• Contact_Us_Slider_Minimize.png
Custom images must have the same name as the original images or else have the same name
with the imgmod suffix applied. Custom images must be stored in the same folder.
Contact Us can now be configured with a WebCallback subroutine at the queue level. Obtain
the GUID for the subroutine and update the associated configuration file for Contact Us. This
identifier enables Contact Us to pass along the correct subroutine to be used to initiate a callback
routing for the given queue.
1. Open SQL Server Management Studio or any other SQL management program.
2. Query the following select statement:
1. Test Chat and/or Contact Us locally on the Enterprise Server with no reverse proxy,
SSL, or firewall.
2. If your deployment uses SSL, add SSL and test Chat and/or Contact Us on the
Enterprise Server with no reverse proxy or firewall.
3. Add your reverse proxy and test Chat and/or Contact Us externally.
4. Add your firewall and test Chat and/or Contact Us externally.
Workflows enable flexible routing of email, chat, SMS, and open media interactions to the queues
and agents best suited to handle them. For examples of how Inbound, Inqueue, and Response
workflows create the routing rules for email, chat, SMS, and open media interactions, see
"Multimedia Contact Center default workflows". For information on configuring the activities that
comprise workflows, see "Activity list".
Inbound workflows – Determine the first paths interactions follow to reach destinations in
an organization. Inbound workflows can search the properties of incoming interactions and
determine the destinations to which these interactions should be directed, for example a sales
team or a support team. Inbound workflows also support other actions such as sending response
messages, running executable scripts, and performing database queries.
Inqueue workflows – Determine the conditions for routing interactions in queue to agents.
Examples include when to overflow interactions to different queues, when to requeue an
interaction, when to interflow interactions to different agent groups, and when to transfer
interactions to available agents. Inqueue workflows are executed once interactions have been
delivered from the Inbound workflow to their queue destinations.
• In push models, the system offers interactions waiting in queue to available agents
• In pick models, agents select their interactions from queues
• In mixed models, agents select their interactions from queues, but interactions waiting
in queue past a specified time are offered to available agents
Response workflows – Enable post-contact options and activities. Performed by queues after
an interaction has been handled, Response workflows enable the automation of processes such
as removing fields from the system or writing data to an external source, inserting information
about the handled interaction into the database, or emailing a transcript from a chat session.
• A customizable workspace
• The Outline pane
• The Search field
• Focusing and breadcrumbs
• The Overview window and Pan function
• The Zoom feature
• The Expand All, Collapse All, and Restore buttons
Toolbar, Properties, and Outline panes can be minimized, expanded, or pinned to the workspace.
This enables administrators to choose how much of the screen is comprised of the workflow
versus configuration panes. These enhancements enable administrators to customize their
workspaces and manage screen space to better facilitate their work.
Administrators can configure activities or branches directly from the Outline pane by selecting
the activity in the tree and clicking the Properties pane and by right-clicking the activity in the
search tree. Right-clicking also highlights the activity in the workflow, providing a clear means of
referencing a specific activity being configured. If, for example, the workflow has several similar
activities, highlighting minimizes errors by helping administrators confirm they are configuring the
correct activity.
Searches can be performed based on complete or partial search terms. For example, searching
‘sched’ will return results for all workflow items containing ‘Schedule’ in the name or system
name.
After locating an item in the Search field, administrators can edit the item either by right-clicking it
or by toggling to the Properties pane.
When focusing on an activity or branch, the Workflow Canvas opens in a Breadcrumb view.
Breadcrumbs at the top of the Canvas indicate the portion of the workflow being viewed and
the parent elements of those portions. After focusing on a specific portion of the workflow, the
view of the workflow can be incrementally expanded by tracing back through parent relationships
using breadcrumbs. Administrators can also right-click an activity and select ‘Go To Parent’.
The Breadcrumb view provides an ordered way of redirecting focus in the workflow from precise
elements to the bigger picture.
Note that when working in the Breadcrumb view, only the items in focus can be configured. In
order to configure other items in the workflow, select the breadcrumb that brings the item into
focus. (See the following figure.)
The Pan mode enables administrators to ‘grab’ the Workflow Canvas and, using the mouse,
choose what portion of the workflow is centered on the Canvas without worrying about dragging
activities around the workflow in the process.
We recommend that administrators perform actions for designing workflows from the
• Inbound Routing and Response Routing tabs on the Media servers page, for Inbound
and Response workflows
We recommend that administrators perform actions for managing workflows from the Workflows
page, located by selecting Multimedia > Workflows.
Note:
When creating Inbound email workflows, ensure they contain either a Transfer, a Junk Email,
or a No Reply Email activity. If they do not, email contacts will remain in system storage,
using system memory and causing performance issues.
To copy a workflow
To delete a workflow
Administrators can export workflows from Multimedia Contact Center to save on a machine or
network. Exported and saved workflows can be imported. Administrators should assess any
validation errors, to ensure the workflow is fully configured. See "Validating workflows" for more
information.
To import a workflow
To export a workflow
If validation is enabled, workflows with errors cannot be saved until the errors are corrected. If
validation is not enabled, workflow with errors can be saved.
The pane lists the number of errors and warnings, the activity to which the error or warning
is associated, and what is required to fix the problem. Double-clicking the error and warning
information in the Validation pane brings the specific activity into focus, for ease of identification.
For more information on focusing, see "Viewing specific portions of a workflow: Focusing and the
Breadcrumb view".
To validate a workflow
1. Right-click on the active portion of the Workflows Canvas and select Save as
Image….
2. Select the desired image type for the workflow.
3. Navigate to the location to which the image will be saved, and click Save.
• Right-click on the active portion of the Workflows Canvas and select Copy as Image.
We recommend building inbound and response workflows from the Inbound Routing and
Response Routing tabs on the Media servers page. This automatically associates the workflow to
the server. However, workflows built from the Workflows page can be associated to the server as
follows.
Note:
Workflows execute once validation is enabled and any programming and configuration errors
are corrected. For more information, see "Validating workflows".
1. Click Multimedia > Workflows, and select the Inbound or Response workflow.
2. Click Media Server Membership.
3. Under Available members, select the media server and click >.
4. Click Save.
We also recommend modifying an Inqueue workflow from the Routing tab of a selected queue.
This automatically associates the workflow to the queue. Workflows built from the Workflows
page can be associated to queues as follows.
Note:
Workflows execute once validation is enabled and any programming and configuration errors
are corrected. For more information, see "Validating workflows".
3. Under Available members, select the queues to which the workflow is associated and
click >.
To build subroutines, administrators drag and drop activities on a Canvas and configure them
with routing conditions. Activity availability varies by media type. For more information on
activities in multimedia routing, see "Building visual workflows in Multimedia Contact Center:
Activities".
Note:
Variables in Response workflows/subroutines are based on the agent’s reply, not the
customer’s original interaction. For example, in Inbound and Inqueue workflows/subroutines
the <<From>> variable populates with the customer’s sending address. The <<To>> variable
populates with the queue’s address.
Administrators must first add a Subroutine activity to a workflow. A subroutine of the appropriate
media type can then be assigned to the activity. When the workflow reaches the Subroutine
activity, the subroutine executes. For more information, see "Executing subroutines with the
Subroutine activity".
To edit a subroutine
To delete a subroutine
Administrators can export subroutines from Multimedia Contact Center to save on a machine or
network. Exported and saved subroutines can be imported.
To import a subroutine
To export a subroutine
Multimedia Contact Center can add the following as data providers to query for data:
Multimedia Contact Center also supports the following platforms as generic data providers to
query for data:
• SAP
• Salesforce
• Microsoft Dynamics CRM
• Sugar CRM
• NetSuite
Multimedia Contact Center can also import ODBC connections configured using the Windows
ODBC;Data Source Administrator. Multimedia Contact Center supports the following reference
platforms for ODBC connections:
• IBM DB2
• Oracle Database
• MySQL
• Microsoft Access
• PostgreSQL
Note:
The Excel worksheet must be shared as a workbook and located on a UNC (Universal
Naming Convention) path, also known as a shared network path. The syntax for a UNC
path is \\ComputerName\SharedFolder\Resource. An example of the syntax format is \
\IVRMACHINE\IVRDIRECTORY\WORKSHEET.xls. Locating the worksheet on a UNC
enables IVR Routing to access the data provider remotely.
5. Click Open.
6. Click Test Connection.
7. Click Save.
• SAP: Enter the client number, the system number, and the connection type,
separating the values by semi-colons. For example: 250;25;SOAP
• Salesforce: Enter your Salesforce security token.
Note:
When adding an ODBC connection for Multimedia Contact Center, you must use the 32-bit
Windows Server tool. For more information, see the following Mitel Knowledge Base article:
https://mitel.custhelp.com/app/answers/answer_view/a_id/1001249/loc/en_US.
Note:
Multimedia Contact Center is unable to delete ODBC data providers from the data providers
list.
1. Select the data providers you want to delete from the data providers list.
2. Click Delete.
3. When prompted, click OK.
collect customer data, perform database queries, and build simple or complex conditions to route
interactions.
Multimedia Contact Center ships with System variables relevant to all media types and variables
specific to media types. To view these variables and see a description of each, open YourSite
Explorer and go to Multimedia > Variables.
Administrators can
Note:
Variables in Response workflows/subroutines are based on the agent’s reply, not the
customer’s original interaction. For example, in Inbound and Inqueue workflows/subroutines
the <<From>> variable populates with the customer’s sending address. The <<To>> variable
populates with the queue’s address.
Note:
Note:
5. If Mask Type is available to this type of variable, select the variable’s mask from the
dropdown list.
• NoMask– The variable will not be masked within Multimedia Contact Center and
associated screen pops, databases, etc.
• FullMask– The entire variable will be masked within Multimedia Contact Center and
associated screen pops, databases, etc.
• MaskAllExceptLastX– The variable will be masked except for the specified
number of final characters
• MaskAllExceptFirstX– The variable will be masked except for the specified
number of first characters
6. If you selected MaskAllExceptLastX or MaskAllExceptFirstX, specify the number of
characters to be left unmasked.
7. To enable this variable to display in a toaster notification or screen pop select the
Send to agent desktop check box.
8. To enable this variable to display in a web Ignite toaster notification select the Show
on agent toaster check box.
Note:
The Show on agent toaster check box is disabled if the Send to agent desktop check
box is not selected.
9. After Display Name, type the name this variable has when it appears in a toaster
notification or screen pop.
10. If you selected Dollars, Euros, or Pounds as the variable type, after Currency Format,
select the format from the drop-down list.
11. If you selected Date Time as the variable type, after Date Format, select the date
format from the drop-down list. After Time Format, select the time format from the
drop-down list.
12. Click Save.
To edit a variable
To delete a variable
Note that activity availability varies by media and workflow type. For example, administrators can
use the Ask activity in a Chat workflow but not in an Email workflow. The Offer to Agent Group
activity can be used in an Inqueue workflow but not in an Inbound workflow.
Multimedia Contact Center ships with default workflows. We recommend administrators create
workflows by duplicating and modifying reconfiguring, adding, and deleting activities in the default
workflows to suit the contact center’s needs. For more information, see "Multimedia Contact
Center default workflows".
Note:
• Schedule conditions
• Queue conditions
• Variable compare conditions
While the individual types of expressions that can be added to conditions and their configuration
may vary between the conditions being built, Multimedia Contact Center’s interface for adding,
deleting, and grouping expressions remains consistent throughout Multimedia Contact Center.
Note:
To remove an expression
• Select the expression you want to delete and click the Delete button.
Alternatively,
• Click the expression's selector column on the left side of the expression's row.
Operator Use
!= With this operator the expression will only look for value that do not
match the exact value entered. This operator is case-sensitive.
Operator Use
= With this operator the expression will looks only for the exact value
entered in the expression. This operator is case-sensitive. If this
operator is being used in a comparison, then the expression will look for
an exact string match between the two items being compared.
Contains With this operator, the expression matches values that contain the
entered string. It is not case-sensitive.
Length With this operator the expression will look for a value with the specified
number of characters.
Starts With With this operator, the expression will look for any value that starts with
the entered value.
Note:
We recommend you do not exceed eight nested levels of grouping within a group of
expressions.
• AND: Expressions grouped by the AND clause require that all the expressions in a
group be met to successfully meet the condition.
Note:
• OR: Expressions grouped by the OR clause require that only one of the expressions in
a group be met to successfully meet the condition.
To group expressions
1. Press the CTRL or Shift key and select the expressions you want to group. Clicking
'CTRL' enables you to select items one at a time and omit items from selection.
Clicking 'Shift' selects a span of items.
2. Click either the Group AND or Group OR buttons.
Note:
You can change the grouping clause by selecting the drop-down beside 'And' or 'Or', and
changing your selection.
Note:
If you cannot add an expression to an existing group, ungroup the expression and then
regroup it with the expression you want to add.
Note:
The following explains how to add activities to Inbound, Response, and Inqueue workflows
1. Click Multimedia > Media servers and select the media server associated to the
workflow.
2. Drag the activity from the Toolbox to the Workflows Canvas.
3. Configure the activity and validate any configuration errors. For more information,
consult the configuration procedures for specific activities in this guide. See also
"Validating workflows".
4. Click Save.
1. Click Multimedia > Queues and select the queue associated to the workflow.
2. Drag the activity from the Toolbox to the Workflows Canvas.
3. Configure the activity and validate any configuration errors. For more information,
consult the configuration procedures for specific activities in this guide. See also
"Validating workflows".
4. Click Save.
Note:
Some activities are specific to media and workflow types. For example, a Say activity is
used in Chat workflows but not Email workflows. The Offer to Agent group activity is used in
Inqueue workflows but not Inbound workflows. Only cut and paste activities and branches
into the appropriate media, workflow, and activity types.
Note:
If a system name is not provided, activities and branches are given sequential system
names by default. For example, TerminateActivity1, TerminateActivity2.
4. Click Save.
• Change the condition and value by typing or using the drop-down lists.
• Add a new condition by clicking Add and typing the desired values.
• Delete a condition by selecting the condition and clicking Delete.
3. Click OK.
4. Click Save.
You must select ‘Child Reporting Enabled’ for any branches and conditions on which you want to
run Workflow Condition reports. For more information on Workflow reports, see the reports guide
appropriate to your MiContact Center Business licensing level.
Note that system names are used to report on branches and branching conditions. For this
reason, we recommend naming branches and branching conditions with unique and easily
identifiable system names. For more information on naming, see "Naming activities and
branches".
1. Select the branch or branching condition and, in the Properties pane, select the
Reportable or the Child Reporting Enabled check box.
Note:
Selecting 'Child Reporting Enabled' on parent activities selects all child activities.
2. Click Save.
For an example of annotating activities, see the default workflows included with Multimedia
Contact Center.
To annotate an activity
• Click the Notepad icon on the activity. This closes an open annotation and opens a
closed annotation.
Note:
The Ask activity can also be used to collect information from contacts. Contact responses are
stored in the <<LastDataCollected>> variable. Using a Set Variable activity, this information can
be set into other variables for use elsewhere or saved to a database with a Query activity. For
more information on Set Variable activities, see "Populating variables with the Set Variables
activity". For more information on Query activities, see "Querying data providers with the Query
activity".
URLs entered into the Message field are turned into hyperlinks. Some website content can be
embedded into chat sessions using the Ask activity. If a link to a supported website’s content,
such as a link to a YouTube video, is entered into the Message field, the content is embedded
directly into the chat session. The following websites are supported for embedded content in
chat:
• "https://twitter.com/"
• "https://soundcloud.com/"
• "http://www.youtube.com/"
Note:
• Ignite supports embedding content from Google Maps in chat sessions. However,
this requires the use of embed maps URL, available from Google Maps, to embed
a Google map, such as: <iframe
src="https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d2804.500978803945!
2
d-
75.90911198444678!3d45.3386984790996!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!
3m3!1m2!1s0x4cd1fff1517da8a9%3A0xe6bc8a721e90f2a5!2sMitel+Networks!5e0!3m2!
1sen!2sus!4v1445531227487" width="600" height="450" frameborder="0" style="border:0"
allowfullscreen></iframe>
• SMS does not support embedded content.
• Ignite supports embedding Twitter content in chat sessions, however this is only
possible when you use the Copy link to Tweet in the More menu option available
from the Twitter site. The Embed Tweet menu option will not work in the chat
window.
The Ask activity is available to Chat and SMS Inbound and Inqueue workflows.
The Ask activity poses questions to contacts from the automatic response username for the
media server or the queue. It is recommended that the question be clearly worded and that if it
requires specific responses, that these be listed.
By default, the user can respond incorrectly three times before they are routed down the Failure
branch. The Invalid branch informs them that their response was invalid using a Say activity. By
default, the user has 30 seconds to respond before they are routed down the Timeout branch and
informed, using a Say activity, that they timed out and to try again. By default, users can timeout
three times before being routed down the failure branch. For information on configuring the Say
activity, see "Responding to interactions with the Say activity".
In a chat session, the question will be asked using the chat media server’s auto response
username or the chat queue’s username. In an SMS session, the question will be asked using
the SMS media server's name or the SMS queue's phone number.
4. Click Save.
After configuring the question, you must configure the accepted responses the contact may enter
to be used as branching conditions. Responses can be a set value or the can be a variable.
When using a variable as a response, the Ask activity compares the <<LastDataCollected>>
variable to the selected variable as if it were a Variable Compare activity. For more information on
the Variables Compare activity, see "Routing interactions with the Variable Compare activity". An
answer branch may have multiple conditions applied to it. All conditions configured together in a
single branch have the ‘Boolean And’ applied to them.
• != Not Equal
• = Equal
Note:
This operator is case-sensitive. If this operator is being used in a comparison, then the
expression will look for an exact string match between the two items being compared.
• Contains
• Length
• Starts With
5. In the third column, set the Value for the answer or select a Variable.
6. Repeat steps 2-4 for each additional answer value you want to route down this branch.
7. To enable reporting for this branch, select Enable reporting.
8. If you want to add another branch, click Add at the bottom of the window.
9. Click OK.
10. Click Save.
Setting the duration of Delay activities specifies how long Multimedia Contact Center suspends a
workflow.
Email activity templates support HTML and text-based content. Template fields can be populated
with variables, and attachments can be populated with variables or files.
You can set email properties to avoid sending multiple auto- response emails when an incoming
email is requeued or transferred.
For example, an administrator uses the End Session activity in an Inqueue chat workflow that
only has automated responses from Ask and Say activities to end the interaction’s chat session
with the queue while enabling the workflow to continue to a Query activity that writes a transcript
of the interaction's back to SQL.
The End Session activity requires no configuration. Administrators can optionally provide
the activity with a name and system name. See "Naming activities and branches" for more
information.
The End Session is available in all Chat and SMS Inbound and Inqueue workflows.
• Executable/Script – Runs an *.EXE file or *.BAT script on the server and delivers
return values or parameters if the script executes successfully.
Note:
The Execute activity requires *.EXE files and *BAT scripts to be on a UNC path.
• PowerShell – Runs a PowerShell script on the server and delivers return values or
parameters if the script executes successfully.
Note:
• Web Service – Enables the Execute activity to retrieve an XML response from an
external web service using SOAP or REST and delivers return values if the script
executes successfully.
Note:
The data being returned must be valid XML characters. Any invalid characters (such as
&, <, or >) will not return successfully and the workflow will route down the Failure branch.
The XMLNode object type is not supported.
• CRM Service – Sends user defined queries to a Microsoft CRM 2011, Microsoft CRM
2013, or Microsoft CRM Online system and delivers return values if the script executes
successfully.
For example, an administrator uses the Execute activity to retrieve customer information from a
Web Service database. This information is stored in a custom variable for use within the workflow
or to pass on to agents in a screen pop for enhanced customer service.
For an example of a workflow that uses the Execute activity to execute PowerShell and perform
a web service SOAP call to a publicly accessible web service, see the following Mitel Knowledge
Base article: https://mitel.custhelp.com/app/answers/answer_view/a_id/1000724/loc/en_US.
Although the workflow is for IVR Routing, the configuration of the Execute activity is the same for
Multimedia Contact Center workflows.
Note:
A success return value indicates the process executed without errors, and the Success
branch is followed. A failure return value indicates the process exited with errors and did not
complete as expected, and the Failure branch is followed.
The following procedures explain how to instruct the Execute activity to run
• Executable/Script processes
• PowerShell processes
• Web Service processes
• CRM Service processes
1. Right-click the Execute activity and select New Process > Executable/Script or
PowerShell script.
2. For Executable/Script processes, after Path, click the Browse button and navigate to
the *.EXE or *BAT script. The script must be on a UNC path.
3. For Executable/Script processes, select the Separator required by the .exe file. The
separator is the character separating the parameters in the process’ command line
statement.
4. For PowerShell processes, navigate to the PowerShell script.
5. To add a set of Input Parameters, click Add and select the Parameter the process
uses to execute.
Note:
Note:
7. Repeat steps 5 and 6 for each set of input parameters the process uses. To delete a
set of parameters, click the arrow to the left of Parameter and click Remove.
8. Under Test Value, enter values to test the process and click Execute.
Note:
• For Executable/Script processes, the Results dialog box lists return values and
output pipeline values.
• For PowerShell processes, the Results dialog box lists return values and
PSObject[X] values.
• Right-click the Execute activity and select New Process > Web Service.
• Type the Web Service URI and, for the Web Service Type, select SOAP.
• If using a SOAP Web Service, click the Scan button to verify the Web Service.
• Select a Web Method from the drop-down list. The Web Method populates the
Parameters field.
Note:
SOAP Web Services populate the Web Methods field with a drop-down list of available
functions.
CAUTION:
If you are using the Execute activity with a web service as a part of a PCI compliant
workflow, ensure that you:
• If the return or input fields of the SOAP call contain sensitive information, use masked
variables in the Input and Output parameters of the Execute activity.
1. Right-click the Execute activity and select New Process > Web Service.
2. Type the Web Service URI and, for the Web Service Type, select REST.
CAUTION:
If you are using the Execute activity with a web service as a part of a PCI compliant
workflow, ensure that you
• If the return or input fields of the SOAP call contain sensitive information, use masked
variables in the Input and Output parameters of the Execute activity.
1. Right-click the Execute activity and select New Process > Microsoft CRM.
2. Type the CRM URI used to communicate with the CRM system.
Note:
The following procedure explains how to store data retrieved by the Execute activity as a
variable. These variables can be used later in the workflow.
1. In the Process Setup window, under Mapping, select a variable from the drop-down
list to correspond to each Output value.
2. Click OK.
When a contact progresses through the workflow, each variable in the Mapping field is
assigned the value indicated in the Output field.
3. Click Save.
Specifying options for following the Success, Timeout, and Failure branches
• Instruct the system to follow the Success branch before a process completes
• Specify how long a process has to complete successfully before the Failure branch is
followed
To specify routing options for the Execute activity’s Success, Timeout, and Failure branches
For example, an administrator configures a From activity to recognize the email addresses of
Platinum customers and route their emails to a Priority queue.
Note:
To route based on specific email addresses in the ‘From:’ field, we recommend selecting
‘Contains’ and typing an email address for the activity to identify. This option identifies a wide
range of content in email ‘From:’ fields. For example, <<From>> Contains [email protected].
• NotEqual (!=)
For example, administrators can specify that emails not sent from '[email protected]'
are not sent to the priority sales branch.
• Equal (=)
For example, administrators can specify that emails sent from '[email protected]'
are directed to the priority branch.
Note:
• Contains
For example, administrators can specify that emails with 'priority' in the From: field are
directed to the priority branch.
• Length
For example, administrators can specify that emails sent from addresses longer than 25
characters are directed to a branch for spam.
• StartsWith
For example, administrators can specify that emails sent from addresses starting with
'priority' are sent to the priority sales branch.
4. Click <Value> and enter a criterion to branch emails, for example, ‘priority’.
5. Click OK to create the branch or click Add to add the current branch to the workflow
while leaving the dialog box open to create new branches.
6. Click Save.
Note:
Directing emails based on variables requires first inserting and configuring an activity on
the Canvas capable of populating the From activity’s destination variable. For a list of Email
variables, go to Multimedia > Variables.
Note:
For example, an administrator is configuring the Offer to Agent Group activity for an Email
Inbound workflow. The Go To activity, embedded in the Offer to Agent Group activity, is set with
a destination of the Offer to Agent Group activity. If the system cannot offer an email to an agent,
the Go To activity directs the email back to the Offer to Agent Group activity and the system
searches again for an agent.
The following procedure explains how to specify where the Go To activity sends contacts
The Interflow activity is available to Inqueue workflows for all media types.
Note:
This variable must be a queue reporting number, dialable number, or name associated to
the queue.
Note:
• To add a queue to the list, click Add and follow the appropriate steps under
"Adding multimedia queues".
• To add a queue group to the list, click Add and follow the appropriate steps
under "Adding queue groups".
4. Optionally, to keep the current queue's priority for the interflowed interaction in the
destination, select Maintain Queue Priority.
5. After Timeout Duration, set the time allotted for the interflow before the call is routed
down the Failure branch.
6. Click Save.
Note:
Note:
This variable must be a queue reporting number, dialable number, name, or email address
associated to the queue. The variable cannot be a personal email address.
4. Optionally, to keep the current queue's priority for the interflowed interaction in the
destination, select Maintain Queue Priority.
5. After Timeout Duration, set the time allotted for the interflow before the call is routed
down the Failure branch.
6. Click Save.
For example, an administrator configures a Variable Compare activity to identify spam keywords
found in emails. Emails containing these words are directed to a branch containing a Junk Email
activity. The Junk Email activity removes the interaction from the workflow, preventing spam from
reaching the queue.
The Junk Email activity requires no configuration. Administrators can optionally add a name and
system name to the activity. See "Naming activities and branches" for more information.
The Junk Email activity is available to Email Inbound and Inqueue workflows.
For example, an administrator configures a Variable Compare activity to identify the words ‘Out
of Office’ in email subject fields. Interactions meeting these conditions are directed to a branch
containing a No Reply Email activity. The No Reply Email activity removes the interaction from
the workflow. The No Reply Email activity prevents messages not requiring a response from
taking up space in queues and being sent to agents.
The No Reply Email activity requires no configuration. Administrators can optionally add a name
and system name to the activity. See "Naming activities and branches" for more information.
The No Reply Email activity is available to Email Inbound and Inqueue workflows.
If an agent in the group is available, the Agent Available branch is followed and the agent is
offered the interaction. If the agent accepts, the Success branch is followed. If the agent does not
accept, the Failure branch is followed and the system checks again for an available agent. If an
interaction terminates in the queue before reaching an agent, the Completed branch is followed.
This activity also offers overflow options if agents are unavailable, if interactions wait in queue
too long, and if agents in the primary group are logged out. Configuring the Offer to Agent Group
activity also enables administrators to implement push, pick, and mixed model routing.
An agent group can only be associated with an Offer to Agent Group activity once per Inqueue
workflow. Attempting to associate an agent group with additional Offer to Agent Group activities
returns a validation error.
The Offer to Agent Group activity is available to Inqueue workflows for all media types.
The following procedures explain how to configure routing options for offering interactions to
agent groups.
Note:
• You must add the "Offer to Agent Group" only to the inqueue workflows and not to
the inqueue subroutines.
• To enable mixed model routing, where agents select their interactions from
queues, but interactions waiting in queue past a specified time are offered to
available agents, see "Enabling mixed model routing".
For example, if a support agent is handling an ongoing issue with a customer, the Offer to
Preferred Agent activity directs all incoming interactions from the customer to that agent. If
the agent is not available, the system waits until the Overflow Time is reached and follows the
Overflow branch. Administrators can configure the activity to overflow interactions instantly if the
agent is logged out.
The Offer to Preferred Agent activity offers the interaction to the preferred agent only if their
Workload permits handling this interaction. The activity can also be configured to offer the
interaction to the preferred agent only if that agent is currently answering for the queue the
interaction came in on.
Preferred Agent is not set for agents handling emails that originated internally within a contact
center. If an agent is responding to an email from another internal queue, Multimedia Contact
Center does not set that agent as the Preferred Agent. For example, if a customer addressed an
email to two different queues, the Preferred Agent would only be set for the email sent from the
customer, rather than emails sent from the agents.
The Offer to Preferred Agent activity is available to the email Inqueue workflows only. It is not
supported for Chat and SMS workflows.
For information on configuring this activity’s Overflow Time, Interval Time, and the option to
overflow interactions instantly if the preferred agent is logged out, see "Routing contacts with the
Offer to Agent Group activity".
Note:
• You must add the "Offer to Preferred Agent" activity or "Offer to Agent" activity only
to the inqueue workflows and not to the inqueue subroutines.
• Offer to Preferred Agent functionality requires that auto case and ticket number
generation for the email media server is not disabled. See "Adding email to
Multimedia Contact Center" for more information.
• If contact centers use preferred agent routing, we recommend that agents do not
adjust case and ticket numbers in email subject lines. Removing or otherwise
altering case and ticket numbers in subject lines can interfere with preferred agent
routing.
• If the Preferred Agent is deleted or moved to another agent group, they will no
longer be considered to be the Preferred Agent.
To only route interactions to preferred agents currently answering for this queue
For example, an administrator wants emails waiting in queue for four hours to overflow to a
secondary agent group. The administrator adds an Offer to Agent Group activity to a workflow,
and configures the Interval branch with a Queue activity reading the queue’s Agents Available.
The administrator places an Overflow activity after the Queue activity. Once the Queue activity
registers that the queue has less than 2 available agents, the email moves to the Overflow
activity and is directed to the secondary agent group.
The Overflow activity requires no configuration. Administrators can optionally provide the activity
with a name and system name. See "Naming activities and branches" for more information.
The Overflow activity is available to Inqueue workflows for all media types.
For example, an administrator uses a Query activity in an Inbound Email workflow to retrieve
customer account balances from a SQL database. The administrator populates an Email activity
template with a variable that will contain this information, retrieved from the Query activity. The
workflow responds with balance information to customers inquiring via email.
Note:
Connecting Query activities to data providers enables the Query activity to access data and use
this information to route interactions. See "Configuring data providers" for more information.
Note:
The Query activity cannot be saved without a query or write statement configured.
Running simple queries enables administrators to retrieve information from a database and store
it in a variable.
'Database table names' refer to the tables in the data source from which the Query activity
retrieves information.
4. After Column Return Name, from the drop-down list, select the column of data to
query.
'Column return names' refer to the columns in the selected table, from which the Query activity
retrieves information.
5. After Variable Return Name, from the drop-down list, select the variable to populate
with the return value.
'Variable return names' refer to the variables populated as a result of the query.
6. After Column Where Name, from the drop-down list, select the name of the column of
data to compare against.
'Column where names' refer to the columns in the data source against which the Query activity
compares information.
7. After Variable Where Name, from the drop-down list, select the variable to use for
comparison.
'Variable where names' refer to the variables against which the Query activity compares.
8. To test the query, after Test with a value equal to, enter an existing value from the
data provider and click Test Query.
The Raw SQL window displays the SQL statement based on the selections from the drop-
down lists.
9. To clear all fields and return to the Canvas, click Clear. To accept the query, click OK.
10. Click Save.
Advanced queries enable administrators with knowledge of SQL to write SQL statements
retrieving information from a database provider. Advanced queries also support LDAP syntax for
LDAP providers, and advanced queries for MS SQL Server and ODBC data providers support
stored procedures.
Administrators can use an advanced query to retrieve single or multiple records from a database
provider.
The Execute window opens displaying a list of detected input and output parameters.
4. Under Value, type the numbers corresponding to the values contained in the data
provider.
5. Click Run.
6. To assign variables to store information returned by the SQL statements, click the
Variable Assignment tab.
Return Column will be populated with the column names in the data provider.
7. Under Variable Name, select the variables to store information returned by the SQL
statements.
8. To assign values to the parameters filled by the SQL statements, click the Parameter
Assignment tab.
Parameter Name will be populated with the SQL parameters used to query the data provider.
9. After Variable Name, select a variable from the drop-down list to store the information
retrieved by the SQL parameter.
10. To view the values returned from the query, click the Test Results tab.
11. To clear the variables and their parameters, click Clear. To accept the query, click OK.
12. Click Save.
Write statements define a delete, insert, or update statement against a specified data provider.
Write statements enable administrators to delete, insert, or update column values in a data
provider from within a workflow.
The following procedures explain how to configure simple and advanced write statements
Note:
Advanced write statements enable users with knowledge of SQL to write insert, update, or
delete SQL statements.
1. Select the Query activity, click Properties and, after Write statement, click the
Browse button.
2. Select Simple Write and select a Write Type from the drop-down list. Options vary by
data provider.
3. After Table Name, select the table in the data provider against which the write
statement is defined.
4. Under Column Name, select a column in the data provider against which the write
statement is defined.
5. Under Value, select the data to be inserted into the data provider.
6. Under Where, select a column name.
Note:
• =
• <>
• >
• <
• >=
• <=
8. From the third drop-down list, select or type the variables used to evaluate the
information selected from the first column
9. To test the write statement, click Test Syntax.
10. To empty column values, click Clear. To accept the write statement, click OK.
11. Click Save.
The Query activity supports returning multiple results from a query. When a Query activity returns
multiple results from a query, the Success branch is followed for each result. When there are no
more results, the message exits the Success branch of the Query activity and continues along
the workflow.
Multiple result returning Query activities enable contact centers to build more complex workflow
functions, such as providing callers access to an employee directory.
For example, an administrator building an Email Inbound workflow configures the Queue activity
to send emails waiting in queue four hours or longer to a secondary queue. This enables the
contact center to meet its service level goals.
Note:
Multimedia Contact Center evaluates Queue conditions from left to right. To change the order
in which the activity evaluates conditions, see "Changing the order in which branches are
evaluated".
Note:
Associating queue conditions to a variable requires first inserting and configuring an activity
on the Canvas capable of populating the Queue activity’s destination variable.
To see a list of Multimedia Contact Center variables and their descriptions, go to Multimedia >
Variables.
4. Click Add and, from the second column, select a real-time statistic from the drop-down
list.
5. In the third column, select an operator from the drop-down list. Options vary according
to the variable chosen.
6. Click the fourth column and select either Value, Queue Stats, or Variable.
7. For Value, type in a numeric value or enable the check box for the value.
8. For Queue Stats, select a queue stat from the drop-down list.
9. For Variable, select a variable from the drop-down list.
10. To test the conditions, click Test Parameters, enter a value in the relevant fields and
click Test.
11. Click OK.
12. To add another condition, click Add and repeat steps 4-11.
13. Click OK to create the branch or click Add to add the current branch to the workflow
while leaving the dialog box open to create new branches.
14. Click Save
1. Right-click the relevant branch in the Queue activity and select Edit Condition.
2. Click Add and, from the second column, select a real-time statistic from the drop-down
list.
3. In the second column, select an operator from the drop-down list. Options vary
according to the variable chosen.
4. Click the third column and select either Value, Queue Stats, or Variable.
5. For Value, type in a numeric value or enable the check box for the value.
6. For Queue Stats, select a queue stat from the drop-down list.
7. For Variable, select a variable from the drop-down list.
8. To test the conditions, click Test Parameters, enter a value in the relevant fields and
click Test.
9. Click OK.
10. To add another condition, click Add and repeat steps 2-9.
11. Click Save.
• To delete a queue condition, select the row for the condition and click Delete.
1. To import queue conditions, click the Import button and navigate to a *.csv file.
Note:
2. To export queue conditions, click the Export button and navigate to a *.csv file.
3. To test the conditions, click Test Parameters, enter a value in the relevant fields and
click Test.
The Save Callback activity requires the following variables be set with information for the callback
request to be submitted correctly:
Note:
It is recommended that you use the default abandon outbound callback subroutine as
callbacks submitted by a Multimedia Contact Center workflow will not contain a message
to be played for agents.
For additional information on the Save Callback activity and callbacks, see MiContact Center
Business Installation and Administration Guide.
The Save Callback activity has a Success and Pending branch. The activity routes down Pending
when network issues prevent the callback from being submitted. When the network issues are
resolved, the callback will be saved.
The Save Callback activity is available to all Multimedia Contact Center workflows.
Note:
If you are using this activity to submit a callback, you should use New Request.
3. Click Save.
For example, if a chat message is sent to the contact center after hours, the Say activity can
respond with the message 'Thank you for contacting us. Our chat queues are currently closed.
Please try again Monday through Friday 9am – 5pm.'
URLs entered into the Message field are turned into hyperlinks and will open in another window
or tab of the interaction’s browser when the customer clicks on them. Some website content is
embeddable into chat sessions using the Say activity. If a link to a supported website’s content,
such as a link to a YouTube video, is entered into the Message field, the content is embedded
directly into the chat session. The following websites are supported for embedded content in
chat:
• https://twitter.com
• https://soundcloud.com
• http://www.youtube.com
Note:
• Ignite supports embedding content from Google Maps in chat sessions. However,
this requires the use of embed maps URL, available from Google Maps, to embed
a Google map, such as: <iframe
src="https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d2804.500978803945!
2
d-
75.90911198444678!3d45.3386984790996!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!
3m3!1m2!1s0x4cd1fff1517da8a9%3A0xe6bc8a721e90f2a5!2sMitel+Networks!5e0!3m2!
1sen!2sus!4v1445531227487" width="600" height="450" frameborder="0" style="border:0"
allowfullscreen></iframe>
• SMS does not support embedded content.
The Say activity is available to Chat and SMS Inbound and Inqueue workflows.
In a chat session, the message will be said using the chat media server’s auto response
username or the chat queue’s username. In an SMS session, the message will be said using
the SMS media server's name or the SMS queue's phone number.
4. Click Save.
For example, an administrator uses a Schedule activity to route chat messages arriving after
hours to an after-hours branch. Interactions following this branch receive a response indicating
that the contact center is closed and to send the chat again during business hours.
3. Click Add and, from the second drop-down list, select DOW.
4. Click <Value>, select the days of the week the business is open, and click OK.
5. To test the conditions, under Testing, select a date and time and click Test.
6. Click OK to create the branch or click Add to add the current branch to the workflow
while leaving the dialog box open to create new branches.
7. Click Save.
Note:
Administrators may select ‘Reoccur every year’ for date conditions if the business is
regularly closed on that date.
5. To test the conditions, under Testing, select a date and time and click Test.
6. Click OK to create the branch or click Add to add the current branch to the workflow
while leaving the dialog box open to create new branches.
7. Click Save.
Note:
The default schedule conditions determine when Multimedia Contact Center executes
business hour workflows and after hour workflows. These conditions include the default
Monday to Friday, 9:00 AM to 5:00 PM schedule and the default 24/7 schedule. These
default Schedule conditions can be used as is or modified to suit specific hours of operation.
See also "Modifying default business hour schedules".
Note:
5. To test the conditions, under Testing, select a date and time and click Test.
6. Click OK to create the branch, or click Add to add the current branch to the workflow
while leaving the dialog box open to create new branches.
7. Click Save.
For example, an administrator configures a Set Variables activity to retrieve customer data from
incoming emails. This information is used in an Email activity’s template for automatic responses
to the customer.
The Set Variables activity is available to all Multimedia Contact Center workflows.
The following explains how to retrieve workflow data and use it to populate Set Variables
activities.
1. Right-click the Set Variables activity and select Edit Variable Settings.
2. Type a Name for the activity and click Add.
3. Select a variable from the drop-down list and click OK.
To see a list of Multimedia Contact Center variables and their descriptions, go to 'Multimedia >
Variables'.
4. In the third column, either type a Value, an expression in Advanced Text, or select
Variable and select a variable from the drop-down list. If selecting a value, note that
options vary according to the variable selected. Advanced Text is only available with
certain variables.
5. Click OK.
6. To add a variable row, click Add. To delete a variable row, select the row and click
Delete.
7. Click Save.
SMS activity templates support text-based content. Template fields can be populated with
variables.
Note:
Go To activities nested in subroutines can have a target activity in either the subroutine or the
parent workflow.
Note:
Assigning a variable to the Subroutine activity requires first inserting and configuring an
activity on the Canvas capable of populating the variable.
To see a list of Multimedia Contact Center variables and their descriptions, go to Multimedia >
Variables.
3. Click Save.
3. Click Save.
For example, an administrator uses a Terminate Workflow activity to end an Inqueue workflow
once an interaction requires no further routing to an agent.
The Terminate Workflow activity requires no configuration. Administrators can optionally provide
the activity with a name and system name. See "Naming activities and branches" for more
information.
The Terminate Workflow activity is available to all Multimedia Contact Center workflows.
Note:
The To activity checks the 'To:' and 'Cc:';fields of inbound emails or the "To:' field of inbound
SMS messages. The activity performs actions based on specified branching conditions.
Administrators can specify whether the To activity checks one or all of the above fields for email
and administrators can define multiple addresses for SMS;messages.
For example, an administrator configures the To activity to route an email to the Sales queue if
the email contains ‘[email protected]’ in its To: or Cc:;field.
Note:
If your contact center will be transferring emails between mail servers, ensure that all aliases
are entered on the mail server page. For more information about adding aliases to the mail
server, see "Configuring SMTP connections to Multimedia Contact Center".
If you use a destination other than the <<DestinationQueues>> variable in an email Inbound
workflow, the email will be transferred according to the configured destination and will ignore the
email addresses in the To and CC fields of the email.
The Transfer activity is available to Inbound workflows for all media types.
For example, an administrator uses the Variable Compare activity to filter and prevent automatic
email responses from reaching a queue. The Variable Compare activity compares a variable
for automatic responses against an email’s Subject line. If ‘Automatic Reply’ or ‘Out of Office’ is
present in the Subject line, the email follows a branch configured to receive junk emails. If neither
is present, the email follows the No Match branch and continues through the workflow.
The Variable Compare activity is available to all Multimedia Contact Center workflows.
Enabling a mixed model requires administrators first to configure two agent groups, each
containing the same agents. Administrators must then add two Offer to Agent Group activities,
one after the other, to the Workflow Canvas. One of the agent groups is assigned to each activity.
The first Offer to Agent Group activity enables a pick routing model, and allows overflow to a
secondary agent group. The second Offer to Agent Group activity enables a push routing model,
and does not allow overflow. When interactions overflow from the first Offer to Agent Group
activity to the second, they overflow to an agent group with the same agents and are pushed to
the agents’ Inboxes.
For example, Support agents pick the emails they handle, but their supervisor wants to push
emails waiting in queue over 30 minutes to the agents’ Inboxes. The administrator creates
one agent group, called Support Group 1, containing the contact center’s Support agents. The
administrator then creates a second agent group, called Support Group 2, containing the same
Support agents.
The administrator adds an Offer to Agent group activity to the workflow and assigns it Support
Group 1. The activity is configured to follow a pick model and to overflow emails waiting longer
than 30 minutes in queue. The administrator adds the second Offer to Agent group activity,
configures it to follow a push routing model, disables overflow, and assigns Support Group 2.
If emails remain unpicked in the Support queue for more than 30 minutes, they overflow to the
same Support agents and are pushed to the Inboxes of available agents.
The following procedures explain how to enable mixed routing models. For information on
creating agent groups, see "Adding agent groups".
1. Place an Offer to Agent Group activity on the Canvas and click Properties.
2. Deselect the Push Items to Agent check box.
3. After Answering Agent Group, click the drop-down and select Agent Group.
4. Select the agent group to handle interactions and click OK.
5. After Overflow Time, type the time interactions wait in queue before the Overflow
branch is followed and a push routing model begins.
Note:
6. Place a second Offer to Agent Group activity on the Canvas and, in the Properties
pane, select the Push Items to Agent check box.
7. After Answering Agent Group, click the drop-down and assign the second agent
group to handle interactions.
Note:
This group must contain the agents that are in the first agent group, assigned above.
8. Select Do Not Allow Overflow and set the Overflow Time to 00:00:00.
9. Click Save.
Any variable available to the workflow’s media type, which also contains the ‘Send to Agent’s
desktop’ check box, can populate a workflow screen pop with information. Populating URLs and
executable files with workflow variables enables administrators to customize screen pops on a
queue-by-queue basis.
For example, an administrator can configure a workflow to query a database and retrieve
a customer’s name and account history. When the interaction rings in the agent’s Inbox, a
web page pops on the agent's desktop, displaying the customer's information. The agent is
immediately able to provide personalized, informed service.
Administrators must provide webcodes and servers for URLs and the executable codes behind
executable files. URLs must include 'http://' in the URL string.
Executable files may prompt a Windows security warning on client desktops before popping.
Administrators may disable this security setting in the current browser they are using. See your
internet browser documentation for more information.
Note:
• Agents using Ignite (WEB) may need to disable pop-up blockers for the Ignite URL
in order for screen pops to display .
• Ignite (WEB) supports URL screen pops only. Executable file screen pops are not
supported.
• If Contact Center Client and Ignite are used on the same agent desktop and
screen pops are populated with workflow variables in voice, email, chat, SMS, and
open media, then administrators should disable Contact Center Screen Pop in
Contact Center Client. For information on enabling and disabling Contact Center
Screen Pop, see the MiContact Center Business User Guide.
• If Contact Center Client and Ignite are used on the same agent desktop and
screen pops are populated with workflow variables in voice, email, chat, SMS, and
open media, then Administrators should disable toaster notifications in Contact
Center Client. This prevents screen pops and toaster notifications from Contact
Center Client and Multimedia Contact Center from appearing on an agent’s
monitor at the same time.
Note:
If values change after a screen pop has been sent to an agent’s desktop, the screen
pop will not refresh. We therefore recommend placing the Set Variables activity in close
proximity to the Offer to Agent Group activity. This provides optimally current values and
helps prevent the screen pop’s value from being overwritten by another variable query in
the workflow.
4. Right-click the Set Variables activity and select Edit Variable Settings.
5. Click Add and, from the <Select a variable> drop-down list, select
ScreenPopOnRinging.
6. Click <Value> and, in the Value tab, enter a complete URL string or the path to an
executable file.
Note:
The paths to executable files must be accessible to any clients who require its use. For
example, administrators can place the file on a network share.
7. To populate a web page screen pop with variable information, insert the variable’s
name between double angle brackets where applicable in the URL string.
8. Click OK to close the variable dialog box and click OK to return to the workflow.
9. Click Save.
The following sections summarize the default workflows and explain how they operate. For ease
of understanding, we recommend expanding the entire workflow and all annotations.
Each default workflow requires additional configurations to get up and running. For information
on configuring the workflow activities to suit the contact center, follow the cross-references
throughout each summary.
Note:
Inbound Email workflows must contain either a Transfer, a Junk Email, or a No Reply Email
activity. If they do not, email interactions will remain in system storage, using system memory
and causing performance issues.
The following requirements are shared among default workflows. Administrators must
• Validate the workflow and activity configuration and correct any errors detected
Note:
Inbound workflows modified from the Inbound Routing tab of the Media servers pane and
Response workflows modified from the;Response Routing tab are already associated to
that media server.
Note:
Inqueue workflows modified from the Routing tab of the Queues page are already
associated to that queue.
To further illustrate the workflow’s activities and their operations, we recommend expanding the
entire workflow and all annotations.
Description
The first step in the workflow is a;Variable Compare activity. This activity is configured to stop
automatic responses from reaching the queue. The Variable Compare activity checks an
incoming email’s Subject line. If the Subject line contains ‘Automatic Reply’, or ‘Out of Office’,
but does not contain ‘RE,’ the email follows a branch for the matched condition identifying the
email as ‘auto response’. A No Reply Email activity marks the email as requiring no reply, and a
Terminate activity stops the workflow so that the email is not directed to a queue. This prevents
automatic reply messages from bouncing back and forth between a customer’s email account
and the email media server. You can modify or add to these ‘auto response’ conditions based
on responses received by agents. To configure the Variable Compare activity to branch emails
based on a different set, or an additional set, of conditions, see "Routing contacts with the
Variable Compare activity".
If the email’s Subject line contains neither Automatic Reply nor Out of Office, the email follows a
branch with activities routing emails to appropriate queues. In this default workflow, the branch is
named ‘Email is not an Auto Response’.
This branch contains a Transfer activity. By default, the destination of this activity is set to the
<<DestinationQueues>> variable, which compares all addresses in the To and CC field of
incoming email to existing queue email addresses. For example, emails directed to the Sales
branch would be transferred to the Sales queue, and emails directed to the Support branch
would be transferred to the Support queue. Emails failing to transfer to a queue follow the Failure
branch. We recommend administrators configure the Failure branch with activities so that a
course of action is taken if a transfer fails. Emails transferred to the appropriate queue follow the
Success branch. Once an email is transferred to the appropriate queue, a Terminate activity ends
the Email Inbound workflow, and the Email Inqueue workflow executes. To configure the Transfer
activity to direct emails to queues and queue groups in the contact center, see "Routing contacts
with the Transfer activity".
The default workflow ends with three activities designed to notify administrators when emails are
not successfully routed.
The first is an Email activity. Inbound emails reaching this activity have failed to reach a queue.
For example, an email might reach this activity if the address in the email’s To: field was not
recognized by the system. The Email activity is intended to notify an administrator that an
interaction failed to reach a queue. To configure the Email activity with the administrator’s email
address and to assign the Email activity to an SMTP server, see "Enabling mixed model routing".
The second is a Transfer activity. We recommend configuring this Transfer activity with a
destination to receive emails not successfully routed to a queue. For example, an administrator
can specify their email address as the Transfer activity’s destination. See "Routing contacts with
the Transfer activity".
The third is another Email activity, nested in the Transfer activity’s Failure branch. This Email
activity contains a message indicating that the final routing activity in this workflow has failed
and that the interaction can be reviewed as a Failed item in Ignite. To configure the Email activity
with an administrator’s email address and to assign the Email activity to an SMTP server, see
"Sending emails with the Email activity". See also "Rerouting Failed emails".
Note:
To further illustrate the workflow’s activities and their operations, we recommend expanding the
entire workflow and all annotations.
Description
The first step in the workflow is a Schedule activity. The Schedule activity contains a Business
Hours and an After Hours branch. If an email hits the queue from Monday to Friday between 9:00
AM and 5:00 PM, the Business Hours branch is followed. If an email is received after business
hours, the After Hours branch is followed. To configure the Schedule activity with the contact
center’s business hours, see "Routing contacts with the Schedule activity".
The Business Hours and After Hours branches contain Email activities programmed with a
dedicated auto response message. The subject line of the Business Hours branch contains ‘Auto
Response [<<CaseIdPrefix>><<CaseId>> <<TicketIdPrefix>><<TicketId>>]’. The subject line
of the After Hours branch contains ‘After Hours Auto Response [<<CaseIdPrefix>><<CaseId>>
<<TicketIdPrefix>><<TicketId>>]’. This populates the email subject line with the customer’s case
and ticket number and indicates that the message is an automatic response. By default, each
Email activity’s template is set with the From field to <<QueuePrimaryEmailAddress>>, which
uses the queue’s primary email address in responses. For more information on email queue
email addresses, see "Configuring general settings for multimedia queues".
Note:
Emails will not be sent by the email activity if the <<To>> variable is used in the From field
and an inbound email that is addressed to multiple queues arrives in the workflow.
Customers emailing during business hours receive a response message saying 'Hello
<<From>>, Thank you for your email. We have received your message and it is being handled by
one of our agents. Please expect a reply shortly. Thank you'. Customers emailing after business
hours receive a response message saying 'Hello << From>>, You’ve contacted us outside our
regular hours of operation. Please expect a response during our regular business hours. Thank
you'. To configure custom response messages for these branches and to connect the activity to
an SMTP server, see "Sending emails with the Email activity".
Note:
The first activity in this workflow is an Offer to Agent Group activity. This activity offers the
interaction to a specified agent group, in this example named ‘Offer to Primary Agent Group’. If
an agent in the primary agent group is available to receive an email, the Agent Available branch
is followed. An Offer to Agent activity sends the email to an agent’s Inbox. The system evaluates
which available agents have the highest skill level and, of these, pushes the email to the agent
longest idle. If the email is successfully offered to an agent, the Success branch is followed and
a Terminate activity ends the Inqueue workflow. If the system cannot offer the email to an agent,
or if an agent does not accept the interaction, then the Failure branch is followed. A Go To activity
nested in the Failure branch loops back to the Offer to Agent Group activity and the system
searches again for an available agent in the group. If an agent or supervisor picks the email
from the queue, the Completed branch is followed and a Terminate activity ends the workflow. To
specify agent groups to be offered emails for the queue, see "Routing contacts with the Offer to
Agent Group activity". For information on configuring push, pick, or mixed routing models, see
"Configuring routing options for offering contacts to agent groups", and "Enabling mixed model
routing". To specify a different end point for the Go To activity, see "Routing contacts using the Go
To activity".
If agents in the primary agent group are not available, emails sitting in queue for five minutes
follow the Overflow branch. Now the system searches for available agents in the second Offer
to Agent Group activity, named ‘Offer to Overflow Agent Group 1’ in this example. The process
repeats itself, and emails are overflowed to the third and fourth Offer to Agent Group activities if
an available agent cannot be found in the first overflow agent group. The fourth and final Offer to
Agent Group activity is configured to disallow overflow. This is to prevent emails from failing to
route to an agent group, in the event that an agent in the final Offer to Agent Group activity is not
available. Verify that, for the final Offer to Agent Group activity, the ‘Do Not Allow Overflow’ check
box is selected in the Properties pane.
To disallow all overflow, delete the second, third, and fourth Offer to Agent Group activities from
the workflow and follow the instructions on disabling overflow in "Configuring routing options for
offering contacts to agent groups". See this procedure also to maintain overflow but to adjust the
Overflow Time.
Note:
The default workflow does not make use of the Interval branch. For more information on this
branch, see "Configuring routing options for offering contacts to agent groups".
To better illustrate the workflow’s activities and operations, we recommend you expand the
workflow and all annotations.
Description
The first activity in this workflow is a Transfer activity. This activity is configured to route chats
using the <<DestinationQueues>> variable, which is filled automatically when either a queue
is selected from the drop-down list in the chat request page or when a customer uses the chat
queue’s Public URL to start a chat session. If the transfer is successful, the chat is sent to
the destination queue and a Terminate activity ends the workflow. If the transfer fails, the chat
request is sent down the Failure branch.
The next activity in the workflow is an Email activity. If the transfer failed, this activity sends an
email to an administrator to notify them that an emergency routing has occurred for a chat. This
activity must be have an SMTP server added to it. The email’s template must also be altered
for sender and destination. The template may be customized, but changing the variables within
the template is not recommended. For more information on configuring the Email activity, see
"Sending emails with the Email activity".
This activity is followed by a Transfer activity. This activity is intended to transfer chats that do
not route correctly by <<DestinationQueue>> to be routed to a specified chat queue. This activity
requires that a destination queue be selected. For more information on configuring a Transfer
activity, see "Routing contacts with the Transfer activity". The Success branch of this activity
contains a Terminate activity that ends the workflow.
The Failure branch contains an Email activity that sends another email to the administrator,
indicating that the final routing activity in this workflow has failed and that the interaction can be
reviewed as a Failed item in Ignite. The template must have a destination added. The template
may be customized, but changing the variables within the template is not recommended. For
more information on configuring the Email activity, see "Sending emails with the Email activity".
The failed chat session is then routed to the final activity of the workflow, a Terminate activity,
which ends the workflow.
To better illustrate the workflow’s activities and operations, we recommend you expand the
workflow and show all annotations.
Description
The first activity in the Chat Inqueue workflow is a Schedule activity. The schedule activity
contains a Business Hours and an After Hours branch. If a chat arrives in queue from Monday
to Friday between 9:00 AM and 5:00 PM, the Business Hours branch is followed. If a chat is
received after business hours, the After Hours branch is followed. To configure the Schedule
activity with the contact center’s business hours, see "Routing interactions with the Schedule
activity".
The After Hours branch contains a Say activity programmed with a dedicated auto-response
message. The Say activity sends a greeting to the interaction that states: “Hello, and thank you
for contacting us. Our chat queues are currently closed. Please try again during our regular
business hours. Thank you.” To reconfigure the Say activity’s message, see "Responding to
interactions with the Say activity". The next activity in the After Hours branch is an End Session
activity, which ends the chat session with the interaction. The branch continues to a Terminate
workflow activity, which ends the workflow.
The Business Hours branch contains a Say activity. The Say activity sends a greeting to the
interaction that states: “One moment while we check for an available agent.” To reconfiguring the
Say activity’s message, see "Responding to interactions with the Say activity".
The next activity in this workflow is the Offer to Agent Group activity. This activity offers the chat
session to the configured agent group for the activity, in this example named ‘Primary Agent
Group’. After you configure this activity with an agent group, it will offer the chat to that group first.
An agent group must be associated to the activity. To specify agent groups to be offered chat
sessions for the queue, see "Routing interactions with the Offer to Agent Group activity".
Note:
The default workflow does not make use of the Interval branch. For more information on this
branch, see "Routing interactions with the Offer to Agent Group activity".
If there are available agents in the primary agent group, the chat request is routed to the
Agent Available branch. This branch contains an Offer to Agent activity that sends the chat to
the agent’s Ignite client. The system evaluates which available agents have the highest skill
level and, of these, pushes the chat to the agent who has been the longest idle. If the chat is
successfully offered to the agent, the Success branch is followed and a Terminate activity ends
the Inqueue workflow. If it fails to be offered to an agent, it is routed to the Failure branch which
contains a Go To activity that loops back to the Offer to Agent Group activity and the system
searches for another available agent in the group.
If the overflow timer for the Offer to Primary agent group activity is exceeded, the chat session is
routed down the Overflowed branch to the next Offer to Agent Group activity.
By default, the Overflow Time in the Properties pane is set to 5 minutes. If you do not want to
direct chats to an overflow group, set the Offer to Agent Group’s Overflow Timer to 0, select the
‘Do Not Allow Overflow’ check box, and delete the following Offer to Agent Group activities. For
more information on modifying the overflow timer, see "Routing interactions with the Offer to
Agent Group activity".
If the chat session is removed while sitting in queue before reaching an agent, the Completed
branch is followed and a Terminate activity ends the workflow.
The next three activities in this workflow are Offer to Agent Group activities. There are three
Offer to Agent Group activities in the workflow, the agent groups configured with each activity
functioning as 1st to 3rd Overflow groups. These activities are identical in configuration to the
first Offer to Agent Group activity. The third and final Offer to Agent Group activity is configured
to prevent overflow, preventing chats from failing to route to an agent group. These activities
can be safely deleted from the workflow, if desired. The fourth and final Offer to Agent Group
activity is configured to prevent overflow, preventing chats from failing to route to an agent group.
Verify that the ‘Do Not Allow Overflow’ check box is selected in the Properties pane and that the
Overflow Time is set to 0:00:00.
To further illustrate the workflow’s activities and operations, we recommend you expand the
workflow and show all annotations.
Description
The first step in this workflow is a Variable Compare activity. This activity checks to see if the chat
queue is configured to send transcripts. If it is, it routes down the “Queue is configured to send
transcript” branch. If it is not configured to send transcripts, the workflow routes down the “Queue
is not configured to send transcript” branch, which continues directly to the Terminate activity at
the end of the workflow.
The “Queue is configured to send transcript” branch contains an Email activity. This activity is
configured with the variables required to send the transcript back to the customer. The template
may be customized, but changing the variables within the template is not recommended. This
activity requires the assignment of a SMTP server. For information on configuring the Email
activity, see "Sending emails with the Email activity".
The final step in the workflow is a Terminate activity. This activity completes the workflow.
To better illustrate the workflow’s activities and operations, we recommend you expand the
workflow and all annotations.
Description
The first activity in this workflow is a Transfer activity. The activity is configured to route SMS
interactions using the <<DestinationQueues>> variable, which is filled in automatically with the
phone number the SMS interaction used and is compared to the phone numbers of the SMS
queues. If the transfer is successful, the SMS interaction is sent to the destination queue and a
Terminate activity ends the workflow. If the transfer fails, the SMS;interaction is send down the
Failure branch.
The Failure branch continues to an Email activity. If the transfer failed, this activity sends an email
to an administrator to notify them that the Transfer activity failed to route and that the interaction
can be reviewed as a Failed item in Ignite. The template must have a destination added to it
and the Email activity must have an SMTP server added to it. The template may be customized,
but changing the variables within the template is not recommended. For more information on
configuring the Email activity, see "Sending emails with the Email activity".
The next activity in the branch is a Transfer activity. This activity is intended to transfer SMS
interactions that do not route correctly by <<DestinationQueues>> to be routed to a specified
SMS queue. This activity requires that a destination queue be selected. For more information
on configuring a Transfer activity, see "Routing contacts with the Transfer activity". The Success
branch of this activity contains a Terminate activity that ends the workflow.
The Failure branch continues to a Terminate Workflow activity, which ends the workflow.
To further illustrate the workflow’s activities and their operations, we recommend expanding the
entire workflow and all annotations.
Description
The first step in the workflow is a Schedule activity. The schedule activity contains a Business
Hours and an After Hours branch. If a SMS arrives in queue from Monday to Friday between 9:00
AM and 5:00 PM, the Business Hours branch is followed. If a SMS is received after business
hours, the After Hours branch is followed. To configure the Schedule activity with the contact
center’s business hours, see "Routing interactions with the Schedule activity".
The After Hours branch contains a Say activity programmed with a dedicated auto-response
message. The Say activity sends a greeting to the interaction that states: “Hello, and thank you
for contacting us. Our SMS queues are currently closed. Please try again during our regular
business hours. Thank you.” To reconfigure the Say activity’s message, see "Responding to
interactions with the Say activity". The next activity in the After Hours branch is an End Session
activity, which ends the SMS session with the interaction. The branch continues to a Terminate
workflow activity, which ends the workflow.
The Business Hours branch routes to an Offer to Agent Group activity. This activity offers the
interaction to a specified agent group, in this example named ‘Offer to Primary Agent Group.
After you configure this activity with an agent group, it will offer the SMS interaction to that group
first. An agent group must be associated to the activity. To specify agent groups to be offered for
the queue, see "Routing interactions with the Offer to Agent Group activity".
Note:
The default workflow does not make use of the Interval branch. For more information on this
branch, see "Routing interactions with the Offer to Agent Group activity".
If an agent in the primary agent group is available to receive an SMS, the Agent Available branch
is followed. This branch contains an Offer to Agent activity that sends the SMS interaction to
the agent’s Ignite client. The system evaluates which agents have the highest skill level and,
of these, pushes the SMS interaction to the agent who has been idle the longest. If the SMS
interaction is successfully offered to an agent, the Success branch is followed and a Terminate
activity ends the Inqueue workflow. If it fails to be offered to an agent, it is routed to the Failure
branch, which contains a Go To activity that loops to the Offer to Agent Group activity and the
system searches for another available agent in the group.
If the overflow timer for the Offer to Agent Group activity is exceeded, the SMS activity is routed
down the Overflowed branch to the next Offer to Agent Group activity. By default, the Overflow
Time in the Properties pane is set to 1 hour. If you do not want to direct SMS interactions to an
overflow group, set the Offer to Agent Group’s Overflow Timer to 0, select the ‘Do Not Allow
Overflow’ check box, and delete the following Offer to Agent Group activity. For more information
on modifying the Overflow Timer, see "Routing interactions with the Offer to Agent Group
activity".
If the SMS session is removed while sitting in queue before reaching an agent, the Completed
branch is followed and a Terminate activity ends the workflow.
The next activity in this workflow is an Offer to Agent Group activity. This activity offers SMS
interactions to the overflow agent group. This activity is identical in configuration to the first Offer
to Agent Group, except that it is configured to prevent overflow, preventing SMS from failing
to route to an agent group. Verify that the ‘Do Not Allow Overflow’ check box is selected in the
Properties pane and that the Overflow Time is set to 0:00:00.
To further illustrate the workflow’s activities and their operations, we recommend expanding the
entire workflow and all annotations.
Description
The first (and only) activity in the default workflow is an Offer to Agent Group activity, in this
example named ‘Offer to Primary Agent Group’. This activity offers the interaction to a specified
agent group. If an agent in the primary agent group is available to receive an open media item,
the Agent Available branch is followed. An Offer to Agent activity sends the open media item to
an agent’s Inbox. The system evaluates which available agents have the highest skill level (this
only occurs, if skill-based routing is enabled on the agent group) and, of these, pushes the open
media item to the agent longest idle. If the open media item is successfully offered to an agent,
the Success branch is followed and a Terminate activity ends the Inqueue workflow. If the system
cannot offer the open media item to an agent, or if an agent does not accept the interaction, then
the Failure branch is followed. A Go To activity nested in the Failure branch loops back to the
Offer to Primary Agent Group activity and the system searches again for an available agent in the
group.
If the overflow timer for the Offer to Primary agent group activity is exceeded, the open media
item is routed down the Overflowed branch to the next Offer to Agent Group activity. For more
information on the overflow timer, see "Routing interactions with the Offer to Agent Group
activity".
If an agent or supervisor picks the open media item from the queue, the Completed branch is
followed and a Terminate activity ends the workflow.
Note:
The default workflow does not make use of the Interval branch. For more information on this
branch, see "Configuring routing options for offering interactions to agent groups".
To better illustrate the workflow’s activities and operations, we recommend you expand the
workflow and all annotations.
Description
The first activity in this workflow is a Transfer activity, in this example named ‘Transfer to Queue’.
This activity offers the interaction to a queue. If the interaction is successfully accepted into
a queue, the Success branch is followed and a Terminate activity ends the workflow. If the
interaction is not accepted by the queue, then the Failure branch is followed.
The next activity in the workflow is an Email activity, which sends an email to an administrator
to notify them that the first attempt at routing the interaction has failed. This activity must
have an SMTP server added to it. The email’s template must also be altered for sender and
destination. The template may be customized, but changing the variables within the template is
not recommended. For more information on configuring the Email activity, see "Sending emails
with the Email activity".
This activity is followed by a Transfer activity, in this example named ‘Transfer to Routing
Failure Destination’. This activity is intended to transfer open media items that did not route
correctly to a specified open media queue. Transfer to Queue activity is configured to use the
<<OpenMediaDestinationQueue>> variable. <<OpenMediaDestinationQueue>> variable is
automatically filled in when a Queue is specified in the POST Open Media API that creates a
new open media item to be routed. For more information on configuring a Transfer activity, see
""Routing interactions with the Transfer activity". The Success branch of this activity contains a
Terminate activity that ends the workflow. If the open media item fails to route to the destination
queue, it follows the Failure branch, where an Email activity, in this example named ‘Final Email
Warning’ sends a second email to the administrator advising them of the routing failure.
• Add items to and clear items from Ignite’s global spell checking dictionary
• Configure bounced email detection settings
• Configure maximum email message size
• Accessing diagnostics reports sent from Ignite (WEB)
Note:
Administrators can configure Ignite's global dictionary to include words that are used by agents
across your contact center but are not included in the default dictionary. Examples include
product names and services.
Adding items to Ignite’s global dictionary eliminates the need for each agent to add these words
to their local dictionary while ensuring agents spell the words correctly.
For information on adding items to Ignite’s global dictionary, consult the following Knowledge
Base article: https://mitel.custhelp.com/app/answers/answer_view/a_id/1002633/loc/en_US.
Note:
You must use SSL to send emails in order to fully support bounce detection settings.
Ignite can be configured to filter bounced emails and either automatically junk them or place them
in:
• DESKTOP - the Auto Replies/Failed Delivery subfolder (contained in the Failed folder)
of the agent who last handled the email and the global failed route folder (where
supervisors can view and process bounced emails when agents are absent).
• WEB - the Inbox of the agent who last handled the email and History > Failed (where
supervisors can view and process bounced emails when agents are absent).
This applies only when the contact center mail server is configured to operate in SSL mode
For configuration setting details, see the following Mitel Knowledge Base article: https://
mitel.custhelp.com/app/answers/answer_view/a_id/1000650/loc/en_US.
of the mail server with the lowest supported message size. When set accurately, and an agent
attempts to send an oversized email, an error message displays and they are given the option of
editing the email size and resending.
For configuration setting details, see the following Mitel Knowledge Base article: https://
mitel.custhelp.com/app/answers/answer_view/a_id/1000649/loc/en_US.
Note:
You must use SSL to send emails in order to fully support maximum email message size
setting associated behavior.
Note:
You may experience higher than normal bandwidth use, depending on the number of agents
enabling continuous logging from Ignite.
A single file is created per employee. Additional reports append to this file. Reports contain log
lines from employees’ browsers and, for on-demand reports, any details added.
SMS is supported in 8.0+. Historical SMS data from a pre-8.0 instance of Multimedia Contact
Center will be available after an upgrade because in previous versions SMS was treated as
email.
Supervisors - Managing a multimedia
contact center
6
• Setting alarms to monitor agent performance and customer service
• Accessing real-time information with Contact Center Client
• Accessing historical real-time information with Contact Center Client
• Accessing real-time information with Ignite (WEB)
• Managing a multimedia contact center with Ignite
• Managing Agent Groups and Agent Skill Levels
Supervisors use the following applications in order to effectively manage contact center employees.
Within Contact Center Client, supervisors can access and oversee real-time customer activity and
agent response using a series of desktop monitors, as well as review historical activity. They can
affect service levels by manipulating agent group presence and distributing interactions among
queues. Using monitor alarms they can be notified when agents are inappropriately inactive or queues
become inordinately busy and react to these situations quickly and effectively to improve the customer
experience and optimize agent productivity.
Ignite is available as either a desktop or Web version. They share much of the same functionality
but also offer unique agent and supervisor experiences enabling you to choose the application that
suits your individual needs. In our documentation, we refer to desktop Ignite and its features as Ignite
(DESKTOP) and Web Ignite and its features as Ignite (WEB) or, where appropriate, as DESKTOP or
WEB only.
When circumstances dictate, supervisors licensed for Multimedia Contact Center can use Ignite to
temporarily handle interactions, alleviating customer wait times and ensuring a satisfactory service
level is maintained. Searching email, chat, SMS, and open media history can also be done in Ignite.
This sort of information is essential when building a case history, following a trail to investigate a
customer complaint or compliment, or to track agent performance.
With Ignite (WEB), supervisors can access real-time monitors to view current queue statistics and
callback requests. They can also view agent and employee statistics and interact with agent presence
to improve service levels.
Note:
Supervisors have unrestricted access to search email, chat, SMS, and open media history items
with an Advanced Supervisor or System Administrator license.
Assessing the statistical information that is found in the wide array of multimedia reports available
is an essential part of effective contact center supervision. Reports can be generated, viewed, and
scheduled in CCMWeb, your center for reports, setting preferences, and accessing the Help resource
documentation.
You can set alarms to notify you when there are a specified number of emails, chats, SMS, or
open media waiting or when agents have been in an unavailable state, such as Make Busy,
for a specified length of time. If alarms indicate a queue is overloaded with interactions or
understaffed, you can join that queue as an agent (dependent on licensing) or find an agent who
is capable of handling the media type for that queue and use the Agent Group Presence controls
to place them in the group associated to that queue. If an alarm demonstrates to you that an
agent has been unavailable for an extended period of time, you can remove the agent from Do
Not Disturb or Make Busy, if appropriate.
Client alarms are specific to each computer. To notify you that performance thresholds are not
being met, you can configure alarms so that
The following section describes typical supervisor usage of the monitors available in Contact
Center Client. For more detailed information regarding Contact Center Client, see "Real-time
Monitors".
Note:
Launching client-side desktop applications from the task bar causes them to bypass
the MiContact Center Updater Service process. To ensure successful updates from the
Enterprise Server, after an upgrade close all client-side applications for 15 minutes or reopen
them from the Start menu/Start screen.
You use Contact Center Client to access real-time monitors and functionality. Supervisors can
view real-time voice, email, chat, SMS, and open media statistics. After starting Contact Center
Client, supervisors can choose to minimize it to either the system tray or the taskbar.
1. In Contact Center Client, click the Contact Center Client button > Options.
2. Under Device control, clear the Display monitor device control option check box.
3. Click OK.
Note:
If Contact Center Client becomes disconnected from the server, upon re-connection agent
states will be automatically synchronized with the server.
The following table displays Employee state icons and their meanings.
The following table displays Agent state icons and their meanings.
Outbound - - - An agent on an
outgoing voice
interaction
• Ringing
• ACD
• ACD Hold
• Non ACD
• Non ACD Hold
• Outbound
• Outbound Hold
• Work Timer
• Do Not Disturb
• Make Busy
• System Idle
• Idle
You can customize the card design to display information in the monitors to suit your work
environment. For more information on customizing Contact Center Client monitors, see
"Customizing the information displayed on position and time monitors".
Contact Center Client real-time monitors and charts are briefly described in the following section.
If you require a more detailed description of the monitors and charts available with Contact
Center Client, see "Real-time Monitors".
For example, if an email agent in ACD was handling two emails, one at 5:30 and the other at
1:30, the displayed ACD time would be 5:30. If the employee finished handling the oldest email,
the time would change to 1:30.
The following table lists the Agent or Employee State by Time column headings and their
associated agent states.
Table 17: Agent State by Time and Employee State by Time column headings
The following table lists the Agent State by Time for Queue column headings and their
associated agent states.
The following table lists the Agent Shift column headings and their definitions.
Last Event Received Last Event Recd The most recent time an
agent event occurred
ACD Hold Time ACD Hold Time The duration of time ACD
interactions spent on hold
Non ACD Time Non ACD Time The duration of Non ACD
interactions handled, from
agent pickup to completion
(not including hold time)
(voice only)
Non ACD Hold Time Non ACD Hold Time The duration of time Non
ACD interactions spent on
hold (voice only)
Outbound Hold Time Out Hold Time The duration of time outbound
calls spent on hold, for agents
(voice only)
Do Not Disturb Time DND Time The duration of time the agent
entered the Do Not Disturb
State
Non ACD Count Non ACD Cnt The number of Non ACD
interactions handled by the
agent (voice only)
Hold ACD Count Hold ACD Cnt The number of times ACD
interactions were placed on
hold
Non ACD Hold Count Non ACD Hold Cnt The number of times Non
ACD interactions were placed
on hold (voice only)
Contacts Per Hour Contacts Per Hour The total ACD interaction
count minus the ACD short
handle count, divided by the
shift time for the agent
Logged In Not Present Time Logged In Not Present Time The duration of time the agent
was logged in to but not
present to any of their agent
groups, and the duration
of time the agent was not
present in a media type
across all groups
The following table lists the Queue by Period column headings and their definitions.
Note:
Note:
Total Conversation Time Ttl Conv Time The total time members spent
communicating (talking,
chatting, or replying) with
interactions during the 15-
minute interval
Average Conversation Time Avg Conv time The average time members
spent communicating with
interactions during the 15-
minute interval
Service Level % Level Scv Lvl % Tday During the 15-minute interval,
the percentage of interactions
answered within the Service
Level Time specified for the
queue
Note:
Note:
Note:
Note:
Note:
The Queue Group Now monitor enables supervisors to view aggregated statistics for Reporting,
Virtual, and Unified queue groups in real-time, as well as expand individual queue groups in the
monitor to view statistics for the queue group’s associated queues. (See the following figure.)
The following table lists the real-time and over-the-business-day Queue Now and Queue Group
Now queue and queue group statistics and their definitions.
Note:
Some statistics in the Queue Now monitor display in the Queue Group Now monitor as
member statistics.
Table 21: Queue Now and Queue Group Now queue statistic column headings
Available (Queue Now) Avail (Queue Now) The total number of members
logged in and not in Do Not
Agents Available (Queue Agts Avail (Queue Group Disturb, Make Busy, Work
Group Now) Now) Timer, Ringing, Reseize
Timer, Unknown, and Offline
(Ignite, WEB)
Note:
Note:
Average Time to Handle Avg Time Hndl The average time it takes for
the interaction to be taken
out of queue (answered or
picked) by a member
Average Time to Abandon Avg Time Abn The current average amount
of time customers wait in
queue before abandoning
interactions
Note:
Time to Handle Last Hour Time Hndl Last Hour The time interactions waited
in queue during the last hour
of business before being
handled by an agent
% Handled Last Hour % Hndl Last Hour For a queue, this is the
percentage of interactions
handled in the last hour of
business, compared to the
total number of interactions
offered to the ACD queue for
the day.
Service Level % Last Hour Svc Lvl % Last Hour For a queue, this is the
percentage of interactions
answered or picked within
your Service Level Time value
in the last hour.
interactions answered or
picked within your Service
Level Time value in the last
hour.
Unavailable Last Hour Unavail Last Hour The total number of times,
in the last hour of business,
interactions were rerouted
because the queue they tried
to access was in Do Not
Disturb or had no members
logged in
Average Handling Time Last Avg Hndl Last Hour The average duration of
Hour interactions from agent pick
up to client hang up (including
hold time) during the last hour
of business
Time to Handle Last 15 Time Hndl Last 15 Min The time interactions waited
Minutes in queue during the last 15
minutes of business before
being handled by a member
% Handled Last 15 Minutes % Hndl Last 15 Min For a queue, the percentage
of interactions answered
in the last 15 minutes of
business, compared to the
total number of interactions
offered to the ACD queue for
the day
Service Level % Last 15 Svc Lvl % Last 15 Min For a queue, this is the
Minutes percentage of interactions
answered or picked within
your Service Level Time
value in the last 15 minutes of
business.
Unavailable Last 15 Minutes Unavail Last 15 Min The total number of times,
in the last 15 minutes of
business, contacts were
rerouted because the queue
they tried to access was in
Do Not Disturb or had no
members logged in
Average Handling Time Last Avg Hndl Last 15 Min The average handling
15 Minutes duration of interactions
from interaction pickup
to interaction completion,
including hold time, during the
last 15 minutes of business
Abandoned ÷ Interaction
Offered)
% Abandoned Last Hour % Abn Last Hour For a queue, this is the
percentage of interactions
that were abandoned in the
last hour of business
Note:
Note:
Note:
Note:
The following table lists the real-time and over-the-business-day Queue Now and Queue Group
Now member statistics and their definitions.
Table 22: Queue Now and Queue Group Now member statistic column headings
Term Meaning
Term Meaning
Note:
Shift Time The total elapsed time logged for the member,
calculated based on the difference between
log in and last event received
Note:
Term Meaning
Note:
Note:
Hold Non ACD Time The duration of time Non ACD interactions
spent on hold (voice only)
Term Meaning
Note:
Term Meaning
Hold Non ACD Cnt The number of times Non ACD interactions
were placed on hold (voice only)
Note:
Contacts per Hour The total ACD interaction count minus the
ACD short handle count, divided by the shift
time for the member
Term Meaning
Not Present Time The duration of time the member was logged
in to but not present in an agent group or Ring
Group
Note:
Note:
Interactive Visual Queue works in conjunction with Contact Center Client. Before you use
Interactive Visual Queue, ensure your configuration in YourSite Explorer mirrors that of your
telephone system.
Note:
In order to use Interactive Visual Queue, you must enable all HCI options on Class of Service
Assignment form 1 (COS 1).
Note:
If the telephone system settings and Interactive Visual Queue settings do not match,
Interactive Visual Queue will not display the correct voice contact activity. For example, if
Queue 1 is set to a priority of 10 on the telephone system and a priority of 20 in YourSite
Configuration, Interactive Visual Queue will display voice contacts in Queue 1 as priority 20.
However, the actual queue will handle the voice contacts as priority 10.
Users can specify which statistics display in their charts. The following figure shows a Queue
Now Integer Chart
• Handled (Default)
• Abandoned (Default)
• Interflowed (Default)
• Calls Waiting
• Agents Available
• ACD
• Idle
• Non ACD
• Outbound
• Unavailable
• Offered
• Requeue
• Total Hour
• Interflowed Last Hour
• Unavailable Last Hour
• Offered Last 15 Minutes
• Handled Last 15 Minutes
• Abandoned Last 15 Minutes
• Interflowed Last 15 Minutes
• Unavailable Last 15 Minutes
• Logged out
• Logged in not present
• # Handled by 1-4
• Service Level %
• Handled %
• % Handled by 1-4
• % Handled Last Hour
• Service Level % last Hour
• % Handled Last 15 Minutes
• Service Level % Last 15 Minutes
• %Abandoned
• %Abandoned Last Hour
• %Abandoned Last 15 Minutes.
• Longest Waiting
• Average Time to Handle
• Average Time to Abandon Minutes
• Average Talk Time
• Ttl Talk Time
• Time to Handle Last Hour
• Average Time to Handle Last Hour
• Hdnl Last 15 Min
• Average Handling Time Last 15 Minutes
• Rmt Long Wtg
• Total Work Timer minutes
• Total make busy minutes
• Total occupancy minutes
For descriptions of the statistics, see "Queue Now and Queue Group Now column heading
definitions".
Note:
The following statistics are only for ACD path voice queues and multimedia queues
and will not display information for Ring Groups:
• Requeue
• # Handled by 1, 2, 3, 4
• % Handled by 1, 2, 3, 4
The following figure displays a Queue Performance by Period chart displaying the default
statistics of the Integer series.
Note:
Multimedia interactions in queue tagged as Junk or No Reply from Interactive Visual Queue
and Ignite are not included in queue Handled, Completed, and Offered counts.
The Integer series shows the following statistics across 15 minute intervals for queues or queue
groups:
• Handled (Default)
• Interflowed (Default)
• Offered
• Short Abandoned
• Abandoned
• Requeue
• # Handled by 1-4
The Percentage series shows the following statistics across 15 minute intervals for queues or
queue groups, by default:
• % Handled by 1-4
• Service Level % Today
• % Handled
The Time series show the following statistics across 15 minute intervals for queues or queue
groups, by default:
For more information for the definitions of these statistics, see "Queue by Period monitor".
Note:
The following statistics are only for ACD path voice queues and multimedia queues
and will not display information for Ring Groups:
• Requeue
• # Handled by 1, 2, 3, 4
• % Handled by 1, 2, 3, 4
• Total Work Timer Minutes
• Total make busy minutes
• Log employees and their agents in and out of their voice and multimedia applications
• Have agents join or leave their agent groups
• Place employees in and remove them from Make Busy
• Place employees in and remove them from Do Not Disturb
• Cancel the employee Work Timer
• Cancel the employee Reseize Timer
Using Interactive Contact Center with Contact Center Client, you can control agents on the
following monitors: Agent and Employee State by Position, Agent and Employee State by Time,
and Agent Shift.
Using Interactive Contact Center with Ignite (WEB), you can control agents on the following
monitors: Employee State and Agent State.
Individual supervisors can be restricted through security roles from managing particular monitors
and devices. For more information, consult your System Administrator.
When agent groups are created, an employee’s agents are assigned a default group presence,
either Present or Absent. If an employee's default presence is Absent will be set in the Logged
In Not Present agent state when they log in. To handle that media type, the employee has to
manually change their agent presence in Ignite or Contact Center Client. Employees whose
agents default presence is Present will be set in the Idle agent state when they log in. For details
about agent states, see "Employee and Agent state indicators".
Note:
Context sensitivity and monitor control are not supported with Ignite (WEB). You can alter the
state for only one employee or agent at a time.
Supervisors can control employees on the following Contact Center Client monitors:
• Employee State
Agent Control gives you control over individual agents in an agent monitor. Agent monitor
controls enable supervisors a more targeted look at specific aspects of an employee`s presence,
enabling supervisors to limit their influence to specific agents or media types. Since agent
monitors enable supervisors to view agents by agent group, Agent Control enables supervisors to
better manage their agent groups. (See the following figure.)
Supervisors can control agents on the following Contact Center Client monitors:
• Agent State
Note:
• An ACD Hot Desking Agent must enter an extension number each time the agents
logs on to the ACD routing system using Interactive Contact Center. The agent
cannot rely on the extension number last used when logging on. This is because
the ACD data stream unifies the agent ID and the extension. After a Hot Desking
Agent logs on or off of the ACD routing system using Interactive Contact Center,
sometimes the Interactive Contact Center agent controls are not available to the
agent for two to five minutes.
• You will be unable to log on an agent to the system if there are no available user
licenses.
• If your contact center participates in the use of PINs, supervisors with the correct
Class of Service do not require an agent’s PIN to interactively log in a Hot Desking
Agent.
• Depending on security roles and telephone switch settings, employees who are
licensed as Advanced Supervisor or System Administrator may not be prompted to
enter a PIN when logging into Interactive Contact Center, Softphone, or PhoneSet
Manager.
• If a Hot Desking Agent logs into an extension that serves as the overflow point for
a Ring Group, calls to that Ring Group will not be offered to the extension and will
remain queued or ringing until abandoned or answered.
• Hot desking users logging into a Ring Group extension must also be a member of
the Ring Group to ensure accurate reporting.
You log employee voice agents in and out in either an open Employee or Agent Monitor in
Contact Center Client. Multimedia agents are not logged in with voice agents.
• Right-click the cell of an employee and click Employee control > Log in > voice
agent. Alternatively, select the employee cell in an open monitor, click Log in from
the Employee Control tab on the Contact Center Client ribbon, and select the voice
agent.
Note:
When you log in an employee’s voice agent, you must enter the extension for the agent.
See the procedure below.
1. Right-click the cell of an employee and click Employee control > Log in > By
extension.
2. If the employee has multiple voice agents, select the agent to log in from the drop-
down list.
3. Type the Agent’s extension.
4. Click OK.
• Right-click the cell of a voice agent who is not logged into and click Agent Control >
Log in > voice agent. Alternatively, select the agent cell in an open monitor and click
Log in from the Contact Center Client ribbon.
Note:
When you log in a voice agent, you must enter the extension for the agent. See the
procedure below.
1. Right-click the cell of a voice agent and click Agent control > Log in > By extension.
2. If the employee has multiple voice agents, select the agent to log in from the drop-
down list.
3. Type the Agent’s extension.
4. Click OK.
The following procedures take place in either an open Employee monitor or an open Agent
monitor in Contact Center Client.
• Right-click the cell of an employee and click Employee control > Log off.
Alternatively, select the employee cell in an open monitor and click Log Off from the
Employee Control tab on the Contact Center Client ribbon.
Note:
Logging off an employee's agent logs off all of the employee's agents simultaneously.
• Right-click the cell of an agent and click Agent control > Log off. Alternatively,
select the agent cell in an open monitor and click Log Off from the Agent Control
tab on the Contact Center Client ribbon.
1. Right-click the monitor and click Monitor control > Log off.
Alternatively, click the Monitor Control tab in the Contact Center Client ribbon and select Log
Off.
2. Click Yes.
1. Right-click the monitor and click Monitor control > Log off.
Alternatively, click the Monitor Control tab in the Contact Center Client ribbon and select Log
Off.
2. Click Yes.
The following procedure takes place in either an Agent State or Employee State monitor in Ignite
(WEB).
Note:
This step is not required if the agent is set to automatically log in when the ‘Available’ state
is selected.
The following procedure takes place in either an Agent State or Employee State monitor in Ignite
(WEB).
Note:
• An agent's ACD hot desk line remains in service while they are logged in as
an ACD hot desk user even if they are not present in any ACD groups and not
receiving ACD calls.
To join an agent to or have an agent leave an agent group in an open Employee monitor
1. Right-click the cell of an employee and click Employee control > Join/Leave Agent
Group > [Agent].
Alternatively, select the cell of an employee and in the Employee Control tab of the Contact
Center Client ribbon, click Join/Leave agent group > [Agent].
2. Select the agent group(s) to which you want the employee’s agent(s) to join or
deselect the agent group(s) to have the employee’s agent(s) leave the agent groups.
3. Click OK.
To join an agent to or have an agent leave an agent group in an open Agent monitor
1. Right-click the cell of an agent who is logged on and click Agent control > Join/
Leave Agent Group.
Alternatively, select the cell of an agent and click Join/Leave Agent Group from the Agent
Control tab in the Contact Center Client ribbon.
2. Select the agent group(s) to which you want the agent(s) to join or deselect the agent
group(s) to which you want the agent(s) to leave.
3. Click OK.
The following procedures take place in either an Agent State or Employee State monitor in Ignite
(WEB).
1. In the monitor, select the agent for which you want to modify agent group presence.
2. Click Agent Groups.
3. Hover over the agent group's avatar and select Join All.
4. Click Update.
1. In the monitor, select the agent for which you want to modify agent group presence.
2. Click Agent Groups.
3. Hover over the agent group’s avatar and select Leave All.
4. Click Update.
1. In the monitor, select the agent for which you want to modify agent group presence.
2. Click Agent Groups.
3. To join an agent to all agent groups, click Join All > Update.
4. To remove an agent from all agent groups, click Leave All > Update.
1. In the monitor, select the agent for which you want to modify agent group presence.
2. Click Agent Groups.
3. To become available to answer interactions of a specific media type, click the media
icon in the agent group so the icon displays in blue.
4. To become unavailable to answer interactions of a specific media type, click the media
icon in the agent group so the icon displays in grey.
5. Click Update.
Note:
Employees in Work Timer can apply Busy/Make Busy or DND, but will remain in a Work
Timer state until the Work Timer expires or is cancelled.
Placing employees into Make Busy places both employees and all of their agents into Make
Busy.
The following procedures take place in either an open Employee monitor or an open Agent
monitor in Contact Center Client.
• Right-click the cell of an employee and click Employee control > Set Make Busy
> reason code. Alternatively, select an empty cell in an open monitor and click Set
Employee Make Busy > reason code from the Employee Control tab in the Contact
Center Client ribbon.
1. Right-click the monitor and click Monitor control > Set Make Busy > reason code.
Alternatively, select an empty cell in an open monitor and click Set Make Busy >
reason code from the Monitor Control tab in the Contact Center Client ribbon.
2. Click Yes.
• Right-click the cell of an agent and click Agent control > Set Employee Make Busy
> reason code. Alternatively, select the agent cell in an open monitor and click Set
Employee Make Busy > reason code from the Agent Control tab in the Contact
Center Client ribbon.
1. Right-click the monitor and click Monitor control > Set Employee Make Busy >
reason code. Alternatively, select an empty cell in an open monitor and click Set
Make Busy > reason code from the Monitor Control tab in the Contact Center Client
ribbon.
2. Click Yes.
The following procedures take place in either an open Employee monitor or an open Agent
monitor in Contact Center Client.
• Right-click the cell of an employee whose agents are in Make Busy and click
Employee control > Remove Make Busy. Alternatively, select an empty cell in an
open monitor and click Remove Make Busy from the Employee Control tab in the
Contact Center Client ribbon.
1. Right-click the cell of an employee who is in Make Busy and click Monitor control
> Remove Make Busy. Alternatively, select an empty cell in an open monitor and
click Remove Make Busy from the Monitor Control tab in the Contact Center Client
ribbon.
2. Click Yes.
• Right-click the cell of an agent in Make Busy and click Agent control > Remove
Make Busy. Alternatively, select the agent cell in an open monitor and click Remove
Make Busy from the Agent Control tab in the Contact Center Client ribbon.
1. Right-click the cell of an employee and click Monitor control > Remove Make Busy.
Alternatively, select an empty cell in an open monitor and click Remove Make Busy
from the Monitor Control tab in the Contact Center Client ribbon.
2. Click Yes.
Note:
Employees in Work Timer can apply Busy/Make Busy or DND, but will remain in a Work
Timer state until the Work Timer expires or is cancelled.
Placing an employee into Busy places them in Busy across all media types for which they answer
interactions. While in Busy, they can receive transferred multimedia interactions, however,
inbound multimedia interactions will not be routed to them. They can also receive Non ACD voice
interactions and pick interactions waiting in queue.
The following procedure takes place in either an Agent State or Employee State monitor in Ignite
(WEB).
The following procedure takes place in either an Agent State or Employee State monitor in Ignite
(WEB).
1. In the monitor, select the employee you want to remove from Busy.
2. Under State, select an alternate state, or, click X button next to Busy... to remove the
busy code.
Note:
Note:
• If an agent on an ACD calls puts themselves into MKB or DND, Work Timer events
are not received for that call.
• Employees in Work Timer can apply Busy/Make Busy or DND, but will remain in a
Work Timer state until the Work Timer expires or is cancelled.
Placing employees into Do Not Disturb places employees and all of their agents into Do Not
Disturb.
The following procedures take place in either an open Employee monitor or an open Agent
monitor in Contact Center Client.
• Right-click the cell of an employee and click Employee Control > Set Do Not Disturb
> reason code. Alternatively, select the employee cell in an open monitor and click Set
Employee Do Not Disturb > reason code.
1. Right-click the monitor and click Monitor control > Set Do Not Disturb > reason
code. Alternatively, select an empty cell in an open monitor and click Set Do Not
Disturb from the Monitor Control tab in the Contact Center Client ribbon.
2. Click Yes.
• Right-click the cell of an agent who is logged on and click Agent control > Set
Employee Do Not Disturb > reason code. Alternatively, select the agent cell in an
open monitor and click Set Do Not Disturb > reason code from the Agent Control tab
in the Contact Center Client ribbon.
1. Right-click the monitor and click Monitor control > Set Do Not Disturb > reason
code. Alternatively, select an empty cell in an open monitor and click Set Do Not
Disturb from the Monitor Control tab in the Contact Center Client ribbon.
2. Click Yes.
The following procedures take place in either an open Employee monitor or an open Agent
monitor in Contact Center Client.
• Right-click the cell of an employee who is in Do Not Disturb and click Employee
control > Remove Do Not Disturb. Alternatively, select the employee cell in and click
Remove Do Not Disturb from the Employee Control tab in the Contact Center Client
ribbon.
To remove all of a monitor’s employees in an open Employee monitor from Do Not Disturb
• Right-click the monitor and click Monitor control > Remove Do Not Disturb.
Alternatively, select an empty cell in an open monitor and click Remove Do Not
Disturb from the Monitor Control tab in the Contact Center Client ribbon.
• Right-click the cell of an agent who is in Do Not Disturb and click Agent control >
Remove Do Not Disturb. Alternatively, select the agent cell in an open monitor and
click Remove Do Not Disturb from the Agent Control tab in the Contact Center
Client ribbon.
To remove all of a monitor’s employees in an open Agent monitor from Do Not Disturb
• Right-click the monitor and click Monitor control > Remove Do Not Disturb.
Alternatively, select an empty cell in an open monitor and click Remove Do Not
Disturb from the Monitor Control tab in the Contact Center Client ribbon.
Note:
Employees in Work Timer can apply Busy/Make Busy or DND, but will remain in a Work
Timer state until the Work Timer expires or is cancelled.
Placing an employee into Do Not Disturb places them in Do Not Disturb across all media types
for which they answer interactions. While in Do Not Disturb, they are unable to receive inbound
multimedia interactions and internal voice interactions, including transfers.
The following procedure takes place in either an Agent State or Employee State monitor in Ignite
(WEB).
1. In the monitor, select the employee you want to place in Do Not Disturb.
2. Under State, click Do Not Disturb….
3. Choose a DND code.
The following procedure takes place in either an Agent State or Employee State monitor in Ignite
(WEB).
1. In the monitor, select the employee you want to remove from Do Not Disturb.
2. Under State, select an alternate state, or, click X button next to Do Not Disturb... to
remove the DND Reason code.
Note:
Note:
Employees in Work Timer can apply Busy/Make Busy or DND, but will remain in a Work
Timer state until the Work Timer expires or is cancelled.
In an Employee monitor or Agent monitor, you can cancel Work Timer for one or more
employees. The following procedures take place in either an open Employee monitor or an open
Agent monitor in Contact Center Client.
• Right-click the cell of an employee who is in Work Timer and click Employee control
> Cancel Work Timer. Alternatively, select the employee cell in an open monitor and
click Cancel Work Timer in the appropriate media section of the Employee Control
tab in the Contact Center Client ribbon.
• Right-click the monitor and click Monitor control > Cancel Work Timer. Alternatively,
select an empty cell in an open monitor and click Cancel Work Timer in the media
type’s section of the Monitor Control tab in the Contact Center Client ribbon.
• Right-click the cell of an agent who is in Work Timer and click Agent control > Cancel
Work Timer. Alternatively, select the agent cell in an open monitor and click Cancel
Work Timer from the Agent Control tab in the Contact Center Client ribbon.
• Right-click the monitor and click Monitor control > Cancel Work Timer. Alternatively,
select an empty cell in an open monitor and click Cancel Work Timer from the
Monitor Control tab in the Contact Center Client ribbon.
Note:
Employees in Work Timer can apply Busy/Make Busy or DND, but will remain in a Work
Timer state until the Work Timer expires or is cancelled.
The following procedure takes place in either an Agent State or Employee State monitor in Ignite
(WEB).
1. In the monitor, select the employee you want to remove from Work Timer.
2. Click State and select an alternate state.
Note:
To cancel Reseize Timer for an employee’s voice agent in an open Employee monitor
• Right-click the cell of an employee who is in Reseize Timer and click Employee
control > Cancel Reseize Timer. Alternatively, select the employee cell in an open
monitor and click Cancel Reseize Timer in the appropriate media section of the
Employee Control tab in the Contact Center Client ribbon.
To cancel Reseize Timer for all employee voice agents in a monitor in an open Employee monitor
• Right-click the monitor and click Monitor control > Cancel Reseize Timer.
Alternatively, select an empty cell in an open monitor and click Cancel Reseize Timer
from the Monitor Control tab in the Contact Center Client ribbon.
To cancel Reseize Timer for an employee’s voice agent in an open Agent monitor
• Right-click an agent who is in Reseize Timer and click Agent control > Cancel
Reseize Timer. Alternatively, select the agent cell in an open monitor and click
Cancel Reseize Timer in the appropriate media section of the Agent Control tab in
the Contact Center Client ribbon.
To cancel all of the voice agents on a monitor in the Reseize Timer state in an open Agent
monitor
• Right-click the monitor and click Monitor control > Cancel Reseize Timer.
Alternatively, select an empty cell in an open monitor and click Cancel Reseize Timer
from the Monitor Control tab in the Contact Center Client ribbon.
Interactive Visual Queue is comprised of a Queued media grid and, for voice media, an
Abandoned media grid and a Callback to be processed grid. The Interactive Visual Queue
Queued media grid displays all types of media interactions that are currently queued. It does not
display items that have already been offered to agents or are currently being handled by agents.
Using a drag-and-drop operation, supervisors can balance traffic by moving interactions from
busy queues to less active queues and ensure optimum customer service by directing high
priority interactions to experienced agents. Supervisors can pick interactions from the queue and
handle them, and can tag email interactions as junk or no reply needed to remove them from the
queue. Supervisors can also preview email interactions.
For information on using Interactive Visual Queue with voice media, see "Interactive Visual
Queue".
Note:
• Virtual, Reporting, and Unified Queue Groups are shown in the Queue groups
list.
The following list provides descriptions of the column headings available in the Queued media
grid:
• Position (#) displays the answer position relative to other interactions in the queue
• Media icon displays the media type
• Queue Name displays the name of the queue
• Queue Dialable displays:
• Voice—caller # / ANI
• Chat—Chat email address from pre-chat form
• SMS—From mobile number
• Email—From email address
• Subject displays
• Voice—blank
• Chat—Chat subject from pre-chat form
• SMS—blank
• Email—Email subject
• Is Callback indicates if the queued media is a callback request (voice only)
• Service level countdown provides a countdown in seconds when the contact will
exceed the target time to meet the service level
• Contact Name is the name associated with the contact (if available)
• Voice—caller ID
• Chat—Chat name from pre-chat form
• SMS—blank
• Email—Email “From” name, if available
• Time Offered to Queue is the time the contact entered the current queue
• DNIS (To Address) displays
• Voice—DNIS Number
• Chat—blank
• SMS—blank
• Email—receiver's email address
• To Name displays
For information on other Interactive Visual Queue grids that are voice media only, see "Interactive
Visual Queue monitor grids". For information on hiding or making columns visible, sorting data in
a column, or re-arranging columns, see "Real-time Monitors".
When you redirect an interaction manually, the interaction always adopts the default priority level
of the destination queue.
When you redirect an interaction manually, the interaction always adopts the default priority
level of the destination queue. For example, suppose Queue 1 has a priority of 1 and Queue
2 has a priority of 15. When an interaction first enters Queue 1, it has a priority of 1. However,
if you manually move that interaction to Queue 2, using either a drag-and drop operation or
the right-click menu, the interaction priority lowers to 15. The rules work the same in reverse.
If you manually move a priority 15 interaction from Queue 2 to Queue 1, the interaction priority
increases to 1 when it enters Queue 1.
Interflow
You can configure Inqueue workflows to automatically move an interaction from one to queue to
another after a specific duration through the Interflow activity. For example, you could configure
your system to move an interaction from Queue 1 to Queue 2 if the interaction has not been
answered within 30 seconds. For more information on the Interflow activity, see "Routing
interactions with the Interflow activity".
Redirection
Using Interactive Visual Queue, you can manually redirect an interaction from a queue to another
queue, to an agent, or, if it is a voice interaction, a dialable number.
There are two ways a voice interaction can be removed from the system. If a voice interaction is
moved more than 10 times, either by redirection or by interflow, the interaction is dropped
from the system. You can see the current number of times an interaction has moved between
queues in the Queue Hops column. A voice interaction will also be automatically removed
from the system if its total time in the system exceeds 24 hours. The Total Time column lists
the interaction’s duration in the system. Email, SMS and chat interactions are removed from the
system if they are offered to agents over 50 times.
If an interaction is an email interaction, it can also be set to No Reply or Junk and removed from
the system.
You can manually redirect an interaction in the Queued media grid using the following methods:
You may notice that the first two methods perform the same action. However, the second method
is convenient when a queue monitor is maximized and you want to move an interaction without
having to resize one or more monitors.
You can remove interactions in the Interactive Visual Queue Monitor in the following ways:
When you manually redirect (drag and drop) an interaction in Interactive Visual Queue, Mi
Contact Center Business changes the way the voice interaction is pegged on the Queue
Performance reports. If you redirect an interaction before the short abandon time set for the
queue, the interaction is pegged as Unavailable. If you redirect an interaction after the short
abandon time set for the queue, the interaction is pegged as Interflowed. An internal ACD
interaction is pegged as Abandoned if the interaction is redirected at any time.
1. In the Queued media grid, click anywhere in the row of the interaction you want to
move.
2. Use a drag-and-drop operation to move the interaction from its original queue monitor
to a new queue monitor.
Note:
• You can drag an interaction only from one Interactive Visual Queue monitor to
another if the destination monitor has the same media type (such as email to
email, chat to chat, and so on).
• Only one interaction can be moved over at a time.
• If the destination monitor has multiple queues for the same media type, the
system will assign the redirected interaction to the queue with the fewest
interactions in queue.
1. In the Queued media grid, right-click the row of the interaction you want to redirect and
click Send to > Queue.
Note:
You can use the search button to locate a specific queue, either by name or reporting
number.
2. Click the name of the queue to which you want to redirect the interaction.
3. Click OK.
1. In the Queued media grid, right-click the row of the interaction you want to redirect and
click Send to.
2. In the list of queues beneath Queue, select a queue.
1. In the Queued media grid, right-click the row of the interaction you want to redirect and
click Send to > Agent.
A list of available agents who can handle the interaction’s media type displays.
Note:
You can use the search button to locate a specific agent, either by name or reporting
number.
2. Click the name of the agent to which you want to send the interaction.
3. Click OK.
1. In the Queued media grid, right-click the row of the email interaction you want to
redirect and click Send to > [Destination].
2. When you click [Destination], it changes to a text box.
3. Type an email address into the text box and press Enter.
You can enter multiple email addresses, separating each with a semi-colon (e.g.
[email protected];[email protected]).
Note:
If you are licensed to access multimedia functionality in Ignite, you can alternatively
redirect interactions directly to an agent by forwarding or transferring. See "Handling
emails in Ignite" and "Handling chats in Ignite".
1. In the Queued media grid, select the interaction(s) you want to tag as Junk.
Select multiple emails by holding CTRL or Shift and clicking the emails.
2. Right-click the row of the interaction you want to tag as Junk.
3. Click Junk Conversation.
4. Click Yes.
Note:
1. In the Queued media grid, select the interaction you want to tag as No Reply needed.
Select multiple interactions by holding CTRL or Shift and clicking the emails.
2. Right-click the row of the interaction you want to tag as No Reply needed.
3. Click No Reply.
Note:
The following figure shows a previewed chat session. Previewed chats show the content of the
chat session. Supervisors can open links in the previewed chat session, but they cannot view
embedded media or participate in the chat. A supervisor can preview only one chat at a time.
Supervisors previewing chats must have an associated chat agent.
The following figure shows a previewed SMS interaction. Previewed SMS interactions show the
content of the SMS session. Supervisors can open links in the previewed SMS session, but they
cannot view embedded media or participate in the SMS interaction. A supervisor can preview
only one SMS interaction at a time. Supervisors previewing SMS interactions must have an
associated SMS agent.
While the preview window is open, no other actions can be taken in Contact Center Client,
although you can still answer phone calls from the desktop notification. Previewing a multimedia
interaction does not impact the ability of that multimedia interaction to interflow to another queue,
to be offered to or picked by an agent, or any other activity in Multimedia Contact Center.
The following procedures take place in an open Interactive Visual Queue monitor in Contact
Center Client.
• Right-click the email, SMS or chat you want to preview and select Preview.
The Forecasting tool forecasts for each media separately when generating forecasts and does
not adjust for agent Workload. Agents allowed to handle simultaneous interactions are likely to
be more efficient than those handling a single call due to their ability to multitask. As a result,
the number of required agents in a forecast may be met by fewer agents if their Workload
permits them to handle different media interactions and numbers of interactions concurrently.
Supervisors should adjust their forecast statistics to compensate for the Workload of the agents
being forecasted. It is recommended that Workload be the same for all members in an agent
group being forecasted.
For more information on forecasting, see the Forecasting chapter of the MiContact Center
Business User Guide. For information on using the Forecasting tool within Workforce Scheduling
to schedule your employees based on multimedia queue traffic needs, see the Workforce
Scheduling chapter of the MiContact Center Business User Guide.
For example, you notice that on July 15 you have 12 interactions abandon between 10:00 AM
and 10:15 AM. You can review the interactions and the agents’ actions on that date for that
time period with Auditor. Did all of the interactions arrive at the same time? Did all of the agents
go on break at the same time? If all of the interactions arrived at once, you need to schedule
more people. If all of the agents went on break at the same time, you need to adjust their break
schedule.
Using Auditor you can also track when employees log on and log off the system. It is easy to
determine if any of the employees consistently start late or finish early.
With Auditor, you can use existing profiles, including alarm thresholds, when viewing past days
run in real time.
The first toolbar consists of real-time monitors that provide information on agent availability,
queue statistics, and graphic displays on queues. (See the following figure.)
Note:
When viewing a Queue or Queue Group monitor, emails in queue that arrived from a
previous day in the auditing period will not show up in the monitor statistics until an action
is taken on them during the auditing period.
3. Start Auditor.
Note:
When viewing a Queue or Queue Group monitor, emails in queue that arrived from a
previous day in the auditing period will not show up in the monitor statistics until an action
is taken on them during the auditing period.
3. Start Auditor.
Note:
If you are using the Contact Center Client marquee, Contact Center PhoneSet Manager,
Contact Center Softphone, or Interactive Visual Queue applications (which function only in
real time), open Auditor in another instance of Contact Center Client.
The speed of the audit, expressed as a ratio of real time to play speed, displays on the right of
the speed icon.
5. Move the slider to select the time of day at which you want to start monitoring.
6. Click the play button to play the real-time events of the selected date.
• Employee State
• Agent State
• Queue Now
• Callback Requests
Note:
To learn how to add and configure settings for real-time monitors in Ignite (WEB), see
"Configuring Ignite (WEB) dashboards".
Note:
Only one employee at a time can display in the Employee State monitor, but you can
optionally add several employee monitors to a dashboard to access information for multiple
employees.
The Employee State monitor in Ignite (WEB) is accessible from your Ignite (WEB) Dashboard,
To learn how to add and configure settings for the Employee State monitor in Ignite (WEB), see
"Configuring Ignite (WEB) dashboards".
Each column lists agents in order of time in state, with the longest in state at the top. For
example, the agent at the top of the Idle column is the next longest idle agent and should receive
the next inbound interaction.
The following table lists and describes real-time agent state information that displays in the Agent
State monitor in Ignite (WEB).
STATISTIC DESCRIPTION
The Agent State monitor in Ignite (WEB) is accessible from your Ignite (WEB) Dashboard,
To learn how to add and configure settings for the Agent State monitor in Ignite (WEB), see
"Configuring Ignite (WEB) dashboards".
Queue statistics include Offered, Service Level %, Interactions Waiting, Requeued, and Longest
Waiting. Handled, Interflowed, and Abandoned counts can also be accessed by hovering over
‘Offered’ for each queue or queue group.
The following table lists and describes queue statistics that display in the Queue Now monitor in
Ignite (WEB).
STATISTIC DESCRIPTION
STATISTIC DESCRIPTION
Note:
Note:
STATISTIC DESCRIPTION
Note:
The current number of agents, by state, also displays for each queue or queue group for the
following agent states:
• Idle: includes agents who are available for ACD but not currently handling any
interactions
• ACD: includes agents in ACD and ACD Hold
• Non-ACD: includes agents in Non ACD, Non ACD Hold, Outbound, and Outbound
Hold
• Unavailable: includes agents in Do Not Disturb, Busy, and Work Timer
The Queue Now monitor in Ignite (WEB) is accessible from your Ignite (WEB) Dashboard,
To learn how to add and configure settings for the Queue Now monitor in Ignite (WEB), see
"Configuring Ignite (WEB) dashboards".
The Callback Requests monitor enables users to requeue, reject, and delete callbacks from
within the monitor. Requeued callbacks are re-entered into their queue. Rejected callbacks are
removed from the queue and will not be offered to employees. Deleted callbacks are removed
from the monitor, but are not removed from the system.
• In the row of the call you want to interact with, in the Actions column, left-click either
Requeue, Reject, or Delete.
The following table lists and describes the statistics available in the Callback Requests monitor.
STATISTIC DESCRIPTION
The Callback Requests monitor in Ignite (WEB) is accessible from your Ignite (WEB) Dashboard,
To learn how to add and configure settings for the Callback Requests monitor in Ignite (WEB),
see "Configuring Ignite (WEB) dashboards".
Ignite is also useful for directly transferring interactions to specific agents or as an alternative
method for tagging interactions as Junk or No Reply Needed. In addition, supervisors access
Ignite to search email, chat, SMS, and open media history.
Supervisors can use the real-time monitors available in the Ignite (WEB) Dashboard to view real-
time queue, agent, and employee statistics as well as interact with agent presence to improve
service levels. You can also view callback requests and choose to requeue, reject, or delete
items from the list.
Note:
Employees must be licensed for Multimedia Contact Center to access the full multimedia
features in Ignite. For more information, see "Adding multimedia capabilities to employees".
See the Ignite section of this guide for information regarding handling interactions in Ignite.
See "Searching Ignite’s folders" and "Reviewing contact history" for more information.
For more information, see "Configuring Ignite (WEB) dashboards", "Accessing real-time
information with (WEB)", and "Interacting with agent presence to improve service levels".
This page lists the names and reporting numbers of group members (agents).
5. Select one or multiple agents from the list to add to the selected agent group.
6. Select a suitable skill level from the Skill Level drop-down list. This is applied for one
or multiple agents that you select.
7. Select a presence status for the agent by clicking on the presence icons.
8. Click Apply.
This page lists the names and reporting numbers of the group members (agents).
5. Select one or multiple agents from the list that you want to update.
6. Select a suitable skill level for the agent from the Skill level drop-down list.
7. Select a presence status for the agent by clicking on the presence icons.
8. Click Apply.
This will update the skill level and presence status of the agents.
This page lists the names and reporting numbers of the group members (agents).
5. Select one or multiple agents to be deleted from the group.
6. Click Remove from agent group button.
• This will remove the selected agents from the agent group.
Agents - Handling customer
interactions in a multimedia contact 7
center
• Managing agent preferences
• Ignite
Agents in a multimedia contact center are enabled to handle interactions of various media types,
including voice, email, chat, SMS, and open media. Ignite enables agents to interact with customers,
view and adjust their Agent Group Presence and Busy/Make Busy and Do Not Disturb states, and
view statistics in real time to determine availability of other agents and to be aware of current contact
center conditions.
Agent preferences, such as login ID and language, can be modified in CCMWeb, your online center
for personal settings and accessing the Help resource documentation.
Agent preferences, such as login ID and language, can be modified in CCMWeb, your online
center for personal settings and accessing the Help resource documentation.
Agents can manage their preferences in CCMWeb, a web-based application that provides agents
with the ability to view and change settings associated with their login ID. Using the options under
CCMWeb’s My options tab, agents can set their language preferences, view their security roles,
change their password, and manage lists of contacts for emailing reports. Via options under the
Help tab, agents can access help documentation, view software information, and download the
Client Component Pack installation file.
See "Setting up user preferences" to learn how to set user preferences, view security roles, and
configure email contacts.
7.2 Ignite
Ignite is used by agents to handle all types of media, including voice, email, chat, SMS, and open
media.
Note:
The Desktop Ignite application is not supported on MiCC Business for Open SIP. Agents
must use Web Ignite for all agent functionality.
Ignite is available as either a desktop or Web version. They share much of the same functionality
but also offer unique agent and supervisor experiences enabling you to choose the application
that suits your individual needs. In our documentation, we refer to desktop Ignite and its features
as Ignite (DESKTOP) and Web Ignite and its features as Ignite (WEB) or, where appropriate, as
DESKTOP or WEB only.
If you want access to the following features, we recommend using Ignite (DESKTOP):
• State indicator collaboration (state changes in either Ignite or MiCollab are reflected
in each application)
• Ability to dock Ignite to MiCollab Client and minimize/maximize both applications
simultaneously
• Auto-logout from MiCollab Client when agent logs out of Ignite
• Recording and implementing pre-announce and agent greetings
• Requesting help from other agents or supervisors while on a call
• Viewing agents' Inbox contents
• Being notified by email of Enterprise Server alarms
• Using the ‘Next Longest button’ to access longest-waiting Chat and SMS
interactions with a single click
• Grouping, sorting, and organizing interactions using the card and grid views
If you want access to the following features, we recommend using Ignite (WEB):
Note:
When Ignite (WEB) is used on a desktop PC, laptop PC, or a tablet, the machine enters
sleep mode after a certain period of inactivity. Upon waking up the device, Ignite (WEB) need
to be refreshed to re-establish connection to the MiContact Center Business. Considering
this, MiContact Center Business does not support or recommend the usage of Mobile
devices to connect to Ignite (WEB) as Mobile devices have a much shorter awake time and
will constantly enter the sleep mode, because of which new notification of conversations
might not be received by the device.
Note:
Using MiCollab Client in conjunction with Ignite, to handle voice interactions, but without
integration functionality, such as collaborative state updates, docking, minimizing/maximizing
together, click to IM other agents and supervisors, and MiCollab Client auto-logout when
logging out of Ignite.
The following sections describe Ignite's functionality and include procedures for working in Ignite,
with a focus on non-voice media types. If your contact center also handles voice interactions, we
recommend implementing the MiCollab and Ignite integration described in the MiContact Center
Business User Guide.
Voice agents should consult "Logging in and out of Ignite (DESKTOP)" for important instructions
on logging into Ignite in conjunction with Contact Center Softphone, PhoneSet Manager, or hard
set desk phones.
For information on accessing the Ignite web client, see "Logging into Ignite (WEB)".
Note:
Employees without Multimedia Contact Center licensing can be licensed to use Ignite but will
have access to voice interactions only.
• Open Ignite
• Close Ignite
Note:
When Ignite closes, it logs the agent out of all associated devices.
To open Ignite
• Ignite can be opened from Windows’ Start menu, Programs menu, Taskbar, or from a
Desktop shortcut.
Note:
• Launching client-side desktop applications from the task bar causes them to
bypass the MiContact Center Updater Service process. To ensure successful
updates from the Enterprise Server, after an upgrade close all client-side
applications for 15 minutes or reopen them from the Start menu/Start screen.
• If MiContact Center Business applications are configured to use Windows
Authentication, opening Ignite also logs agents into the program.
To close Ignite
• In the Sidebar, click the Sign Out or Exit button and select Exit Application.
We recommend that agents using Ignite log into their voice device before logging into Ignite.
Once logged into their voice device, the agent can minimize Contact Center Client to the system
tray and log into Ignite.
Agents can configure Contact Center Client to launch Ignite when logging into the phone, so
the agent only has to launch one application to handle voice and multimedia. If you choose the
‘Remember Me’ option on the Ignite Sign In screen, Ignite launches and automatically logs you
in. For more information, see "Automatically launching Ignite upon voice login (DESKTOP)". This
option is available for Contact Center Softphone and PhoneSet Manager only.
Agents may find that, after logging into their phone and into Ignite, they are placed in Make Busy
across all agent capabilities. This is a recommended administrative configuration. After logging
into Ignite the agent can remove Make Busy and become available to receive ACD voice and
multimedia interactions.
When an employee logs out of Ignite, all agents representing the employee are logged out,
including voice agents. However, voice agents on active calls are not logged out until the call is
complete. Logging out of the voice device logs multimedia agents out of Ignite and may requeue
items in the Inbox, depending on administrative configurations.
Agents logging out of Ignite with interactions in the Inbox are notified if active interactions will
requeue. Interactions that requeue are indicated in Ignite’s List pane and display a larger media
icon than interactions that do not requeue. To avoid losing work on these items, agents should
finish their reply or transfer the items to a queue before logging out.
1. Start Ignite.
2. If prompted, type your Username and Password and verify the Enterprise Server IP
address.
3. If you use Secure Socket Layer, select SSL.
4. Optionally, select Remember my credentials.
5. Click Login.
To log out of Ignite and restart the program to the login screen
• In the Sidebar, click the Sign Out or Exit button and select Sign Out.
The agent is logged out of Ignite, and Ignite restarts to the login screen.
• In the Sidebar, click the Sign Out or Exit button and select Exit Application.
This option can be saved to your Contact Center Client profile. However, the option is only
available when using PhoneSet Manager and Contact Center Softphone.
Note:
If you have not configured a profile, see "Setting up the soft phone" in the MiContact
Center Business User Guide.
3. In the ribbon, select Soft Phone and click the Soft Phone icon.
4. In the Soft phone configuration window, select the Automatically launch the Ignite
Client on ACD login check box.
5. Click OK.
6. On the ribbon, click Save.
Note:
If you are running the MiCollab Client Ignite integration, when you log into MiCollab Client,
Ignite is automatically launched. You can set your profile to also automatically launch
MiCollab Client when you start and log into Ignite. See "General settings (DESKTOP)".
The following figure illustrates Ignite’s UI, in the My Folders view. This is the view where agents
perform most of their tasks related to handling multimedia interactions.
Note:
If you display taskbars on multiple monitors, maximizing Ignite on the secondary display
does not cover the taskbar and in some instances causes the taskbar to obscure a portion of
Ignite. To correct this, see the following Mitel Knowledge Base article: http://micc.mitel.com/
kb/KnowledgebaseArticle52017.aspx.
Agents with multimedia and voice capabilities should follow best practices for logging into voice
and multimedia. For more information, see "Logging in and out of Ignite".
Note that the availability of Ignite’s functionality depends on employee licensing. If you log into
Ignite and are not able to access its functionality, or if you receive a message saying you are not
configured for ACD, contact your supervisor or system administrator.
If permitted, agents can adjust their agent group presence on this screen.
For information on accessing the Agent Group Presence Status screen, see "Viewing Agent
Group Presence in Ignite".
For information on using the Agent Group Presence Status screen to become present in, or
absent from, agent groups, see "Adjusting Agent Group Presence in Ignite".
Agents can expand or collapse Ignite’s Folders pane to give more or less space to the Media
Folder and Queue Folders views. By default, the Folders pane is expanded.
To expand or contract Ignite’s Folders pane, click the arrow button beside Folders, at the top of
the Folders pane.
See "Viewing Agent Group Presence in Ignite" and "Adjusting Agent Group Presence in
Ignite".
• Make Busy
• Request help
Agents can select up to three agent handling statistics, by media type, to display in the
Sidebar. If you are enabled for multiple media types, you can toggle between media-specific
statistics using the icon directly above the statistical displays. Select the headphone icon for
voice, the envelope icon for email, the interaction icon for chat, or the phone icon for SMS
statistics. By default the Sidebar displays Shift Time, DND Time, and MKB Time. However,
using the 'Settings' button in the Sidebar, you can select any agent statistics to display.
• Settings
See "Logging in and out of Ignite (DESKTOP)" and "Opening and closing Ignite (DESKTOP)".
• Expand Ignite / Collapse Ignite
Clicking the 'Expand Ignite / Collapse Ignite' button toggles the view based on your configured
settings. See "Your Ignite profile (DESKTOP)".
For information on handing multimedia using the Action bar, see "Handling multimedia contacts in
Ignite", "Handling emails in Ignite", "Handling chats in Ignite", and "Handling SMS in Ignite".
Note:
The Status bar is only visible to employees with associated multimedia agents. For example,
supervisors without an associated voice, email, chat, or SMS agent do not see the Status bar
in Ignite.
• Time in Ringing – Displays when an employee has ACD interactions ringing in the
Inbox
• Time in ACD – Displays when an employee has placed ACD interactions in reply
mode
• Time in ACD Hold – Displays when an employee has placed ACD interactions on
hold
• Time in Non ACD – Displays when an employee is handling Non ACD interactions
• Time in Non ACD Hold – Displays when an employee has placed Non ACD
interactions on hold
• Time in Outbound – Displays when an employee has placed an outgoing call
• Time in Work Timer – Displays after the employee has handled an interaction,
provided none of the employee’s agents are in an ACD, Non ACD, Outbound, Make
Busy, or Do Not Disturb state
Note:
If Work Timer is the overriding state, the Status bar displays the Work Timer state that the
agent has been in longest.
• Time in Do Not Disturb – Displays when the employee is in a Do Not Disturb state
For more information, see "Setting and removing Do Not Disturb in Ignite".
• Time in Make Busy – Displays when the employee is in a Make Busy state
For more information, see "Setting and removing Make Busy in Ignite".
• Time Logged in Not Present – Displays when an employee is not present in any of
their agent groups
An overriding state is one that ‘trumps’ another state, as represented by the list above. States
higher in the list override the states appearing lower in the list. Note that all of the employee’s
agents are considered when the system calculates overriding state.
For example, if an employee’s Chat agent is Idle, but their Email agent is ACD, the Status bar
displays ACD. In this example, ACD is the overriding state. If the employee’s Chat agent is in
Work Timer, and their Email agent is in Make Busy, the Status bar displays Work Timer until Work
Timer expires or is removed. In this example, Work Timer is the overriding state.
The oldest time for a state ‘trumps’ other times for the same state if an agent is handling multiple
interactions. For example, if an employee had two emails in ACD, the displayed value in the
status bar would be the time of the oldest email. When the oldest email is completed, the
displayed value in the status bar would switch to the other email’s Time in ACD.
Ignite’s Status bar also contains statistics on agent performance, offering agents quick access to
their current handling statistics across media types. Icons indicate the media type to which the
following statistics pertain.
• Average Handling Time (mins) – The average time the agent has taken to handle
interactions of each media type
• Workload (current + Work Timer / maximum) – Displays active interactions, and
any Work Timer states, against the maximum number of interactions an agent can be
pushed per media type, as defined by the agent’s Workload. Note that Work Timer
states count against Workload, and will affect whether agents are pushed interactions.
For more information, see "Work Timer".
• ACD (count / duration) – Displays the number of ACD interactions the agent has
handled for a media type, and the time spent handling interactions of that media type
• Non ACD (count / duration) – Displays the number of Non ACD interactions the
agent has handled for a media type, and the time spent handling the interaction.
• Unavailable % – Displays the percentage of time the agent is unavailable during their
shift, including DND, MKB, Unknown, and Work Timer states, and when the agent is
logged in but not available to receive ACD interactions.
Agents access their handling statistics by clicking the ^ button on the right-hand side of the
Status bar. (See the following figure.)
The color of the multimedia icons in the Status bar indicates the agent’s state.
• Yellow – Indicates either a Make Busy or Work Timer state, or that the agent is logged
in but not present in any of their agent groups.
• Blue – Indicates the agent is in a Non ACD state
• Gray – Indicates the agent is logged out or otherwise Unavailable
A red banner indicates the number of interactions ringing in the agent's Inbox. For more
information, see "Ringing states in Ignite".
The My Folders view is divided into the Folder, List, and Preview panes. (See the following
figure.)
For more information, see "The Folders pane", "The List pane", and "The Preview Pane".
• View the My Folders folder, which includes the Inbox, Drafts and Drafts subfolders, My
History and My History subfolders, and Failed folder.
• View the Processed folder, which includes the In Progress (supervisors only), History
and History subfolders, and Failed folder.
The My History and Processed folders pertain only to email, chat, SMS, and open media
interactions. For more information on Ignite's folders, see "The Media Folders view (DESKTOP)".
For information on the specific interactions agents can view in Ignite’s media folders, see
"Viewing and organizing contacts in Ignite (DESKTOP)".
The Card view indicates when an interaction entered the Inbox and how long an agent has to
handle an interaction before the Service Level timer expires. (See the following figure.)
Agents can customize how data displays in the Card view. For more information, see "Choosing
how contact data displays in the Card view (DESKTOP)".
Figure 44: Data displayed in the List pane's Card view Inbox
In the Grid view, agents can see extended interaction information and customize the data
displayed. For more information, see "Choosing how contact data displays in the Grid
view (DESKTOP)".
The Media Folders view is divided into three main folders: My Folders, Processed, and Failed.
Each is comprised of several subfolders.
Note:
The My History and Processed folders pertain only to email, chat, SMS, and open media
interactions.
My Folders – The agent’s ‘Personal’ folder. This folder contains multimedia interactions being
offered to the Inbox, multimedia interactions the agent has handled, the agent’s email replies,
and multimedia interactions that were unable to route. My Folder is organized into the following
subfolders.
• Inbox – Contains interactions being offered to the agent and interactions on which the
agent is working. The Inbox indicates the number of ringing interactions, in red. When
a customer responds to a chat, the number of chat interactions awaiting the agent's
response is indicated, in orange. An interaction selected in the Inbox becomes the
active interaction.
• Drafts – Contains the agent's emails in progress. These interactions are organized
into the following subfolders:
• Handled – Contains the email, chat, and SMS interactions to which the agent has
replied or transferred from reply mode
Note:
For email, the Handled folder displays only the original, inbound emails.
Processed – A queue-level folder. This folder contains email, chat, SMS, and open media
interactions that agents answering for the queue have worked on and are currently working
on.;Processed also includes email interactions in the process of being sent, and email and chat
interactions that were unable to route. Processed is organized into the following subfolders.
Note:
• History – This folder contains email and chat interactions that agents have worked on.
These interactions are organized into the following subfolders.
• Handled – Contains the email, chat, and SMS interactions to which the agent has
replied or transferred from reply mode
Note:
For email, the Handled folder displays only the original, inbound emails.
Failed – Contains email, chat, and SMS interactions that were unable to route in the queues the
agent or supervisor have permission to view.
• Failed – Contains email, chat, and SMS interactions that were unable to route
• Failed to Send – Contains emails that failed to send because they exceeded the
supported email message size for the mail server
• Auto Replies/Failed Delivery – Contains emails that failed because the recipient had
no more space in their inbox, the recipient had an out of office reply configured, the
message was delayed by the recipient's mail server, or there were invalid addresses in
the delivery list
The interactions contained in each folder can be searched and sorted according to various
criteria. For more information, see "Searching Ignite’s folders".
Unified Queues – A collection of queues of different media types receiving interactions for a
single service group. For example, a Unified Queue Group called ‘Technical Support’ can contain
a voice, a chat, an email, and an SMS queue receiving tech support interactions. You can view
these queues in a single folder, ‘Unified Queues’, in Ignite. You can control which queues are
visible under Unified Queues in Settings. For more information, see "Queue selection settings
(DESKTOP)".
Reporting Queues – A collection of queues, typically of a single media type, created for
reporting purposes. For example, a collection of queues called ‘Email Technical Support’ can
contain all email queues receiving tech support interactions. You can view these queues in
a single folder, ‘Reporting Queues’, in Ignite. You can control which queues are visible under
Reporting Queues in Settings. For more information, see "Queue selection settings (DESKTOP)".
Individual Queues – Queues of a single media type, either voice, email, chat, or SMS, which
are not part of a Unified Queue. Individual Queues that are grouped into Reporting Queues also
display here. You can control which queues are visible under Reporting Queues in Settings. For
more information, see "Queue selection settings (DESKTOP)".
Selecting a specific queue folder updates Ignite to display the interactions in queue. See "Viewing
contacts in Ignite’s folders (DESKTOP)" for more information. You can organize your queues and
queue groups in alphabetical or reverse-alphabetical order for ease of viewing.
Agents can choose which queues display in Ignite. For more information, see "Queue selection
settings (DESKTOP)". Supervisors can restrict the devices that agents can view in Ignite. For
more information, see "Configuring security roles".
• The number of agents available in each queue’s answering agent groups. For
Reporting Queues and Unified Queue Group folders, the total number of agents
available for the queues is displayed.
• The number of interactions in queue, or 'InteractionsWaiting', for the queue and the
queue groups
• The time that the longest waiting interaction has been in queue
• The queue or queue group’s Service Level. This Service Level is color-coded to give
an indication of how the queue is faring. 75% or greater is green, 50% to 74% is
orange, and less than 50% is red.
To view the queues within Reporting Queues and Unified Queue Groups
Note:
Each view can display different interaction details. For information on customizing the data
displaying in the List pane’s Card and Grid views, see "Choosing how contact data displays in the
Card view (DESKTOP)" and "Choosing how contact data displays in the Grid view (DESKTOP)".
To expand or collapse the List pane, click the arrow beside the Search box at the top of the List
pane. By default, the Line pane is expanded.
• When in Card view, expand the right-hand border of the List pane until it displays in
Grid view.
• When in Grid view, reduce the right-hand border of the List pane until it displays in
Card view.
Requeued emails contain any response text drafted. This text is visible to other employees who
handle the email. Agents can choose to include the drafted content when previewing requeued
emails in queue.
Requeued chat and SMS interactions contain all of the previous interaction between contact and
agent.
For voice interactions, the Preview pane displays call information such as the caller’s ANI.
The Preview pane is the location for formatting replies, applying Account Codes, and viewing
historical transcripts of communications. Functions available in the Preview pane vary by a
interaction’s media type.
Note:
In this guide, ‘reply mode’ refers to the state of the Preview pane when an agent has selected
an interaction in their Inbox or in queue and has clicked either ‘Reply’, ‘Reply all’, or ‘Pick &
Reply’. ‘Preview mode’ refers to the state of the Preview pane when an agent has selected
an interaction without clicking reply.
• Queue Groups
• Queues
• Agent Groups
• Agents
• Employees
Agents can customize which devices within a group display in the Monitor. For more information,
see "Ignite’s Realtime Monitor (DESKTOP)" and "Viewing device statistics in Realtime
Monitor (DESKTOP)".
Selecting a folder in the Folders pane displays its contents in the List pane. Agents can organize
how Folder content displays in the List pane. These options vary depending on whether the List
pane is in Card view or Grid view.
Under My Folders, agents can only view interactions that they personally have handled. For
queues, agents can only view interactions sent to the queues for which the agent answers. To
view interactions handled by other agents in the queue you must search the Processed folder.
employees must have a Multimedia Contact Center license and multimedia agents assigned to
the queue.
Descriptive information on folders in Ignite can be found in "Getting started with Ignite
(DESKTOP)".
• Choosing how interaction data displays in the List pane’s Card view
• Choosing how interaction data displays in the List pane’s Grid view
• Searching Ignite's folders
This order prioritizes real-time interactions, and places interactions with the lowest Service Level
time or, if expired, the longest waiting time, at the top of the list.
Agents can choose how and what interaction data displays in the List pane’s Card view.
4. Expand individual rows to see interactions matching the grouping criteria. Expand all
rows by clicking the plus icon beside the grouping conditions drop-down list.
1. From the Folders pane, select a folder for which you want to remove grouping
conditions.
2. In the List pane’s Card view, after No Group, select the drop-down list.
3. Select No Group.
1. From the Folders pane, select the folder to restore default sorting conditions.
2. In the List pane’s Card view, click Custom Sorting.
3. Click Defaults.
Note:
For the Processed folder, clicking ‘Defaults' removes all sorting conditions.
4. Click Close.
Note:
To complete the following procedures, expand the Card view’s right-hand borders until the
List pane displays in Grid view.
3. Select data columns to display. Deselecting data columns removes them from display.
The following figure lists the interaction statistics you can choose to see in the Grid view.
Note:
Agent Received The time at which the interaction arrived in the agent's Inbox
Agent Time How long since the interaction arrived in the agent’s Inbox
Collected Information Digits collected from the caller, such as an account number
Last Agent Action The last action taken by the agent on the interaction
Last Agent ID The reporting number of the agent who last responded to the
Response interaction
Last Agent Response The time since the agent last responded to the interaction
Last Agent Response The date and time since the agent last responded to the interaction
Date/Time
Last Customer The time since the customer last responded to the agent
Response
Last Handled Agent The name of the agent who last handled the interaction
Name
Priority The priority level of the queue the interaction is in. 64 is the default
Queue Received The time at which the interaction entered the queue
Retries Exceeded Whether the interaction’s maximum send attempts have been
exceeded
System Received For inbound email interactions, the date/time that an interaction was
received by the mail server
System Time How long since the interaction entered Multimedia Contact Center
• Drag and drop a column into the desired position. Animated arrows display when a
column can be dropped into position.
Note:
When grouping with the drag-and-drop method, animated arrows indicate when an item can
be dropped into position.
Color bars on each device statistic window indicate the device’s state. You can use these
bars to view device availability. To see the states indicated by each color, see "The Status bar
(DESKTOP)".
Note:
For a description of statistics viewable in the Monitor, see "Realtime Monitor statistics
available in Ignite (DESKTOP)".
• Select the Realtime Monitor tab and select either Queue Group, Queue, Agent
Group, Agent, or Employee.
1. Select the Realtime Monitor tab and select either Queue Group, Queue, Agent
Group, Agent, or Employee.
2. Select the radio-button for the item you want to display.
Note:
Select multiple devices by holding 'Shift'. Optionally, display all items by clicking Select
All.
3. To clear selections, deselect the associated radio buttons. Optionally, clear all
selections by clicking Deselect All.
Note:
Note:
Icons beside media-specific devices identify an item's media type. For example, an email
icon identifies an email queue.
To clear a search
For example, when the contact center is busy, the agent group answering emails for the Training
queue is offered emails from the Support queue. An agent in Training wants to transfer a support-
related email back to the Support agent group, but needs to see who is available to take the
email. In the Realtime Monitor, the agent pins the ‘Support’ agent group. When the agent toggles
the Monitor to agent statistics, only agents in the Support group display. The Training agent can
see who is available in Support to receive the transfer.
The following procedure explains how to pin items to the Monitor and remove pins.
1. Click Realtime Monitor and select either Queue Group, Queue, Agent Group,
Agent, or Employee.
2. Click the pin icon on a device item. Toggling devices displays only items associated to
the pinned item.
Note:
To view statistics for additional items, select them in the device pane. To revert back to
viewing only statistics associated to the pinned item, click ‘Select Related Only’.
3. To remove a pin, click the pin icon again. Alternatively, click the X button in the device
pane.
Statistics in the Realtime Monitor dynamically update as device conditions change. Color bars on
each device statistic window indicate the device’s state. You can use these bars to view device
availability. To see the states indicated by each color, see "The Status bar (DESKTOP)".
Note:
• The specific statistics displaying in the Agent Realtime Monitor vary by media type.
• Interflow statistics include interactions manually transferred from one queue to
another.
Longest Waiting The amount of time an interaction has been waiting in queue the
longest
Offered The number of interactions sent to the queue that were completed,
interflowed, or abandoned
Service Level % The percentage of interactions handled, abandoned (voice and chat
only) and interflowed before the defined Service Level time
Requeued The number of interactions sent back to the queue after being
offered to an agent
Non ACD The number of Non ACD interactions handled by agents in the agent
group. Not applicable to email, chat, SMS, and open media.
MKB The number of times agents in the agent group went into Make Busy
DND The number of times agents in the agent group went into Do Not
Disturb
Hold The number of times agents in the agent group put interactions on
hold
Non ACD Count The number of Non ACD interactions handled by the agent
ACD Time The amount of the agent’s shift spent handling ACD interactions
Average Handled The average amount of time taken to handle ACD interactions
MKB Count The number of times the agent went into Make Busy
DND Count The number of times the agent went into Do Not Disturb
Employee statistics
• Employee name
• Employee ID
• The number of interactions handled for each media type
Note:
Note:
• How long the employee has been logged on, or how long the employee has been
logged off
Each time you close Ignite your profile is automatically saved. When Ignite is reopened with
your username, your most recent profile settings are reloaded. If Ignite shuts down suddenly, it
resumes your last saved profile on restart.
Ignite always opens to the Inbox in the My Folders view. Ignite remembers the device monitors
you had open in the Realtime Monitor view, if the Realtime Monitor view was open when Ignite
was closed. Your profile does not reopen folders that were active when you last shut down Ignite.
• Displayed columns
• Column order
• Grouping
• Card view:
• Grouping
• Filtering
• Custom sorting
• Realtime Monitor:
You can reset your profile to Ignite’s default settings when logging into Ignite. Resetting your
profile restores all elements to their default display.
2. As Ignite is signing you in, press and hold CTRL+ R. Hold these keys until Ignite
indicates it is restoring your profile and loading the configuration.
In addition to auto-settings, Ignite offers general and Sidebar stats configuration options via the
Settings button in the Sidebar.
• Launch MiCollab Client if installed but not running when signing into Ignite: This
setting is selected by default and automatically opens MiCollab Client, if not currently
running, when an agent signs into Ignite.
Note:
You will be prompted to register and log in your voice agents in MiCollab Client before
signing into Ignite.
• Always show Sidebar: This setting is checked by default. If unchecked, you will not
have access to the options listed below and you will need to use the arrow icon to
show or hide the Sidebar.
• Expand Ignite when a multimedia item is accepted: This setting is checked by
default. When selected, if the main Ignite window is collapsed and an email, chat,
SMS, or open media is accepted via the toaster, the main Ignite window automatically
expands. If not selected, Ignite will not automatically expand when an email, chat,
SMS, or open media is accepted and the agent must expand it manually by clicking
the arrow at the bottom of the Sidebar.
• Expand Ignite when a voice item is accepted: This setting is not checked by default
and if the main Ignite window is collapsed and a call is accepted via the toaster, Ignite
does not automatically expand. We recommend deselecting this setting as the main
Ignite window is not essential for handling voice interactions. If selected, if the main
Ignite window is collapsed and a call is accepted via the toaster, Ignite automatically
expands.
• Collapse Ignite on startup: This setting is not checked by default. When you start
Ignite, the main window will not collapse. If this check box is selected, only the Ignite
Sidebar displays at startup. You can use the arrow icon at the bottom of the Sidebar to
expand the main Ignite window. If this setting is not selected, when you start Ignite the
main window and the Sidebar will display.
• Collapse Ignite when inbox is emptied: This setting is not checked by default. When
selected, and your inbox empties, the main Ignite window collapses. If not selected,
the main Ignite window does not collapse when your inbox has been emptied.
You can select which queues are visible by clicking the Settings button in the Sidebar and
clicking Queue Selection. You are still offered interactions for the queues to which you are
assigned, even though they may not be visible.
Ignite can display a maximum of 64 queues. If your profile is new, from an upgrade, or has been
restored from a reset, Ignite automatically loads the maximum number of queues, starting with
Unified Queues and then Individual Queues. Queues under Reporting Queues are never loaded
by default.
Ignite can display a maximum of 64 queues. If your profile is new, from an upgrade, or has been
restored from a reset, Ignite automatically loads the maximum number of queues, starting with
Unified Queues and then Individual Queues. Queues under Reporting Queues are never loaded
by default.
The Agent Greeting feature enables agents to record messages (as .wav files) that play
automatically to callers when the agent answers an inbound ACD call. The greeting can provide
a consistent experience for each caller and free the agent from having to repeat the same
introductory phrase for every call.
Agents can record multiple greeting messages in Ignite and assign them to different queues or
use the same recorded greeting on all queues. The agent greeting is a two-way playback, where
both the caller and the agent hear the recording.
Agents record and manage their greetings on the Agent Greeting tab on the Settings page.
Note:
• When the agent greeting is playing, the caller is able to hear the agent speaking.
To prevent the caller from hearing the agent or other contact center background
noise during the agent greeting, mute the agent's headset for the duration of the
greeting.
• Administrative settings determine whether you have access to Agent greeting
functionality. If your contact center is not enabled for agent greetings, the Agent
Greeting tab will not display in Ignite.
• Record greetings
• Assign greetings to specific queues
• Designate a recording as the default greeting
• Play or re-name an existing greeting
• Re-record or delete an existing greeting
Note:
When recording messages, your voice agent is in a Non ACD state, and is not offered calls
from any incoming queues.
1. Click the Settings button in the Sidebar, then click the Agent Greeting tab.
2. Hover over the Add New Recording label to make the Record button visible on the
right-hand side.
3. Click the Record button.
The Record Agent Greeting workflow is triggered and instructs the system to call your DN.
5. Answer the incoming call and follow the system prompts to record and save your
greeting.
By default, the system selects the first recording as your default recording. The default recording
is played on all incoming calls, regardless of the originating queue, unless there is a specific
recording assigned to the queue. For more information, see "Assigning a recorded greeting to a
queue (DESKTOP)".
You can record additional greetings and designate any one of your saved recordings as the
default recording, or you can choose not to use a default recording.
1. Click the Settings button in the Sidebar, then click the Agent Greeting tab.
2. Click on the down arrow beside the Advanced Options heading to expand the
section.
3. Hover over the Add New Recording label to make the Record button visible on the
righthand side.
4. Click the Record button.
5. Enter a name for the recording and click OK.
The Record Agent Greeting workflow is triggered and instructs the system to call your DN.
6. Answer the incoming call and follow the system prompts to record and save your
greeting.
Note:
If you do not have a designated default recording, you must assign a recording to each
queue explicitly. If there is no default recording, and a queue does not have a recording
assigned to it, no greeting is played to customers on incoming calls from that queue.
The Queues section of the Agent Greeting (under Advanced Options) lists all of the queues to
which you are assigned. The recorded greeting that plays on incoming calls from a queue is
shown to the right of the queue name.
1. Click the Settings button in the Sidebar, then click the Agent Greeting tab.
2. Click on the down arrow beside the Advanced Options heading to expand the
Advanced Options section.
3. Under the Queues heading, select the queue to which you want to assign a recording
by selecting the check box beside it.
• You can search for a specific queue by typing the name in the Search box.
• You can filter the list of queues to show only the queues that do not have the default
recording assigned to them by clicking the Only Show Non-Default option.
4. Click the Apply Recording button.
The Apply Recording window opens. The selected queue is displayed at the top, and a list of
available recordings displays below.
5. Hover over the recording you want to assign to the queue to make the check mark
visible on the right-hand side.
6. Click on the check mark to apply the selection.
The check mark turns green and the new recording displays beside the selected queue in the
Queues list on the main Agent Greeting tab.
7. To remove the custom greeting from the queue and revert back to using the default
recording, click the X button beside the recording you just assigned to the queue.
• Play a greeting
• Re-record a greeting
• Rename a greeting
• Designate a greeting as the default greeting
• Delete a greeting
To play a greeting
1. Click the Settings button in the Sidebar, then click the Agent Greeting tab.
2. To select a non-default greeting, click the down arrow beside the Advanced Options
heading to expand the section.
3. Under the Recordings section, hover over the name of the recording in the list to
make the row of icons visible on the right-hand side.
4. Click the Play button (second icon from the left).
To re-record a greeting
1. Click the Settings button in the Sidebar, then click the Agent Greeting tab.
2. Click on the down arrow beside the Advanced Options heading to expand the
section.
3. Under the Recordings section, hover over the name of the recording in the list to
make the row of icons visible on the right-hand side.
4. Click the Record button.
The Record Agent Greeting workflow is triggered and instructs the system to call your DN.
5. Answer the incoming call and follow the system prompts to record and save your
greeting.
Note:
You can also re-record the default greeting. Hover over the greeting listed under the Default
Greeting header and click the Record button (as noted above) to re-record the greeting.
To rename a greeting
1. Click the Settings button in the Sidebar, then click the Agent Greeting tab.
2. Click on the name of the recording you want to rename (either in the Default Greeting
section or the Recordings section).
1. Click the Settings button in the Sidebar, then click the Agent Greeting tab.
2. Hover over the name of the recording in the list to make the row of icons visible on the
right-hand side.
3. Click the Pin button to make the greeting the default greeting.
To delete a greeting
1. Click the Settings button in the Sidebar, then click the Agent Greeting tab.
2. Hover over the name of the recording in the list to make the row of icons visible on the
righthand side.
3. Click the Trash button to delete the greeting.
Note:
• The intended users of Ignite (WEB) are employees connected either locally on the
LAN, through VPN, or via the Mitel Border Gateway.
• Ignite (WEB) does not support Compatibility Mode.
• Ignite (WEB) requires JavaScript be enabled on your browser. For more
information, consult your browser documentation.
• When configuring screen pop notifications to be used with Ignite (WEB), you can
execute only web URLs. Direct file execution (for example, .EXE or .BAT files)
does not work in Ignite (Web) as the browser considers it as a security risk.
Launch Ignite by typing the following URL into a supported web browser:
• http://<EnterpriseServerName >/Ignite
OR
• http://<EnterpriseServerIP>/Ignite
Note:
If your system uses SSL, type ‘https’ in place of ‘http’ and insert a valid domain or FQDN
in place of an IP address.
For a list of supported web browsers, contact your supervisor or system administrator. Ignite
supports default browser configuration settings.
Note:
• We recommend that you do not use the Ignite (WEB) and Ignite (DESKTOP)
applications simultaneously.
• Editing responses across multiple, open browsers simultaneously is not supported.
• If you are drafting an email response and change browsers, hit 'Refresh' to pull
down your drafted content.
Note:
After signing in to Ignite and becoming Available, you may be placed in Make Busy across
all agent capabilities. This is an administrative configuration. To remove Make Busy, see
"Setting and removing Make Busy in Ignite".
Your default sign-in state is Offline. This means you are signed into Ignite but your ACD agents
are logged out. You cannot receive ACD interactions until your state is Available. To change
states, see "Adjusting agent states in Ignite (WEB)".
If you are enabled for voice, you can set Ignite to log you in to your phone. See ‘To sign in to
Ignite and log in to the phone’, below. Otherwise, we recommend you log into your phone before
signing into Ignite so that your agents may become Available.
Logging out of the phone or exiting/disabling MiCollab Softphone will log out only the voice agent
(multimedia agents are not affected). Logging out of Ignite will log out all agents (voice and
multimedia) and may requeue items in the Inbox, depending on administrative configurations. To
avoid losing work on these items, agents should finish their replies or transfer inbox items to a
queue before logging out.
To sign in to Ignite and log into an External Number as an External Hot Desk Agent
Note:
Note:
If you use Windows Authentication, enter your DOMAIN\Username and your domain
password.
Note:
• This feature is supported for hot desk and external hot desk agents only.
• You can set or change phone settings from Ignite’s Options page.
• MiCCB supports MiCollab ACD Softphone on thick clients and WebRTC.
Note:
Note:
If you use Windows Authentication, enter your DOMAIN\User name and your domain
password.
Note:
The MiCollab Client needs to be loaded onto the client machine and the Softphone
enabled on it before selecting Login in Ignite. A warning message stating to make sure
the client application is opened, and the Softphone enabled will appear.
5. To log in to your phone once your sign-in is complete, select the Remember my
Extension check box.
Note:
• Clicking Save dismisses the dialog window and signs you in as Offline. However, the
phone information is saved to your profile and you are logged in to your phone once
your state is Available.
• Clicking Cancel dismisses the dialog window and signs you in as Offline across all
media types.
• If no concurrent voice agent license is available, a "Login failed - No voice agent
license" message is displayed and the agent login is blocked. A "Blocked voice login"
alarm is triggered and visible in Ignite (WEB) for supervisors.
Note:
• Voice agents on active calls are not logged out until the call is complete.
• Directly closing the browser does not log you out of Ignite (Web); you must
manually log out of Ignite (Web).
Note:
If you are using MiCollab Softphone, you do not need to select base extension. To use
MiCollab Softphone, in Ignite click the MiCollab Softphone radio button.
To reconnect Ignite:
Our forums enable you to send feedback directly to the people building the product. While we
cannot comment on every suggestion, feedback is analyzed and considered for future releases.
Note:
Please do not use the forums to submit product defects. To submit product defects, please
contact your administrator or dealer.
OR
The following sections describe how agents can use Ignite to:
OR
Note:
Please do not use the forums to submit product defects. To submit product defects, please
contact your administrator or dealer.
Icon term
Add
Accept
Apply Code
Associate Participant
Cases Inqueue
Case
Call
Conference
Icon term
Decline
Dissociate Participant
Edit
Export to .csv
Follow up Calendar
Forward
Go to
Icon term
Hold
Import Contacts
Invite
Junk
Merge
No Reply
Pending
Reply
Icon term
Reply All
Request Help
Resolve
Send
Swap
Text
Transfer
Using the Contact button in Ignite, agents can search for employees who are configured in
YourSite Explorer and Active Directory as well as contacts who have been added as customers.
They can also search for queues. By default, when clicking the Contact button all contacts
are available to be searched but agents can filter their search by Employees, Queues, Active
Directory, and External.
Note:
For an Active Directory contact to be displayed in a Web Ignite contact search, at least one
of the following must be configured for the contact: email, phone number, or mobile phone
number.
Contacts that you have often contacted are listed under Contact History. You can edit or delete
a contact that is listed in Contact History. Hover over the contact avatar and click Edit to modify
the contact information, or click the X button to remove the contact from Contact History.
Agents can view cases associated with a contact thus enable them to have an overview about
the customer’s calls before handling the customer issue.
For information on using Contacts, see "Sending outbound emails", "Sending outbound SMS
contacts", or "Making calls".
1. Click Contacts. In the Search field, type the external contact name you want to edit. A
list of contacts matching the search are displayed.
2. Hover over the contact avatar and click Edit, or click the contact and then click Edit.
3. In the Edit Contact window, under Details tab, modify contact information and click
Update.
If history information is available for the selected contact. You can view information such as
old phone numbers or old email addresses, are listed under History tab.
Note:
Agents can also edit contact information during an interaction. For example, an agent in
the Sales queue is on a call with a customer and updates the customer’s email address or
mobile number. The agent can now view the updated contact information and, if required,
can transition to an alternate interaction type, such as email.
Note:
.csv file contains a list of personal contacts in the “Name, Email, Phone number, Mobile
number” format.
Scott Alan,[email protected],,5879856541
Jon Doe,,5096308945
3. Click Import.
Ignite confirms the import by displaying the following message “Contacts imported
successfully”.
Note:
If the .CSV file contains duplicate records, the system alerts you; based on the preferences
set in the Customization page, the import action is either terminated or continued. Ignite
confirms the import status by displaying a message; for example, “Process completed. 10
successful, 2 already exists, 3 unknown”.
1. Click Contacts. In the Search field, type the contact name you want. A list of contacts
matching the search are displayed.
2. Hover over the contact avatar and click Cases.
For example, you can merge duplicate contacts with the following information:
After you merge two contacts, the resultant contact is as shown below:
1. Click Contacts, and in the Search field, type the contact name.
The Merge Contacts window is displayed with details for the selected source contact.
3. In the Merge Contacts window, in the Search field, type the target contact name.
In the Merge contacts window, the source and target contact details are displayed.
5. In the Merge Contacts window, from Select Fields, select the contact details you
want to display in the merged contact. The selected details are displayed under
Result Contact. A dialog box appears, displaying the message: “Are you sure you
want to merge these contacts?”.
6. In the dialog box, click OK to merge the contacts.
Note:
When you merge external contacts, the changes are updated in cases and their
associated calls.
The color of the circle over the avatar indicates your current presence.
If you have been enabled to adjust your agent group presence and agent state, you can click
your avatar to both view and change your agent group presence or agent state. For information
on your agent state, see "Viewing agent state and state statistics (WEB)".
For information on changing your agent group presence and status, see "Managing agent group
presence and agent states".
For information on changing your avatar, see "Your Ignite profile (WEB)".
An overriding state is a state that supersedes other states. States higher in the list override the
states appearing lower in the list. Note that all an employee’s agents are considered when the
system calculates the overriding state.
The oldest length for a state supersedes other times for the same state if an agent is handling
multiple interactions. For example, if an employee had two emails in ACD, the displayed value
in the status bar would be the time of the oldest email. When the oldest email is completed, the
displayed value in the status bar would switch to the time of the other email.
Agent states by media are available in the Inbox. For more information, see "Viewing agent
handling statistics (WEB)".
In the Inbox, the History, and the Queues pages, you can switch between Grid view and List view.
In Grid view, all interactions for the selected page are displayed in a grid format.
Note:
You can click anywhere on the row for that interaction to select an interaction, select the check
box for that interaction. You can select multiple interactions. You can also customize the order in
which columns appear in the grid. This allows you to view all the interaction properties at once
and to sort or group by specific interaction properties.
1. Select a page and in Grid view, click the Show column chooser button at the top-
right of the grid. A list of available columns displays.
2. Click the columns you want to display in the grid. A tick mark against the column
name indicates that it is selected, and an X mark indicates that it is not selected.
Note:
An administrator can enable a custom variable in the YSE application by selecting the
Send to agent desktop check box. For more information about custom variable creation,
see "Creating Custom Variables".
• On the column header, click the drop-down arrow, and select Sort Ascending/ or
Descending.
• On the column header, click the drop-down arrow and select Remove Sort.
• On the column header, click the drop-down arrow, and select Hide Column.
1. On the column header, click the drop-down arrow, and select Group.
Note:
You cannot group the following column headers: Interaction Id, System Received, Action
Time.
• On the column header, click the drop-down arrow and select Ungroup. The column
data are ungrouped and restored to the default.
7.2.7.6 Dashboards
The Dashboards page enables you to customize different dashboard displays of information
relevant to your agent. You can add the following widgets to a dashboard:
• Employee State
• Callback Request
• Queue Now
• Agent State
• Web Browser
For more information on creating dashboards, see "Configuring Ignite (WEB) dashboards".
When there is an active interaction or draft in the Inbox, a red badge appears over the Inbox icon,
indicating how many interactions and drafts there are in the Inbox.
When you select an interaction in Inbox, in addition to the handling options, you can quickly
access the case details, notes, calls, all the participants of the case, other cases from the same
customer, and URLs by using the corresponding tabs. This saves time when you are interacting
with a customer. For more information about these tabs, see the "Cases (WEB)".
An agent can view any call’s variable values that contain a URL under a separate tab, URLs.
The URLs tab consists of a drop-down with all the variables and their associated value (URL). By
default, the first URL is displayed in the frame. To open the URL in a new window, click Open.
Additionally, the Inbox displays current real time agent handling statistics. For more information,
see "Viewing agent handling statistics (WEB)".
If the interaction is a draft, it will be labeled as such. When you select an interaction in your
inbox, in addition to the handling options, you can quickly access the case details, notes,
interactions, all the participants of the case, and other cases from the same customer by using
the corresponding tabs. This saves time when you are interacting with a customer. For more
information about these tabs, see the "Cases (WEB)".
If an interaction consists of an URL, an agent can view the URL under a separate tab, URLs.
The URLs tab consists of a drop down with all the variables and their associated value(URL). By
default, the first URL is displayed in the frame. To open the URL in a new window, click Open.
You can choose to view the interactions in List view or in Grid view by clicking the respective
option. Also, you can choose to view the case details in the additional pane that appears in the
Inbox when you click the down arrow in the top header of the Inbox. (See the following figure).
You can expand or collapse the navigation pane using the < and > buttons.
Each media type’s icon indicates the corresponding state of the employee’s agents. The following
table outlines the different states.
Outbound -- -- -- -- An agent on an
outgoing voice
interaction
Offline An agent
unavailable to
handle interactions
• ACD (Count / Duration) -- Displays the number of ACD interactions the agent has
handled for a media type, and the time spent handling interactions of that media type
• Non-ACD (Count / Duration) -- Displays the number of Non ACD interactions the
agent has handled for a media type, and the time spent handling the interaction
• Average Handling Time (hours:mins:secs) – The average time the agent has taken
to handle interactions of each media type
• Unavailable % -- Displays the percentage of time the agent is unavailable during the
shift, including Do Not Disturb, Make Busy, Unknown, and Work Timer states, and
when the agent is logged in but not available to receive ACD interactions. (See the
following figure.)
By clicking the More button, agents can change the statistics being displayed. (See the following
figure.)
Supervisors can filter all the interactions by type and also view the interactions that are being
handled by agents and are in agent’s Inbox, or put on hold, or are in draft state. This gives the
supervisor a better visibility into the interactions that are being handled by the agents.
Note:
Supervisors will not be able view agents’ SMS interactions that are in draft state.
You can also reply to participants of all interactions (except Chat) from History. When you select
an interaction in History, in addition to the handling options, you can quickly access the case
details, notes, interactions, all the participants of the case, other cases from the same customer,
and URLs by using the corresponding tabs. This saves time when you are interacting with a
customer. For more information about these tabs, see the "Cases (WEB)".
An agent can view any interaction’s variable values that contain a URL under a separate tab,
URLs. The URLs tab consists of a drop-down with all the variables and their associated value
(URL). By default, the first URL is displayed in the frame. To open the URL in a new window, click
Open.
You can choose to view the interactions in List view or in Grid view by clicking the respective
option. See the "List pane (WEB)".
For more information on filtering historical interactions, see "Filtering historical contacts (WEB)".
For more information on reviewing interaction history, see "Reviewing interaction history".
For more information on sending replies to participant(s), see "Replying to participant(s) of a case
from History (WEB)".
The following are the important details you must note while sending email, SMS, and voice
replies to the participants:
4. To select all or some participants, in the Participants tab, hover over the participant’s
avatar and click to select all or some participants and click Email button.
In the email reply editor, the participant’s email address is automatically inserted in the To
field. The subject of that email is prepended by ‘RE: the subject of the last email interaction
[case and ticket information]’.
5. Type the content and click Send.
The participant’s phone number is automatically inserted in To field. Click From to select the
SMS queue before sending the reply message.
5. Type the reply message and press Enter.
For example, an agent in the Sales queue handling an email can review the interaction history
for that case, or preview other interaction to that case. Agents can also move an interaction to or
merge interactions from another case.
Note:
When upgrading from MiContact Center 7.x or 8.x or 9.x to MiContact Center Business 9.2
cases are automatically created for emails (beginning with the most recent email and ending
with the oldest email). Emails that are associated to a particular customer calls are grouped
within a single case to consolidate information.
In addition, contact information based on historic emails is added to the MiContact Center
Business database. For MiContact Center version 8.1 customers who implemented the Omni
Channel Tech Preview cases are also created for SMS and Chat during an upgrade to MiContact
Center Business version 9.2.
Cases are deleted when the email interaction related to the customer are all Junked. If an email
is accidentally set as ‘Junked’ and it would be the only item in a case, you must find and forward
it to the customer to enable it to display in the list of cases.
For more information on handling cases in Ignite (WEB), see "Working with cases in
Ignite(WEB)".
Queues displays queues, both queues not associated to a queue group as well as queues
belonging to queue groups. You can search for queues and queues to display or you can set
queues and queue groups as favorites so that they always display when you go to Queues.
The Queues page contains a searchable archive of all calls sent to the queues for which the
agent answers.
When you select a call in Queues, in addition to the handling options, you can quickly access the
case details, notes, calls, all the participants of the case, other cases from the same customer,
and URLs by using the corresponding tabs. This saves time when you are interacting with a
customer. For more information about these tabs, see the "Cases (WEB)".
An agent can view any interaction’s variable values that contain a URL under a separate tab,
URLs. The URLs tab consists of a drop-down with all the variables and their associated value
(URL). By default, the first URL is displayed in the frame. To open the URL in a new window, click
Open.
You can choose to view the interactions in List view or in Grid view by clicking the respective
option. See the "List pane (WEB)".
Agents can pin queues and queue groups as favorites so that your most handled queues are
always readily available. By selecting a pinned queue or queue group in the Queues page,
agents can view interactions in queue. Each queue and queue group indicate
• The number of agents available in each queue’s answering agent groups. For
reporting queue groups and unified queue groups, the total number of agents available
for their component queues is displayed.
• The number of interactions in queue, or ‘interactions Waiting’, for the queue and the
queue groups.
• The queue or queue group’s Service Level percentage.
Agents can search for pinned queues and queue groups by keyword. Ignite displays all queues
and queue groups matching the keyword. The search remains until you navigate away from the
Queues page. You can sort search results and favorites by name or queue media type. Sorting
by name sorts the queues and queue groups alphabetically. Sorting by media arranges queues in
the order of Chat, Email, SMS, and Voice and sorts queue groups in the order of Unified, Virtual,
and Reporting.
1. Click Queues.
2. Click the Select Favorite Queues button.
3. Select the queues and queue groups you want to favorite.
4. Click Save.
1. Click Queues.
2. In the Search field, enter the keyword.
1. Click Queues.
2. Click Name.
1. Click Queues.
2. Click Media.
1. Click Queues.
2. From the queue groups, click the queue of your choice to view its interactions.
Note:
3. Click the interaction of your choice to view its details in the right pane.
Note:
A Back link is available for you to navigate back to the Queues page.
Web Ignite allows the agents to record multiple agent greetings. These greetings can then be
assigned to all queues as the default agent greeting or assigned to specific queues to allow for a
more custom experience.
The agent greeting is a two-way playback, where both the call and the agent hear the recording.
Note:
All queues that do not have a specific agent greeting will be updated to show the
newly selected default greeting, visible with the (Default Greeting) as part of the
name.
Note:
All selected queues will be updated to show the new agent greeting. Unlike the
default agent greetings, these will show the name of only the selected agent greeting.
Note:
All queues that have an agent greeting labeled with (Default Greeting) will be cleared.
These queues will not have an agent greeting when a call comes in.
Note:
• When recording messages, your voice agent is in a Non ACD state and is not
offered calls from any incoming queues.
• When you click the Record button to create a recording, the system’s Record
Agent Greeting workflow is triggered. The Record Agent Greeting workflow
instructs the system to call your DN and prompts you to record and save a
greeting.
• Internet explorer does not support .wav file playback. While using the Agent
Recording feature, for playback of your recording, use any of the browsers
supported by MiContact Center Business.
• Mobile view—If this option is enabled, the email editor is optimized for the hand-
held device and the text formatting icons are not displayed.
• Use last reply template folder location—If this option is enabled and when you
browse for a reply template, you can directly access the folder location where the
last used reply template is stored.
• Quick reply templates—If this option is enabled, you can access and apply an
existing template when replying to emails.
• Clear Quick reply templates view after Insert—If this option is enabled, the quick
reply templates view will be cleared after you have inserted the template.
• Expand Headers—If this option is disabled, all the header fields are collapsed
except the top-level header. To expand or collapse the header fields, click the down
arrow or up arrow buttons.
3. Click Save.
You can create, preview, edit, and delete existing personal reply templates.
Note:
The variable name used in the reply template must match the variable name
defined in YSE and Send to agent desktop must be selected in YSE. Otherwise,
the email reply will leave the text as it is enclosed within quotes. (that is,
“<<VariableName>>”). Consult with the system administrator to obtain a list
of variables, from which you can choose the variables you want to insert in a
personal reply template.
4. To insert an image, click Insert picture and browse to the image you want to insert.
5. To insert a link, click Insert/edit link and copy and paste the text for the link you want
to insert.
6. Type the name you desire for the reply template.
7. Click Save.
<<VariableName>>. You can insert multiple variables. In the email reply, Ignite
replaces the variable with the actual value of the variable defined in YourSite Explore
(YSE).
Note:
The variable name used in the reply template must match the variable name defined in
YSE and Send to agent desktop must be selected in YSE. Otherwise, the email reply
will leave the text as it is enclosed within quotes. (that is, “<<VariableName>>”). Consult
with the system administrator to obtain a list of variables, from which you can choose the
variables you want to insert in a personal reply template.
Note:
The variable name used in the reply template must match the variable name defined in
YSE and Send to agent desktop must be selected in YSE. Otherwise, the email reply
will leave the text as it is enclosed within quotes. (that is, “<<VariableName>>”). Consult
with the system administrator to obtain a list of variables, from which you can choose the
variables you want to insert in a personal reply template.
In Inbox, agents can view interactions they are handling or are currently ringing them. For
Queues, agents can view interactions sent to the queues for which the agents answer.
For more information on Inbox, History, and Queues, see "Inbox (WEB)", "History (WEB)", and
"Queues (WEB)".
• All—All interactions.
• Handled—All interactions to which the agent has replied or transferred from reply
mode.
Note:
For email, the Handled folder displays only the original, inbound emails
• Sent—All outbound emails and SMS interactions and agent replies to email
interactions.
• No Reply—Contains email and SMS interactions designated as needing no reply,
such as out of office messages.
• Junk—Contains email and SMS interactions designated as Junk.
• Failed—Contains voice, email, chat, SMS, and open media interactions that were
unable to route.
Historical interactions can also be limited to interactions you have handled or sent display, rather
than all interactions for the queues you handle.
Supervisors can filter all the interactions by type and also view the interactions that are being
handled by agents and are in agent’s Inbox, or put on hold, or are in draft state. This gives the
supervisor a better visibility into the interactions that are being handled by the agents.
Note:
• Supervisors will not be able view agents’ SMS interactions that are in Draft state.
• Agents will be able to Reply and Reply All to the email interactions that are in
Handled, Sent, No Reply, and Junk historical states.
• Agents will not be able to Reply and Reply All to the email interactions that are in
Inbox and Failed historical states.
The interactions contained in each filter can be searched for more specific interactions. For more
information, see "Searching Ignite".
1. Click History.
2. Select the Filter.
1. Click History.
2. Select Only show my items.
Note:
The agent who has worked last on a particular call gets the ownership of the calls and is
displayed in that agent’s call history when the Only show my items option is checked.
For example, if Agent A answers a call and then transfers to Agent B, this call is not displayed
in Agent A’s history if the Only show my items option is checked. It is displayed in Agent B’s
history when the Only show my items option is checked.
You can multi-select email and SMS interactions using either the Ignite (WEB) UI or Windows’
CTRL+ or SHIFT+ functionality.
Once multi-select is invoked, handling options and the option to select all items display.
Note:
The option to multi-select displays only on the History and Queues pages.
Note:
On the History page you may perform an action only across items that failed to route.
Note:
On the History page, you may perform only an action across items that failed to route.
1. Once multi-select is active, at the top of the items list, select the ‘master’ check mark.
If all items are selected, disregard this step.
2. Once all items are selected, at the top of the items list, select the 'master' check mark.
• History
• Favorited queues
• Dashboard
• Default landing page
• Phone settings, including Extension, PIN, and automatic login to your phone
• Automated diagnostics reporting
• Filter selection preference
You cannot delete your profile; however you can reset the above to Ignite’s default settings.
An agent can configure the durations (in seconds) for the following notifications: new interactions,
follow up, and info/error messages displayed on the Ignite screen.
Note:
Note:
These settings enable login to your phone from Ignite. This feature is supported for hot desk
and external hot desk agents only.
The next time you sign into Ignite and set your state to Available, you will be logged in to your
phone.
Note:
You can send on-demand reports in addition to automated reporting. See "Reporting
performance issues in Ignite (WEB)".
Note:
Resetting your profile to Ignite's default settings resets the Clear quick reply
templates view after insert option.
On-demand reports are sent in addition to Ignite's automated diagnostics reporting. For
information on enabling automated diagnostics reporting, see "Your Ignite profile (WEB)".
Supervisors looking to access diagnostics reports should consult "Accessing diagnostics reports
from Ignite (WEB)".
display in each, combine different widgets, and give them meaningful names to indicate their
purpose.
Dashboards provide supervisors with fixed-layout display of agent data and enhanced visibility of
queue abandoned statistics.
Note:
The real-time monitors in Ignite (WEB) are known as ‘widgets’ in the dashboard user
interface.
See "Accessing real-time information with Ignite (WEB)" for information on how to use the real-
time monitors.
Note:
If this is your first use of Ignite (WEB), only the Default Dashboard is displayed.
1. Click Dashboards.
2. Click the Add Dashboard button.
3. Click Save.
To delete a dashboard:
1. In the dashboard you want to delete, click the Delete Dashboard button.
Note:
The dashboard you want to delete must be one that was previously saved. If not, then you
must save it first before deleting.
2. Click Delete to delete the dashboard. Clicking Cancel to retain the dashboard.
When a dashboard is in edit mode, you can edit the content within widgets, collapse widgets,
change the widgets’ location on the dashboard, or remove widgets from the dashboard.
Note:
When you are editing a Web Ignite Dashboard that includes a Web Browser widget, you will
not see the webpage in the widget.
Note:
You can collapse or expand the widget at any time (you do not have to be in edit mode).
The following procedure describes the editable features that are common to all widgets.
• Click the Settings button to edit the content within the widget (see the relevant
procedures for each widget for specific details).
• Click the Collapse button to collapse the widget or the Expand button to expand
the widget.
• Select the Move button to drag and drop the widget to a different position on the
dashboard.
• Click the Delete button to remove the widget from the dashboard.
3. If you edited the content within the widget, click Apply.
4. Click Save to save the changes to the dashboard or Undo to revert the change to the
dashboard.
When you configure options in the Callback Requests widget, you can change the name of the
monitor and add or remove the device to be monitored.
You can select up to six variables to display, and Queue Now widget displays six statistics
variables that you have selected.
4. Click the drop-down beside Queue and select either Queue or Queue Group.
5. Optionally, enter text into the Search field to search for queues or queue groups.
6. Select the check box beside each queue or queue group you want to monitor, or select
the check box beside ID to select all queues or queue groups.
7. Click Apply.
8. Click Save to save the change to the dashboard. Clicking Undo reverts the changes
made.
Note:
You can optionally select multiple voice agents for each employee, if applicable, by
selecting the check boxes located under the voice (telephone) icon, beside the employee
name.
6. Click Apply.
7. Click Save to save the change to the dashboard or Undo to revert the change to the
dashboard.
Note:
The Agent State widget in the Dashboard contains active/maximum license counts
for concurrent voice/multimedia agents visible to supervisors. The active counts
indicate the current number of logged in agents and maximum counts indicate the
number of available licenses.
Note:
When you are editing a Web Ignite Dashboard that includes a Web Browser widget you will
not see the webpage in the widget while in edit mode.
Agents may search only interactions sent to queues for which the agents answer.
WEB - Agents may search only interactions sent to queues for which the agents answer.
Employees licensed as Advanced supervisors or System Administrators may search all
interactions in the History tab of Ignite (WEB). This search capability does not require the
supervisor be licensed to handle multimedia.
Time stamps on interactions reflect the Ignite client time. To search interactions by date or time,
use the date or time for the Ignite client.
Interactions that are removed from the queue are removed from queue folder search results.
New interactions in queue matching search criteria will not be displayed until the search is
executed again.
DESKTOP - You cannot search for voice interactions, but you can filter voice interactions to view
them selectively. See "Choosing how interaction data displays in the Card view (DESKTOP)" on
page 315, and "Choosing how interaction data displays in the Grid view (DESKTOP)" on page
316 for more information.
WEB - You can search for voice interactions in Ignite Web version 9.1.
WEB - You can perform a keyword search for either historical interactions or interactions in
queue.
1. From the Folders pane, select a folder. If necessary, expand the My Folders,
Processed, Unified Queues, Reporting Queues, or Individual Queues folder.
2. In the Search or Filter field, type keywords over the ghost text.
Note:
1. Click History.
2. Optionally, select a Filter.
3. Optionally, select Only show my items.
4. In the Search interactions field, type the keyword(s). To clear search texts, click
Clear.
Use the following search criteria in any combination to search for historical interactions.
Use the following search criteria in any combination to search for in queue interactions.
DESKTOP - This includes Ignite's In Progress folder, which enables supervisors to see
interactions currently in agent Inboxes. This search capability does not require Multimedia
Contact Center licensing. However, to view and search interactions in queue using Ignite,
employees must have a Multimedia Contact Center license and multimedia agents assigned to
the queue.
The following explains how to use filters to search Ignite. This information does not apply to voice
interactions.
Note:
• Time stamps on interactions reflect the Ignite client time. To search interactions by
date or time, use the date or time for the Ignite client.
• To display more search results, click 'Show more results….
Using the filters in the following table, you can perform the following searches in Ignite.
Note:
Filter Explanation
NOT Finds interactions containing one word as long as it does not also
contain another
Filter Explanation
Month name Finds interactions received on a specific month. You can also
search by a specific date in the month.
Filter Explanation
Note:
> (for searches by date Finds interactions by dates after the specified date or date keyword
or attachment size)
For example, date:>August 18 2013, or date:>August, or
date:>August 18
>= (for searches by Finds interactions by dates after or on the specified date or date
date or attachment keyword
size)
For example, date:>=August 18 2013, or date:>August, or
date:>=August 18
Filter Explanation
< (for searches by date Finds interactions by dates before the specified date or date
or attachment size) keyword
<= (for searches by Finds interactions by dates before or on the specified date or date
date or attachment keyword
size)
For example, date:<=August 18 2013, or date:<=August, or
date<=August 18
NOT or - (for searches Finds interactions received on one date but not another
by date)
For example, date:This month NOT Last week, or date:This month -
Last week
Filter Explanation
from: Finds interactions received from a specific sender. You can search
by the sender's first name, last name, full name, or email address.
cc: Finds interactions cc’d to a specific recipient. You can search by the
recipient’s first name, last name, full name, or email address.
Filter Explanation
agent: Finds interactions last handled by a specific agent. You can search
by the agent’s first name, last name, full name, or by reporting
number.
or
agent:1000
or
attachments:<200KB
Note:
General searches – Any keywords can be typed in the search field, and the search returns
interactions containing the keywords.
For example, if an agent types ‘sales order’ in the Filter field, Ignite searches for interactions in
the selected folder containing the terms sales and order.
In the Inbox, the History, and the Queues pages, while you type the search keywords in the
Queue box, the system displays a predictive list of results based on the letters you type.
For example, if an agent types ‘a’ letter in the Queue box, Ignite (Web) displays any queue
names that contain ‘a’ (i.e. chat_queue12, email_queue33) as a predictive list of results.
Targeted searches – You can limit searches to fields and folders by inserting a colon between
the field and the search term.
For example, an agent searching interactions’ Subject fields for the word ‘order’ can type
‘subject:order’. In this example, Ignite searches the ‘Subject’ fields of interactions in the selected
folder for the term ‘order’.
Multiple targeted searches – You can limit searches to more than one field using semi-colons.
For example, an agent searching for an order placed by a specific customer can type
‘subject:order;from:Renee’. Ignite interprets this as (Subject contains Order) AND (From contains
Renee). In this example, the program searches the Subject fields of contacts to find orders from
Renee.
Note:
• If at least one of the filters ends with ‘:’, you must separate all filters with “;”. For
example, 'from:Renee;date:yesterday'.
• If at least one of the filters ends with ‘:’, you cannot use ‘NOT’, ‘-‘, and ‘OR’
between the filters. For example, typing ‘order:Renee OR from:Tom to retrieve
orders placed by either Renee or Tom is invalid. Typing ‘order;from:Renee OR
from:Tom’ is valid and will retrieve orders placed by either Renee or Tom.
Complex targeted searches – You can perform complex searches to further narrow results
returned.
For example, an agent searching for a completed order, placed by a specific customer, can type
‘completed;subject:sales order;from:Renee’. Ignite interprets this as: Completed AND (Subject
= (Sales AND Order)) AND (From contains Renee). In this example, Ignite searches the Subject
fields of contacts for completed sales orders placed by Renee.
Email attachment size searches - You can search emails by attachment size. Searches by
bytes (‘b’), kilobytes (‘KB’), and megabytes (‘MB’) are supported. If no size unit is specified, the
default search unit is bytes. If searching for attachments by size, specifying "attachments.size:" in
your query returns results more efficiently.
Agents present in an agent group can receive interactions in the Inbox, pick interactions out of
queue, and be sent interactions from a supervisor. Agents absent from an agent group cannot
handle interactions for the queue.
Agent states refers to an agent’s availability to receive ACD interactions. Examples of agent
states include Available, Busy/Make Busy and Do Not Disturb. An agent’s state determines Ignite
handling options available to them.
WEB - An agent in the Offline state is logged in to Ignite but their ACD agents are not logged in to
the system. In this state interactions cannot be handled for the queue.
Note:
When you configure Agent Group Presence for agents who use an ACD softphone, you must
set the default presence to Absent. If the presence is set to Present, agents will receive
ACD calls when they log in to MiCollab, without logging in to Ignite.
Agents can view Agent Group Presence on a group-by-group basis across media types. If
administrative configurations permit, agents may also make themselves present in and absent
from agent groups and the media types that the group handles.
Check marks display beside agent groups to which the agent is present. Media types that an
agent is present in handle display a blue background. Media types that an agent is not present
in handle display a white background.
Media types that an agent is present in handle display in blue. Media types that an agent is
not present in handle display in grey.
Adjusting Agent Group Presence enables agents to make themselves available or unavailable
for interactions of different media types. For example, agents belonging to the Sales (voice and
chat) and the Training (email) agent groups can make themselves available to answer only email
interactions by becoming absent from the Sales group.
Agents can also make themselves available or unavailable to answer interactions of specific
media types. For example, the agent makes herself available to answer only Sales voice
interactions by becoming absent from chat in the Sales agent group.
Agents can also make themselves available or unavailable to all agent groups of which they are
members, in one action.
DESKTOP - When agents are not present in any of their agent groups, Ignite’s Status bar
displays a ‘Time Logged in Not Present’ status. See "The Status bar (DESKTOP)" for more
information.
WEB - When agents are not present in any of their agent groups, their state becomes Away (Not
Present). See "Viewing agent state and state statistics (WEB)".
Note:
Agents may be made automatically present in their agent groups upon logging in to
Ignite, with multimedia interactions routing as soon as the login is complete. This is an
administrative configuration and is not controlled by the agent. However, without this
administrative configuration, agents must make themselves present in agent groups in order
to be offered interactions.
You become present in all agent groups and media types within the group.
4. To become absent from all agent groups, click Clear All.
5. Click Apply.
You become absent from all agent groups and media types within the group.
2. To become present in all agent groups, click Join All > Update.
3. To become absent from all agent groups, click Leave All > Update.
• Available: Agents are logged into Ignite and their ACD agents are available to receive
ACD interactions.
• Offline: Agents are logged into Ignite and can peruse the interaction repository, but
their ACD agents are offline and cannot receive ACD interactions.
Note:
Setting Busy/Make Busy for one agent capability applies a Busy/Make Busy status to all of the
employee’s agents. Inbound multimedia interactions are not routed to the agent; however, agents
in Busy/Make Busy can receive transferred interactions. While in Busy/Make Busy, voice agents
are able to receive Non ACD voice interactions without being removed from Busy/Make Busy and
can pick interactions waiting in queue.
Entering Busy/Make Busy while handling interactions ensures that agents are not offered more
once finished. However, existing voice, email, chat, SMS, and open media interactions continue
until one of the parties ends the interaction.
Agents also enter Reseize Timer when they decline an interaction, fail to answer a ringing
interaction within the allotted time, and place an item on hold for longer than is permitted. In
each instance, the agent is automatically put into Busy/Make Busy across all media capabilities,
and a System Make Busy is registered for the employee. For information on the time allotted to
answer a ringing interaction and the duration for which interactions can be on hold, contact your
supervisor or system administrator.
Note:
Agents must remove Busy/Make Busy to become available to receive inbound multimedia
interactions and internal voice interactions.
Note:
Agents cannot program MKB codes and can only select from the list provided.
3. To change a Make Busy code assigned to you, follow the above steps.
Note:
Do Not Disturb and Busy/Make Busy states layer. If an agent in Busy/Make Busy changes
their state to Do Not Disturb, the agent will remain in Busy/Make Busy once Do Not Disturb
is removed. This prevents agents from receiving interactions when switching states between
Busy/Make Busy and Do Not Disturb.
Note:
To remove DND and revert to Make Busy, click your avatar, click the X button next to Do Not
Disturb
Note:
Do Not Disturb and Busy/Make Busy states layer. If an agent in Busy/Make Busy changes
their state to Do Not Disturb, the agent will remain in Busy/Make Busy once Do Not Disturb is
removed. This prevents agents from receiving contacts when switching states between Busy/
Make Busy and Do Not Disturb.
Agents in DND can receive external voice interactions, and existing chat and inbound/internal
voice interactions continue until one of the parties ends the interaction.
Setting DND for one agent capability applies a DND status to all of the employee’s agents.
Note:
Agents must remove DND to become available to receive inbound multimedia interactions
or internal voice interactions
Note:
Agents cannot program DND codes and can select only from the list provided.
Note:
If an agent changes their DND state to MKB, the agent remains in DND until this state is
removed.
Note:
If an employee applies a MKB state while in DND, the employee remains in DND until the
DND state is removed.
Note:
• When agents are in Work Timer, Interactions remain in the Inbox until Work Timer
is removed .
• Employees in Work Timer can apply Busy/Make Busy or DND, but will remain in a
Work Timer state until the Work Timer expires or is cancelled.
WEB - Interactions in Work Timer are marked with yellow and a clock icon.
If administrative configurations permit, agents are placed in a Work Timer state after completing
an interaction. During Work Timer agents can complete after-contact work, such as speaking with
a supervisor, without having this downtime affect their performance statistics.
Work Timer counts against an agent’s Workload, and can determine whether agents are pushed
interactions. If agents are in a Work Timer state for the maximum number of interactions they can
handle for a media type, they are not offered another interaction of that media type until Work
Timer expires or is removed. For example, an agent permitted to handle two emails at a time is
in Work Timer for both. Until one Work Timer state expires or is removed, the agent is not offered
another inbound email. However, this agent will be pushed chat interactions, unless they are
also in Work Timer for the maximum number of chat interactions their Workload permits them to
receive.
Ignite displays Workload statistics, including the number of Work Timer states the agent is in for
each media type. See "The Status bar (DESKTOP)" for more information. See "Viewing agent
handling statistics (WEB)". For more information on Workload, see "Handling multimedia contacts
in Ignite".
The duration of Work Timer is configured on a queue-by-queue basis. To determine this duration,
contact your supervisor or system administrator.
When Work Timer is the overriding state, agents can remove Work Timer and put themselves
back into an overriding state across all media capabilities. Once agents have removed Work
Timer, they cannot put themselves back into this state.
Note:
Alternatively, click your avatar, select State, and choose an alternate state.
Note:
To retain the integrity of Excel charts pasted in Ignite, first copy the Excel table to Word and
then copy/paste it in Ignite.
Multimedia Contact Center supports skills-based routing. When an agent is available, they
receive interactions based on the following criteria
Agents can handle multiple interactions at a time. However, an employee's Workload determines
the number and type of media interactions that can be pushed to an agent at any one time. For
example, agents may not be permitted to receive voice and chat interactions concurrently. Or,
agents may be permitted to receive a maximum of five emails and two chats at one time.
When traffic levels necessitate, supervisors with appropriate licensing can log into Ignite
and alleviate congestion by handling interactions. Emails can be configured to overflow to a
supervisor after a specified length of time in queue. If a supervisor primarily uses Contact Center
Client, they can minimize Ignite and be notified when they receive an overflow email.
If you are not being pushed interactions, it may be that you have reached the maximum number
of interactions your Workload permits you to handle. For more information on viewing your
Workload status, see "The Status bar (DESKTOP)".
Note also that agents who have reached their Workload maximum for a media type can pick
items out of queue and can receive transferred interactions of that type.
To provide context on how interactions reach queues and agents, this section explains
In addition, the following sections explain general interaction handling procedures, including
For information on procedures specific to handling different media types, see "Handling calls in
Ignite", "Handling emails in Ignite", and "Handling chats in Ignite".
Transition from one interaction type to other can be done. For more information on Transition to
other type, See "Transitioning from one conversation type to another (WEB)".
Once an interaction has reached a queue, it is offered to an agent group. Agents in the group
are responsible for accepting the interaction. Interactions wait in queue until an agent from an
assigned agent group accepts them. Overflow and interflow are two routing methods designed to
reduce the length of time that interactions wait in queue
Overflowing interactions
Overflow is the process of offering an interaction, already offered to one agent group, to
additional agent groups after the interaction has been waiting in queue past a set time. The
amount of time before an interaction overflows is determined by an administrative configuration,
and the system overflows the interaction without agent intervention.
Interflowing interactions
Interflow is the process of taking an interaction out of one queue and routing it to a different
answer point, such as another queue or an external email address. Interflow is an administrative
configuration occurring under specified queue conditions, and occurs without agent intervention.
Note:
Push, Pick, and Mixed routing models determine how agents receive email and chat
interactions in queue. Delivery of voice interactions is determined by programming on
the 3300 ICP. For more information, contact your supervisor or system administrator.
Push model
In Push model interactions in queue are sent to an available agent’s Inbox. The number
of interactions that can be pushed to an agent’s Inbox at one time depends on the agent’s
Workload, as configured in the system, and can vary by media type. For example, the system
may be permitted to push five emails at a time to an agent’s Inbox but only two chats.
Interactions are also pushed to agents on the basis of Agent Skills (as configured in the system),
Queue Priority, and Preferred Agent. A Preferred Agent is one who is engaging in an ongoing
interaction with a customer.
With the exception of transferred interactions, agents do not receive items in their Inbox if the
Inbox contains ringing interactions of the same media type.
Pick model
In Pick model agents pick interactions out of queue exclusively. Agents in Do Not Disturb cannot
pick interactions out of queue.
Mixed model
In Mixed model agents pick interactions out of queue, but items sitting in queue past a set time
are pushed to agents’ Inboxes. Workload determines the number and type of media interactions
that can be pushed to an agent at any one time. For more details, see ‘Push model’, above.
With the exception of transferred interactions, agents do not receive items in their Inbox if the
Inbox contains ringing interactions of the same media type.
• DESKTOP - Ignite marks ringing interactions in red, and indicates in red the number of
interactions ringing in the Inbox.
• WEB - Ignite marks ringing interactions with a ‘ringing’ icon, and the agent’s state
indicates ‘Incoming’.
Note:
• With the exception of transferred interactions, in Push and Mixed routing models
agents do not receive items in their Inbox if the Inbox contains ringing interactions
of the same media type. Once ringing interaction is put into reply mode, another
interaction of that media type is pushed to the Inbox in a ringing state if the agent's
Workload permits. This behavior continues until an agent's Workload is met.
• For MiVoice Connect phones, if the ring count for ACD calls exceeds the requeue
timer, which is set to 30 seconds by default, calls will directly connect to agent's
voice mail.
Toaster notifications indicate the interaction’s media type and display information such as
originating phone number, subject, and queue name. Information displayed varies by media type.
Agents can accept or decline the interaction by selecting the appropriate option on the toaster
notification. Option availability varies by the interaction's media type.
Note:
Accepting emails sends them to the agent's Inbox. Agents can open them in reply mode with
Cc'd recipients included in the reply.
DESKTOP
• If agents are permitted to preview interactions, clicking anywhere within the notification
opens Ignite with the item ringing in the Inbox. Agents are then able to preview the
interaction.
• If the agent does not act on the notification by accepting, declining, or previewing the
interaction, the Ignite icon flashes in the taskbar and eventually remains a solid color
until the application is selected.
WEB
• When Ignite is in focus, the toaster notification pops with options to Accept and,
depending on the interaction's media type, Decline the interaction. If Ignite is not in
focus, a notification indicates a ringing interaction. Clicking a notification takes you to
the relevant interaction.
• When Ignite is minimized, clicking the notification opens Ignite with the item ringing in
the Inbox. Agents are then able to handle the interaction.
• When accepting open media interactions, the link that displays depends on Target Uri
settings and, as such, may display as embedded content within Ignite (WEB) or as
a new page in the browser. Please note that some web applications do not support
iframe embedded content, such as is used with Ignite (WEB). If you want content to be
embedded in Ignite (WEB), you must enable iframe embedding in such third party web
applications.
Screen pops differ from toaster notifications. Toaster notifications alert agents to ringing
interactions and indicate basic information such as the interaction’s media type. A screen pop
displays information relevant to handling a specific interaction.
For example, a screen pop may display a web page listing a customer’s recent interaction history.
Agents use screen pops to provide more personalized, informed customer service. It is the
agent’s responsibility to close the screen pop once the information is no longer required.
Screen pops open on agents’ desktops when a ringing item is selected in the Inbox.
If you are receiving two screen pops and/or two toaster notifications for a single interaction,
consult your supervisor or system administrator. For more information on toaster notifications,
see "Receiving toaster notifications of new interactions".
Note:
• If you receive a security warning when your screen pop displays, consult your
supervisor or system administrator about disabling the warnings.
• WEB - By default, screen pops open in a new tab but obey browser configuration
and may therefore open in a new window.
• WEB - If screen pops are not displaying you may need to disable pop-up blockers
for this site.
For example, an agent gets a response from a customer saying, 'How do I do that?'. However,
the customer has deleted all prior communication in the email chain. The agent can retrieve
transcripts of previous interactions with the customer in order to answer the question.
If an interaction’s history is not visible via the History function, we recommend searching Ignite’s
repository. For more information on searching, see "Searching Ignite".
Note:
This function is available only if the system has case and ticket numbers enabled. This is
an administrative configuration and cannot be adjusted by agents.
Note:
You can pare down the list of interactions displaying on the History page using filters. For
information, see "Searching Ignite using search filters".
1. Select an interaction or hover over the item’s avatar and select History.
2. Select either Case or Customer and select the interaction to review.
You can display specific interactions by entering search criteria in the ‘Search interactions’
field.
3. To exit out of this view, click Back to <page>.
1. In the Folders pane, select a folder and select an interaction in the folder.
2. In the Preview pane, select History and Account Codes, and select By Case.
3. To see more items, double-click Show more results....
4. Optionally, sort items in each pane in ascending or descending order by clicking the
column headers.
5. To view a transcript of the communication, double-click the interaction in the pane.
1. In the Folders pane, select a folder and select an interaction in the folder.
2. In the Preview pane, select History and Account Codes, and select By Customer.
3. To see more items, double-click Show more results....
4. Optionally, sort items in each pane in ascending or descending order by clicking the
column headers.
5. To view a transcript of the communication, double-click the interaction in the pane.
For example, an agent handling chats for three catalog companies enters an Account Code
of ‘01’ to indicate that the customer is inquiring about Company A. Later in the same chat
interaction the agent enters an Account Code of ‘06’ to indicate that the customer is inquiring
about Company A’s mail-out services.
Agents can apply Account Codes only when replying to interactions. Agents can tag interactions
with multiple Account Codes but cannot configure Account Codes in Ignite.
Please note the following limitations regarding tagging voice interactions with Account Codes in
Ignite
• Voice interactions handled in Ignite can only be tagged only with non-verified Account
Codes. Verified Account Codes are entered before an outbound voice interaction and
can be applied via Contact Center Client. For more information on verified Account
Codes in your contact center, contact your system administrator.
• Tagging interactions with Classification Codes is supported from Ignite for voice
interactions only. Classification codes associate the entire interaction handling
duration to the Account Code selected. This includes transfer time. It also includes
Work Timer duration if 'Include queue work timer as part of handling time' is enabled
on the queue. To learn more about applying Classification Codes to voice interactions,
see "Tagging calls with Classification Codes".
Note:
Classification Codes are not supported for multimedia interactions, only Account Codes may
be used on multimedia interactions.
Note:
Account Codes on emails are terminated after employee logout. Agents logging in to Ignite to
resume work on emails must re-enter their last Account Code.
1. In the Preview pane, expand History and Account Codes and select Account
Codes.
2. Expand any Account Code groups, if required.
3. Beside the Account Code you are using to tag the interaction, click Apply.
Note:
Alternatively, apply Account Codes via the Account Code button that displays in the
Sidebar.
1. Select an interaction or hover over the item avatar and click Apply Code. The account
codes/categories are displayed in tree view (as configured in YSE) in the Apply
Classification/Account Code window.
2. Select an Account Code. You can type the name or number of a code in the Search
field. Optionally, use the Expand or Collapse buttons to view account codes and
select the required account code.
Note:
If you enter a number or the name in the search field, and the system returns only one
result, you can apply the Code by pressing Enter.
Interactions can be sent back to the queue for several reasons. First, interactions requeue
when declined by an agent. Second, ringing interactions in the Inbox requeue when the ringing
timer expires. Third, interactions on hold requeue when the hold timer expires, including emails
automatically placed on hold after agent's logout. Fourth, interactions in the Inbox can requeue
on employee logout. However, administrative configuration determines requeue behavior for
email interactions in the Inbox.
In each instance, the interaction is returned to the queue as the longest waiting. Unless logged
out, the employee is put into a Busy/Make Busy state across all agent capabilities, and a System
Make Busy is registered.
Agents logging out of Ignite with interactions in the Inbox are notified whether relevant
interactions will be requeued (DESKTOP). However, in these instances a System MKB is not
registered against the employee.
Requeued emails contain any response text drafted. This text is visible to other employees who
handle the email. Agents can choose to include the drafted content when previewing requeued
emails in queue.
Requeued chat and SMS interactions contain all of the previous interaction between contact and
agent.
If the system immediately requeues interactions on logout, to avoid losing work we recommend
that agents either complete their work or transfer the item to a queue before logging out.
Note:
• The time allotted to answer ringing interactions, the duration for which interactions
can be on hold before requeuing, and requeue behavior for email interactions
on employee logout is determined by administrative configuration. For more
information, contact your supervisor or system administrator.
• Logging in and logging out of Ignite does not reset the duration interactions can be
on hold before requeuing.
The agent can transition to an alternate interaction type only if the agent is associated with that
media type and if the customer’s relevant contact details are available. Agents can also edit
contact information during an interaction.
Note:
Agents cannot transition from other media types to a chat interaction, as chats are inbound
only.
1. Click Inbox and select the interaction or hover over the item avatar.
2. Click the action icon based on the interaction type.
For example, with an email interaction, click Reply, or with a chat interaction, reply to the chat
messages.
3. From the handling icons, click the interaction type icon to which you want to transition.
Optionally, you can hover over the item avatar in the Inbox to view the handling icons.
Note:
You can edit the contact information for the customer during the interaction and you
can view the updated contact information and, if required, can transition to an alternate
interaction type.
Optionally, you can hover over the avatar to view the Edit icon.
3. In the Edit Contact window, update the contact details, and click Update.
Note:
You cannot edit a case that is being edited by another agent or supervisor. A lock icon
displays next to the action icons to indicate that a case is being edited by another agent or
supervisor. Only one person can perform the following actions at a time in Ignite—edit the
subject of the case, change the state of the case, add or edit notes, cut from case, or merge
cases.
If you know the case details, you can use the search and filter capabilities to locate the required
case.
• Case details—Displays case details such as customer details, subject, details of the
agent who handled the last interaction in the case, or the queue details, date modified,
and the state.
• Notes—Lists the notes entered for the selected case. You can search for notes by
entering the string in the search field in the Notes tab.
• Interactions—Lists all interactions related to the selected case. You can filter and
search for interactions in this tab.
• Participants—Lists the contact details of all participants.
• Other cases for this customer—Lists the other cases associated with this
customer(s). You can filter and search for cases in this tab.
• State—Indicates the current state of the case. Possible values include
•
Pending—Cases are indicated by icon. Cases are automatically assigned this
state when inbound interactions are received by the system. This state is assigned
even if the linked case was previously closed. The only exception is when a new
interaction is already linked to an existing case whose state is marked as ‘Follow up
required’. You can see cases in the pending state only for the queues to which you
are assigned.
• In Progress—Cases are automatically assigned this state when you accept
interaction associated with that case. The only exception is when a new interaction
is already linked to an existing case whose state is marked as ‘Follow up required’.
• Follow up required—Cases are indicated by a red badge. When an agent handles
an interaction, and wants to mark the interaction for further follow up, the case can
be flagged as ‘Follow up required’.
• Follow up required now—Cases are indicated by a red badge. When an agent
marks an interaction for a follow up at a specific date and time, just before the
specified date and time, the interaction is which is flagged as ‘Follow up required’
changes to ‘Follow up required now’, a notification icon on the top panel prompts
the agent to take action on the interaction.
• Waiting for customer—Cases are indicated by an orange badge. When an agent
completes an interaction, or marks the interaction as ‘No Reply’, the case’s state
is set to ‘Waiting for customer’ unless it was previously set to ‘Follow up required’
or ‘Resolved’, in which case it remains unchanged. When an agent sends an
unsolicited outbound email or SMS to a customer, a new case is automatically
created and assigned with this state.
• Resolved—Cases are indicated by a blue check mark icon. You can set the case
to ‘Resolved’ when you no longer need to interact with or track it. Cases in ‘Waiting
for customer’ state are automatically moved to ‘Resolved’ state after the configured
number of days (by default, it is 14 days) when no interactions are added or actions
are taken.
•
Closed—Indicated by icon. Cases in ‘Resolved’ state are automatically moved to
‘Closed’ state after the configured number of days (by default, it is 7 days) when no
interactions are added, or actions are taken.
The details are displayed in the right pane. The default subject is based on the most recent
interaction associated to the case, relevant to the interaction media type.
3. Click Edit Subject icon.
4. Enter the subject in the text box.
5. Click Save.
1. Click Cases, and in the Search cases field, enter a search string.
2. For a more detailed search, click the Advanced Search in the Search cases field
and enter specific details in the fields displayed. For Media, Queue, and Employee
fields, you can use the Only search most recent check box next to fields to search
for cases having the particular media, queue, or employee as their last one.
For example, let us assume that there is a case linked to two interactions; a chat (first
interaction) and a voice call (second and last interaction). If you select “chat” in the Media
drop-down menu and:
• Do not select the Only search most recent check box next to Media, Ignite will
find this case because it will search for all cases that have a chat interaction.
• Select the Only search most recent check box next to Media, Ignite will only
search for cases whose most recent interaction type is “chat”, hence, the above
case is not found as the last interaction for the above case is not “chat”, but is
“voice”.
3. Click Search to display the search results.
4. Click the filter name to filter the search results based on case states. The available
filters are All, Pending, In progress, Waiting for customer, Follow up required,
Resolved and Closed.
Note:
• If an agent selects the Only show my items check box, Ignite displays only
cases associated with that agent.
• In Case folder, agents will be able to Reply and Reply All to the email
interactions only in Waiting for Customer, Follow up required, Resolved, and
Closed case states.
• In Case folder, agents will not be able to Reply and Reply All to the email
interactions in Pending and In progress case states.
Note:
This state can be set only for cases that are currently in an ‘In Progress’, ‘Waiting for
customer’, or ‘Resolved’ state.
3. Click the Flag for follow up icon. The Case Follow-up screen is displayed.
4. Select the notification date and time. If you are a supervisor, you can choose an agent
you want to notify.
5. Click OK. You will receive a reminder notification at the set date and time. You can
review the case by clicking the notification toaster from your Inbox.
In case you want to edit the notification details, click the Follow up Reminder icon and make
the changes.
The details are displayed in the right pane. Any new case that is responded to, is flagged as
Waiting for customer and denoted by an orange badge.
3. Click the Resolve icon. A confirmation window is displayed.
4. Click OK.
To merge cases (and their associated interactions and notes) into a single target case
1. Click Cases.
2. From the list of cases, click the case you want to merge into the target case.
3. In the Other Cases for this customer tab, click Merge.
4. In the Confirm the merge of case dialog box, click OK.
Note:
When merged, all notes and interactions from the original case are moved to the target
case and the original case is deleted. If the target case was closed before the merge, it is
reopened only after the merge if the original case was neither closed nor reopened, and its
new state will match the state of the original case.
To search notes
• In the Notes tab, type the text in the Search notes field. Optionally, you can include
the system notes to your search by clicking Show system notes option.
To add notes
To edit notes
Note:
You can edit only the most recent note that you have created.
*: When a customer sends an email without a case ID in the subject to the contact center, a new
case is always created (Ignite does not reuse an existing case ID).
Note:
When you initiate an outbound email, the previous case ID is not automatically reused, but
Ignite displays the reusable case found and you can choose to reuse the Case ID if you wish
to.
You can enable or disable the option to search for reusable cases on the Options >
Customization page.
You can filter, search, view the status of the interactions, move interactions from a case to
another case, and go to the corresponding folders(Inbox, History or Inqueue) from the cases
page.
Click the down arrow in the Search field and enter the specific details.
Optionally, you can filter based on case state – All, Draft, Inqueue, Ringing, Inbox, Handled,
Sent, No Reply, Junk, and Failed. You can also select the Only show my items check box to
filter your interactions.
You can also view all the cases, or the customer related to an interaction by clicking Case tab
or Customer tab next to the Search interaction field.
Note:
An agent can only Pick or Pick and Reply All to one interaction at a time from a case. Pick,
Pick and Reply All are available for Multimedia interactions, whereas only Pick is available for
Voice and Open Media interactions (replying to those can be performed only from the Inbox).
1. In the Inbox, identify and select the Inqueue interaction you just picked.
2. On the right pane, click either Reply or Reply All.
Note:
If the email to which you are replying has an existing draft, the To:, CC:, and BCC: fields
are cleared and refilled with the default addresses based on the reply type selected
3. The interaction opens in reply mode with all recipients copied. Type the content and
click Send.
To activate Pick or Pick and Reply All buttons in the Interactions tab
1. Click Cases, and from the list of cases, select the case of the Inqueue interaction.
2. In the Interactions tab, click Pick to assign the Inqueue interaction to yourself.
3. Click OK.
1. Click Cases, and, from the list of cases, select the case of the Inqueue interaction.
2. In the Interactions tab, click Pick and Reply All to assign the Inqueue interaction to
yourself and reply.
Note:
If the email to which you are replying has an existing draft, the To:, CC:, and BCC: fields
are cleared and refilled with the default addresses based on the reply type selected
3. The Interaction opens in reply mode with all recipients copied. Type the content and
click Send.
For example, for an interaction in your Inbox that contains a related interaction in the History
folder, you can navigate to the interactions tab and use the Go to icon next to this related
interaction to navigate to the History folder and view the related interaction.
Note:
• The Go to button is not displayed for the currently selected interaction in the Inbox,
but is displayed only for the other related interactions for the same customer.
• The Go to button is not displayed for the inbox items, that do not belong to you.
The following are the important points you must be familiar with before moving interactions from
the source case to other cases:
• If the source case is the only case the customer is associated with, you can select
one or many interactions to cut from that case, but not “all” of them. The selected
interactions will be moved to a new case.
• When the customer has more than one case, you can select one, many, or all
interactions from the source case and move them to an existing target case of the
same customer.
• The state of the new case will be same as the source case.
• The subject for a case is based on the last interaction associated with the case.
Therefore, after interactions are moved from one case to another, the subject of the
latter case might change.
1. Click Cases.
2. From the list of cases, select the case that contains the interaction(s) you want to
move.
3. In the Interactions tab, select the interaction from the list. Optionally, you can select
multiple interactions from this list.
4. Click Cut from Case icon next to the interaction or hover over the interaction avatar
and click the Cut from Case icon.
If you want to move multiple interactions, click the avatar and select many or all interactions,
and click Cut from Case icon at the top.
5. Paste the selected interactions to a new case or to an existing case:
• To paste to a new case, click the Paste to new case button. A new case is created
containing the interaction you moved there.
• To paste to an existing case (if there is one for this customer), click the Paste to
other case button, and search and select the target case in the dialog box that
displays.
Note:
• If you selected all interactions from a case to be moved, all the notes from the
case are moved to the target case and the source case is deleted.
• If the selected interactions are not the only interactions for the source case,
Ignite will display a list of notes that were created after the first interaction you
want to cut, and you can decide which notes (if any) you want to cut and paste it
into the target case.
6. Click OK.
7.2.15.10 Participants
You can view the list of participants associated with each case. The participants list includes
employees and external contacts.
Note:
Participants list can also contain contact information derived from Active Directory. Active
directory is supported only in single-tenant configuration.
• Search for the participants associated with a case using the search field
• Edit external participants’ contact information by clicking on the Edit icon. Note that
you cannot edit employee or active directory records. For information on editing
external contacts, see "Contacts (WEB)".
• View all the cases that the participant is associated with by clicking on the Case icon.
For information on viewing case information related to participants, see "Contacts
(WEB)".
• Associate or dissociate external contacts from cases by using the Associate and the
Dissociate icons. For information on associating and dissociating external contacts
from a case, see "Associating or disassociating participants to a case".
• Merge external contacts by clicking on the Merge icon. For information on merging
external contacts, see "Merge External Contacts".
• Search for an existing contact and associate the contact with the case—In the
Search field, type the contact name. Under Results, hover over the contact avatar
and click to select it and click OK.
• Add a new contact and then associate that contact—Click the Add Contact icon.
The Create and Associate Contact window is displayed. Enter the contact details
and click Save.
Note:
When you create a contact in Ignite(WEB), you must add an extension to the phone
number if multiple contacts share the same phone number.
The contact you associated with the case is listed in the Participants tab.
Note:
Removing or otherwise altering case and ticket numbers in subject lines before handling
emails can interfere with preferred agent routing. Agents should contact their supervisors or
system administrators before editing case and ticket numbers in email subject lines.
• Preview emails
• Preview drafted content for emails in queue (DESKTOP)
• Pick emails out of queue
• Reply to emails
• Forward emails
• Add attachments to emails
• Insert images in emails
• Preview and save attachments
• Transfer emails to internal and external destinations
• Decline emails
• Mark emails as ‘No Reply’ and ‘Junk’
• Place emails on hold and retrieve emails from hold
• Transition to alternate interaction types
• Correct spelling in email responses
• Create personal reply templates
• Apply personal reply templates to emails
• Apply reply templates to emails
• Apply personalized signatures to emails
• Apply quick reply templates to emails
• Reroute Failed emails
• Handle oversized emails
• Handle bounced emails
• Send outbound emails
Note:
DESKTOP - To complete the following procedures, you must be in Ignite’s My Folder’s View.
• Click Inbox and select an email to preview. In addition to handling options, you can
quickly access the case details, notes, calls, all the participants of the case, and other
cases from the same customer. This can save time when you are interacting with a
customer.
Normally agents see only the original content of the email interaction when viewing emails in
the List pane or the Preview pane. Requeued emails, however, may contain content drafted
by employees for use by other agents in the contact center. Agents can choose to filter the List
pane’s contents for a queue to show only the emails in queue that have drafted content from
other agents and include the drafted contents in the List pane and in the Preview pane. If agents
navigate away from the queue to another queue, the filter is removed.
Note:
Previewing drafted content for emails in queue in Ignite requires agent previews to be
enabled on the media server. See "Configuring Advanced options for media servers" for
more information.
1. In the Folders pane, right-click the email queue for which you want to preview drafted
content.
2. Select Drafts.
The List pane displays the requeued emails in queue that have drafted content. The Folder
pane displays the queue name in orange and italics.
The List pane displays all emails in queue. Drafted content is not displayed.
Emails picked out of queue ring in the agent’s Inbox until the interaction is put into reply mode.
For more information on ringing behavior, see "Ringing states in Ignite".
Note:
• Agents cannot pick or pick and reply to interactions from the queue if they are in
Do Not Disturb.
• Agents may only pick or pick and reply to interactions from the queue if they have
the appropriate permissions.
1. From the Folders pane, select the queue from which the email will be picked.
2. From the List pane, select an email from the queue and, from the Action bar, click the
Pick button.
Note:
Additional handling options display in the Action bar. For information on handling the
email, see the appropriate procedures in this section.
Note:
This action functions as 'reply all' if there are recipients Cc’d on the original email.
1. In the Folders pane, select the queue from which an email will be picked.
2. In the List pane, select an email from the queue and, from the Action bar, click the
Pick & Reply button.
The email is transferred to your Inbox and opens in reply mode, with all recipients copied.
Note:
The interaction is transferred to your Inbox and opens in reply mode with all recipients copied.
Note:
When replying to an email, you can select the Paste as Text button to paste the content
into the email message as plain text. When you click Paste as Text for the first time, Ignite
displays the message, “Paste is now in plain text mode. Contents will now be pasted as
plain text until you toggle this option off. The latest state of the toggle button is saved to your
profile.
DESKTOP - Emails to which an agent has replied display under ‘Handled’, in the Folders pane.
Formatted URLs entered by agents in email responses will become links when the agent sends
the email reply.
Note that, by default, the maximum file size for emails, including attachments, signatures, and
images, is 25 MB.
Note:
If the email to which you are replying has an existing draft, the To:, CC:, and BCC: fields
are cleared and refilled with the default addresses based on the reply type selected.
3. Insert addresses in the To: field, and copy or blind-copy additional recipients by filling
in the appropriate fields. Separate multiple addresses with semi-colons.
4. If enabled for this queue, you can select a different From address by clicking From
and selecting the email address.
By default, From is set to the email address of the last queue the email was handled from.
5. Type the email’s contents and, in the Action bar, click Send . An icon displays over
the Preview pane, indicating the email is being sent.
Note:
Additional handling options display in the Action bar. For more information, see the
appropriate procedures in this section.
1. Click Inbox and select an email or hover over the item avatar.
2. Click Reply and select either Reply or Reply All.
Note:
If the email to which you are replying has an existing draft, the To:, CC:, and BCC: fields
are cleared and refilled with the default addresses based on the reply type selected.
3. Insert addresses in the To: field, and copy or blind-copy additional recipients by filling
in the appropriate fields. Separate multiple addresses with semi-colons.
Note:
If you want to initiate an email to multiple customers without manually entering the
addresses, select the interaction in Inbox, in the preview pane, click Participants tab,
click the avatars of the desired contacts, a check mark is displayed against the selected
contacts, now click the email icon next to the Contacts Selected text. A new draft with all
the selected customer email addresses in the To field is initiated.
4. If enabled for this queue, you can select a different From address by clicking From
and selecting the email address.
By default, From is set to the email address of the last queue the email was handled from.
5. Type the email's contents and click Send.
DESKTOP - You can forward emails from the My History folder and its subfolders, the History
folder and its subfolders, and the Failed folders. Forwards in progress are housed in the agent's
personal Drafts folder, in the Forward subfolder. When forwarding an email that failed to route,
the options to reroute or junk the email will not be available.
WEB - You can forward emails from the History page. Forwards in progress are housed as drafts
in the Inbox.
Agents cannot forward emails from reply mode. Instead, agents can transfer emails to internal
and external destinations. For more information, see "Transferring emails to internal and external
destinations" and "Replying to emails".
Note:
When replying to an email, you can select the Paste as Text button to paste the content
into the email message as plain text. When you click Paste as Text for the first time, Ignite
displays the message, “Paste is now in plain text mode. Contents will now be pasted as
plain text until you toggle this option off. The latest state of the toggle button is saved to your
profile.
• Forward an email
• Discard forwards in progress
Note:
When you forward an email to an external email address, the contact information is
automatically added to the associated case and in the database. Also, the state of the case is
updated to "Waiting for customer".
• Click Inbox and either select the forward in progress or hover over the item avatar and
click Discard.
Note that, by default, the maximum file size for emails, including attachments, signatures, and
images, is 25 MB.
1. When replying to an email, click the Add attachment icon. This icon displays as a
paperclip.
2. Navigate to the file and click Open. You can select multiple files.
3. To remove an attachment, click the X button beside the attachment.
Inserting an image into an email embeds the image in the body of the email at the cursor point.
Dragging and dropping an image adds the image as an attachment. Copying and pasting an
image into an email embeds the image in the body of the email.
50 inserted images will be visible in Ignite email responses. After 50 the images will show as an X
in Ignite, but will display to the recipient in full.
Note that, by default, the maximum file size for emails, including attachments, signatures, and
images, is 25 MB.
Note:
Previewing and saving attachments are currently available in Ignite desktop only. The Ignite
web client allows for downloading attachments only.
Agents can preview the following attachments on incoming emails: PDF, Word, Excel, and
Windows Media files (.wma). Note that these applications are not included with Ignite and must
be installed on the agent’s desktop for previewing to function. Agents can also save attachments
to their hard drives, and remove attachments from received emails.
• Save attachments
• Remove attachments
Note:
If the list of attachments exceeds two lines, use the scroll bar to navigate attachments.
1. In the Preview pane, click the attachment and select Save. If the list of attachments
exceeds two lines, use the scroll bar to navigate attachments.
2. Browse to a save location and click Save.
Note:
Save dialog options may vary depending on your operating system. If more information is
required, please consult Microsoft Windows documentation.
Agents transfer emails internally to other agents and to queues. To receive transfers, devices
must be enabled to handle the interaction’s media type.
Agents who are logged out, in DND, Offline (WEB), or whose presence is Unknown cannot
receive transferred emails. Agents who are either in Busy/Make Busy or at their email Workload
limit can receive transferred emails.
When agents transfer emails from their Inbox, the email retains any text entered. This enables
agents receiving transferred mails to see and build on responses other agents have drafted.
Note:
• You may transfer interactions only if you have the appropriate permissions.
• If you are transferring an email with drafted content, the To:, CC:, and BCC:
fields will be cleared and replaced by the default addresses when another agent
chooses to Reply or Reply All to the email.
Note:
To transfer directly from the queue, select the email from the queue and, in the Action bar,
click ‘Transfer’. Follow steps 4 onward.
2. In the List pane, select an email and, in the Action bar, click Reply.
3. In the Action bar, click Transfer.
4. Select the Internal Transfer radio button and select an agent or queue. Expand the
device list if necessary. You can search for an internal transfer destination by typing
the name of an agent or queue in the ‘Search’ field.
5. Click Transfer.
1. Click Inbox and select an email or hover over the item avatar and click Accept.
To transfer from the Cases page, under Interactions tab, select the inqueue or inbox email
and click Goto icon. The Queues page is displayed. You can now transfer the email from the
Queues page. Follow steps 4 onward.
2. Click Reply and select either Reply or Reply All.
3. Click Transfer.
4. Select the email or hover over the item avatar and click Transfer icon.
Note:
Optionally you can select multiple emails from the Inbox or the Queues page and click
Transfer. The Transfer window is displayed. The list of available Employees and Queues
are displayed in the Results section.
Note:
To transfer directly from the queue, select the email from the queue and, in the Action bar,
click ‘Transfer’. Follow steps 4 onward.
2. In the List pane, select an email and, in the Action bar, click Reply.
3. In the Action bar, click Transfer.
4. Select the External Transfer radio button and, in the Transfer To: field, type an email
address. Separate multiple addresses with semi-colons.
Note:
Invalid entries return an error message. Re-type a valid entry and click ‘Transfer’.
5. Click Transfer.
1. Click Inbox and select an email or hover over the item avatar and click Accept.
To transfer from the Cases page, under Interactions tab, select the inqueue or inbox email
and click Goto icon. The Queues page is displayed. You can now transfer the email from the
Queues page. Follow steps 4 onward.
2. Click Reply and select either Reply or Reply All
3. Click Transfer.
4. Select the email or hover over the item avatar and click Transfer icon.
Note:
Optionally you can select multiple emails from the Inbox or the Queues page and click
Transfer. The Transfer window is displayed. The list of available Employees and Queues
are displayed in the Results section.
Note:
When an agent declines an interaction, they are automatically put into Busy/Make Busy
across all media capabilities. A System Make Busy and a requeue count is registered for the
employee . For more information, see "Setting and removing Busy/Make Busy in Ignite".
• Click Inbox and select an email or hover over the item avatar and click Decline.
Agents can also junk emails directly from 'Failed' rather than attempting to reroute them.
Marking interactions as No Reply and Junk removes the interactions from Ignite. If the item is in
queue or the Inbox, responses in progress are deleted.
Note:
1. In the Folders pane, either click Inbox, select the queue in which the email is waiting,
or select a Failed folder.
2. In the List pane, select an email and, in the Action bar, click either No Reply or Junk.
• Click Inbox and select an email or hover over the item avatar and click either No
Reply or Junk.
Note that administrative configurations may limit how long interactions may be on hold before
being requeued and a System Make Busy is registered for the employee. For information on this
limit, contact your supervisor or system administrator.
• Click Inbox and select an email, or hover over the item avatar, and click Hold.
1. In the Folders pane, click Inbox and, in the List pane, select the email on hold.
2. In the Action bar, click Remove Hold.
• Click Inbox and select an email on hold or hover over the item avatar and click
Remove Hold.
See the "Transitioning from one conversation type to another (WEB)" section in this guide.
Ignite’s spell check button is located in the formatting toolbar, along with additional formatting
options. Ignite’s spell checking function assists agents in sending polished responses to
customers.
Note:
• Right-click an underlined word and select the correct spelling from the list provided.
Note:
This function reverts words to their original spelling. It does not clear additions made to the
dictionary.
• In the Ignite formatting toolbar, from the dictionary language drop-down list, select a
language. See the following figure.
Note:
Note:
1. In the Ignite formatting toolbar, click the Delete Personal Dictionary button. (See the
following figure.)
2. Either refresh the page or log out of Ignite and log back in for the changes to take
effect.
• Click the Spellcheck As You Type button. (See the following figure.)
Note:
1. When an email is in reply mode, place the cursor in the body of the email response.
2. On the formatting toolbar, click the Insert Reply Template button.
3. In the Insert Reply Template window, begin typing the file name or the text that the
template contains. Templates matching the file name or the text will display.
4. To insert the template, in the Insert Reply Template window, click the template you
want to insert and click Insert. The text is inserted in the email, at the cursor point.
5. Optionally, delete the text from the window and repeat the above steps.
To apply reply templates by selecting the templates from the list (WEB)
1. When an email is in reply mode, place the cursor in the body of the email response.
2. On the formatting toolbar, click the Insert Reply Template button.
3. From the Insert Reply Templates window, select the reply template you want to apply
from the list and click Insert button.
4. Reply template is inserted in the email, at the cursor point.
5. Optionally, delete the text from the window and repeat the above steps.
1. When an email is in reply mode, place the cursor in the body of the email response.
2. On the formatting toolbar, click the Reply Template button.
3. In the Reply Template window, click the Browse Reply Templates button.
Note:
• The image must be in .jpg format while using a messaging file in the reply
template.
• The Chat reply templates must be saved in UTF-8 encoding or Unicode encoding.
1. When an email is in reply mode, place the cursor in the body of the email response.
2. On the formatting toolbar, click the Insert Reply Template button.
3. In the Insert Reply Template window, from the list of reply templates, type to search
for a reply template that you want to insert, or, click the reply template you want to
select from the list.
4. Optionally, click Preview to preview the selected reply template before inserting.
5. Click Insert.
Note:
1. Click Inbox, select an email, or hover over the item avatar, and click Reply or Reply
All.
The most recently used templates display at the bottom of the window.
2. Click the reply template you want to insert into the email response.
Note:
Quick reply templates is enabled by default, The Clear quick reply templates view after
insert is disabled when you disable the quick reply templates.
Agents may also mark these emails as Junk or forward the email. Forwarding emails from Failed
does not remove the original copy from these locations. Forwards in progress are housed in the
agent's personal Drafts folder (DESKTOP), in the Forward subfolder (DESKTOP) or in the Inbox
(WEB). If you reroute an email that has existing forward drafts, the drafts will be deleted.
For information on handling bounced and oversized emails, see "Handling bounced emails" and
"Handling oversized emails".
We recommend that agents and supervisors check Ignite frequently in order to reroute emails
that failed to route.
• DESKTOP - Under Processed, supervisors may see all emails that failed to route.
Agents see only the emails sent to the queues for which they answer.
• WEB - In HistoryFailed, supervisors will see all emails that failed to route. Agents see
only the emails sent to the queues for which they answer.
• While rerouting emails removes them from Failed immediately, there may be a delay
before the emails are transferred back to the queue.
• Agents may junk interactions only if they have the appropriate permissions.
If you select 'Forward,' the interaction is delivered to the Inbox where you can specify
recipients.
If administrative settings do not match the limits of your organization’s mail server, you may not
receive the error message. Subsequently, Ignite displays the following behavior:
DESKTOP - The email fails to send and displays in the Failed to Send subfolder (contained in
the Failed folder), where it can be selected, edited to reduce its size, and re-sent. Failed to Send
emails also display in the supervisor’s Failed to Send folder, where they can optionally edit and
resend them if the associated agent is inactive.
When there are items in the Failed to Send subfolder, the font color of this folder name, and of
the parent Failed folder, display in red, followed by a number indicating how many active items
currently reside in the folder.
WEB - The email fails to send and displays in the Inbox where it can be selected, edited to
reduce its size, and re-sent. Items that fail to send are marked in red and a failure message
displays. Supervisors can also view these items in History.
If your system is configured to support bounced email detection, and you have one or more
bounced emails pending, Ignite displays the following behavior:
DESKTOP - The number of bounced items displays beside your Auto Replies/Failed Delivery
subfolder (contained in the Failed folder). The font color of this folder name, and of the parent
Failed folder, displays in red. You can select an item and either Junk or forward it.
WEB - Bounced items display in the Inbox and are marked in red, with 'Auto-Reply' text. You can
select an item and either Junk or forward it. Supervisors can also view these items in History.
Note:
• Real-time and reporting statistics are not available for outbound email activity at
this time. We recommend instead that agents put themselves into Busy/Make
Busy, with an ‘Outbound email’ Reason Code applied, when drafting outbound
emails. Make Busy reports and real-time queue statistics will then display time
spent drafting outbound emails.
• If contact centers use preferred agent routing, we recommend that agents do not
adjust case and ticket numbers in email subject lines. Removing or otherwise
altering case and ticket numbers in subject lines can interfere with preferred agent
routing.
DESKTOP - Outbound emails in progress are housed in the agent's personal Drafts folder, in the
New Emails subfolder. This functionality is available to employees with email agents answering
for queues. Agents can only send outbound emails only from the email queues for which they
answer.
WEB - Outbound emails in progress are housed in the Inbox, marked as 'Draft'.
By default, the maximum file size for emails, including attachments, signatures, and images, is 25
MB.
Queue signatures are automatically inserted in outbound emails, if signatures are configured for
the queue. Queue signatures are inserted each time a queue is selected as the ‘From’ address.
If you are permitted to use personalized signatures in outbound emails, see "Applying
personalized signatures to emails".
Agents can perform common email functions when sending outbound emails, including inserting
images, attachments, and applying reply templates to email drafts. See the appropriate topics in
this guide for applicable procedures.
Outbound email functionality supports preferred agent routing, to enable ongoing interactions
between agents and email recipients.
Note:
Note:
Queue signatures are inserted each time a queue is selected as the ‘From’ address.
4. Insert addresses in the To: field, and copy or blind-copy additional recipients by filling
in the appropriate fields. Separate multiple addresses with semi-colons.
5. Type the email’s contents and, in the Action bar, click Send . An icon displays over
the Preview pane, indicating the email is being sent.
1. Click Contacts.
2. If the email destination is not a recent contact, type the email address in the Search
field.
3. Hover over the appropriate address and click the Email icon. For emails to agents, a
colored dot on the avatar indicates its availability.
The system checks if the selected contact is associated with any open cases and if there is
an existing open case, the Reusable case found dialog is displayed with the details of the
most recent open case for that contact. You can view the case information such as Case ID,
subject and the email body and decide if you want to reuse the existing Case ID for this email.
To reuse the Case ID, click Yes, else, click No.
Note:
If you do not wish to search for reusable cases in future, click the Disable searching for
reusable cases in the future check box. You can enable or disable the option to search
for reusable cases on the Options > Customization page.
Note:
Queue signatures are inserted each time a queue is selected as the ‘From’ address.
Agents are responsible for deleting non-applicable queue signatures from outbound email
drafts.
5. You can alternatively search for contacts and their associated email addresses by
clicking the To:, CC:, or Bcc: buttons. In the Contacts dialog box, select the required
contacts, the email address are auto-entered in the appropriate fields.
6. Type the email’s contents and click Send.
Note:
If Contacts is open, click Contacts again to close the window and expose the desired
controls.
Note:
If Contacts is open, click Contacts again to close the window and expose the desired
controls.
• Click Inbox and select a draft or hover over the item avatar and click Discard.
Note:
The Drafts folder contains the agent's emails in progress. To search for sent outbound
emails, search the Sent folder.
See "Performing keyword searches" for detailed search information and procedures.
Note:
If you are using Contact Center Messenger Chat, for more information see "Handling Contact
Center Messenger in Ignite"
Handling chats in Ignite mirrors common instant messaging applications, providing a familiar and
user-friendly experience. Chat sessions are initiated by customers via your contact center’s chat
request page or corporate website.
Interactions are automatically sent to your Inbox if you are the longest idle agent, the preferred
agent, or the agent with the highest skill level in your agent group, if your agent group uses skill
levels. Agents can also pick chat interactions out of queue.
Note:
DESKTOP - To complete the following procedures, you must be in Ignite’s My Folder’s View.
Chat interactions picked out of queue ring in the Inbox until the interaction is accepted. For more
information on ringing behavior, see "Ringing states in Ignite".
Note:
• Agents cannot pick or pick and reply to interactions from the queue if they are in
Do Not Disturb.
• Agents may only pick or pick and reply to interactions from the queue if they have
the appropriate permissions.
1. From the Folders pane, select the queue from which an interaction will be picked.
2. From the List pane, select a chat from the queue and, from the Action bar, click the
Pick button.
Note:
Additional handling options display in the Action bar. For information on handling the chat,
see the appropriate procedures in this section.
1. In the Folders pane, select the queue from which a chat will be picked.
2. In the List pane, select a chat from the queue and, from the Action bar, click the Pick
& Reply button.
Note:
Additional handling options display in the Action bar. For information on handling the chat,
see the appropriate procedures in this section.
2. Select an interaction or hover over the item avatar and click Pick > Pick and Reply.
Note:
Additional handling options display in the Action bar. For information on handling the chat,
see the appropriate procedures in this section.
• Click Inbox and select a chat session or hover over the item avatar and click Accept.
Note:
When an agent declines an interaction, they are automatically put into Busy/Make Busy
across all media capabilities. A System Make Busy and a requeue count is registered for the
employee . For more information, see "Setting and removing Busy/Make Busy in Ignite".
• Click Inbox and select a chat or hover over the item avatar and click Decline.
Note:
If you are using Contact Center Messenger Chat, for more information see Handling
Contact Center Messenger in Ignite
The following figure presents the Input pane during a chat session.
Ignite indicates to agents and customers that the other is typing a response. Ignite indicates that
customers have sent a response in an active chat as follows:
• DESKTOP - When the Inbox is not in focus and a customer sends a message in an
active chat, an orange indicator alerts agents and displays a number listing how many
interactions are waiting for replies.
• WEB - When Ignite is not in focus, a notification indicates that the customer has
entered a response. When Ignite is in focus but the active chat is not selected, an
exclamation mark displays beside the interaction and a notification displays. Clicking a
notification takes you to the relevant interaction.
Ignite permits content to be copied and pasted from other sources and turns URLS into
hyperlinks.
Ignite supports embedding content from Google Maps in chat sessions. However, this requires
the use of embed maps URL, available from Google Maps, to embed a Google map, such as:
<iframe src="https://www.google.com/maps/embed?pb=!1m18!1m12!
1m3!1d2804.500978803945!2d- 75.90911198444678!3d45.3386984790996!
2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0
x4cd1fff1517da8a9%3A0xe6bc8a721e90f2a5!2sMitel+Networks!5e0!3m2!
1sen!2sus!4v144553122 7487" width="600" height="450" frameborder="0"
style="border:0" allowfullscreen></iframe>
Ignite also supports the 'Share' link from the following websites. Cutting and pasting URLs from
the following sites embeds the content in a chat session.
• https://twitter.com/
• https://soundcloud.com
• http://www.youtube.com
If your message fails to send, a red icon displays beside the unsent message. To resend the
message, you can copy and paste the message from your chat window or you can retype it.
• Type a message in the Input pane and either press Enter or click the Send Message
button.
See the "Transitioning from one conversation type to another (WEB)" section in this guide.
Ignite’s spell check button is located in the formatting toolbar, along with additional formatting
options. Ignite’s spell checking function assists agents in sending polished responses to
customers.
Note:
• Right-click an underlined word and select the correct spelling from the list provided.
Note:
This function reverts words to their original spelling. It does not clear additions made to the
dictionary.
• In the Ignite formatting toolbar, from the dictionary language drop-down list, select a
language. (See the following figure.)
Note:
Note:
• In the Ignite formatting toolbar, click the Delete Personal Dictionary button. (See
the following figure.)
• Either refresh the page or log out of Ignite and log back in for the changes to take
effect.
• Click the Spellcheck As You Type button. (See the following figure.)
Note:
1. When a chat is in reply mode, place the cursor in the body of the chat response.
2. Click the Reply Template button.
3. Type the text that the template contains.
Note that administrative configurations may limit how long interactions may be on hold before
being requeued and a System Make Busy is registered for the employee. For information on this
limit, contact your supervisor or system administrator.
• When participating in a chat session, in the Action bar, click the Hold button.
• Click Inbox and select the chat or hover over the item avatar and click Hold.
Note:
1. Select your Inbox and, in the List pane, select the chat on hold.
2. In the Action bar, click Remove Hold.
Note:
• Click Inbox and select a chat on hold or hover over the item avatar and click Remove
Hold.
For example, an agent is handling three different chat sessions. Clicking ‘Next Longest’ highlights
the active chat session to the chat session that has been waiting the longest for an agent
response and switches that interaction back into the Active Contact pane.
When switching between active interactions, the chat session indicates that the agent is joining
and leaving the chat session as appropriate.
An active chat is one that is no longer ringing and has been joined.
3. In the Action bar, click Next Longest.
The system takes you to the next longest waiting active chat session in the Inbox.
Agents transfer chat sessions to other agents and to queues. To receive transfers, devices must
be enabled to handle the interaction’s media type.
Agents who are logged out, in DND, Offline (WEB), or whose presence is unknown cannot
receive transferred chats. Agents who are either in Busy/Make Busy or at their chat Workload
limit can receive transferred chats.
Note:
You may transfer interactions only if you have the appropriate permissions.
Note:
You can search for a transfer destination by typing the name of an agent or queue in the
Search field.
5. Click Transfer.
1. Click Inbox and select a chat or hover over the item avatar and click Accept.
To transfer from the Cases page, under Interactions tab, select the inqueue or inbox chat
and click Goto icon. The Queues page is displayed. You can now transfer the chat from the
Queues page.
2. Select the chat or hover over the item avatar and click Transfer icon.
Note:
Optionally you can select multiple interactions from the Queues page and click Transfer.
The Transfer window is displayed. The list of available Employees and Queues are
displayed in the Results section.
1. When participating in an active chat session, click the End Your Session button.
Forwards in progress are housed in the agent's personal Drafts folder (DESKTOP), in the
Forward subfolder (DESKTOP) or in the Inbox (WEB).
1. In the Folders pane, select either History, My History, one of the Handled
subfolders, or one of the Failed folders.
2. In the List pane, select a chat transcript and, in the Action bar, click Forward.
3. Insert addresses in the To: field, and copy or blind-copy additional recipients by filling
in the appropriate fields. Separate multiple addresses with semi-colons.
4. Click Send. An icon displays over the Preview pane, indicating the transcript is being
sent.
Note:
If you attempt to forward a transcript and receive a warning that the email address is
invalid, the queue that handled the chat may not have been configured for sending
transcripts. Contact your supervisor or system administrator.
Note:
You can also discard forwards in progress by clicking ‘Discard Draft’ in the Action bar instead
of ‘Send’.
• Click Inbox and either select the forward in progress or hover over the item avatar and
click Discard.
Note:
Agents may junk interactions only if they have the appropriate permissions.
If you select Forward, the interaction is delivered to the Inbox where you can specify
recipients.
SMS sessions are initiated by customers using contact information or, optionally, through the
contact center’s SMS request page or corporate website. SMS interactions are then routed to
appropriate queues.
Interactions are automatically sent to your Inbox if you are the longest idle agent or the agent with
the highest skill level in your agent group, if your agent group uses skill levels. Agents can also
pick SMS interactions out of queue.
Note:
Note:
DESKTOP - To complete the following procedures, you must be in Ignite’s My Folder’s View.
First, agents can pick interactions out of queue and send them to the Inbox. When the
interactions ring in the Inbox, agents can handle them.
Second, agents can choose to pick and reply to an interaction. Choosing to pick and reply to
an interaction sends the interaction to the agent's Inbox from where the agents can handle the
interaction.
SMS interactions picked out of queue ring in the Inbox until the interaction is accepted. For more
information on ringing behavior, see "Ringing states in Ignite".
Note:
• Agents cannot pick or pick and reply to interactions from the queue if they are in
Do Not Disturb.
• Agents may only pick or pick and reply to interactions from the queue if they have
the appropriate permissions.
1. From the Folders pane, select the queue from which an interaction will be picked.
2. From the List pane, select an SMS interaction from the queue and, from the Action
bar, click the Pick button.
Note:
Additional handling options display in the Action bar. For information on handling the SMS
interaction, see the appropriate procedures in this section.
1. In the Folders pane, select the queue from which an SMS interaction will be picked.
2. In the List pane, select an SMS interaction from the queue and, from the Action bar,
click the Pick & Reply button.
Note:
Additional handling options display in the Action bar. For information on handling the SMS
interaction, see the appropriate procedures in this section.
Note:
Additional handling options display in the Action bar. For information on handling the SMS
interaction, see the appropriate procedures in this section.
• Click Inbox and select an SMS session or hover over the item avatar and click
Accept.
After you join an SMS session, Ignite goes into Reply mode and the Input pane displays,
enabling you to reply to the interaction. Send responses using the arrow button.
Note:
When an agent declines an interaction, they are automatically put into Busy/Make Busy
across all media capabilities. A System Make Busy and a requeue count is registered for the
employee . For more information, see "Setting and removing Busy/Make Busy in Ignite".
• Click Inbox and select an SMS interaction or hover over the item avatar and click
Decline.
The spell check button is located in the formatting toolbar, along with additional formatting
options.
Note:
• Right-click an underlined word and select the correct spelling from the list provided.
Note:
This function reverts words to their original spelling. It does not clear additions made to the
dictionary.
• In the Ignite formatting toolbar, from the dictionary language drop-down list, select a
language. See the following figure.
Note:
Note:
1. In the Ignite formatting toolbar, click the Delete Personal Dictionary button. (See
the following figure.)
2. Either refresh the page or log out of Ignite and log back in for the changes to take
effect.
• Click the Spellcheck As You Type button. (See the following figure.)
Note:
1. When an SMS interaction is in reply mode, place the cursor in the body of the
response.
2. Click the Browse Reply Templates button.
The Browse Reply Template button displays as a magnifying glass in the formatting toolbar.
3. Type the text that the template contains.
Note that administrative configurations may limit how long interactions may be on hold before
being requeued and a System Make Busy is registered for the employee. For information on this
limit, contact your supervisor or system administrator.
• Click Inbox and select the SMS or hover over the item avatar and click Hold.
Note:
1. Select the Inbox and, in the List pane, select the SMS interaction on hold.
2. In the Action bar, click Remove hold.
Note:
• Click Inbox and select an SMS on hold or hover over the item avatar and click
Remove Hold.
See the "Transitioning from one conversation type to another (WEB)" section in this guide.
For example, an agent is handling three different SMS sessions. Clicking ‘Next Longest’
highlights the active SMS session that has been waiting the longest for a response and switches
that interaction back into the Active Contact pane.
When switching between active interactions, the SMS session indicates that the agent is joining
and leaving the SMS session as appropriate.
An active SMS session is one that is no longer ringing and has been joined.
3. In the Action bar, click Next Longest.
The system takes you to the next longest waiting active SMS session in the Inbox.
Agents who are logged out, in DND, Offline (WEB), or whose presence is unknown cannot
receive transferred SMS interactions. Agents who are either in Busy/Make Busy or at their SMS
Workload limit can receive transferred SMS interactions.
Note:
You may transfer interactions only if you have the appropriate permissions.
Note:
You can search for a transfer destination by typing the name of an agent or queue in the
Search field.
5. Click Transfer.
1. Click Inbox and select an SMS interaction or hover over the item avatar and click
Accept.
To transfer from the Cases page, under Interactions tab, select the inqueue or inbox SMS
and click Goto icon. The Queues page is displayed. You can now transfer the SMS from the
Queues page. Follow steps 3 onward.
2. Select the SMS or hover over the item avatar and click Transfer icon.
Note:
Optionally you can select multiple SMS from the Inbox or the Queues page and click
Transfer. The Transfer window is displayed. The list of available Employees and Queues
are displayed in the Results section.
1. When participating in an active SMS session, click the End Your Session button.
Forwards in progress are housed in the agent's personal Drafts folder (DESKTOP), in the
Forward subfolder (DESKTOP) or in the Inbox (WEB).
DESKTOP - You can forward SMS transcripts only from the My History folder and its Handled
subfolder, from the History folder and its Handled subfolder, and from the Failed folders.
WEB - You can forward SMS transcripts from the History page.
1. In the Folders pane, select either History, My History, one of the Handled
subfolders, or one of the Failed folders.
2. In the List pane, select an SMS transcript and, in the Action bar, click Forward.
3. Insert addresses in the To: field, and copy or blind-copy additional recipients by filling
in the appropriate fields. Separate multiple addresses with semi-colons.
4. Click Send. An icon displays over the Preview pane, indicating the transcript is being
sent.
Note:
If you attempt to forward a transcript and receive a warning that the email address is
invalid, the queue that handled the SMS interaction may not have been configured for
sending transcripts. Contact your supervisor or system administrator.
Note:
You can also discard forwards in progress by clicking ‘Discard Draft’ in the Action bar instead
of ‘Send’.
• Click Inbox and either select the forward in progress or hover over the item avatar and
click Discard.
Note:
Agents may junk interactions only if they have the appropriate permissions.
If you select 'Forward,' the interaction is delivered to the Inbox where you can specify
recipients.
Agents can also junk SMS interactions directly from 'Failed', rather than attempting to reroute
them.
Marking interactions as No Reply and Junk removes the interactions from Ignite. If the item is in
queue or the Inbox, responses in progress are deleted.
Note:
1. In the Folders pane, either click Inbox, select the queue in which the SMS message
is waiting, or select a Failed folder.
2. In the List pane, select an SMS message and, in the Action bar, click either No Reply
or Junk.
• Click Inbox and select an SMS interaction or hover over the item avatar and click
either No Reply or Junk.
WEB– Outbound SMS interactions in progress are housed in the Inbox, marked as 'Draft'.
1. Click Contacts
2. If the destination is not a recent interaction, type its name or number in the Search
field.
3. Hover over the destination's avatar and click the SMS icon. For SMS;interactions to
agents, a colored dot on the avatar indicates its availability.
4. Under From (queue), select an SMS queue.
Note:
Queue signatures are inserted each time a queue is selected as the ‘From’ address.
Agents are responsible for deleting non-applicable queue signatures from outbound SMS
drafts.
A new case is automatically created and assigned with "Waiting For Customer" state.
Note:
If Contacts is open, click Contacts again to close the window and expose the desired
controls.
Note:
If Contacts is open, click Contacts again to close the window and expose the desired
controls.
• Click Inbox and select a draft or hover over the item avatar and click Discard.
MiCollab Client is recommended for performing advanced call handling functions. For information
about handling voice Interactions in MiCollab Client, see the MiContact Center Business User
Guide .
The following procedures explains all the actions that you can perform while handling calls.
For other call handling functions such as conferencing and supervised transfers, refer the
appropriate sections for Contact Center Softphone, PhoneSet Manager, and Ignite (Web) in the
MiContact Center Business Online Help.
For important information about signing in and out of Ignite for voice agents, see "Signing into
and out of Ignite (WEB)".
Note:
• DESKTOP - Ignite provides call control for Inbound ACD interactions only. Agents
must make outbound calls using Contact Center Softphone, PhoneSet Manager,
or a hard set or use Web Ignite.
• DESKTOP - If your contact center focuses on voice interaction handling, we
recommend that you implement the MiCollab Client and Ignite integration
described in the .
• Ignite’s phone functionality does not support multiple lines.
• Ignite’s phone controls are not supported for External Hot Desking Agents.
Note:
• Agents cannot pick or pick and reply to interactions from the queue if they are in
Do Not Disturb.
• Agents may only pick or pick and reply to interactions from the queue if they have
the appropriate permissions.
1. From the Folders pane, select the queue from which a call will be picked.
2. From the List pane, select a call from the queue and, from the Action bar, click the
Pick button.
Note:
Additional handling options display in the Action bar. For more information, see the
appropriate procedures in this section.
Note:
For more information on silent monitoring, see the MiContact Center Business User Guide. For
more information on the Request Help feature, see the appropriate section in this guide.
You can answer incoming calls from Ignite. Ignite displays a toaster for each incoming call and
allows you to accept the call from the toaster.
• In the Ignite toaster, click Accept, select the call in the List pane and, in the Action
bar, click Reply.
To answer a call
• In the Ignite toaster, click Accept. Alternatively, select the call or hover over the item
avatar and click Accept.
Alternatively, in the Conversation window, in the bottom toolbar, click the Hang Up button.
• Click Inbox and select a call or hover over the item avatar and click Hang Up.
DESKTOP — You can place a call in Ignite by either searching for a destination or entering the
destination in the dial pad.
Note:
The system supports partial matching on names and numbers. For example, if you type
‘12’, the system returns a list of employees whose IDs start with ‘12’.
3. In the New Call window, to the right of the destination, click the phone button to place
the call. Note that the phone icon is disabled if the contact is an agent who is in DND.
If the destination is available, the system places the call. The call is transferred to your Inbox
and your desk phone rings. Answering the call connects you to the destination.
If the call fails, a failure message displays in the New Call window.
1. Click Contacts.
2. If the destination is not a recent contact, type its name or number in the Search field.
Note:
You can also create external contacts or import contacts from the Contacts page. For
more details, see "Contacts (WEB)" in this document.
3. Hover over the destination’s avatar and click Call. If applicable, hover over multiple
Call avatars to select the appropriate dialable number. For calls to agents, a colored
dot on the avatar indicates its availability.
Note:
If Contacts is open, click Contacts again to close the window and expose the desired
controls.
Optionally, you can also make a call using the New Call button (Phone icon). You can choose
the name and number that should be displayed on the external phone when making a call to an
external destination.
Note:
The outbound CLIP numbers are populated from the DNIS device list in YourSite Explorer.
3. Select the number from the list. The customer sees the selected name and number on
their display when they are contacted.
Note:
For SIP Platform, Mitel Interaction Recording is supported only for MiVoice 5000 and MX-
ONE PBXs only.
To ensure customer confidentiality or to create a record of volatile or sensitive calls, you can start
or stop the call recording. This functionality is supported only for Mitel Interaction Recorder when
using Web Ignite.
By default, the call is recorded for all the incoming and outgoing calls in web ignite.
Note:
The Contact Center Client does not have this functionality when using Mitel
Interaction Recording.
Note:
• Click Inbox and select a call, or hover over the item avatar, and click Hold.
• Click Inbox and select a call, or hover over the item avatar, and click Hold.
• Click Inbox and select a call or hover over the item avatar and click Remove Hold.
• You can apply multiple Classification Codes, and this can be done at any point during
the (call or interaction) or its Work Timer. All Classification Codes applied to a call
are pegged with the full call duration, from the time the call arrives until the call ends.
This includes transfer time. It also includes Work Timer duration if 'Include queue work
timer as part of handling time' is enabled on the queue. If the same code is entered
twice, it is not double pegged in reporting statistics.
• Classification Codes can be ‘forced’, meaning the agent must enter a Classification
Code either during the call or when in Work Timer to remain within compliance.
• Account Codes can be entered only during a call, but Classification Codes can
be entered during or after a call (while in Work Timer). There are often scenarios
within which you set single or multiple Account Codes during a call and then set a
Classification Code when the call terminates.
Note:
Classification Codes are supported only for ACD voice (calls or interactions).
Note:
During a call, apply Classification Codes as you would Account Codes, using the list of
Account Codes in the ‘Set Account Code’ rolling panel in the Sidebar or in the 'History and
Account Code' section of the Preview pane.
1. In the Sidebar, click the Classify button to open the Classify rolling panel.
When the call ends, the Classify button displays (and flashes if forced Classification Codes
are enabled) and Work Timer is activated.
2. Select the applicable Classification Code from the list that displays and click Apply.
Note:
If you are handling more than one item in the Inbox, for example, one email and one call,
and you apply a Classification Code during the call, it will be applied to the call regardless
of which item is currently selected in the Inbox. If you apply a Classification Code after the
call when in Work Timer, the voice interaction stays in your Inbox and you must use the
‘Classify’ button in the Sidebar to apply a Classification Code to the voice interaction.
3. If Work Timer has not been configured to automatically cancel after entering a
Classification Code, cancel Work Timer by clicking the Remove Work Timer button in
the Sidebar.
Note:
Forced Classification Codes prevent canceling Work Timer until a Code is entered. Failing
to enter a Classification Code before Work Timer expires or is removed by entering Busy/
Make Busy or DND can result in a default Classification Code of ‘-1 Non-Compliant’
applied automatically.
Note:
During a call, apply Classification Codes as you would Account Codes, but select
‘Classification’ in the Classify dialog window.
Note:
If you enter a number in the search field, you can apply the Code by pressing ‘Enter’ when
prompted.
receiving calls concerning account renewals can transfer these calls internally to the Sales
queue, or agents can transfer calls externally to a supervisor’s cell phone.
To receive transfers devices must be enabled to handle the interaction's media type.
Agents who are logged out, in DND, Offline (WEB), or whose presence is Unknown cannot
receive transferred calls, but the call can be transferred to their voicemail. Agents who are either
in Busy/Make Busy or at their call Workload limit can receive transferred calls.
Call transfers in Ignite are always blind transfers. In blind transfers, there is no communication
with transfer destinations before sending calls. Calls are transferred immediately, and the system
does not monitor the outcome.
To perform a supervised transfer, you must use MiCollab Client, Contact Center Softphone,
Contact Center PhoneSet Manager or Ignite Web. See the MiContact Center Business User Guide
for more information.
Note:
• You cannot transfer calls on hold. Hold must be removed before the call can be
transferred.
• You may transfer interactions only if you have the appropriate permissions.
Note:
This option is available only with Click to Call. For more information, see "Contacting
agents before transferring calls".
Note:
This option is available only with Click to Call. For more information, see
"Contacting agents before transferring calls".
Note:
Invalid entries return an error message. Re-type a valid entry and click ‘Transfer’.
3. Click Transfer.
1. Click Inbox and select a call or hover over the item avatar and click Accept.
2. Select the call or hover over the item avatar and click Transfer.
Transfer window lists all the numbers from available queues, employees, external, or Active
Directory contacts.
3. To select a contact to transfer the call, hover over the contact. This enables the Blind
Transfer and Consultation Call buttons.
4. Hover over the Blind Transfer button to list the dialable numbers associated with the
contact.
• If the contact has only one associated dialable number, you can select the dialable
number or click on the transfer button to transfer the call.
• If the contact has more than one dialable number, select a dialable number to
transfer the call.
The call is now ringing the other party and you are disconnected. The conversation will stay in
your inbox if a Work Timer applies to it.
1. Click Inbox and select a call or hover over the item avatar and click Accept.
2. Select the call or hover over the item avatar and click Transfer.
Transfer window lists all the numbers from available queues, employees, external, or Active
Directory contacts.
3. To select a contact to transfer the call, hover over the contact. This enables the Blind
Transfer and Consultation Call buttons.
4. Hover over the Consultation Call button to list the dialable numbers associated with
the contact.
• If the contact has only one associated dialable number, you can select the dialable
number or click on the Consultation Call button to transfer the call.
• If the contact has more than one dialable number, select a dialable number to
transfer the call.
The call now is ringing the other party and the caller is placed on hold.
5. Before the other party accepts the transfer, you can do the following:
• Click Cancel Transfer to cancel the call with the other party whom you consulted
and connect back to the caller.
• Click Complete Transfer to complete the transfer.
6. After the other party accepts the transfer, you can do one of the following:
• Click Cancel Transfer to cancel the call with the other party whom you consulted
and connect back to the caller.
• Click Complete Transfer to complete the transfer.
• Click Conference to connect the three parties together.
• Click Swap to swap the hold. (Applicable to MiVB only).
• Click Hold to put both parties on hold. (Applicable to SIP only).
• Click RemoveHold to remove hold. (Applicable to SIP only).
After you leave the call, the conversation will stay in your inbox if a Work Timer applies to it.
While you are on a call with a customer, you can invite other parties into the call to create a
conference. You cannot transfer a call that is in a conference. You can hang up to leave the
conference or put the call on hold, muting the person who puts it on hold, and keeps them from
hearing the conference. Other parties in the conference can also invite others to the conference.
You can initiate a conference through a supervised transfer. See the “Transfer calls” section for
details.
1. When on a call, in the Conversation window, click the Invite More People button
2. Type the name or number of the participant you want to invite.
3. Select a participant and click the Invite button.
The system calls the specified participant. When the participant answers, they are added to
the call.
4. To invite additional participants, repeat the above steps.
1. While on a call, click the Invite button. The Invite window opens.
2. In the Invite window, you can search and filter to find the required contacts from the
available queues, employees, or external or Active Directory contacts.
3. Click the avatar. You can include up to five parties in a conference call.
The first agent who answered the call will be in ACD state during the conference and if the call
was transferred to another agent, the second agent will be in Non ACD state. You can view all
the participants of the conference under the Participants list in Ignite.
See the "Transitioning from one conversation type to another (WEB)" section in this guide.
Employees who accept requests for help join the call in Silent Monitor mode and are not audible
unless they escalate to Coach or Barge.
The Request Help button is available as soon as a call is delivered to your Inbox. You can send
multiple requests for help during a call, but you can send only one request at a time. Requests
sent to employees in unavailable states fail.
Ignite displays a list of voice-enabled employees and enables you to look up contacts in the
Active Directory (AD)
2. In the Request Help window, do one of the following:
Note:
You cannot cancel requests in progress. The Request Help button is disabled (turns gray)
while the call is being established. Hover over the button with your mouse to view the
connection status in a tool tip.
• If the request is answered within 180 seconds, notification that the request help is
established is displayed, and the Request Help icon is displayed next to the caller's
icon and on the Inbox item. The Request Help Call Control button is no longer
available until the employee that answered the Request Help call hangs up.
• If the request is declined or times out, a notification that the request help was
declined is displayed. The Request Help Call Control button is available, and the
employee can make a new Request Help call.
Note:
• If the request is answered within 180 seconds, a notification that the request
help is established is displayed, the Request Help icon is displayed next to
the caller's icon and on the Inbox item. The Request Help icon is no longer
available till the employee that answered the Request Help call hangs up
• If the request for help is not answered within 180 seconds, the request times out
and you can make another request for help.
Note:
The length of time a request help call rings for is defined in the Ignite configuration. By
default, duration is set to 180. See the KB article SO3146 in Mitel Knowledge Management
System for information on how to change this, and how it interacts with the Agent COS.
DESKTOP - The Click to Call option is not displayed when agents are in Do Not Disturb or
absent from their agent groups.
Note:
• If an agent has multiple voice agents, Ignite provides call control for the number
associated with the currently active voice agent
• DESKTOP - Click to IM does not support group IM sessions.
Note:
The recipient's presence displays, advising of their availability to receive your call or
instant message.
1. Click Contacts.
2. If the destination is not a recent contact, type its name or number in the Search field.
3. Hover over the destination’s avatar and click Call.
For procedures on specific call handling actions supported in the Active Call window, see the
appropriate sections of this guide.
For procedures on using Contacts to reach another person, see the appropriate sections of this
guide.
The agent will get similar notification for the incoming chat as in the legacy chat. If the agent
accepts the incoming chat, both agent and customer will see a system message that the agent
has joined.
Note:
• Agents are not allowed to use Desktop Ignite, if Contact Center Messenger is
configured.
• Administrator must enable Contact Center Messenger for the agent to accept
incoming chats.
As with any normal chat, an agent or supervisors can transfer chats from the Web Ignite and from
the Interaction Visual Queue.
With Contact Center Messenger, spell checks are done using the built in spell checker in the
browser. Most internet browsers have spell-checking enabled by default. You will know it is
turned on when misspelled words you are typing have a red line below them, to show they are
incorrect like the two words below.
After you join a chat session, Ignite goes into Reply mode and the Input pane appears, enabling
you to chat with the customer.
The following figure presents the Input pane during a Contact Center Messenger Chat session.
Ignite indicates to agents and customers that the other is typing a response. Ignite indicates that
customers have sent a response in an active chat as follows:
• WEB - When Ignite is not in focus, a notification indicates that the customer has
entered a response. When Ignite is in focus but the active chat is not selected, an
exclamation mark displays beside the interaction and a notification displays. Clicking a
notification takes you to the relevant interaction.
To chat (WEB)
• Type a message in the input pane text box and press Enter.
• If agents are configured to use Contact Center Messenger for chat, then the agents
will not be able to log in to desktop Ignite. If they try to connect to desktop Ignite, an
error message will be displayed recommending them to use Web Ignite.
• If the agent accepts the incoming chat, both agent and customer will see a system
message that the agent has joined.
Note:
1. To create new templates, go to Tools > Chat Personal reply template editor.
2. Enter the reply content in the text box and click Save.
3. If you want to use an existing template to create a new template, then click Insert
reply template.
4. Choose the existing template that you would like to use, the content will appear in the
editor, you can make the required changes and click Save.
5. To edit or delete an existing template, click Browse and choose the template you want
to edit or delete from the list of templates.
You can accept a chat and click icon to insert a reply template to the chat window.
• You can toggle Use reply template button to use the last reply template to the new
chat; otherwise the agent can select a template form the Reply Templates list.
• The Chat reply template is inserted into the chat dialogue line. Agents can preview the
message before sending the conversation.
The Chat UI component is replaced with the entire chat transcript during worktimer or after you
end or transfer a chat.
The system displays the default suggestions for the customer conversation. However, you can
also change it for show agent messages to be displayed.
•
Click the message icon to navigate the message in the interaction pane and to
view a list of suggestions.
• The time stamp for each suggestion that you received from Google Agent Assist is
displayed.
• The message from the conversation for which the suggestion given is also displayed.
•
Click the button, by clicking which you can expand the relevant Frequently Asked
Questions and Articles.
• Articles:
• You can have multiple articles as suggestions; the total number of articles is
displayed at the top.
• Articles are arranged based on the priority of recommendation; the most
recommended article appears first.
•
Click buttons to views next or previous suggestions. Click buttons to
navigate to the first and last suggestions.
• The articles displayed will contain a title and a snippet. If there is no title, then the
system displays only the snippet.
• Click the Send Snippet icon to send the snippet as a message in the conversation.
•
Click the icon to send the pdf link of that article as a message in the
conversation.
•
Click the icon to open an article in a new browser tab, which can be used to
view the full article.
•
Click the icon to provide feedback for the article suggestion. The system
displays the following options:
• Correct
• Partially
• Wrong
Feedback helps to refine the suggestions, if the context of the conversation is similar.
• FAQs:
• You can have multiple FAQs as suggestions; the total number of FAQs are
displayed at the top.
• FAQs are arranged based on the priority of recommendation; the most
recommended FAQ appears first.
•
Click buttons to views next or previous suggestions. Click buttons to
navigate to the first and last suggestions.
• The FAQs have answers listed. Click the Send Answer button to send the answer
as a message in the conversation.
•
Click the icon to provide feedback for an FAQ suggestion. The system
displays the following options:
• Correct
• Partially
• Wrong
Feedback helps to refine the suggestions, if the context of the conversation is similar.
Note:
If there are more than 50 suggestions for a conversation, when you close the
conversation or refresh the browser, by default the system displays the last 50
suggestions with the recent suggestions towards the bottom.
This feature is available as the Suggestions drop-down menu in Web Ignite. A text box for
manual search is also available.
Note:
By default, the Smart Suggestions feature is enabled in YSE for a customer. An
administrator can disable the Smart Suggestions feature in YSE > Enterprise >
Smart Suggestions and select the Enable Smart Suggestions check box for
customers who do not want to use it.
An administrator can enable or disable Smart Suggestions for particular Agents and Supervisors.
To do this, go to YSE > Security Roles, and select a security role. Select the Ignite tab, and
toggle May See Suggestions, to enable and to disable the feature. This option is set to ON by
default.
Note:
If an administrator sets the Enable Smart Suggestions option in YSE to ON
and sets the May see suggestions option to OFF or vice versa for an Agent or
Supervisor, the Web Ignite UI for Smart Suggestions does not appear for that Agent
or Supervisor. Agent and Supervisor must log out and log in if the UI elements were
already loaded on the browser.
An agent or supervisor can also add a user note in a Case, or a supervisor can create a Global
Reply Template. For more information on Global Reply Templates, see Global Reply Template
section.
suggestion, the Supervisor can click the dislike icon to remove that suggestion from the list
of suggestions.
• Click Like or Insert Response (when available) for suggested responses presented in
the Web Ignite Inbox or Queues sections.
• Find corresponding responses in the Web Ignite History or Cases sections and Click
the Like button. In addition to text-based search, users can use the Advanced Search
feature to find responses based on the number of likes or reuses, disliked responses,
or responses having warnings.
Popular responses get a minor score boost when they are suggested.
numbers, carrier tracking numbers, email addresses, and Social Security Numbers are masked
from suggested responses.
The system reminds the Agent that there could be sensitive data in a suggestion and that the
Agent must check before proceeding to present it as a response. The following disclaimer is
displayed for every suggested response:
Warning:
• Like: Agents and Supervisors can like an interaction or case in the inbox suggestion
response window, history, or in the case it is associated with. If they click the like icon
for a suggestion, the score of the suggestion will receive a minor boost, which will
increase the popularity of the suggestion.
• Warning: Agents can mark a warning for a suggestion. If they do so, a Supervisor can
see the warning and take the necessary action for that suggestion. If the warning can
be ignored, Supervisors can remove it by pressing the "x" button on it.
Note:
• The other agents will see these warnings too and they cannot use the
suggestions that contain warnings. If you ignore a warning associated with a
suggestion and decide to reuse the suggested response anyway, Web Ignite
displays a message to confirm the decision so that warning is considered.
• Warning reasons are configured in YourSite Explorer by the Administrator. To
add Warning reasons, an Administrator must go to YSE > Enterprise > Smart
Suggestions and click Managing Warning reasons. Administrator will see a
list of preconfigured warning reasons, the list includes Ambiguous, Contains
Sensitive data, Contains typos, Incorrect, Obsolete by default.
To add new warning, click Add and enter the new warning reason and click Save.
To edit a warning, select a warning reason and click Edit; update the warning and click
Save.
• Dislike: Only a Supervisor can dislike a response. The response is then not presented
in any list of suggestions.
1. Select an interaction from the inbox or from the queue. The system searches the
content of email, chat and SMS interactions, and on finding a match for the text
entered by the customer, lists a set of suggestions.
For any media the Agent can search multimedia interactions, case user notes, and reply
templates by entering relevant text in the Suggestions text box displayed.
2.
Select a suggestion and click the See Response icon to view the suggested
response.
3. Select the Response to use the suggested response and click Insert response. This
will insert the selected suggestion as your response to the interaction you opened.
Note:
The Response check box is suggested only for chat, SMS, and notes and not for
email or templates. If you edit the response, the check box is automatically selected.
For presenting an email response, click View entire thread link to view the entire email
thread and use the response inline.
3. Click Add and enter the terms (words or phrases) that you want to add.
When an open media item is routed to the desktop and accepted by an agent, depending on the
settings for the variables used for the API request (TargetUri and TargetUriEmbedded), one of the
following occurs:
Note:
• Agents cannot pick or pick and reply to interactions from the queue if they are in
Do Not Disturb.
• Agents may only pick or pick and reply to interactions from the queue if they have
the appropriate permissions.
• Pick an open media interaction out of queue and handle the open media interaction
• Pick and automatically reply to an open media interaction
To pick an open media interaction out of queue and handle the open media interaction
• Click Inbox and select an open media interaction or hover over the item avatar and
click Accept.
To receive transfers, devices must be enabled to handle the interaction’s media type. Agents
who are logged out, in DND, Offline (WEB), or whose presence is unknown cannot receive
transferred open media interactions. Agents who are either in Busy/Make Busy or at their open
media Workload limit can receive transferred open media interactions.
Note:
You may transfer interactions only if you have the appropriate permissions.
1. Click Inbox and select an open media interaction or hover over the item avatar and
click Accept.
To transfer from the Cases page, under Interactions tab, select the inqueue chat and click
Goto icon. The Queues page is displayed. You can now transfer the chat from the Queues
page.
2. Select the open media interaction or hover over the item avatar and click Transfer
icon.
Note:
Optionally you can select multiple interactions from the Inbox or the Queues page and
click Transfer. The Transfer window is displayed. The list of available Employees and
Queues are displayed in the Results section.
To search queues, type the name of the queue in the Search field.
5. To transfer the open media interaction, select the name of the appropriate person or
queue.
Note:
When an agent declines an interaction, they are automatically put into Busy/Make Busy
across all media capabilities. A System Make Busy and a requeue count is registered for the
employee. For more information, see "Setting and removing Busy/Make Busy in Ignite".
• Click Inbox and select an open media interaction or hover over the item avatar and
click Decline.
Agents can also junk open media interactions directly from 'Failed', rather than attempting to
reroute them.
Marking interactions as No Reply and Junk removes the interactions from Ignite. If the item is in
queue or the Inbox, responses in progress are deleted.
Note:
• Click Inbox and select an open media interaction or hover over the item avatar and
click either No Reply or Junk.
Note that administrative configurations may limit how long interactions may be on hold before
being requeued and a System Make Busy is registered for the employee. For information on this
limit, contact your supervisor or system administrator.
• Click Inbox and select an open media interaction, or hover over the item avatar, and
click Hold.
• Click Inbox and select an open media interaction on hold or hover over the item
avatar and click Remove Hold.
Note:
The Silent Monitoring option in the flyout menu will be visible if both the
supervisor and agent's voice agents are logged in.
• Select Silent Monitor from the flyout menu that appears while the Supervisor is
hovering over the voice agent's avatar. The Supervisor can see an Outbound call to
the agent in their inbox.
• When the silent monitored agent goes off hook, then the badge will display "MONITORING".
An agent can be silent monitored if they are in the idle, ACD, Non ACD or Outbound state
• Select Silent Monitor from the flyout menu that appears while the Supervisor is
hovering over the Employee Avatar.
The Supervisor can see an Outbound call to the agent in their inbox, if the silent monitor is set
successfully. The inbox item shows a blue badge displaying "MONITORING" along with the
Silent Monitor icon.
Once the silent monitoring is initiated, the Silent Monitoring button is no longer available when
hovering over the agent's avatar. Now, the next available monitoring level (Coach) is available.
Similarly, once Coach is enabled, the next available monitoring (Barge) level is available. The
color of the badge will change to yellow and the supervisor can now end the silent monitoring by
hanging up the outbound call.
Silent Monitoring level in Web Ignite can be escalated from Employee State Dashboard, Agent
State Dashboard or Inbox conversation.
1. When the Silent Monitor is active on an Employee, and they are in ACD, hovering over
the Employee's avatar displays a Coaching ON flyout button
2. Clicking the Coaching ON button escalates the Silent Monitor to Coaching. The
Employee avatar should now display a lighter blue badge that says COACH ON as
well as the Coaching icon.
3. While the Employee is being coached, hovering over the employee's avatar shows a
Barge ON flyout button.
4. Clicking the Barge ON button escalates the Silent Monitor to Barge. The Employee avatar will
now display a yellow badge that says BARGE ON as well as the Barge icon.
1. When Silent Monitor is active on an Employee, and they are in ACD, hovering over the
Agent's avatar shows a "Coach" flyout button
2. Clicking the "Coach" button escalates the Silent Monitor to Coaching. The Agent
avatar should now display a badge that says "Coaching ON"
3. While the Agent is being coached, hovering over the agent's avatar shows a Barge
ON flyout button.
4. Clicking the Barge ON button escalates the Silent Monitor to Barge. The Agent avatar will now
display a yellow badge that says BARGE ON as well as the Barge icon.
Inbox
1. Hovering over a silent monitored call in the inbox, or in the call details header will
show a "Coaching ON" button.