Katharine King

Hi James,

We have a few different reasons we'd like to access this info in the ticket today, but ultimately having the org information in the ticket would help us build new workflows in the future. For example, if a user has both a personal account and an enterprise membership with us, any ticket they submit should be treated with enterprise-level SLAs since we do not require them to log in to submit a ticket.  

We'd also like to arm our agents with as much info as possible, and currently have a macro that pulls the primary org information onto the ticket for them, using Liquid to help direct them identify membership end dates and the like. 

We have many users who have multiple memberships. For each membership we create an organization in zendesk. Users don't necessarily know which organization to select if we made this field available, and we also need the ability for non-users to submit tickets without organization. 

When we have anew ticket from a user, we would love to be able to pull in every organization they're part of in Zendesk to an internal note. That way we could start our troubleshooting knowing that this user has multiple memberships. 

Right now {{ticket.requester.organization}} only pulls the first organization attached to the user, when I would need it to pull every organization. 

Ideally the output of the following would be "organization 1, organization 2, organization 3" if the users had 3 organizations on their user record.

{% for organization in ticket.requester.organization %}

{{organization.name}} 

{% endfor %}

Does anyone have a workaround for this or a way to identify the existence of multiple memberships attached to a ticket requester? 

We have webforms going through a third party product to filter into our zendesk tickets, recently the email that they enter with has been marked as spam multiple times. We've added both the domain and the exact email address to the whitelist, however after about a week these tickets end up in spam again. Any thoughts?