Approvals are requests that agents make on behalf of other agents and end users. Agents send requests to approvers. Approvers are other agents or end users who have the authority to review the request information and make a decision.
- Increase agent efficiency: Approvals in Zendesk remove the need for manual interventions or dependence on external applications.
- Ensure compliance: Track approval decisions within Zendesk to ensure adherence to your organization’s compliance policies.
- Maintain quality control: Add an approval step into your organization’s standard operating procedures to uphold quality assurance.
- Provide transparency: Requesters and approvers have visibility into the status of approval requests.
This article provides an overview of approvals and how they work in Zendesk. It describes who can make approval requests, who can approve requests, and examples of how approvals are used in both customer service and employee service cases.
This article contains the following topics:
- About the approval request process
- Understanding who makes requests and who approves requests
- Approval request examples
Related articles:
About the approval request process
The main steps of the approval request process consist of the following:
- An agent creates an approval request from a ticket in the Agent Workspace.
- The agent then sends the request to an approver. An approver can be either another agent or an end user.
- The approver receives an email notification
- The approver then responds to the request by approving
or denying.
End user-approvers respond to requests from the help center, while agent approvers respond from the Agent Workspace.
- The agent who created the approval request receives the approver’s response.
The image below illustrates an overview of the approvals workflow:
There may be times when the request process doesn’t follow these exact steps. For example an agent may withdraw a request before or after it’s approved.
Understanding who makes requests and who approves requests
Agents make approval requests on behalf of other agents and end users. They create requests on tickets they’re working on from the Agent Workspace and send them to approvers.
Agents may want to create a request when there is a ticket assigned to them that requires approval from someone else. For example, tickets requesting access to software or tickets requesting refunds beyond a certain threshold. See Creating and managing approval requests to learn more.
Approvers are users who have the authority to review approval request information and make a decision. They respond to requests, but are not acting to solve an issue.
Both agents and end users can be approvers.
- On the Zendesk Employee Service Suite, all agents and
end users are employees of the same organization. In this
context, agents are employees with an agent seat and can
access the Agent Workspace in Zendesk Support to respond to
approvals.
End users, or employees without an agent seat, have access to your organization's internal help center where they can respond to approvals.
- On the Zendesk Suite, agents respond to approval requests from the Agent Workspace. In this context, end users are requesters and are generally not part of the same organization as the agent. However, end users, or requesters, can still approve requests.
See Responding to an approval request to learn more.
Approval request examples
Approvals are available on both the Zendesk Suite and Zendesk Employee Service Suite. Depending on how your organization uses Zendesk, you can use approvals for both customer service and employee service needs.
Some examples of how you may want to use approvals include:
- Software and hardware procurement and access
- Employee promotions or job changes
- Long-term leave requests
- Payroll issues
- Refunds
For example, say your organization uses the Zendesk Employee Service Suite. A new employee in your company needs access to software and opens a ticket. An employee with an agent seat can create an approval request on the new employee’s behalf in the Agent Workspace and send it to an approver for review. In this example, the approver could be the new employee’s manager or another employee in your IT department. The other employee may or may not have an agent seat.
Alternatively, if your organization uses the Zendesk Suite, you can also request approvals to resolve customer service tickets. For example, an agent has been assigned a ticket requesting a refund. They need authorization to proceed with the refund so they create an approval request and send it to an approver in your organization. The approver in this example may be the agent's team lead.
In all of the examples above, the approval decisions are tracked in the approval request on the ticket and in messages on the ticket conversation so that you can keep track of approvals in your organization.
10 comments
mfg
A few questions:
1
Scott Tynan
This is great!
A few questions:
Can an approval be assigned to a group? (To allow anyone in that group to approve it)
Can a ticket have multiple approvals? (We often need to seek approval from different operational teams before responding to a customer)
For end users can an approval be assigned to an organisation rather than a specific user?
Is there a way to identify users (or groups) as being “approvers” so that organisations with 100's of end users can have the correct people assigned? (our agents wouldn't always know who in a customer organisation has the authority to approve things).
If an approval was to be assigned to an Organisation, could it be restricted to only notify and be shown to the people identified as “approvers”?
1
Martha De La Paz Castro
This is an awesome start!
I love the simplicity of creating the approval and the workflow behind it.
We have a couple complex Approvals workflows that need to have prefilled fields before being sent out to the recipient (Agent or End-user). Along with the questions already asked, I'd like to suggest a few features:
1
Rahul Narsinghani
mfg thanks for the feedback and questions. Here are the responses for the same:
1
Rahul Narsinghani
Scott Tynan - We are glad that you liked it. Here are the responses to the questions and feedback.
If an approval was to be assigned to an Organisation, could it be restricted to only notify and be shown to the people identified as “approvers”?
CC Jian Wei Liau
2
Rahul Narsinghani
Martha De La Paz Castro - This is great feedback and we are glad that you liked our simple design of creating approval requests.
We also understand the complex needs for Approval workflows to be pre-configured and triggered automatically.
We shall consider all of the great feedback in future prioritisation and development plans.
1
Liv
Is reporting on the roadmap for approval requests?
I think people may want to see a breakdown of how many approval requests are being sent out, how many approved/denied (and if denied - what was the reason?)
Additionally, people may also want to understand how long it has taken for an approval request to be responded to, after it's been sent. This would be a good feature to see.
1
Sana Stephens
Approval Template
Right now the approval request is very simple which is nice. However, if we could apply an approval form, with required fields that would be great. We have multi-brand and we also have multiple products within a brand. It would be nice if we could restrict the Approval Request icon to certain brands/forms that require approval. In addition, many of our approval request are around SOW so the ability to attached the SOW/document would be nice.
Approval User Types:
Agents: In most cases, light agents would be approvers (for example, managers or executives) that don't answer tickets but need to give approval. It would be nice if both Full and Light agents can be approvers.
End Users: Like above, we'd need the ability to assign end users to an approval group(s) within an organization. If only 1 approval group is allowed per organization, we'd need to have the option to send to that group, or add 1 or more people from the approval group. There could be different sets of approvers based on the type of approval request.
End User Email Approval:
Not all organizations allow end users to access the support portal. Therefore all contact with the client is via email, we'd need a way to email the approval request to the end user and not force them to login to the support portal to approve or deny the request.
Reporting:
It would be good to have a way to report on approvals in reporting and the dashboard. We create scheduled dashboards for a few clients and where a client requires an approval process we need a way to track approvers for an organizations but also who approved a specific request, denied requests, # of requests on a ticket, # of withdrawn request, withdrawal reason.
Multiple Approvers: We have two examples of this type.
1. We need more than 1 approval on a ticket like the above request, i.e. more than one department needs to give approval. It would we nice if we could add an order to the multiple approvers as well, meaning it would first need to be approved by say InfoSec, before going to Legal. If it is denied by InfoSec then the approval from Legal wouldn't go out until the issues with getting InfoSec to approve it is resolved.
2. We only need 1 person to approve it but we'd want the option to send it to multiple people to approve. Any one of them can approve it. We'd also want the ability to set a trigger notification, so once it was approved, all approvers emailed requesting approval are informed that the request was approved and no additional action is required at this time.
1
Rahul Narsinghani
Thanks Liv for insights and feedback. Your feedback is very valuable for us.
We understand that Reporting is an important feature and it is certainly in our roadmap.
We will certainly look at it during our prioritising and planning for the future development of this feature.
0
Rahul Narsinghani
Hi Sana Stephens, Thank you for the detailed feedback and insights, this is very valuable for us.
We loved the way you have taken the effort and provided detailed feedback, this is super helpful for us.
We will certainly consider all of the insights in our next prioritisation activity and future development planning.
For this EAP, Approvers can be light agents, Agents or Endusers.
We do understand your needs to attach the documents to the approval request. Also, ability to configure Approval workflows that can be sent to multiple departments sequentially.
Ability to approve via email, and also reporting needs.
For End users, in EAP, you can give them access to Helpcenter, and they can approve it from Helpcenter(Guide) as they do not have access to the Support Portal.
CC Ashwin Raju
0