Pipe in data from an organizational hierarchy to your action.
By leveraging contextual attributes in organizational hierarchies, you can tie rules to the organization's structure rather than specific individuals or resources. This lets you create a few rules that can handle different situations flexibly and close the feedback loop more efficiently, instead of many rules for specific scenarios.
Example
You are a clothing store with multiple locations. A customer calls your support line about a defective item they purchased at your Vancouver location. The agent opens a case. After two days with no action, the action emails the Vancouver store's manager about the pending case.
The action is configured to email a particular node in the organization's structure. It pipes in the manager's email associated with the Vancouver store, as defined in the organizational hierarchy. Since the organizational hierarchy contains the contact information for all locations of your business, you only need to configure one action to handle the same situation across all locations. If the manager of one store changes, you can update the organizational hierarchy with the new manager's email, without needing to make changes to the rule.
-
When setting up an action, click the
Insert Variable button.