Elevating CX with AI: Tracking and Measuring Success. Join Lauren Inman-Semerau, Head of CX at Rothy’s, as she shares how to track AI success and measure its impact. REGISTER NOW
You can add or edit users one at a time, but this is not always efficient when you add/update many users simultaneously. But with the Export and Import feature, you can add (or update) user data — in bulk — with less effort.
Under the People category, click Users. The Users page will show you a list of your Gladly users. For ease, you can also see a preview of roles assigned to users, the number of Teams and Inboxes they belong to, and their account status.
Click Export. This downloads a CSV of all your existing users to your local folder.
Open the CSV and add rows to the bottom of the CSV based on the number of users you are adding.
Note – Do not edit user rows you do not want to change/update.
You could also delete all the rows from the CSV except for row 1 (column headers) and add your user(s) starting on row 2.
Enter the following information in each column. Columns with an * are required.
Column A (name)* – Enter the user’s full name.
Column B (email)*– Enter the user’s email address.
Column C (roles)* – Enter the role(s) you want to be assigned to the user. If you’re assigning more than one role for a user, separate each role with a comma and a space right after each role. For example, adding Administrator and Compliance Administrator gives the user Administrator and Compliance Administrator permissions. See Roles and Permissions to learn more.
Column D (inboxes)– Enter the Inbox (or Inboxes) the user should be a member of.
To add an Inbox, enter it as one Inbox. For example, Returns.
To add multiple Inboxes, use commas with a space to separate the Inbox names and add quotes to isolate them. For example, “Returns, Refunds, Design Services.”
Column E (teams) – Enter the Team(s) the user should be a member of. Use commas with a space right after to separate the Team names.
Columns F (deactivated) – Enter whether the user’s access to Gladly should be activated or deactivated. Enter Yes to deactivate a user’s access to Gladly (until you’re ready to activate them). If you want the user active in Gladly from the start, enter No into the field or leave the field blank. You can also skip the column entirely if you want all your users activated.
Columns G (stationId) – Only use this column if you use an external phone system instead of Gladly’s built-in Voice; otherwise, you can skip this column entirely.
Note – How you enter skills depends on the Skill feature structure (flat vs. hierarchical). See Skills Hierarchy to learn how to enter skills in this field.
Save the CSV. If you’re using Excel, save it as Comma Separated Values.csv. Do not use CSV UTF-8 or any other format.
Proceed to upload the CSV through the Users page. This time, click Import.
CSV is limited to 5MB. You must upload a separate list if you exceed this limit.
Click Upload CSV from the prompt and upload the CSV from your local drive.
A confirmation prompt appears if your upload is complete.
How you enter skills in the CSV depends on how your skills are structured (flat vs. hierarchical).
Skill has no hierarchy (flat)
Enter the skill as is. For example, Spanish. Separate each flat skill with a comma to add more skills. For example, Spanish, Retention.
Skill part of a hierarchy
If a skill has a unique name but is in a hierarchy, simply enter the unique name. For example, if the skill is set up as Language > Spanish, then enter Spanish.
If the skill is set up as a flat list (e.g., Spanish) or is part of a hierarchy (e.g., Language > Spanish), in either case, enter Spanish, and the uploader knows to assign the Spanish skill to the user.
Skill is not unique and is used across other skills
In cases where a skill (e.g., Retention) is used across different hierarchies and in both flat and hierarchy style, you must differentiate the skill assigning using “>”
If Spanish is part of other skills (e.g., Language > Spanish, Retention > Spanish, Spanish), then enter the skill as Language>Spanish, Retention>Spanish, Spanish using a comma to separate each skill/hierarchy.
Other uncommon skill structure
The uploader recognizes varying types of skills. See below for how to enter them on the CSV.
To add skill with literal formatting and using special characters like Languages > German, enter is as “””Languages > German”””.
To add skill with literal formatting using ” like Languages “like” French, enter is as “””Languages “”””like”””” French”””.
To add skill with literal formatting using both > and ” like Languages > German, or Languages “like” French, enter is as “””Languages > German”””,”””Languages “”””like”””” French”””.
To add a skill with a combination of formatted skills and hierarchical skills like:
Languages > German (hierarchical)
Languages>English
Languages “like” French
Languages>Spanish>Intermediate (hierarchical)
Enter the above as “””Languages > German”””,Languages>English,”””Languages “”””like”””” French”””,Languages>Spanish>Intermediate.
The Export feature can be used to not only upload users in bulk, but it can also be used to edit user details in bulk. For example, you can assign new Inboxes to users and update user roles for multiple users at once rather than editing user details one at a time.
Tip – Update users in small batches
If you’re not comfortable making many changes at once, we suggest updating user data in small batches. If you need to make changes for 20 users, start by updating five first.
Review the following before you edit/update user data in bulk.
The email column is the most critical of data which tells Gladly which users you want to update. Users not in the CSV are not updated.
Do not delete the name column to prevent overwriting names as a blank field.
If you delete the inboxes, teams, or deactivated columns, those fields are ignored, and no changes are made.
If you leave a field blank (e.g., name, inboxes, team, etc.), the data will be overwritten as a blank. For example, if a user is assigned to the Support Inbox, enter Support in the inbox field to keep the Support Inbox assigned to the user.
Don’t leave the deactivated field blank if you want the user to remain deactivated. Leaving the field blank activates a user’s account.
When you have the CSV ready with updated user data, upload the CSV through the Users page using the Import feature.
Click on top left corner of the screen.
Click Settings.
Under the People category, click Users. The Users page will show you a list of all of your Gladly users. For ease, you can also see a preview of roles assigned to users, the number of Teams and Inboxes they belong to, and their account status.
Click Export. This downloads a CSV of all your existing users to your local folder.
Open the CSV and find the users you need to edit.
Note – Do not edit user rows you do not want to change/update.
Edit the following information in each column as needed. Columns with an * are required.
Column A (name)* – Edit the user’s full name.
Column B (email)*– Edit the user’s email address.
Column C (roles)* – Enter the role(s) you want assigned to the user. If you’re assigning more than one role for a user, separate each role with a comma and a space right after each role. For example, adding Administrator and Compliance Administrator gives the user Administrator and Compliance Administrator permissions. See Roles and Permissions to learn more.
Column D (inboxes) – Edit the Inbox (or Inboxes) the user should be a member.
To add an Inbox, enter it as one Inbox. For example, Returns.
To add multiple Inboxes, use commas with a space to separate the Inbox names and add quotes to isolate them. For example, “Returns, Refunds, Design Services.”
Column E (teams)– Edit the Team (or Teams) the user should be a member of. Use commas with space right after to separate the Team names.
Columns F (deactivated) – Edit whether the user’s access to Gladly should be activated or deactivated. Enter Yes to deactivate a user’s access to Gladly (until you’re ready to activate them). If you want the user active in Gladly from the start, enter No into the field or leave the field blank. You can skip the column entirely if you want all your users activated.
Columns G (stationId)– Only use this column if you’re using an external phone system instead of Gladly’s built-in Voice; otherwise, you can skip this column entirely.
An error message like the one below may appear if the upload encounters an error.
Click Download issues (CSV).
Open the User Upload Error CSV, which will have two rows:
Row – Displays the row number based on the recent CSV upload
Error – Issue that caused the error
Open the recently uploaded CSV (do not sort or filter the columns) and compare the row number from the User Upload Error CSV to find the user with the error.
Review and fix the errors and attempt to upload the updated CSV using the Import feature again.
Follow the suggestions below based on the error you receive.
Upload Error – File Size Exceeds 5MB
What it means:
If you see the error message above, it means your file exceeds the 5MB size limit.
What you should do:
Reduce the size of your file by splitting your spreadsheet into one or more separate files.
Invalid Roles
What it means:
The role is not recognized by Gladly. Confirm the role is correct and is spelled properly.
What you should do:
Correct the role column.
Mandatory Column(s) Missing
What it means:
A user must have an email and role before they can be added to Gladly. If your spreadsheet doesn’t have a column for email and/or roles, it will be considered invalid and won’t be uploaded.
What you should do:
Add the missing email and/or roles column(s) to your spreadsheet, complete with your Agents’ corresponding information.
Upload Incomplete
What it means:
There are errors in the information you provided in your spreadsheet, e.g., a misspelled email address or a non-existent Inbox. We’ll provide you the Error report identifying the issues blocking the upload in cases like these. Some examples of errors include:
email field cannot be blank
roles field cannot be blank
email must be a valid email address
invalid roles
inboxes not found
What you should do:
Let’s say you uploaded a file with (i) a missing email address in the 2nd row, (ii) a misspelled inbox name in the 3rd row, (iii) an invalid email address in your 4th row, and (iv) a blank role in your 5th row, like so:
The Error Report would look like this:
Create a new spreadsheet with the correct user details and upload the new file.
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.