Connect Learning Available in eLearning format in Connect Learning
Configure Quick Reply buttons to appear on Glad App. The order in which Quick Reply buttons are displayed to Customers depends on whether Onboarding is used. See Create and Configure Glad App for general instructions on how to set up Quick Reply buttons in Glad App.
Understand how to automate routing and responses based on button selection using Rules. Remember to review how to plan Quick Reply buttons before configuring Glad App to receive input via Quick Reply buttons.
Tip – Use ‘Only’ as a Rule Qualifier
Use “Only” along with “Message Body” as a Rule Qualifier to ensure activities from a Quick Reply button only trigger the Rule.
Watch Out – Changing Quick Reply button names can break related Rules
If you change the name of a Quick Reply button, you must also update any Rules using Quick Reply button’s previous name to the new name.
With Chat as a Channel, button names are passed on as plain text in a Message Body, allowing Rules to detect the selected button. So if a “Product Question” button is clicked, “Product Question” is passed on as plain text. Then, you can create a Rule set up as Communication received as (Trigger), Message Body – Contains – Only = Product Questions (Conditions) to detect that this is a request from a Quick Reply button.
Channel
Message Body
New Contact
Use New Contacts (Condition) to ensure the Rule only applies to newly created Contacts.
Based on the button — in this example, “Product Questions” — you can route the request to an Inbox that can answer product-related questions like a Support Inbox.
Another example supposes a Quick Reply button called Returns and Exchanges is clicked. In that case, a Rule can be configured to detect that Message Body from the chat is Returns and Exchanges, and the Rule appropriately routes the request to the Returns and Exchanges Inbox.
Suppose you have a button called Order Status and a website where Customers can track their order status. If a Customer clicks the Order Status button, you can automatically reply with a Messaging Answer with a link to track their order. It may say something like:
“You can track the status of your order by going to retale.com/orderstatus. Please wait while we connect you to an associate.”
From there, they can either self-serve or wait for their request to be routed to an Agent.
The above scenario could have a Rule that looks like this.
Route requests to a specific Inbox based on when they came in using Business Hours. Let’s say a Quick Reply button called Custom Design is clicked, and suppose you have Business Hours configured with your regular operating hours (e.g., 9 AM to 6 PM). In that case, you can configure a Rule for Custom Design requests to only route to the Custom Design Inbox during regular operating hours.
Below is a sample Rule where a request comes in through a Quick Reply button (Custom Design) during regular operating hours, and the request routes to a specific Inbox.
Using the example above, you can:
Create another Rule to route Custom Design requests to route to a general Inbox outside normal operating hours
Optionally, you can use our API with Quick Reply buttons to create automated workflows and triggers through automation partner apps.
Buttons that use the MESSAGE/RECEIVED webhook trigger these events. You’ll need to configure these as webhooks.
Use conversationItemId using the GET Item API where content.type will be CHAT_MESSAGE, and the content.messageType will be QUICK_REPLY_RESPONSE. Content.messageData will give you more information on what the Customer selected.
Use the POST Reply To Message API to send a response programmatically.
Add the Quick Reply buttons you want to appear on Glad App. These buttons are immediately visible to Customers as soon as you save the buttons in Glad App so it’s best to have your button names and Rules to be associated with each button configured before adding the Quick Reply buttons.
Refrain from creating too many buttons. Five is a balanced number of buttons to have without overwhelming Customers.
Click on the top left corner of the screen.
Click Settings.
Under the Channels category,click Glad App. The Glad App page will show you a list of Glad Apps you currently have.
To the right of the Glad App you want to add Quick Reply buttons, click, then select Configure.
Scroll down to find the How Would You Like the Customer to Reply? setting.
Change the selection from Type A Message to Quick Reply Button.
A row of fields will appear where you can add the names of your buttons.
Button Label – Enter the button label with text (e.g., Refunds) representing an option.
Note – Button labels begin to wrap (create a second line) at around 40 characters and make the button bigger. The maximum limit is 50 characters.
Button ID – Used to identify the button by an automation partner or API . It can be alphanumeric text or numbers. Although required to save a button, it’s not used to create automation through Rules. We suggest using an ID that makes the button easily identifiable.
+ Add Button – Add more buttons.
Click Save.
The buttons are now visible on Glad App for Customers attempting to use Chat.
Tip – Quick Reply button color
The color set in Help App Chat Launcher on the Glad App configuration page is the same color used as the button border color for Quick Reply buttons. If the color is set to #FFF (white), Gladly will automatically use the fallback hex color #E3E3E3 (gray) to ensure visibility.
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.