<translate>= Email Tab for Services & Campaigns =
The fields, values, and options for the Email tab in Services & Campaigns are described in this document.
Acknowledgement
Acknowledgment is the message sent as an immediate response to inbound emails associated with a service to acknowledge receipt of a request and advise the sender about the estimated reply time.
|
Acknowledgment isn't considered a reply and doesn't affect metrics related to this service. It is only sent for the initial email in an email thread. | |
Acknowledgments must initially be prepared as articles in the Knowledge Base.
Select an article to use as acknowledgment for the given service by clicking the link, entering article keywords in the search field, and choosing the language. Matching articles will be listed. Select the desired article to display it in the preview field.
Acknowledgment can be defined in one language only in the current product version.
Distribution method
Distribution method is the method of email delivery to the Agent Desktop.
Use the pull method to keep incoming emails in the service queue. Emails will be visible to the agents of the teams assigned this service. Agents select emails to process from this queue.
Use the push method to send incoming emails to the Agent Desktop, just like calls and chats. Agents accept incoming emails for immediate processing or move emails to My Queue for later processing. For information about agents' availability to process email interactions, see section Omni-Channel Routing.
The order in which incoming emails are delivered is determined first by priority and then by the shortest remaining time to breach the configured service level. (See the description of the Service Level settings below.) For more information about email priority, see section Scenario Entries - Email.
|
|
When emails are delivered to agents (push) or appear in the service queue (pull), they are sorted by priority and then by the shortest remaining time to breach the configured service level. For more information about email priority, see section Scenario Entries - Email. | |
Enable personal routing
Enable personal routing indicates whether personal email routing is enabled for this service.
If enabled, the system attempts to deliver any email identified as part of an existing email thread to the agent who sent the previous reply within that thread.
Personal routing timeout
If personal routing is enabled and the Distribution method is push, Personal routing timeout specifies how long the system waits in minutes, hours, or days, for the agent who sent the previous reply to become available before distributing the email to qualified agents via push.
|
|
Values set in minutes may be rounded to the nearest upper multiple of five. | |
This timeout applies to the push method. For the pull method, such emails are immediately delivered to the agent’s My Queue.
- Personal Queue Management
' specifies how long the system will wait (from the moment the email is placed in an agent’s My Queue) before returning this email to the general service queue.
Select "return emails to general queue if SLA is breached" to return such messages back to the general queue, even if the emails is put in the agent's My queue after the SLA is breached.
- SLA is breached
- This setting indicates whether emails that have breached service level while in My Queues will be returned to the general service queue. See the description of the following Service Level settings.
- Service Level Target
This setting controls the parameters of response service level.
- Replied emails
- This setting specifies the percentage of emails associated with this service that are expected to be replied within the specified service level threshold (see below) relative to all replied emails.
- Within threshold
- Service level, Within threshold sets the service level threshold for this service. A service level threshold is the amount of time in which emails associated with this service are expected to get a reply. The reply time is measured from the moment the email is placed in the service queue to the moment when the first reply is sent. Acknowledgement (see above) is not considered a reply. Please note that when an email is moved from one service queue to another, it's time in queue will now apply against the new service's threshold, and may instantly breach it.
The email service level threshold can be specified either in hours or in days. Either case excludes the time that is outside of the hours of operation specified for the given service.
- Screenpop
- Label
- Enter the name of the tab in which the screen pop content will appear in this field.
- Open in popup window
- Use this box to indicate whether screen pop should appear in the Context Information Area of the Agent Desktop application (default) or in a separate window.
- Keep open when interaction is finished
- Selected this option to keep the pop-out browser tab open when an interaction is finished. This option is not available for selection unless Open in popup window is selected.
- URL of the page to open
- Enter the URL of the web page that will be displayed by the Agent Desktop application when the agent receives an email associated with the given service . A query string can be added to supply variables for the screen pop.
The following variables are supported:
- $(item. From)
- sender’s email address
- $(item.to)
- emails address in the To: field
- $(item. Subject)
- content of email subject
- Additional URLs
- Click add to specify URLs for additional (optional) web pages to be opened. A separate label can be specified for each additional screen pop tab. The labels are used as page or tab titles.
</translate>