How do I configure the outgoing email settings (SMTP server configuration)?
To set up outgoing emails, you must configure Bold360 AI ticket email replies to go through your SMTP server
To set up outgoing emails, you must configure Bold360 AI ticket email replies to go through your SMTP server
See How do I configure the outgoing email settings (SMTP server configuration)? to set up outgoing emails.
Emails in Bold360 AI are handled through the ticketing system. Therefore, you must first create a new ticket:
You can associate your support e-mail address with the Bold360 AI ticketing system.
To answer an open ticket, do the following:
You can set up automatic replies to your customers' emails. This is useful when you want to confirm that you have received an email.
Setting up the Digital DX AI ticketing system with your SMTP server is part of your initial configuration and setup process. The Digital DX AI ticketing system is the default ticketing system available to you, offering the ease of out-of-the-box technology, and automatically connecting to your knowledge base. The system also enables agents to leverage the Digital DX AI knowledge base, meaning that they can provide full and accurate answers to customers in a speedy, efficient and timely manner.
There are three steps involved in setting up your ticketing system to function correctly and work in the most efficient manner possible:
Once you have your Digital DX AI account, the first step in setting up your ticketing system is to configure your SMTP server to forward incoming customer support emails to the Digital DX AI ticketing system.
Sending Ticketing to Specific Departments
You can further hone the scope of how customer support tickets are handled, by creating email ticketing specific to an internal department of the company, such as Sales, Marketing, IT Support or Billing.
The next step is to specify how outgoing customer support mail is handled, by configuring your SMTP server for outgoing mail.
Digital DX AI then performs a verification of the entered SMTP settings to check that the SMTP server can function. The settings will only be saved once the verification has determined that they are correct. The verification may take a few minutes.
If the verification fails, a message is displayed, with an explanation as to why the SMTP settings were not saved.
You can further subdivide labels into groups to easily manage which agent handles what kind of ticket. User groups help differentiate between agents and their responsibilities, by enabling permissions to a group that determines which tickets can be assigned to members of that group. To create a group, do the following:
Digital DX AI supports all e-mail forwarding integrations, which can be used across CRM and ticketing systems such as Salesforce, Kayako, or Zendesk.
Digital DX AI supports two e-mail forwarding modes:
The email forwarding integration can be set under: Admin Center > Ticketing Settings > Ticketing Basics tab and then select 3rd party integration.
You can use the Digital DX AI ticketing system to process customer escalations.
You can access the ticketing system of Digital DX AI by selecting Ticketing from the menu on the left.
Once you open it, you have the option to view:
Open tickets is the main interface for the ticketing system. When a customer escalates a question to an agent, it is displayed in Open Tickets. This category contains the following:
With the ticketing system, you can:
In some cases, such as holidays and national holidays, it is important to add exclude dates to your SLA business hours.
You can use the Bold360 AI Ticket Export API to download ticket data to XML or CSV format.
https://my.Nanorep.com/common/api/ticketexport.xml?account=ACCOUNTNAME&apiKey=APIKEY&kb=KB&label=labelid&month=7&year=2013&includeText=true&closeOverdue=true&format=xml
Name | Description |
---|---|
username | The username used to log into my.Nanorep.com (user account requires KB manager or admin permission). |
password | The password used to log into my.Nanorep.com (user account requires KB manager or admin permission). |
kb | The target Knowledge Base. |
label | The label ID when you want to export tickets from a specific label. |
month | The target month, for example 7. |
year | The target year, for example 2013. |
includeText | Set to true to include the ticket correspondence. |
closeOverdue |
|
format | Format should be set to one of the following:
|
The returned data will include the list of tickets, and each ticket will include the following information:
To view and work on the data in Excel, please follow the steps below:
When setting up your ticketing system, you can configure your tickets and other outgoing system-based emails to display a signature. Signatures can be configured for emails sent from each of your Knowledge Bases. Bold360 AI has several out-of-the-box basic signatures and you can also add new personalized signatures.
To Create an Email Signature, do the following:
To enter an image, ensure that you have your image saved to a proprietary URL. Click the image icon and enter the URL in the dialog displayed. To enter a tagline, select and replace the generic text.
Optionally, use the following placeholders:
You can create an HTML form and submit it as a ticket to your Bold360 AI inbox.
Your Bold360 AI inbox will receive a ticket, containing all the fields that are part of the submitted form.
Below is an example of an HTML form that submits a ticket to the Bold360 AI inbox:
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Create ticket API (Custom Contact-Form)</title>
</head>
<body>
<form action="https://my.Nanorep.com/common/api/createTicket" method="post" enctype="multipart/form-data">
Subject: <input type='text' name='subject' value='This is the title of the ticket'
/><br />
Body: <textarea name="body">This is the body of the ticket</textarea><br />
Email: <input type='text' name='email' value='test@company.com' /><br />
Name: <input type='text' name='name' value='johnny' /><br /> <!-- name custom field. You can create as many fields as you like. -->
Phone: <input type='text' name='phone' value='123456' /><br /> <!-- phone custom field. You can create as many fields as you like. -->
Label: <select name='labelId'> <!-- label selection by the dropdown selection-->
<option value='-1'>Select the inquiry type:</option>
<option value='12F1BE'>Billing</option> <!-- The value of the label (Label ID) can be obtained in the Bold360 ai inbox. -->
<option value='78907B'>Support</option>
<option value='103C8C'>General</option>
<option value='9E0A'>Sales</option>
</select><br />
<div id='textD'></div> <input type="hidden" name='account' value='Nanorep' /> <!-- Enter your Bold360 ai account name --> <input type="hidden" name='kb' value='8CB9462F7AB2120' /> <!-- The target knowledge-base / inbox --> <input type="hidden" name='security_token' value='8CB9462F7AB2120' /> <!-- Please do not modify --> <input type="hidden" name='success_redirection_url' value="/common/api/nonProtocolCreateTicketResponse.html" /> <!-- success url redirection -->
<input type="submit" value="submit"/>
</form>
</body>
The HTML form should meet the following requirements:
The ticket will be available in the Bold360 AI inbox and will include all the fields, which will be displayed under the ticket Details section.
For example:In our last example ; For the Support group, we already selected the ticketing permission "View and take selected labels". Because we chose one of our 'take' options, the lables' table opens to choose labels. In our case, we chose only one label: the "Support" label. We chose it since we want all tickets labeled as "Support" to be viewed and taken by Dan, Roy and David, our support agents. We still need to set the ticket assignments abilities. This can be done once the group is created and we associated our agents, Dan, Roy and David with the "Support" group. These steps will be described next.
The email forwarding integration can be set as follows:
You may want your customer to fill in a contact form, and essentially create a ticket in the Bold360 AI platform. In this case, you can turn the contact form into a conversation so that only one question (field) is presented at a time.
To set up a conversational form, do the following:
Contact forms that customers filled in are listed in Bold360 AI under Ticketing > Open Tickets.
Tickets have two statuses: open and close. You can set a ticket status when an agent replies to a ticket as follows:
When you add the new label to a ticket, the ticket will be set according to the label class status.
You can either use the existing Bold360 AI ticketing system for escalation of customer service calls or, if you already have an existing ticketing / CRM system, you can forward your Bold360 AI tickets.
Zendesk's ticketing system can serve as an escalation channel by sending tickets to the publishing center of Bold360 AI.
To integrate Zendesk with Bold360 AI, do the following:
Once the trigger is created, the suggestion feature is available.
A draft is automatically created in the Bold360 AI publishing center if the agent selects the Suggest my answer option when sending the response.
To view the full ticket correspondence on each ticket, a variable to the signature must be added as follows:
The ticket's history will now include each reply sent to the customer .
Actions are the main issue. Without an action, the rule has no meaning because the rule addresses the action and determines the conditions under which the action occurs automatically. The actions you can set in a rule are:
You can set a rule to automatically label tickets with a certain title (keyword) to a certain label. You first need to create the label (tag) to use.
Once you have labels, you can use the rule.
For SMTP server configuration, do the following:
Refer to Microsoft's instructions here.
To un-label questions, follow the same steps and click on the "Clear labels" link. W hen inside an answer, click the Label button and clear the label.
See also How can I search by a label?
You can set a rule to send auto replies to all tickets created in the inbox.
Rules automate how your tickets behave.
You can set a rule to automatically label tickets created in the inbox. You can use it to label tickets from a certain URL or using a key word.
For example: Suppose we set a rule to label (action="Add label") tickets from our pricing page URL as "Sales"
You can set a rule to automatically close tickets created in the inbox. You can use it to close spam tickets in advance or any other unnecessary tickets you can predict by keywords, contact form fields, URL from which the ticket was sent, and so on.
For example:Suppose we set a rule to close tickets (action="Change ticket status - Closed") that contain the word "test" in the body or title, so internal tickets we use will automatically be closed.
Add the action "Apply default signature" to the rule, and select the signature of your choosing from the drop down menu to apply a specific signature to a ticket.
When a user opens the ticket to write a response, the specified signature is automatically selected for that user.
If you want the ticket answered by a non-agent, you can forward it by email by clicking the 'Forward button' and fill in the email address.
Once this person answers the question, the answer is added to the 'Publish answers' section in the 'Publish' where it can be uploaded to the online knowledge base (or edited and then uploaded).
Rules location is there to prioritize the system rule checking in the trigger. Once a trigger starts, such as 'a ticket is created in the inbox', the system checks for rules in the trigger.
When just one rule applies for the ticket, tickets' location is irrelevant.
For example: Suppose you have a rule that determines when a ticket's title or body contains "support", it is assigned to "Support" and when a ticket's title or body contains "new" it is assigned to "New". If no tickets contain both "Support" and "New" there's no problem, each is assigned to its respective assignee.
But sometimes, more than one rule applies.
The rules are processed in order. Once a rule is successful, the system executes the actions defined in the rule and then continues checking for and running other rules that also apply. For example: Suppose you have a rule that determines that all tickets are assigned to "Support" (you decided not to use any condition) and a rule that determines when a ticket's title or body contains "new" it is assigned to "New". A ticket that contains "new" is assigned to both "Support" and "New".
When more than one rule applies, the decision which rules to execute is made by 2 variables: the 'Continue processing rules / Stop processing rules' drop-down in the rule itself and the location of the rule in the trigger.
If it weren't for the 'Stop processing rules' option inside the rule, rules' location would still have no meaning. BUT, the option does exist. At the bottom of each rule, there's a drop-down list with 2 choices: either you choose 'Continue processing rules' or 'Stop processing rules'. Choosing to 'stop' means that once the current rule applies for the ticket, the system will stop checking if lower located rules apply for the ticket as well (but higher located rules will be counted). Choosing the 'Continue' option means the system will continue checking for lower located rules.
For example:
Let's go back to our last example; what happens with a ticket that contains both "support" and "new"? The "Support" rule comes first, and then the "New " rule.
If we choose to "Continue" in the 'Support' rule, then the ticket is assigned to both "Support" and "New" (because we continued the check to the next rule that applies, the "New" rule). If we choose the 'Stop' option, the ticket will only be assigned to "Support" (because we stopped checking after executing the rule). If it would have been the other way around and the "New" rule would have been first, then the ticket would have been assigned only to "New" - That is why rules numbers within a trigger has significant meaning.
The rule location in the trigger should be defined in order of importance.
If the rules before a given rule have no relations to it (so there is no chance that a trigger might trigger it as well), or you don't mind that those rules will also be executed, then the decision is easy: just number it however you like.
However, if you want a rule to be executed alone, with no other rules in the trigger to be also executed, then you must define the rule first and then choose the "stop" option in the bottom drop-down inside the rule.
A rule may have zero or more conditions. Conditions are defined by:
Triggers are repetitive system behaviors, such as the commonly used trigger 'a ticket is created in the inbox', that trigger different actions to assign the ticket that was created to a certain agent, forward it, label it and so on. The triggers available for your use are:
You can create templates for an auto-response email to a ticket. The template is created via the ticketing system's rules, so you can create different templates for different conditions (as per the source email, the ticket title, etc). You can also define different outgoing e-mail settings to different Knowledge Bases.
Result: The Edit Email dialog is displayed.
Bold360 AI allows you to forward tickets from one KB to another KB using a 3rd-party integration.
To export the tickets, do the following:
You can use the Bold360 AI ticketing system to process customer escalations. Customer queries can end up in your Bold360 AI ticketing system in a number of ways:
To see the origin of the ticket, proceed as follows:
Result: You are taken to the ticket's details.
When an agent responds to a ticket, the user who sent the ticket gets an answer e-mail. This is the 'Outgoing e-mail'. For each knowledge base an outgoing email settings need to be created and selected.
For more information, see How do I configure the outgoing email settings (SMTP server configuration)?
Ticket rules are a set of conditions that allow you to automate different actions to occur once a ticket's trigger is activated and, this way, to add your business logic to the ticketing system. It is intended for routing tickets or ticket management purposes.
By providing a variety of triggers, conditions and actions, the Rule Engine allows you to tailor the ticketing system logic to your needs so that you can control labels, assign users, sending auto-responses and alert emails, and so on. Rules are meant to save you the time of doing those actions that follow the trigger repeatedly.
Here are some rules that can be easily added:
Click here to learn more.
Bold360 version 21.10 contains the following new enhancements:
Going forward, there will no longer be an option to choose (non-secure) HTTP-only connections when generating widget touchpoint scripts. HTTPS will be enforced across all touchpoints going forward and HTTP-only widget configurations will no longer be supported as of December 31, 2021. Any widget script using HTTP only will need to be changed by this date in order to continue uninterrupted
Access to the Genesys DX AI management (*.nanorep.co) will only be accessible through HTTPs
In-product announcements will be present to raise awareness of this change
Important: Any widget script using HTTP only will need to be changed by this date in order to continue uninterrupted.
As part of the transformation to Genesys DX, the product interfaces are now rebranded to reflect this change. Logos, product names, and company links are now updated to Genesys branding and is present within each of the product interfaces.
Using the "getEstimatedWaitTime" API call will provide the estimated wait time that the visitor would spend waiting before starting a live chat with an agent.
Details on using this API can be located in this article.
Bold360 version 21.11 contains the following new enhancements:
New KB Launchpad Intent Library for COVID-19/Vaccinations
In order to help businesses with providing just-in-time information related to updates to COVID-19 and vaccination protocols, a new entry in the KB Launchpad is now available with intents that can be used to deploy knowledge to keep your workforce informed of new policies and information that you may need to enforce.
Not familiar with the KB Launchpad? The KB Launchpad contains pre-defined intent libraries to help you add industry and use-case specific questions/intents to your KBs with your own specific responses to help with adding commonly asked questions for newly created KBs.
We will be enabling the KB Launchpad as a default setup option on all accounts shortly but contact your Account or Success Manager to get it enabled early if necessary.
ICO Cookie Compliance
In order to support ICO cookie compliance in regions that require end-user consent for allowing cookies to be set, Genesys DX now complies with this standard by making the tracking and analytics related cookies that are set through the touchpoint and visitor monitoring HTML snippets to be optional.
By default, all cookies will continue to be set upon page load. To restrict these cookies from loading automatically and only upon end-user consent, additional steps will be required on the website that the Genesys DX code is being deployed to.
You can learn more about what this compliance is and how to update your Genesys DX deployment to be compliant by reviewing the details in this article: ICO Cookie Compliance.
Every year, Genesys® orchestrates billions of remarkable customer experiences for organizations in more than 100 countries. Through the power of our cloud, digital and AI technologies, organizations can realize Experience as a Service℠, our vision for empathetic customer experiences at scale. With Genesys, organizations have the power to deliver proactive, predictive, and hyper personalized experiences to deepen their customer connection across every marketing, sales, and service moment on any channel, while also improving employee productivity and engagement. By transforming back-office technology to a modern revenue velocity engine Genesys enables true intimacy at scale to foster customer trust and loyalty.
Copyright © 2022 Genesys. All rights reserved.
Terms of Use | Privacy Policy | Email Subscription | Accessibility Feedback | Cookie Preferences