Recent searches


No recent searches

About approvals and how they work (EAP)



image avatar

Colleen Hall

Zendesk Documentation Team

Edited Feb 06, 2025


2

10

10 comments

A few questions:

  • Does an ‘approver’ need to have a paid seat? 
  • Is ‘approver’ a new role?
  • How does this differ from a side conversation? 
  • Does it use a separate / new API endpoint?

1


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


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: 

  • being able to build a workflow of an approval based on a trigger (fields, status, etc…) and have the recipient pre-selected based on the fields.
  • multiple approval recipients  
  • ability to add more than an Approve button. Example: Denied, “Other”, and more custom buttons. 
  • ability to adjust the security and permissions of the specific approval based on team/group/form/etc…
  • additional fields to add for the recipient to see and make the appropriate decision
  • branding of approval, recipients see that it's from a no-reply email or custom email instead of the agent/end-user/requester name
  • feature that allows the approval to be sent to themselves
  • customizable tags for the approvals 
  • allow public/internal comments for the recipient and the sender

 

1


mfg  thanks for the feedback and questions. Here are the responses for the same: 

  • Does an ‘approver’ need to have a paid seat? 
    • For now, Approvers can be Agents or end users, and if the approver is an end user (they can make approval decision from helpcenter (Guide), then no paid seat, if the approver is an Agent, then agent seat. 
  • Is ‘approver’ a new role? 
    • No.
  • How does this differ from a side conversation? 
    • Approval Request is different from side conversations and has the decision to be made, whereas side conversations are conversations.
  • Does it use a separate/new API endpoint?
    • Yes, Approval requests have a separate API 

1


Scott Tynan  - We are glad that you liked it. Here are the responses to the questions and feedback. 

 

  1. Can an approval be assigned to a group? (To allow anyone in that group to approve it)
    1. Not in EAP, but we will certainly consider this an important feedback to do Group approvals in future. 
  2. Can a ticket have multiple approvals? (We often need to seek approval from different operational teams before responding to a customer)
    1. Not in EAP, but multiple approvals is certainly a good feature to be added in future. We will update on this based on future prioritization. 
  3. For end users, can an approval be assigned to an organisation rather than a specific user? 
    1. Not in EAP. 
  4. 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).
    1. This can be solved by Admin configuring the Approval workflows and the approvals being triggered automatically so Agents need not configure. This is not available in EAP, but we will certainly consider in future plans. 
  5. 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. This is important feedback and we will have to think of it when designing Approval requests being sent to Organizations. 

    CC Jian Wei Liau 

 

 

2


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


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


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.

  • By adding an approval template, we'd also like the option to assign our own tags based on the type of approval.

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.

  • Where a user is part of multiple organizations, we'd need the approval request to first look at the organization assigned to the ticket to pull the approval users/groups, not all the approval groups across all the organizations the users is under.

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


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


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


Please sign in to leave a comment.