Create a Glad App to embed on your website and allow visitors to chat with your Agents. You can also encourage self-service by activating Quick Actions on Glad App, surfacing your most frequently asked questions, and allowing visitors to search your Public Answers.
You can create multiple Glad Apps to embed on different websites or web pages where you want your Customers to access your FAQs or your chat feature.
Use Display Rules in the Configuration section to control where Glad App appears on websites/pages.
The minimized style of the Glad App icon is customizable if you choose not to use the UI defaults.
If Glad App is used with Proactive Chat, note that a Proactive Chat Campaign can override the Glad App Display Rules, so Proactive Chat Campaigns may appear on webpages Glad App is not supposed to.
Look into using Quick Reply if you want to give Customers specific options — by way of buttons — to select what they need help with.
Watch Out – We recommend not adding an Entry Point(s) until you’re ready to receive incoming requests
Upon adding a new Entry Point, incoming requests from that Entry Point automatically route to the corresponding Channel’s primary Inbox. For example, upon adding Instagram Messaging as an Entry Point, direct messages from your Instagram account will automatically create a Conversation in Instagram Channel’s default inbox.
Voice/SMS – Phone numbers can be purchased and held onto until you can complete the setup by connecting them as Entry Points.
Chat (Glad App) – Upon configuring Glad App, it’s available to receive incoming chat requests as soon as it’s embedded on your website. Chats are routed to the Chat Channel’s default Inbox.
Social Channels – Upon adding a social Channel Entry Point (e.g., Instagram or WhatsApp), messages automatically route to the social Channel’s default Inbox.
Email – Once an email address is added, it’s ready to receive inbound emails in the email Channels’ default Inbox as long as email forwarding is activated.
Use Exceptionsto link an Entry Point to a different Inbox if you don’t want to use the Channel’s default Inbox.
Watch the short overview videos below to understand the overall configuration process for setting up Glad App.
Under the Channels category, click Glad App. The Glad App page will show you a list of Glad Apps you currently have. Under the Channels category, click Glad App. The Glad App page will show you a list of Glad Apps you currently have.
Click Create Glad App.
From the New Glad App prompt, enter the name of your new Glad App. You’ll see <domainname.com->prepended. Enter the name of your new Glad App after the “–.” The name you use should help you identify how or where the Glad App is being used.
Special characters are not supported, and space between characters is not permitted.
The same name identifies the Glad App on the Entry Points page.
Click Create. This will immediately take you to the configuration page.
The Glad App configuration page is where you’ll set how Glad App looks and how it behaves.
Tip – Use the UI illustrations
Use the visual illustrations to the right of each option to help you visualize the part of Glad App you are configuring.
There are three sections that you will need to configure. Each section controls a particular aspect of Glad App:
Configuration – Administrative actions such as when to display Glad App, what Quick Actions will be used, Glad App Hours to control the availability of Glad App during business hours, and others.
Style – Configure the look and feel of Glad App, where you can change things like border style, radius, color, and other design elements.
Text – Customize the text on Glad App, including the header, input buttons, and more.
Enable Automation Services for Glad App – When the checkbox is selected, Gladly Sidekick and 3rd party automation services will have access to this Glad App for the purpose of communication and routing. If activating, click Yes, proceed on the confirmation modal.
Note – The third-party automation provider is responsible for coordinating the handoff to Gladly using the Automation API if their automation cannot solve an issue. Unless you’re working with an automation partner, leave this box unchecked.
Enable Search and Quick Actions – If checked, Customers can search Public Answers, view Quick Actions, and see your chat option if within Glad App hours. If the box is unchecked, Customers can only chat during normal operating hours or if the day is not marked as Closed in the Glad App Hours settings. Otherwise, Customers will see the Chat Unavailable Message text.
Note – This box must be checked to allow the use of Audiences and to select the language used to search Answers through Glad App.
Option to allow Glad App to appear on all web pages or no pages.
If Display Glad App on = All Pages, Glad App appears on all web pages unless an exception is added. It’s important to note that a Proactive Chat Campaign can override the Display Rules.
If adding an Exception, When a page = Contains, Exact, or Regex, enter the URL parameter to match the Condition.
Condition
Description
Contains
The URL can match and does not have to be the only URL. For example, the URL “/mens/sneakers” appears in the URL ” retale.com/pages/shoes/mens/sneakers” would be matched using Any. For the word “sneak,” the word “sneakers'” will be matched by also using Any.
Exact
The URL you’re using must match exactly. For example, the URL ” /mens/sneakers” would not match the content ” retale.com/pages/shoes/mens/sneakers” using Only because the text strings don’t precisely match.
Regex
Short for Regular Expression, a form of light coding that lets you match patterns in the text without specifying the entire string. This is particularly useful to distinguish URLs that can be part of other URL strings or match phrases with variable text. For example, by using Regex, “/pages*” would be matched to ” retale.com/pages/shoes/mens/sneakers,” ” retale.com/pages/shoes/womens/sneakers,” and ” retale.com/pages/shoes/kids/sneakers.” Regex matching follows Google’s re2 library.
If Display Glad App on = No Pages, Glad App will not appear on any webpage unless:
Control when Glad App is active on your site. Please select the correct time zone. (Gladly Recommendation – Provide an alternate way for Customers to contact you during non-business hours.)
Timezone – Select the timezone Glad App should follow.
Hours – Enter the hours when Glad App will be active on your website. If you are closed on a particular day, check the Closed checkbox.
Add Time Range – Click this option to enter different time ranges you want Glad App available. For example, if your team works from 6 AM to 6 PM, but you wish to hide Glad App from your website to stop chat requests from 12 PM to 1 PM during your team’s lunch hour, this is possible with the time range setting.
If “Enable Search and Quick Actions” box is checked, your FAQs will remain accessible, but chat will show your “chat is unavailable” message if outside Glad App active hours.
If “Enable Search and Quick Actions” box is not checked, and if a day is marked Closed or is outside Glad App active hours, the Chat Unavailable Message text will appear for Customers attempting to chat in since Agents are not working.
This section only appears if “Enable Search and Quick Actions” box is checked. Quick Actions consist of four required Actions that appear on Glad App. Think of Quick Actions like a “category” or “topic” that point to an external link or Public Answer.
Audience1 – Select the audience Glad App will use to search Public Answers. Selecting “none” allows the searching of all Public Answers not linked to an Audience.
[B] Answer/Website URL – Select whether each action will point to a Public Answer to an external URL/webpage.
[C] Answer or Website URL Value – Insert the value based on [B] selection. (Answer/Website URL).
Answer – If an Answer is selected on [B], select the Public Answer from the list. Note that if an Audience is selected, only Answers linked to the selected Audience are available.
Website URL – If Website URL is selected on [B], enter the URL of the page you want to redirect Customers to.
[D] View Answer – If [B] shows Answer, click View Answer to view the Answer on the Answers admin page.
Option to display an icon or button (with text) when Glad App is minimized. The minimized style of the Glad App icon is customizable if you choose not to use the UI defaults.
Icon – Uses an icon to display Glad App on a webpage.
Text – Uses a button to display Glad App on a webpage. If selected, enter the text you want to show on the button.
Note – Regardless of your selection — Icon or Text — after a Customer starts a chat or clicks on a Quick Action, the icon becomes the default state when Glad App is minimized. To override this behavior, create a custom minimized button on your website, requiring some front-end site resources for HTML & CSS styling.
Close Button – Choose if you want the close button to be signified by an “X” or a “Dash.”
This setting also applies to Proactive Chat. The close icon appears when the visitor hovers over the greeting.
Choose a left or right placement where Glad App appears on your website.
Z-Index – Adjusts the stack order of elements (positioning of the Glad App icon on the page), which applies when Glad App is minimized. Start with “147483000” and adjust as needed.
Powered By Gladly –Choose to allow the “Powered by Gladly” text to appear on Glad App.
This setting is activated by default. (the box is checked)
Privacy Policy Disclaimer – Display a privacy policy statement that Customers accept when starting a chat session.
This setting is deactivated by default (the box is not checked).
Check the box to activate the setting and enter your Privacy Policy statement. For example, “By using chat, you accept our <company name> Privacy Policy.” Keep the disclaimer concise and within the 140-character limit.
Link back to your company’s Privacy Policy page by highlighting the text and inserting the link.
Drop Shadow – Chooseto use (On) or not use (Off) drop shadows around Glad App.
Border Width –Choose Glad App’s border width (1px to 3px).
Border Color – If you have a border width selected, enter a hex color code to change the border color.
Enter the message you want to display outside Glad App active hours. or when chat is unavailable. The message can be written in plain text or styled using HTML. You can also embed a web form.
Configure the messages that Customers see before chatting with an Agent. (Gladly Recommendation –Consider including a text stating that emails are used for communication purposes only and not for marketing purposes.)
Onboarding – If activated, you can collect the Customer’s name and email address before a chat session starts. This information is used to locate an existing Profile and any past Conversations. If not activated, Customers are not identified when starting a chat (not recommended).
Tip – Onboarding information provided by Chat Customers persists for 24 hours, meaning they won’t have to be asked onboarding questions again if they start another chat within 24 hours. Onboarding data is stored locally in the Customer’s browser, and clearing the browser’s cache immediately erases stored onboarding data.
Prompt Order – If Onboarding is activated, select the order you want identifying information to be presented to Customers. (e.g., NAME > EMAIL, or EMAIL > NAME.) This information is used to identify and locate the Customer Profile (if they’re an existing Customer) or create a new Customer Profile with the name and email address.
Tip – Insert links in Message and End Chat text fields
You can insert hyperlinks inside the Message and End chat text fields. To save the text as a link, you must include the URL protocol and subdomain (e.g., https://google.com).
First Message – Enter a greeting that also asks for the Customer’s email address. For example, “Thank you for contacting us. What’s your email? We’ll use your email to find your profile and any past conversations you’ve had with us — not to spam you.”
Getting the email address helps identify the Customer in Gladly and pull up their Profile if they are an existing Customer. Otherwise, a new Customer Profile is created.
Second Message – Enter a message that also asks for the name. For example, “Thanks! Can we get your name?”
This information is also passed to the Customer Profile.
Third Message – Enter a message asking how you can help them. For example, “Thanks <CUSTOMERNAME>! How can we help?” The <CUSTOMERNAME> variable automatically inserts the Customer name.
If using Proactive Chat and onboarding is activated for a Campaign, the Third Message is replaced by the Campaign’s Action greeting.
How Would You Like the Customer to Reply? – Customers can reply to the Third Message by typing a message (Type A Message) or selecting a reply by clicking buttons (Quick Reply Button).
If Type A Message is selected, Customers type a string of text to reply to the Third Message with a question like “How we can help?” The Customer’s reply is taken verbatim and is what the Agent sees when the Customer is routed.
If Select a Quick Reply Button is selected, you can configure specific options, by way of buttons, as input to reply to the Third Message.
Button Label – Enter the button label with text (e.g., Refunds) representing an option.
Button ID – Used to identify the button via API or by an automation partner. It can be alphanumeric text, or numbers. We suggest using an ID that makes the button easily identifiable.
+ Add Button – Click to add more buttons as a Quick Reply.
Fourth Message – You can activate/deactivate a message to let a Customer know you have the information you need to start helping them once their request is routed to an Agent upon typing a message or clicking a button. For example, “Got it! Someone will be with you shortly.”
If the box is unchecked, no additional message is sent to the Customer after they reply to the Third Message and until the request is routed to an Agent and they send a response.
If using Proactive Chat and Onboarding is activated for a Campaign, the Fourth Message may be redundant depending on how generic the Campaign’s greeting is.
First Message – Enter a greeting. Something like “Thank you for contacting us. How can we help you?”
This allows you to greet the Customer without asking for their name and email address in the beginning. Remember that you’ll still need a Customer’s email address to find their Profile in Gladly.
How Would You Like the Customer to Reply? – Customers can reply to the Third Message by typing a message (Type A Message) or selecting a reply by clicking buttons (Quick Reply Button).
If Type A Message is selected, Customers type a string of text to reply to the Third Message with a question like “How can we help?” The Customer’s reply is taken verbatim and is what the Agent sees when the Customer is routed.
If Quick Reply Button is selected, you can configure specific options using buttons as input.
Button Label – Enter the button label with text (e.g., Refunds) representing an option.
Button ID – Used to identify the button via API or by an automation partner. It can be alphanumeric, text, or numbers. We suggest using an ID that makes the button easily identifiable.
+ Add Button – Add more buttons.
Second Message – You can activate/deactivate a message to let a Customer know you have the information you need to start helping them once their request is routed to an Agent upon typing a message or clicking a button. For example, “Got it! Someone will be with you shortly.”
If Onboarding is activated, you must enter a Second Message.
If Onboarding is not activated, check/uncheck the Second Message. If selected, enter a message as a response to a reply from the First Message.
End Chat – Enter the text shown when the chat is ended.
Chat Ended By Agent – Enter the text you want Customers to see when a chat is ended by an the Agent.
Chat Ended By Expiration – Enter the text you want Customers to see if a chat session times out because the Customer did not reply within 24 hours.
Chat Ended By No Reply – Enter the text you want to use if a Customer stops responding.
Chat Ended By a New Active Chat – Enter the text you want Customers to see if Glad App notices a duplicate chat session from the same Customer but on a different device/browser.
On the Settings page, under the Orchestration category, click Entry Points.
Hover over Chat and click the pencil icon to open the Chat Channel’s Entry Point settings.
The Inbox selected in the default Inbox field is where all Glad App chats will be routed. You can stop here if this is the Inbox you want to use to receive chats from your website where Glad App is embedded. You can add an exception if you want chats to go to a different Inbox for a particular Glad App (if you have more than one).
Click + Add exception if the Glad App won’t use the Chat Channel’s default Inbox or Entry Point SLA.
Entry Point – Select the Entry Point you want to exclude from using Chat’s default Inbox. This will be the name of the Glad App you created for the mobile app.
Inbox – Select the Inbox you want incoming chat requests from the mobile app to queue in instead of the default Inbox.
Entry Point SLA (minutes) – Leave this field blank to use the selected Inbox’s SLA. Otherwise, entering an SLA here trumps the Inbox SLA.
You can use fractional minutes. For example, 0.66 is 40 seconds.
You can’t enter “0” or use the “-” (minus) symbol.
Once Glad App is embedded on your website, you do not need to re-embed the Glad App code if you make additional changes to the configuration (e.g., colors, new text, placement, etc.). Any changes will take ~10 minutes to appear on your website.
1Appears if Glad App If “Enable Search and Quick Actions” box is checked.
2Appears if “Enable Search and Quick Actions” is not checked.
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.