Configuring Gladly to send and receive emails for contact center operations is a core product capability and represents one of the popular Channels used to receive or ask for help.
Adding new domains or email addresses is done directly in Gladly. Follow the links below to learn how.
To allow Gladly to send an email from your domain, please add two TXT records to your DNS provider. These entries should be added one week before launch so Gladly can adequately test the email setup.
Please note that we typically only ask you to configure these records in your production environment.
SPF – This allows Gladly to send mail from your email domain name via Gladly’s mail provider. If you already have an SPF record, then you can add include:mailgun.org into the value. For example: v=spf1 include:mandrill.com include:mailgun.org ~all
DKIM – This allows email servers to ensure that emails from Gladly’s email provider are authentic.
Email domains that doesn’t have a website (i.e., a CNAME record), most likely because it’s a subdomain, needs to have MX records created to work with some email providers.
First, go to the Email Settings and clicknext to the sending domain, then click View SPF and DKIM Values.
Log in as an Administrator in GoDaddy.
On the screen’s upper left-hand side, click Domains > All Domains.
Select your email domain.
Scroll down and click on Manage DNS in the Additional Settings panel.
Let’s add your DKIM record
Click ADD.
Select Type = TXT.
In Name, enter the hostname you see in the Gladly Email Settings page for this domain without the hostname. If the Gladly Email Settings page for this domain says the host is smtp._domainkey.something.com, you should enter smtp._domainkey and not smtp._domainkey.something.com.
In TXTValue, enter the value in this domain’s Gladly Email Settings page.
Set the TTL to 1 hour.
Click Save.
Let’s add your SPF record.
If you already have a TXT record on @ with v=spf1 at the beginning.
Click on Edit for that record.
Enter include:mailgun.org into the record after the v=spf1 value. For example, if your previous record looked like v=spf1 include:something ~all, it will now look like v=spf1 include:mailgun.org include:something ~all.
Click on Save.
If you do not have a TXT record on @ withv=spf1 at the beginning.
To receive emails in Gladly from your support email addresses, please follow these steps:
Upon launch, you must configure your mail server (e.g., Exchange, Lotus Notes) to forward a copy of the inbound email to Gladly, which preserves the “from” email address.
Gladly provides you with an emailaddress (or multiple email addresses, depending on your business requirements) to forward the mail copy. The table below outlines an example where the SOMETHING part of the forwarding email address is unique per sending domain in your Gladly organization.
We recommend allowing these dedicated IP addresses to prevent forwarded emails from getting blocked.
This forwarding method is only possible if you have access to admin.google.com with administrator access. Use this forwarding method to redirect emails from your company email account to Gladly if possible.
By default, Gmail will not forward Spam emails to Gladly. We highly discourage doing so but follow these steps if you want to continue forwarding Spam emails to Gladly.
If your website has a form that Customers enter support inquiries into, you must do the following upon launch:
Ensure there are required fields for Customer Name and Customer Email in the web form.
Compile the inquiry into a valid email HTML template upon web form submission.
Forward the inquiry into one of your email inboxes (e.g., <emailinbox>@YOUREMAILDOMAIN.com), making sure to preserve the customer’s email address as the email “reply-to” header, and the customer’s name as the email “friendly name.” If you are utilizing FormStack, this article helps explain how to configure that with no code needed!
Ensure you have forwarded communications from the email inbox to the corresponding Gladly forwarding address.
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.