You know the drill. A sales rep closes a deal at 30% discount. Legal needs to sign off. The approval request lands in someone’s inbox. They’re in back-to-back meetings. Three days later, the quote is stale, the customer is frustrated, and someone’s chasing the approver in Slack.

This is the reality for most Salesforce orgs that haven’t invested in Approval Processes. And honestly? It’s one of the easiest automation wins you can implement—if you set it up right.

What Actually Are Salesforce Approval Processes?

Approval Processes are declarative automation that route records through a decision chain. When a record hits a defined entry criteria—say, an opportunity over $50K or a discount exceeding 15%—Salesforce automatically submits it for approval. Approvers get notified, can approve or reject from anywhere (mobile included), and the record status updates automatically when the chain completes.

No Flow. No Apex. No middleware. This is native Salesforce since Spring ’08. Most orgs use maybe 10% of what’s possible. The rest are still forwarding emails and pasting “Approved – see attached” into spreadsheets.

Why Approval Processes Beat Email Chains

Here’s the data: The average knowledge worker spends about 3.2 hours per week tracking down approvals according to a 2024 Gartner survey I’d actually trust. That’s roughly 160 hours a year—four full work weeks—lost to chasing signatures and waiting on someone’s inbox.

Compare email chains vs. Approval Processes side by side:

• Email chains: Forward three times. Reply-all to wrong people. Lost in spam folder. Zero visibility on status. No escalation. No audit trail.
• Approval Processes: Auto-routed. Sequential or parallel steps. Mobile-friendly. Full history tracked in ProcessInstance. Escalation timers built in. Admins see exactly where each request is.

The gap isn’t marginal. It’s the difference between your ops team firefighting and your org running itself.

Three Use Cases Where Approval Processes Shine

1. Discount Approvals Beyond Threshold

Your sales team has pricing authority up to 15%. Anything above needs manager sign-off. An Approval Process on the Opportunity object checks the Discount_Percent__c field. Over 15%? Auto-submits to the sales manager’s approval queue. Over 25%? Adds the VP of Sales to the chain. Over 35%? Requires CFO sign-off.

We implemented this for a B2B SaaS client with 50 sales reps. Their approval turnaround went from averaging 2.8 days to 3.4 hours. The biggest win? Reps stopped having to chase down managers in Slack to ask “did you approve that yet?”—they could see the status right on the opportunity record.

2. Contract Renewal Terms

A contract renews with a 20% price increase. The account owner submits it. Approval Process checks Contract Amount and Percent Change fields on the Contract object. If change exceeds 10%, routes to customer success director. If it’s a renewal under 12 months since last renewal, it also flags for legal review.

Rejected approvals send the record back with the rejection comments prefilled. No back-and-forth email thread where context gets buried. The submitter gets a Chatter notification and can resubmit with the requested changes. Each resubmission creates a new approval chain with full history.

3. Expense Report Approvals

Expense reports over $500 need manager approval. Over $2,000 need finance sign-off. Reports with specific categories (entertainment, travel, equipment) get parallel approval—finance AND department head both need to approve. If nobody acts in 72 hours, it escalates automatically to the VP.

This works in the Salesforce mobile app too. Your VP can approve expense reports while waiting for their flight. No email. No attachments. No “I’ll look at it when I get back to my desk.”

How to Set One Up (The 10-Minute Walkthrough)

Navigate to Setup > Process Automation > Approval Processes. Click “Create New Approval Process” and choose the standard wizard.

1. Name it clearly: Call it “Opportunity_Discount_Approval” or “Expense_Report_Approval” — not “Approval_v3_final”
2. Entry criteria: A formula that evaluates to true. Example: Opportunity.Discount_Percent__c > 15
3. Designate approver: Options include record owner’s manager, a role, a queue, or a specific user field. “Manager” is the most scalable choice for orgs
4. Add approval steps: Sequential (manager first, then VP) or parallel (finance AND ops both at once)
5. Set escalation: Timed escalation if no action within 24, 48, or 72 hours. Routes to next-level approver automatically
6. Define actions: On approval—update a field (e.g., Discount_Approved__c = True), send Chatter post, trigger email. On rejection—populate Rejection_Reason__c, send notification
7. Test in sandbox: Submit a real-looking record through the process, verify every step fires correctly
8. Activate: Once tested, flip the switch

Total setup time for a single-process chain: about 25-30 minutes for someone familiar with the interface. Plan for two hours if it’s your first time.

What Nobody Tells You About Approval Processes

Here’s the stuff you only learn after supporting this for a few years:

Approver field dependencies will bite you. If your entry criteria uses a lookup field to determine the approver, and that field is blank when the record hits the criteria, the process quietly fails. No error message. No notification. The record just sits there unapproved. Always add a validation rule that requires the approver lookup field before submission.

Recall is real but limited. Submitters can recall an approval request—but only if no approver has acted yet. Once someone clicks “Approve” or “Reject”, the chain is locked. You’d need a custom Apex override to add recall-after-first-approval behavior.

History tracking is automatic but buried. The data lives in ProcessInstance and ProcessInstanceHistory objects. You can build reports on it, but most admins don’t know those objects exist. Build one simple dashboard report early and save it—it’s worth the 15 minutes when audit season rolls around.

Mobile approvals need explicit permission. Approving from Salesforce Mobile requires the “Approve Requests” system permission. I’ve walked into three different orgs where someone built a beautiful approval process, activated it, and spent a week wondering why nobody could approve from their phones.

Entry criteria can reference cross-object formulas. This is an underused feature. Your Opportunity approval process can check Account fields, Contact fields, or even OpportunityLineItem data via formula fields on the Opportunity. You’re not limited to just the record being submitted.

When NOT to Use Approval Processes

I’m going to be direct: Approval Processes aren’t a silver bullet. Here’s where I’d recommend something else:

High-volume, low-value approvals. Expense reports under $50. Time-off requests for a half day. Office supply orders. These don’t justify the overhead of an approval queue with escalation timers. Use Flow with a simple Chatter approval instead.

Complex multi-path decisions. If your approval matrix has 12 different routes based on a combination of region, deal size, product line, and customer tier, Approval Processes will become a maintenance nightmare. You’ll spend more time updating approval steps than the feature saves you. Consider Apex or a CPQ tool with entitlement rules.

Real-time collaboration. Approval Processes are designed for structured, asynchronous sign-offs. If what you actually need is a quick back-and-forth discussion before a decision (“Should we give this customer an extra 5%?” “Let me check with finance”), use Chatter groups or a dedicated Slack channel instead. Don’t force an async tool into a real-time use case.

Approval Process vs. Flow: When to Use Each

A quick mental model I use with clients:

• Single manager sign-off: Approval Process. Native, zero-config, mobile-ready
• Multi-step escalation chain: Approval Process. Built-in timer-based escalation
• Complex field updates on approval: Flow. More flexible than Approval Process actions
• Approval requiring external system check: Flow + Approval Process. Flow checks the external system, then submits for approval
• Parallel approvals (two people must both approve): Flow + Approval Process. Native Approval Processes don’t support true parallel
• Full automation with no human touch: Flow by itself. Approval Processes always need a human approver

Your Move

If your org is still running on email-based approvals or manual spreadsheets, you’re burning time and creating compliance gaps. Approval Processes are declarative, well-documented, and take about an afternoon to set up for your top three use cases.

Start with one. Discount approvals are usually the easiest—they’re high-volume, visible, and the ROI is immediately obvious to the sales team. Set your entry criteria at 15% or whatever your threshold is, wire in the manager chain, test in a sandbox, and watch what happens.

Once you see how clean it works, you’ll start looking for other things to put through the process. Contract renewals. Purchase orders. Partner discounts. It’s contagious in the best way.

Need help designing your approval architecture or want a second look at an existing process? MotionDog.com — we help Salesforce teams stop chasing emails and start automating decisions.