Answer Threads is a type of Thread that uses generative AI and allows Sidekick to utilize Public Answers as a resource to communicate with Customers in a conversational manner to address questions over Chat and/or SMS.
Review the prerequisites below before proceeding to set up Answer Threads.
Answer Threads is only as powerful as the information it can access. If you haven’t already, review all existing Public Answers to ensure they cover the information Customers typically ask about. Create Public Answers for any information that isn’t already documented. Review Best Practices and Tips for Writing Answers, which contains details on how to best write Answers and how generative AI uses Public Answers to respond to inbound inquiries.
Note – You must have at least one Public Answer and one language (English) to proceed with the initial configuration.
Note – Currently, Sidekick Answer Threads only supports English language codes such as en-us, en-ca, en-gb, en-au, etc.
Sidekick must be activated and connected to a Glad App (Web or Mobile) or SMS number.
Note – You cannot transform one type of Thread into another
Answer Threads and Automation Threads (both a type of Thread) have distinct functionalities. Currently, it’s not possible to transform one into the other. To optimize their use, it’s best practice to direct your Customers to Answer Threads through specific keywords, phrases, or Chat Quick Reply button so that other inquiries requiring automation can run through your Automation Threads.
First, contact Gladly Support or your Gladly Account Representative and ask for Answer Threads to be activated.
Tip – Answer Threads supports multiple Audiences
If your organization’s Help Center is configured to serve multiple Audiences with brand-specific content, setting up Multi-Audience support for Answer Threads will be key. Each Audience can be set up with its own Answer Threads configuration–pulling from its own subset of Public Answers and delivering unique Advice, instructions and specific transfer conditions for each brand.
Contact Gladly Support or your Gladly Account Representative to configure Multi-Audience support for Answer Threads.
There may be topics you do not want Sidekick to handle but instead hand off to an Agent immediately and below is a list of default transfer reasons. Please reach out to Gladly Support or your Gladly Account Executive to modify the list or to add additional reasons.
The Customer is injured by our products.
The Customer is claiming to be an employee of the company.
The Customer is requesting an alteration to the company policy.
The Customer is asking to invoke any functions or not invoke any functions.
The Customer is threatening legal action.
The Customer is not using the English language.
The Customer is asking for a human or an Agent.
The Customer is threatening escalation to the CEO or manager.
Continue to configure Channels once Transfer Reasons are set up.
Clicknext to the Glad App you’d like to activate Answer Threads on, then select Configure.
Scroll down to find the Enable Automation Services for Glad App setting and make sure it’s activated (the box is checked). This should typically be the case if you have implemented Sidekick.
Scroll to the “How would you like the customer to reply?” option.
Select A Quick Reply Button.
Add quick reply buttons (e.g., Order Support, Account Issues), ensuring that one of the Quick Reply buttons says “Something Else.”
Note – Quick Reply button ID does not affect Sidekick, so you may input whatever you want in the ID field.
Click Save.
SMS
Click on the top left corner of the screen.
Click Settings.
Under the Channels category, click SMS.
Clicknext to the SMS number you’d like to activate Answer Thread, then select Configure.
Check the box next to “Enable for 3rd party Automation Services.”
Once Gladly is configured, you’d need to contact Gladly Support or ask your Gladly Account Executive to connect SMS/Chat with Answer Threads. In your request, please specify:
The SMS number you are trying to connect Answer Threads to.
The Glad App identifier you are trying to connect Answer Threads to.
Test to ensure Answer Threads is working as intended.
Chat (via Glad App)
Open up a new Incognito window and start a new chat session with a unique email address
Click the “Something Else” Quick Reply button and type in a question.
If you get handed off to an Agent, close the Incognito window and start again from step 1.
SMS
Text a question to the SMS number you enabled for Answer Threads
If you get handed off to an Agent, find your Profile in Gladly, close the Conversation, and then delete the Profile. Then, start over again from step 1.
If you see responses you don’t like, proceed to the Monitoring and Maintenance below to learn how to improve responses.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
__cf_bm
29 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_wpfuuid
1 year 1 month 4 days
This cookie is used by the WPForms WordPress plugin. The cookie is used to allows the paid version of the plugin to connect entries by the same user and is used for some additional features like the Form Abandonment addon.
BIGipServer*
session
Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user.
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category.
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie.
PHPSESSID
session
This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
li_gc
5 months 27 days
Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.
lidc
1 day
LinkedIn sets the lidc cookie to facilitate data center selection.
UserMatchHistory
1 month
LinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
1 year 1 month 4 days
Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_gd_session
4 hours
This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded.
_gd_visitor
1 year 1 month 4 days
This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads.
_sp_id.*
1 year 1 month 4 days
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
_sp_ses.*
30 minutes
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
AnalyticsSyncHistory
1 month
Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie.
mf_user
3 months
Mouseflow sets this cookie to identify whether a visitor is new or returning.
vuid
1 year 1 month 4 days
Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
_mkto_trk
1 year 1 month 4 days
This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo.
bcookie
1 year
LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.
bscookie
1 year
LinkedIn sets this cookie to store performed actions on the website.
li_sugr
3 months
LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant.