Once your call ends, you’ll automatically receive another call depending on the length of time lapses based on the current After Call Work settings. Use this time to finalize your call notes before the next call comes in. To stop receiving calls, you must mark yourself Unavailable for Voice.
Note – Clicking ‘Close & Next’ or ‘Next’ routes you to the next call
Clicking Close & Next or Next immediately after a call overrides the After Call Work settings. For example, if your Team Managers allow you 30 seconds after each call before a new call is routed to you, clicking Close & Next or Next before the 30 seconds is up overrides the After Call Work setting, thus routing you the next phone call before the 30 seconds is up.
Tip – Complete your call notes before ending the call
Save a few seconds at the end of your call to finalize your notes before the call ends. Say something to the Customer like, “Please allow me a few seconds to make sure I have everything we did today noted properly just in case we need to reference this call in the future.” Customers are usually happy to wait a few seconds to ensure their calls are properly documented.
Search for the Agent you want to transfer the Customer to by typing their name in the search box. Agents available to receive call transfers are listed under the Agents Ready section.
Tip – The Agents Ready section doesn’t appear if no one is available on the Voice Channel.
Click the Agent’s name to transfer the call.
Tip – Agents not available to receive a phone call (i.e., they are away or unavailable for Voice) will appear under the All Agents section. It will say “Unavailable” if you attempt to transfer the call if they are on another call, away, or not logged into Gladly.
The receiving Agent will be notified of the call and can Accept or Decline the call.
Agent picks up the call – Provide them with the context of the Customer’s issue. If the receiving Agent agrees to take the Customer, you can complete the transfer by clicking Complete. The Customer will be transferred to the Receiving Agent.
Agent doesn’t pick up the call or says they can’t help the Customer – Cancel the transfer by clicking Cancel and then find another person. If you stop the transfer, click to bring the Customer back on the line.
Agent doesn’t pick up – Click Find Another Agent to find another Agent to transfer the call to.
Search for the Team Manager to whom you want to transfer the Customer by typing their name in the search box. They’ll appear under the All Agents section unless they’re available on the Voice Channel, which they’ll appear under Agents Ready.
Tip – Team Managers not available to receive a phone call (i.e., they are away or unavailable for Voice) will still appear under the All Agents section. It will say “Unavailable” if you attempt to transfer the call if they are not logged into Gladly.
The receiving Team Manager will be notified of the call and can Accept or Decline the call.
Manager picks up the call – Provide them with the context of the Customer’s issue. If the receiving Agent agrees to take the Customer, you can complete the transfer by clicking Complete. The Customer will be transferred to the Receiving Agent.
Manager doesn’t pick up the call or says they can’t help the Customer – Cancel the transfer by clicking Cancel and then find another person. If you stop the transfer, click to bring the Customer back on the line.
Manager is unavailable – The Voice transfer list will say “Unavailable” if they’re not logged into Gladly.
You can search for the Inbox you want to transfer the Customer to by typing the Inbox name in the search box.
The number of Agents ready to accept a transfer is displayed. If none are available, the transferred call is put in the queue to wait for the next Agent.
Note – Contact Gladly Support If the Inbox does not appear in the transfer list. This usually means the Inbox is not linked to a Voice queue.
As you hover over the Inbox name, you’ll see options on the side to initiate either a Warm or Cold transfer.
Warm Transfer – Speak to the Agent you’re transferring the Customer to before completing the transfer. This allows you to brief the Agent on the Customer’s issue rather than having the Customer repeat it.
If no one in the Inbox picks up – The Routing Enginewill find the next available Agent to dial. The warm transfer won’t go through if none are available, and no one will be dialed. You’ll be asked to pick another Inbox to transfer to or another transferee.
Cold Transfer – Transfer the Customer directly to another Inbox and leave the call. The call is routed to another Agent in that Inbox.
If no one in the Inbox picks up, the call will still be transferred to the Inbox. The Customer will wait in the Inbox until the next available Agent becomes available or until they are moved into the queue IVR (if used) experience.
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.