Zendesk Customer Lists
Zendesk customer lists are a saved slice of your user base, defined by conditions rather than by hand. Handy for bulk work, exports and knowing who you support.
What Zendesk customer lists are
A customer list is a set of end users matching conditions you define. Think of it as a view, except it returns people instead of tickets.
Lists come in two flavours. A dynamic list re-evaluates its conditions, so membership changes as your data changes and a user who gains a tag today joins today. A static list is a snapshot: fixed at the moment you built it, useful when you need the population to stop moving while you act on it.
The feature is plan-gated and has moved around Zendesk's packaging over time, so confirm it's included in your account before designing anything around it. If it is not there, most of what follows can be approximated with search and the API, just less comfortably.
What drives membership
Conditions are built on attributes of the person and the organization they belong to.
If you can't see a condition you need, the usual fix is to write the value onto the user first, as a tag or a custom field set by a trigger or your CRM sync, and then segment on that. It is more setup and it puts the logic somewhere you can audit.
The exact condition set differs by account, so open the builder and read what yours offers. One thing to know before you plan: lists segment people by who they are, not by what their tickets did. If the population you want is "everyone who raised a billing ticket last month", that starts in Explore or the search API, not here.
What you can do with a list
A list on its own is just a count. The value is what comes next.
Bulk actions. Add or remove tags, change organization membership, update fields across everyone in the list. This is the workhorse use and it saves hours of clicking. It also does real damage if the conditions are wrong, so check the count before you act and expect no undo.
One habit that pays for itself: export the list before any bulk edit. If the change turns out to be wrong, that export is the only record of who was in the population, and you'll want it. There's no undo button here worth relying on.
Export. Pull the list as a file for a mail merge, a migration, a data-cleanup project, or a spreadsheet someone in marketing genuinely needs.
Targeting outreach. Lists tell you who to contact about a breaking change or a deprecation. The sending usually happens in your email tool, and the segmentation happens here.
Knowing your base. Underrated. How many users have no organization? How many have never signed in? A list answers questions about data quality that nobody thinks to ask until an integration breaks.
Lists, segments, views and organizations
| Returns | Main use | |
|---|---|---|
| Customer list | End users | Bulk edits, exports, outreach targeting |
| User segment | End users | Gating help centre content visibility |
| View | Tickets | The agent work queue |
| Organization | End users | A permanent grouping tickets and reports inherit |
Using them without making a mess
Three habits worth adopting early.
Name lists so the condition is obvious from the name. "Enterprise, active, EU" beats "Marketing list 3" the day somebody else inherits your account.
Prefer dynamic to static. A static list is out of date the moment you save it, and someone will act on it in six months believing it is current.
Decide who is allowed to run bulk actions at all. That permission normally sits with admins, which is correct, and it's worth writing down in your onboarding notes rather than leaving people to discover it in the middle of an incident.
Review the conditions before every bulk action, every time, no matter how familiar the list is. The tag you're about to apply to nine thousand people cannot be taken back with one click. Segments for content visibility work differently and are covered in user segments, so do not assume the two share a definition.
Frequently asked questions
What can you do with a list once you have one?
Three things: a Zendesk bulk user update across everyone in it, a Zendesk user list export for analysis, and Zendesk user segmentation for Guide permissions.
What's a Zendesk customer list?
A saved group of end users matching conditions you set, used for bulk updates, exports and targeting. It returns people rather than tickets, which is what separates it from a view.
Are customer lists available on every plan?
No. Availability is tier-dependent and Zendesk has repackaged it over the years, so check what your account includes rather than assuming.
What is the difference between a customer list and a user segment?
Lists are for acting on people in bulk and exporting them. Segments control who can see which help centre content. Different jobs, similar-sounding names.
Can a list be based on ticket activity?
Conditions are built on user and organization attributes, not on ticket history. To segment by what people raised, start in Explore or the search API and tag the users from there.
Clean users, clean tickets
Duplicate user records split one customer's history in two, which is also how the same request ends up as two tickets nobody links.
Start free trial14-day free trial. No credit card required.