Joel Hellman
Zendesk customer since 2015. I admin a few accounts and develop Zendesk apps.
- Total activity 1203
- Last activity
- Member since
- Following 31 users
- Followed by 14 users
- Votes 342
- Subscriptions 674
Comments
Recent activity by Joel Hellman Sort by recent activity-
Ok. In that case, {{ticket.requester.custom_fields.staff_id}} should work, as long as staff_id is the id of the user field on the current ticket requester. Mind not all placeholders are supported ...
-
Barry Neary please add me to your list.
-
@Константин-Чернышков: Did you mean that field "staff_id" to refer the current user (agent), or the ticket requester? Because it's not possible to reference a custom user fields for the current use...
-
Here is a follow-up/clarification on my tip for clearing the date by setting an unreasonable high (invalid) date. So, this only works for triggers (not automations), and only if the ticket is bein...
-
Nevermind, I found another post in the announcement that details this change.
-
Zendesk Support - New Stuff: We added additional information to tickets indicating if they were created 'From Help Center' or 'From Zendesk Support'. Other channel origins were already represented ...
-
Yeah, I see the same behavior on my end after some tests, it seems this workaround no longer works.
-
Hi Allan. You would need to use the API and developer resources, but if you already got that in place, maybe something like this: (I assume you are using the Help Center API to create user subscrip...
-
Hi Lance Neat idea, but no, I don't see how that would be possible. You might use liquid markup to generate some pseudo-random number, but that would be insecure and I really would advise against i...
-
Hi Anthony These fields are hard-coded and there is currently no way to modify them. You could instead add some fields into your trigger's email body on a trigger with the Email User action, but as...