Entry Points for some Channels, such as email addresses and phone numbers, can be added from the UI, and some can only be added by Gladly Support. Channels and their relevant Entry Points that you can add and configure through the Gladly UI are:
WhatsApp (Currently can’t be configured through the Gladly UI.)
Once Channel Entry Points are successfully configured, they’re immediately activated and linked to the Channel’s default Inbox on the Entry Points settings page unless exceptions are created. This is also where you can link Entry Points to a specific Inbox.
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’re ready to 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 Exceptions to link an Entry Point to a different Inbox if you don’t want to use the Channel’s default Inbox.
This is the Inbox where all incoming requests from the Channel’s Entry Point(s) are queued by default. Entry Points added in the future will use the Channel’s default Inbox unless exceptions are added.
You only need to complete the steps below once, but you can change a Channel’s default Inbox anytime.
Click on the top left corner of the screen.
Click Settings.
Under the Orchestration category, click Entry Points. This page contains Entry Points for all Channels available in Gladly.
Check the Default Inbox column to see the default Inbox for a Channel quickly.
Check the Entry Point SLA column to quickly see the Entry Point SLA for a Channel (if configured). This will be blank if Entry Point SLA is not configured.
Hover over the Channel you want to edit and click .
Click the Default Inbox drop-down list and select the default Inbox all inbound communications from a Channel’s Entry Points are queued.
Entry Point SLA (minutes) – Leave this field blank if you want to use the selected default 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.
Add Entry Point exceptions to exclude certain Entry Points from using a Channel’s default Inbox and/or SLA. This is useful if you have multiple Entry Points that you’d like to link to different Inboxes instead of using the Channel’s default Inbox. Keep in mind that Entry Points not set as an exception automatically use the Channel’s default Inbox.
Tip – There’s no need to add an exception if you only have one Entry Point for a Channel
You don’t need to create an exception since it can utilize the Channel’s default Inbox.
Click on the top left corner of the screen.
Click Settings.
Under the Orchestration category, click Entry Points. This page contains Entry Points for all Channels available in Gladly.
Hover over the Channel you want to edit and click .
Click + Add exception in the Exceptions section.
Tip – Click + Add exception to add additional exception lines.
Configure the following:
Entry Point – Select the Entry Point(s) you want to exclude from using the Channel’s default Inbox.
Inbox – Select the Inbox you want incoming requests from the Entry Point to queue in instead of using the Channel’s default Inbox.
Entry Point SLA (minutes) – Leave this field blank to use the selected Inbox’s SLA. Otherwise, entering an SLA here (on the Entry Point) 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.
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.