Zendesk Approvals

Zendesk approvals cover refunds, discounts, access requests, anything with a signature attached. Zendesk was built for conversations rather than sign-offs, and the gap shows.

Start free trial All guides

What Zendesk approvals actually need

Strip the jargon and an approval workflow is four things.

A request with enough structured detail for somebody to judge it.

A named approver, chosen by rule rather than by asking around.

A decision that's recorded, with who and when, in a place an auditor can find.

A consequence. Approved means the work proceeds, rejected means it stops and the requester is told why.

Most homegrown Zendesk approval flows nail the first two and quietly fail the third. The decision ends up in a Slack thread, and six months later nobody can prove who approved a four-figure refund. That's the bit auditors ask about.

What Zendesk gives you natively

Be clear-eyed here. Classic Zendesk Support has no approval object. There is no field type that means "pending approval by this person", no built-in approve or reject button on a ticket, and no native audit surface designed for sign-offs.

Zendesk has been building approval capability into its employee service offering, which is the natural home for it, so check what your specific plan and product mix includes before assuming you have to build from scratch. That capability is not evenly available across every account and every tier.

If it isn't in your account, you're building the pattern out of the pieces you already have. Which is entirely doable, and the rest of this is how.

The pattern that works

Four components, and the discipline is in keeping it simple.

A field, not a conversation. Add an approval status field with the values Not required, Pending, Approved, Rejected. The status of a request has to be readable at a glance and reportable, and free text in a comment is neither.

Side conversations to reach the approver. A side conversation sends the request out by email or to a Slack channel without dragging the customer into it, and the reply comes back attached to the ticket. That gives you the record in the right place.

Light agents as approvers. Your finance manager doesn't need a full seat to look at a ticket and say yes. Light agents read tickets and add internal notes for free on the plans that include them, which is exactly the approver shape.

Triggers to enforce the consequence. When approval status changes to Approved, notify the assignee and move the ticket on. When it changes to Rejected, notify and set a tag. When a ticket has a refund over a threshold and no approval, don't let it quietly reach Solved.

Add an automation that chases a Pending approval after two days, because the single biggest failure of any approval flow is an approver who is on holiday.

Where apps earn their money

Marketplace apps exist that add proper approval mechanics: a real approve or reject action, multi-step chains, delegation, and an audit view. They are worth paying for when the approval is regulated, when more than one person has to sign, or when finance will be asked to evidence the decision.

They aren't worth it when you approve four refunds a week and everybody sits in the same room. A field and a side conversation covers that, costs nothing, and breaks less.

Whatever you use, keep the custom field as the source of truth. Apps get uninstalled. Fields survive.

When it belongs somewhere else

Some approvals are not support work at all, and forcing them into a customer helpdesk creates a mess that lasts years.

Signs you are in the wrong tool: the approval chain has more than two steps, approvers change based on cost bands or department hierarchy, the request has nothing to do with a customer, or you need a catalogue of request types each with its own approval rule. That is service management, and a purpose-built service desk models it natively instead of asking you to fake it with tags.

A reasonable middle ground is to keep customer-facing approvals in Zendesk, because the conversation lives there anyway, and move internal procurement and access requests into whatever tool your IT team already runs.

FAQ

Frequently asked questions

Is there a Zendesk approval app worth buying?

Several exist, and they earn their place once a Zendesk approval workflow needs an audit trail. A simple Zendesk manager approval process runs fine on a custom field and a side conversation, and the Zendesk approval process only needs an app when somebody has to prove who signed off.

Does Zendesk have built-in approvals?

Classic Support does not have an approval object. Zendesk has been adding approval capability on the employee service side, so check your plan. Most teams build the pattern with a field, side conversations and triggers.

Can a manager approve without a paid seat?

On plans that include light agents, yes. A light agent can read the ticket and record a decision in an internal note for free.

How do I stop tickets being solved without approval?

A trigger that checks the approval field on update, plus a view of tickets over your threshold with approval still pending. Enforcement needs both a rule and a pair of eyes.

Is a side conversation enough of an audit trail?

For low-value internal approvals, usually. For anything regulated, no. You want an explicit field value and a timestamped decision, not a thread somebody has to read.