Trigger for Organization update
BeantwortetI am looking for a way to trigger a notification to a specific agent whenever an update has been made to an Organization that they own (ownership is tracked by tag).
That is - there are a few different use cases where a change could be made to an Organization, completely unrelated to any open ticket. For example, we track active support contracts through custom Organization fields. If there is a change to the contract status, this constitutes as an Organization update, and the "Updated" timestamp of the Organization changes. I don't need to know specifically what changed, only that "Your organization has been updated"
The only condition I find that is close to what I'm looking for is "Account Owner Updated" but that does not match all conditions where an organization would be updated. To satisfy this use case, I'm looking for a more generic "Organization Updated" that falls under the "Organization" category of the condition drop down.
Given that I'm not finding a condition like "Organization Updated", is there another way to do what I'm looking for?
-
Hi Stephanie -
Triggers are only checked when a ticket in Zendesk is created or updated, so unfortunately there's no way to notify an agent using triggers when an Organization is changed. Perhaps adding the Organization fields values to the default "Notify agent..." triggers could help, by reminding agents of the current account status of that customer? See Using placeholders and the Zendesk Support placeholders reference if you're not sure how to do that.
You can also let our product team know this is functionality you'd like to see by posting to our Feedback on Support forum - see Product feedback guidelines & how to write a good feedback post for suggestions on making your post as useful as possible. Thanks!
-
I also have this problem. Our help center and documentation hinges on information in the Organization to form proper segments. Since the segments require tags, and there is no automation around tagging either, you're basically completely out of luck if you want to be proactive and categorize your help content before someone has to open a ticket. When a record update is committed to the database, be it for a ticket, user, or organization, I see no reason why trigger rules can't be evaluated at that time.
Furthermore, it's annoying that the trigger builder lets you build and save a triggers that lack a ticket condition without any warning that they can't fire. That's just poor UX.
-
Our company also has a need to set the organization based on a ticket being created with a certain form. Our company contains coaches who lodge requests on behalf of multiple members. More than one coach can service a member or hospital. It makes it easier for them to see the log of communication at an organizational level in our help center for our coaches who can view all tickets in their organizations. It also helps our coaches when they are in the field to review this area to update our Dr's of their patients. We do not have the organization option open in our form as we extend this form to multiple hospitals and nurses who can also submit tickets on behalf of members.
My question is, is this something that is on the roadmap for the near future?
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
3 Kommentare