| Announced on | Rollout starts | Rollout ends |
| June 29th, 2022 | June 29th, 2022 | July 1st, 2022 |
We’re excited to announce two improvements to Support that will make it easier to identify and search for suspended users and unverified primary email addresses.
What’s changing?
This release features changes to both theCustomerspage and adds two more search terms you can use to quickly narrow down your search results.
Changes to the Customers page
The Customer page now displays “Suspended” next to any suspended user's name.
If a user does not have a verified primary email address, an icon (
) is displayed next to the email address. If you hover over the icon, you’ll see the text “Unverified email”.
For more details, seeAbout the Customers (end users) page.
Leverage search capabilities
Use the following search operators to help you quickly identify suspended users and unverified primary email addresses:
- is_verified:false- Displays a list of all users with an unverified primary email address.
- is_suspended:true- Displays a list of all suspended users.
For more details, seeZendesk Support search reference.
What do I need to do?
You don’t need to take any action. However, if you’re interested in learning more, seeVerifying an end user’s email addressorSuspending a user.
7 Comments
Great stuff! My only wish is that it would show on all views of users. For instance, if I look at an org and switch over to the users associated with that org, I don't see the same things. I can only know that the user is suspended when I open the user. We create a lot of tickets with APIs and they fail if the user is suspended. When I look at the org, I don't see that they're suspended until I open the user. A minor thing, but it would be nice.
That's a great idea Lou - seeing feature parity on the org level list of users would be super!
Thanks for the great feedbackLouwe'll look into it!
Is it possible to filter out suspended users in Explore?
HiJustin Near!
目前,我们不哈ve an attribute yet in Explore that can identify which user is active or suspended. We do have a metric for suspended users but it can only count the suspenders, but no attribute that can accompany it to list the user details such as name and email address.
If you do know the end-user that you suspended, you can just exclude their email address from the report using the "Requester Email" attribute. If the ticket was submitted before the user got suspended, it will appear in the report. But if the user was suspended before the ticket was submitted, it wouldn't show up since tickets from suspended users don't count as tickets yet unless the ticket was removed from the suspended view.
Hope this helps!
Is is_suspended able to be used in import files to bulk update End users for example in the case of updates to a do not contact list?
Hello Sara,
I am afraid the suspended field is not an available field when doing the Bulk import user featurehere. You should be able to update this though via the API as indicatedhere.
Pleasesign into leave a comment.