Approval EAP Feedback | Community
Skip to main content

Approval EAP Feedback

  • March 21, 2025
  • 1 reply
  • 0 views

We appreciate the opportunity to provide feedback on your Approvals EAP. This functionality is a critical addition for Zendesk.

 

After upgrading our custom theme and installing the EAP in our Sandbox environment, we identified a key issue: the requirement for end-users to access the help center to approve requests. Our users are accustomed to approving requests directly from email. When attempting to approve via the help center, users were unable to view pending requests. Our users rarely log in to the help center. Therefore, end-users must be able to approve or deny requests directly from the email notification, eliminating the need to access the help center.

 

Additional Feedback:

  • Group Approvals: Implement the ability to assign approvals to a group, allowing any authorized member to approve requests. This ensures timely approvals, even when specific individuals are unavailable.
  • Multiple Approver Groups: Enable the creation of multiple approver groups, reflecting the diverse approval workflows across our product lines. This is crucial for scenarios requiring multiple levels of authorization.
  • Reporting & Audit: We require comprehensive reporting on approvals for audit purposes. This includes data on the type of access requested, the approver, approval duration, and the number of approvals sent, approved, and denied, categorized by product.
  • Pre-populated Approval Requests: Allow pre-population of approval requests with data from the ticket form, including custom fields. Configurability is essential to accommodate our multiple products.
  • Mixed User Types: Support sending approval requests to both end-users and light agents, enabling direct approval from email for all user types.

1 reply

Jamie15
  • June 6, 2025

We agree with all of these feature requests.

 

To build on the pre-populated:

We'd like 1

1.  To be be able to trigger an approval request based on a ticket (and requester profile attribute) like we can do for a Side Conversation 

2.  To be able to create an approval request via a macro that could set the To:, Subject and body.

3.  To add comments and attachments from the main ticket conversation, like you can do with a Side Conversation.