Firstly, here's a quick video showing you a use case of the Approvals App for Zendesk:
Be sure to check out our June 2017 release of the app and all of the improvements here.
To setup approvals, the first step is to define a list of approvers. To do this click on the approvals icon on the left of the screen and then at the top click on "Approvers". Then, to create an approver click on "Add approver" at the bottom.
Fill in the name and email. For the first approver, you won't be able to choose anything from the 'escalate' options because there's no one else to escalate too just yet. When you've finished, click on "Create User" at the bottom.
Continue to add all of the people you'd like to add as approvers. Where appropriate, use the "Escalate to" drop-down field to specify superiors. Using this method, if ever an approval needs to be escalated, it will only flow up the chain of command.
Creating Approval templates
An approval template is used to define what needs to be approved, who it will be sent to and when it should be sent. Based on the use case, there are many different ways approval templates can be setup, so we've created this article that with different videos to show the setup and process for each:
Approvals use cases + serial & parallel processes with video walkthroughs.
The most important thing to decide when setting up a workflow is whether you want your agents to be able to manually send an approval, or if you want to automatically send it using Zendesk triggers. In many cases, you may actually want to do both. For example. You could have a trigger send off an approval for all tickets submitted via the Travel Request form. However, if the ticket was sent in using a different form or another channel entirely, you may want to give your agents the ability to send the approval once the required information has been gathered.
Here are some checkpoints that help define the differences:
|How to setup manual approvals||How to setup automatic approvals (Videos)|
If you have any questions about how to build the correct workflow for your use case email us at email@example.com