How to set up Salesforce approval processes that actually get used

Let's cut to the chase: most Salesforce approval processes die in the inbox. I've seen them in retail, healthcare, and manufacturing orgs—complex, buried in Setup, and ignored because they don't solve real pain points. Here’s how to build approval flows that *actually get used*, based on 10 years of enterprise deployments.

Start with the "Why," Not the "How"

Don’t jump to "Create Approval Process" in Setup. First, ask: *"What’s the business risk if this isn’t approved?"* If the answer is vague ("It’s a policy"), scrap it. In a healthcare client, their "marketing campaign approval" process was ignored until we tied it to compliance: *Unapproved campaigns risked HIPAA violations*. The new process triggered a mandatory step for legal review before launch. Usage jumped from 12% to 98% in 30 days.

Keep It Simple: One Step, One Goal

Enterprise orgs over-engineer approvals. A manufacturing client had a 7-step process for purchase orders over $5k—requiring finance, procurement, and two managers. Result? POs sat unapproved for weeks. We reduced it to: 1) Finance (for budget), 2) Procurement (for vendor). No more. We added a *mandatory* field on the PO: "Reason for Exceeding Budget" (a picklist: "New Vendor," "Urgent Need," "Forecast Error"). Finance *only* reviewed budget, not the reason. Approval time dropped by 70%.

Automate the Nudges (Don’t Rely on People)

Approvals fail when people forget. In a SaaS company, reps weren’t approving client contracts because they were buried in their queue. We implemented:

• Two email reminders: 24 hours and 1 hour before deadline
• A Lightning component on the contract record showing "Pending Approval: [Name]"
• Approval routing based on role hierarchy: If a manager is on vacation, auto-escalate to their manager *in the same org*, not a generic "Manager" group

Result: 95% of contracts now approved within 24 hours. No more "I forgot" excuses.

Validate with Real Data (Not Assumptions)

Before deploying, check if the process matches actual usage. Run this SOQL to find records *currently* waiting for approval (and why they’re stuck):

SELECT Id, Name, OwnerId, CreatedDate 
FROM Approval 
WHERE Status = 'Pending' 
AND CreatedDate > LAST_N_DAYS:30 
ORDER BY CreatedDate DESC

In a financial services client, this revealed 120 pending approvals for "Travel Reimbursement" where the approver had left the company. We auto-removed those records and added an "Approver Unavailable" button in the UI. Now, the process handles exits gracefully.

Make It Feel Like a Workflow, Not a Hurdle

Approvals should integrate into the user’s *current* task flow. In a retail client, purchase requisitions were approved in a separate tab. We embedded the approval step *inside* the requisition form. Users saw: "Approve this request (30s)" right after saving. No context-switching. Usage went from 35% to 92% in one sprint.

Remember: An approval process is a tool, not a gate. If it slows people down *without* preventing real risk, it dies. Build it around *actual* business outcomes, automate the friction points, and keep it visible where users work. That’s how you get adoption that sticks.

Want to know if your approval processes are secretly dying in your org? Get a free health scan—we’ll show you hidden bottlenecks, unused flows, and exact steps to fix them. No fluff. Just actionable data.