Implementing approval workflows in Zendesk is straightforward, but success depends on understanding native capabilities before considering extensions.
As SweetHawk noted in a recent Gravity CX webinar, workflows can range from a simple setup in 5 minutes to a complex, multi-step process taking up to 5 days. The primary difference lies in workflow design rather than configuration.
The most unsuccessful Zendesk approval implementations result from design issues rather than configuration errors. Before accessing Zendesk or installing Marketplace apps, document your entire approval workflow:
Clarifying these details typically takes 30 to 60 minutes per workflow type and will prevent significant rework later. Each approval type, such as IT access requests, HR leave, procurement sign-off, and vendor onboarding, requires its own logic map.
Zendesk’s built-in Approval Requests feature is recommended if you are on an eligible plan and your approval logic is straightforward.
Eligible plans: Employee Service Suite Growth and above, or Customer Service Suite Professional and above.
In the Zendesk Admin Centre, navigate to Objects and rules, then Approvals. If you are on an eligible plan, the approvals configuration panel will appear. If it is not visible, verify your plan tier, as this feature is restricted to certain plans.
In the Approvals panel, configure the following settings:
Zendesk now supports group-based approvals, allowing any member of the designated approver group to respond. This feature is useful for covering leave and shared responsibilities. Refer to Zendesk’s approval request release notes for the latest updates.
Before deployment, test the workflow from both the agent and approver perspectives:
A common mistake is assuming that approvals function correctly solely based on configuration. Always test with an actual email to a real approver, rather than relying on an admin panel walkthrough.
If you require any of the following, approvals will not be efficient:
For these requirements, use SweetHawk Approve or a custom API integration.
SweetHawk Approve is a Zendesk Marketplace app that adds a dedicated approval panel to each ticket. It is widely used in Australian Zendesk environments and is compatible with all Zendesk Support plans, not only higher tiers.
In Zendesk Admin Centre, navigate to Apps and integrations, then Marketplace. Search for “SweetHawk Approve” and install the app. A SweetHawk licence is required; visit sweethawk.com for current pricing and licensing details.
After installation, SweetHawk adds an approval panel to your tickets. In the SweetHawk admin settings, configure the following:
SweetHawk offers advanced capabilities beyond native Zendesk, particularly for sequential approvals:
For conditional routing based on ticket values (such as request amount, department, or request type), set conditions in the SweetHawk template configuration. This usually involves mapping a Zendesk custom field value to an approver assignment rule.
Instead of creating separate approval templates for each team, department, or cost centre, SweetHawk supports dynamic approver routing. The template references an organisation or user field in Zendesk, allowing the app to determine the approver at the time of the request and route accordingly.
This is worth setting up from the start if your organisation has more than 2 or 3 approval routing rules, or if your team's structures change regularly.
SweetHawk sends approvers a branded email with a single approve or reject button. Approvers can respond without logging into Zendesk, and no Zendesk licence is required.
Key settings to configure:
SweetHawk records every approval event, including requests sent, approved, rejected, and escalated, with timestamps and approver identity. Ensure the audit log is active and accessible to your compliance team in the required format.
For Australian financial services, healthcare, or government organisations, this is often a mandatory pre-go-live check.
Test every approval chain before go-live, including rejection paths and escalation scenarios. These edge cases often reveal configuration gaps. Once the setup is complete, conduct a brief agent training session. While the SweetHawk panel is intuitive, agents should know which template to use for each request type and how to proceed if an approver does not respond.
Starting with the tool before designing the logic. Configuring approvals in Zendesk before mapping the workflow leads to rework. Spend the time up front.
Treating all approval types as a single workflow. HR, IT change, and procurement approvals each have distinct approver structures, compliance requirements, and escalation paths. Build separate templates for each, rather than combining them into one flow.
Not testing the approver experience. Most configuration testing happens from the agent side. Always test from the approver’s side: the email prompt, the approve/reject action, and what happens next, before rolling out.
Underestimating compliance requirements early. Teams may begin with basic approvals and later be asked for an audit trail. If you operate in a regulated industry, design for compliance from the outset, even if it is not immediately required.
Running both native and SweetHawk without a clear policy. While both approaches can operate in parallel, a lack of clear guidelines leads agents to default to their preferred tool. Standardise on one approach per workflow type.
Approval workflows are rarely standalone. In a mature Zendesk environment, they connect to:
For a technical comparison of native Zendesk and SweetHawk capabilities, refer to Native Zendesk vs SweetHawk: Technical Comparison before deciding which approach to use.
For native Zendesk Approval Requests, a basic single-approver workflow can be configured and tested within a day. For SweetHawk Approve, a simple single-stage workflow can be live in as little as 5 minutes, as noted by SweetHawk in a recent Gravity CX webinar. More complex workflows may take up to 5 days. Multi-step chains with conditional routing and dynamic approver fields are more complex. The design phase, including mapping logic, approver groups, and edge cases, usually takes longer than the configuration phase.
No, for both native Zendesk and SweetHawk, approvers receive an email with an approve or reject button and respond without logging into Zendesk. This is important for organisations where approvers are senior stakeholders or department heads who aren’t active Zendesk users.
Yes, but this approach is not recommended for production use. Triggers and side conversations can approximate approval notifications, but lack structured outcome tracking, audit logs, and native ticket status updates based on approver responses. Teams relying solely on triggers often encounter fragile workflows that fail as approval logic becomes more complex.
SweetHawk Approve works with Zendesk Support plans at various tiers. Check SweetHawk’s documentation and the Zendesk Marketplace listing for current compatibility. Native Zendesk Approval Requests, by contrast, require Employee Service Suite Growth or Customer Service Suite Professional as a minimum.
Side conversations let agents loop in an external party (an approver, colleague, or vendor) via email or Slack from within a ticket. But the response is captured as a message thread, there’s no structured outcome, no automatic ticket update, and no audit record beyond the conversation log. Approval workflows (native or SweetHawk) are purpose-built: they capture a structured yes/no decision, automatically update ticket status, and create a traceable record.
Successful approval workflows in Zendesk depend on your specific use cases, compliance requirements, and current configuration. Our team partners with enterprise and mid-market organisations in IT, HR, finance, and procurement to design and implement scalable Zendesk approval workflows.
Want to see it in action? Watch the replay at our Online Webinar Hub. From there, navigate to the on-demand section to see how you can expand your Zendesk with Sweethawk.