Edward Schriger

This is good advice.

It would be nice if there was an easy-to-find article that provides a syntax reference for the notification email body editor.

My assumption is there are many markup items that could be used in addition to this one.

Feature Request Summary: 

As a Zendesk Admin/Product Owner I need better reporting and metrics on user sign ins, email validation responses and general usage activity.

Description/Use Cases: 

We recently bulk uploaded about 300 new users into our Zendesk "space". We assumed it would be relatively straightforward to get reporting and visibility into engagement with our outreach. We manage a restricted Zendesk space - need a sign in for access.

- # of users/users who validated their emails - and did not

- # of users/users who actually signed in - and who has not signed in

We wanted this not only in dashboard widgets but in actionable outputs so we could then communicate to those who did not respond; resend their sign up link, remind them to take action etc.

Business impact of limitation or missing feature:

If you don't know who isn't signing in/validating you can't send them reminders.  You're just stuck.

Other necessary information or resources:

The answer is in Explore but it's not a straight line to get there.

Like a lot of Zendesk functionality, regardless of the search I did, I could not lcoate information about how to obtain this visibility.

Service requests to support were met with the usual stonewalling. "Go read this article" or an answer so full of featurespeak it made no sense.

Ultimately, after raising the urgency and stomping my email feet a little, a resource helped me determine that the User information I was looking for is in the Support/Tickets entity in Explore.  Not super intuitive that I would find it there and not super easy (10 days?) to get to the answer.

So the feedback here is two-fold (FWIW).

1. The Explore datasets aren't intuitive to work with

2. Support around this (and general Zendesk support) is suboptimal. 

My CX in this regard is that smiley-face emoji with the straight line mouth.  My expectations were not met.

I am upvoting as well.   But since this item is from 2019 will it ever be addressed?

The User Segment configuration does not appear to be working as expected or its purpose is entirely unclear.

Our case.  We have 2 basic user segments: Clients and Employees,  Then there are our agents and light agents who need to be able to see Guide content across both user segments.

We expected to use "Organization" to make the distinction.  Add all the Client organizations to the User Profile; any contacts in those organizations adopt the profile.

The problem is that there is a limit on the number of organizations you can add to the profile.

So then we tried tagging all of the Client users and organizations with "Client" and tried to use "Users and Organizations matching ANY of these tags".  This flat out didn't work.

The article above doesn't answer the question.

I have the same general use case.

• Forms 1-4
• External Users of Segment A
• External Users of Segment B
• Segment A users can see/use Forms 1,2
• Segment B users can see/use Forms 1,2
• My internal agents have visibility across both User Segments

I would vote for this.  There are certain situations where we want to collect a date that may:

1. Be past, today or future
2. May only be in the past (something already happened)
3. May only be today or in the past (something already happened)
4. May only be today or in the future (something is going to happen)
5. May only be in the future (something is going to happen)

On our platform we collect a lot of requests notifying us of something that is going to happen in the future.  We don't want to accept a past date.

These options don't exist on my profile page.