Gladly does everything possible to prevent and avoid platform issues and outages, but on the rare occasions they occur, below are suggested actions you can take to reduce Customer impact. This begins with ensuring you’re subscribed to receive outage or maintenance updates through the Status Page.
Ensure you’re subscribed to receive platform updates from Gladly’s Status Page .
While you can get notified by email, SMS, and other channels, we suggest subscribing to receive updates via email, as email provides updates whenever the Status Page is updated.
The recommended actions depend on the severity and duration of a platform issue or outage, and the suggestions below are for extreme cases where communication is impossible.
In the event of a Voice performance issue, the recommended action depends on how Customers are affected. Keep in mind that some problems may not always originate from Gladly. For example, VPN issues within your company network preventing inbound/outbound calls in Gladly, local internet or ISP issues, telecom carrier issues, and other situations outside of Gladly’s control.
If the Voice issue prevents Customers from entering your IVR, it’s best to wait for it to be resolved. Subscribe to Gladly Status Page if the issue originates from Gladly, or wait for an update from your team if the problem is related to your network outside Gladly’s control.
Customers can call in but are unable to reach Agents #
If a Voice issue affects the ability of Customers to reach your Agents, it’s best to turn off your phones temporarily and strive to inform your Customers of the issue. Do this by immediately routing all inbound calls to voicemail by implementing a Voicemail only IVR.
As an Administrator, go to Settings > IVR.
Click Create New IVR.
Enter “Voicemail Only” as the IVR name.
Click Start Building.
Click Voicemail Only under Select a template.
Under Message, the default selection is Text to Speech with the message below:
The message Customers will hear is: “Thanks for contacting us! We are currently not taking phone calls, but you can leave us a voicemail, and we’ll get back to you as soon as possible. Please leave a voicemail with your name, number and reason for calling and we’ll get back to you soon! — You can enter a different message if necessary.
Tip – You can edit this text to customize the message.
Another option is to upload a voice recording instead (download the sample file below) by clicking Text to Speech and clicking Recording to upload the recording. The recording Customers will us: “Hi, thanks for reaching out to us. Our phone system is currently unavailable. You can leave us a voicemail or, if you prefer, contact us via email. We look forward to connecting with you.”
If Customers can call and reach Agents but Agents can’t make outbound calls, it’s best to wait until the issue is resolved or attempt to reach out to the Customer through another Channel, like email or SMS, if available.
If Customers cannot chat from Glad App, or maybe Customers can start a chat, but there’s an issue that’s causing long delays in Agents receiving chat requests, we suggest turning off Glad App on your website by marking the day as Closed to stop chats from coming in temporarily and display information on alternative Channel(s) Customers can use to contact you.
As an Administrator, go to Settings > Glad App.
Find the affected Glad App, click, then select Configure.
Scroll down to the Glad App Hours section and click the Closed box next to the affected day.
Scroll down to the Chat Unavailable section. Take note of the message (e.g., paste it on a notepad), then edit your message to ask Customers to try again later or provide another way (e.g., email address or phone number) to contact you.
Click Save.
Once the issue is resolved, go back to step 3 and uncheck the Closed box next to the day you temporarily closed. Then, go to step 4, edit the message to its previous state, and click Save.
If chat suddenly stops working and Agents cannot reply, or maybe there’s an issue that’s causing long delays in Customers receiving chat replies, we suggest using email to contact the Customer or even calling the Customer to inform them of the issue and to continue helping them until the issue is resolved.
A Customer may be able to SMS during SMS-related issues, but the message may not properly reach Gladly or an Inbox. It’s best to let the outage pass for SMS outages since SMS could be an asynchronous Channel with a slightly longer SLA than Voice.
If Customers cannot message in because they cannot start a message from the messaging platform, it is best to wait until the issue is resolved, especially if it originates from the social platform itself. Monitor the Gladly Status Page for updates.
If Customers are unable to message through the social platform and agents are not receiving messages, we recommend waiting for the issue to be resolved and then following up with messages later.
Email issues are very rare. However, if one does occur, it is best to wait for it to be resolved. Email is an asynchronous channel with SLAs ranging from a few hours to many days, so email issues are likely to be resolved before a reply is required. Your Customers may not even realize there was an issue, to begin with. You can also call (if you know their phone number) while the email issue is ongoing.
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.