Zoho CRM Approval Processes add a human review gate to specific CRM actions – before a deal can be marked Closed Won, a manager must approve it; before a discount above 20% can be applied to a quote, the VP of Sales must sign off; before a contact can be marked as a qualified lead, the lead qualification team must review. Approval processes prevent unauthorised actions, enforce compliance, and build accountability into CRM data quality. This guide covers how to set up approval processes, the types of workflows that benefit from approvals, multi-level approval chains, and what to do when approvals get stuck.
That structure helps reduce mistakes, but only if the approval path is designed around real business rules instead of unnecessary layers.
Zoho CRM approval processes are useful when a deal, discount, or operational change needs review before it moves forward. They turn one-off sign-off habits into a repeatable workflow that the team can follow consistently.
When to Use Approval Processes
Not all CRM actions need an approval gate – overusing approvals creates friction without value. Use approvals when:
| Scenario | Approval Gate |
|---|---|
| Large discount requested on a quote | Manager approval before quote is sent |
| Deal closed with unusual terms | Finance review before marking Closed Won |
| Lead converted to contact and deal | Lead qualification team reviews before conversion |
| Contact data shared with third party | Privacy/legal approval before export |
| New contact created as high-value account | Senior rep or manager assigned and reviews |
Setting Up an Approval Process
Navigate to Settings ? Automation ? Approval Processes ? New Approval Process. Select the module. Configure:
- Trigger condition: What triggers the approval requirement. Example: Deal Amount greater than $50,000, or Discount percentage greater than 15%
- Actions during approval: What happens while approval is pending. Options:
- Lock the record (prevent any edits while pending)
- Lock specific fields (prevent changes to the fields involved in the approval condition)
- No lock (the record remains editable)
- Approver: Who must approve. Options:
- A specific user
- The record owner’s reporting manager (based on the role hierarchy)
- A specific role
- Multi-level approval: Add multiple approval levels – first the direct manager, then the VP if the deal is above $100,000, then the CFO above $250,000
- On approval: Actions to trigger automatically when approved – field updates, workflow triggers, notifications
- On rejection: Actions to trigger when rejected – field updates, notification to the record creator, task to revise
Multi-Level Approval Chains
Enterprise deals often require sequential approval from multiple stakeholders. Configure a multi-level chain by adding approval levels in sequence:
- Level 1: Direct Manager ? must approve within 24 hours
- Level 2 (if deal > $100K): VP Sales ? approves after Level 1 is complete
- Level 3 (if deal > $250K): CFO ? approves after Level 2 is complete
Each level is notified only after the previous level approves. A rejection at any level stops the chain and notifies the originator.
Approving and Rejecting Records
Approvers receive an email notification and can approve or reject directly from email (if enabled) or from the CRM’s approval section:
- In Zoho CRM: navigate to the record awaiting approval, or use the global Approvals view (accessible from the navigation) to see all pending approvals in one place
- Approvers can add a comment explaining the approval or rejection decision – this comment is logged to the record’s timeline
- On mobile: the Zoho CRM mobile app supports approval actions – critical for managers who are often away from their desks
“The approval process isn’t triggering even though the conditions are met”
Check the trigger condition carefully – numeric field comparisons require that the field type in Zoho CRM is set as a Currency or Number field, not Text. If the Amount field is stored as Text, a comparison “greater than $50,000” won’t work correctly. Also verify the approval process is active (not in draft state) and that the user creating the record isn’t the designated approver – some configurations require distinct creator and approver accounts.
“The approver isn’t receiving notification emails”
Check: the approver’s email address in their Zoho CRM profile is correct and active; Zoho CRM email notifications aren’t being blocked by corporate spam filters; and the approval process notification settings have email enabled. Also verify the approver’s Zoho CRM account is active – inactive users don’t receive notifications. As a secondary channel, configure approval notifications via mobile push through the Zoho CRM mobile app, which often bypasses email deliverability issues.
“Records are stuck in pending approval – the approver approved but the record is still locked”
In multi-level approval chains, each level must be completed before the next triggers. If Level 1 approved but Level 2 hasn’t been notified, the record appears stuck. Check the approval process log on the record (visible in the record’s approval section) to see which level is currently pending. Contact the Level 2 approver directly if the notification was missed.
Sources
Zoho CRM, Approval Processes Documentation (2026)
Zoho CRM, Multi-Level Approvals Setup Guide (2025)
Zoho Community, Approval Process Configuration Issues (2025)
Zoho CRM Help Center, Record Locking During Approval (2025)
Maximising Field Productivity with Mobile CRM
Mobile CRM tools are most powerful when field reps integrate them into a structured daily routine rather than using them reactively. Small habit changes can significantly increase the quality and completeness of on-the-go data entry.
How long does it take to see measurable results after implementing a CRM?
Most teams see initial productivity improvements – reduced manual data entry, better follow-up consistency – within the first 30 days. Measurable impact on pipeline velocity and conversion rates typically emerges after 90 days, once sufficient data has accumulated to surface patterns and the team has moved past the learning curve.
What is the biggest mistake organisations make when adopting a new CRM?
Trying to replicate their old process exactly rather than redesigning for the new tool. The migration from spreadsheets or a legacy system is an opportunity to standardise definitions, eliminate redundant steps, and automate manual work. Teams that migrate as-is lose most of the potential value.
How should we handle contacts who exist in multiple systems?
Designate one system as the master of record for contact identity data. Sync from that master to other systems rather than maintaining parallel copies. Run a deduplication process before and immediately after migration, and configure duplicate detection rules in your CRM to prevent future proliferation.
What is a reasonable CRM adoption rate to target in the first 90 days?
Target 80% of your defined “core actions” being logged in the CRM by 80% of users within 90 days of go-live. Core actions should be limited to 3-5 specific behaviours (e.g., log every call, update deal stage after each meeting, create a contact for every new prospect). Measure completion rates weekly and address laggards individually.
When should a business consider switching CRM platforms?
Consider switching when: the current platform’s limitations are blocking more than one strategic initiative simultaneously; the total cost of workarounds (integrations, manual processes, additional tools) approaches the cost of migration; or the vendor’s roadmap has diverged from your business direction over two or more consecutive product cycles.
The strongest approval setup is the one that speeds up decisions without weakening control. If too many steps are added, people will start finding ways around the process.
Common Problems
Problem: Automation Fires on the Wrong Records Due to Loose Trigger Conditions
Overly broad workflow triggers enrol records that should be excluded, sending irrelevant emails or assigning incorrect tasks. Fix: Always pair every trigger condition with at least one exclusion filter. Before activating any automation, run it in test mode against your live database and manually review the first 10 matched records to confirm they are all appropriate targets.
Problem: Sequences Continue Running After a Deal Closes or a Lead Converts
Automated cadences that lack exit criteria keep contacting prospects who have already responded, creating a poor experience and wasting rep capacity. Fix: Add explicit exit conditions to every sequence – at minimum: deal stage = Closed Won/Lost, lead status = Converted, or manual unenrolment by the assigned rep. Test exit conditions explicitly before launch.
Problem: Approval Process Bottlenecks Slow Deal Velocity
Multi-step approvals designed to enforce governance often become the reason deals stall, particularly when approvers are unavailable or the routing logic is poorly defined. Fix: Audit approval process completion time monthly. For any approval step averaging more than 24 hours, introduce a delegate approver rule and an escalation timer that automatically escalates to a manager after a defined period.