15 Zoho CRM Configurations Your CRM Police Should Check

Most businesses implement Zoho CRM and then leave it alone. They assume that because it was set up correctly once, it will continue working correctly forever. That assumption is expensive.

Users change. Processes evolve. Extensions get outdated. Permissions drift. Workflows fail silently. And when the data coming out of the system stops being reliable, the business stops trusting the system — and the entire investment starts eroding.

This guide covers 15 configurations that someone in your organisation — your CRM Police — needs to review on a regular basis. The CRM Police is not a technical role. It is a detailed, organised person who cares about data integrity and system health, and who knows how to identify problems and escalate them to the right people.

If no one in your business owns this function today, that is the first thing to fix.

For a complete implementation foundation, see our Zoho CRM implementation guide

What Is the CRM Police?

The CRM Police is the person responsible for making sure your Zoho CRM is operating correctly — both on the configuration side and the data side. They do not need to be a developer or a Zoho expert. They need to be methodical, detail-oriented, and empowered to flag issues and follow through on resolving them.

Their job breaks into two areas:

Configuration health — making sure the system’s settings, automations, and architecture are working as intended.

Data quality — making sure the records in the system are accurate, complete, and consistent.

This guide covers the configuration side. A companion guide covers the 18 data points that the CRM Police needs to verify on the data side.

We introduced the CRM Police concept in our Zoho CRM Leads Guide — if you have not read that guide yet, it provides the operational context for why this role exists and what it costs businesses that do not have it.

Configuration 1 — Users

Go to: Setup → General → Users

This is the starting point for every configuration audit. Two things to verify.

Headcount accuracy. Former employees who have been offboarded but still have active accounts in the CRM retain access to company data. That is a security risk. Every departing employee’s account should be deactivated immediately — not eventually.

The permission system. Below each user’s name you will see two things: their Role and their Profile. The Role controls what data they can see. The Profile controls what they can do. Both need to be accurate for every user in the system. If your team is not clear on the distinction between roles and profiles, that is worth addressing before the next user is onboarded.

PRO TIP: Every employee should also complete their Personal Settings — name, email, phone number, and time zone. These details are pulled dynamically into email templates, so when James sends an outbound email, his contact information populates automatically. If his profile is incomplete, the template breaks. The CRM Police should verify this for every user, not ask employees to do it themselves.

One additional item: the email signature. This is not set on the personal settings page — it lives under the email compose window. Employees need to be walked through this step individually.

Configuration 2 — Email Deliverability

Go to: Setup → search “Deliverability” → Email Deliverability

Every line on this page should show a green check mark. Anything that does not is a problem. The most common gaps are domain authentication and DMARC configuration. If your domain is not properly authenticated, your outbound emails will land in promotional folders or spam — consistently, silently, and with no error message to alert you.

KEY INSIGHT: Email deliverability failures are invisible from inside the CRM. Your salespeople believe their emails are being sent and received. They are not. Verifying authentication is non-negotiable.

For a step-by-step walkthrough of email authentication setup, the ABR YouTube channel has a dedicated tutorial covering the full process.

Configuration 3 — Email Configuration Per User

Go to: Setup → Email → Email Sharing

This page shows the email configuration status for every user. You are looking for two things:

Configuration type — each user should show as configured, typically IMAP. Any user showing as “not configured” means their emails are not syncing with the CRM.

Sharing setting — must be set to Public. Even a properly configured account with private sharing will not make emails visible on records.

When email is not syncing, two things break. The full email history for a customer record becomes incomplete, making it impossible for AI tools like Zia to provide accurate summaries. And when an employee leaves the company, their email history with customers disappears from the system.

The CRM Police should not send employees a link and ask them to configure it themselves. Sit with them on a screen share and do it together.

Configuration 4 — Email Relay

Go to: Setup → Email Deliverability → Email Relay

By default, automated emails — those sent by workflows, Blueprints, and mass email campaigns — do not go through your configured IMAP mailbox. They go through Zoho’s internal email infrastructure. That system is functional, but it uses shared IP addresses rather than your domain, which affects deliverability for high-volume or reputation-sensitive sending.

An email relay routes all outbound email, including automated messages, through your own mail server. For businesses where email volume and deliverability matter, this configuration is worth the investment. Your IT team or a certified Zoho consultant will need to set it up.

Configuration 5 — Calendar Integration

Go to: Setup → search “GoogCalendar” or “Office 365” depending on your platform.

Calendar integration ensures that every meeting booked through your calendar system appears automatically on the relevant CRM record. When it is working correctly, a meeting with a lead shows up in that lead’s activity feed without anyone manually logging it. It also enables automated triggers — a reminder to the customer 30 minutes before a meeting, a prompt to the salesperson to send meeting notes afterward.

Every user needs to complete this authentication individually. The CRM Police should walk each team member through it rather than sending instructions and hoping for the best.

Configuration 6 — Phone Integration

Phone integration operates on two levels: call logging and call recording.

Call logging means every inbound and outbound call is automatically recorded in the CRM against the relevant contact or lead record. No manual entry. No gaps. The full call history for every customer relationship is in the system.

Call recording goes further. When a dispute arises over what was said in a sales conversation, the recording is the source of truth. Recording retention matters — most phone systems retain recordings for a maximum of 90 days. For most businesses, that is not enough. Problems surface after three months. By then, the recording is gone.

KEY INSIGHT: Call recordings are the foundation for AI-driven sales improvement. When you combine transcripts from calls, meetings, and emails for closed-lost deals, AI analysis can identify patterns in why deals broke. Without the recordings, you have no raw material to work with. The data you do not capture today is analysis you cannot do tomorrow.

Our AI consulting services cover exactly how to connect AI transcription and analysis tools to your Zoho CRM call recording data.

Configuration 7 — Lead Conversion Mapping

Go to: Setup → Modules and Fields → hover over Leads → click the three dots → Lead Conversion Mapping

When a lead is converted, the information in the lead record needs to flow correctly into the contact, account, and deal records it generates. Lead conversion mapping controls which fields transfer to which destinations.

Any field showing “None” across all destinations means that data will be permanently lost on conversion. There is no way to recover it after the fact.

The CRM Police should go through every field in this mapping and confirm that the fields worth preserving are mapped to the right destination module. Fields that are genuinely irrelevant post-conversion can stay unmapped. Fields that matter — anything from lead source to custom qualification data — need a destination.

Configuration 8 — Data Backups

Go to: Setup → search “Backup” → Data Backup

Zoho CRM offers scheduled backups. The recommended free option is twice per month. The backup produces two downloadable files: one for data and one for attachments. Both should be downloaded and stored in a secure location outside of Zoho — a separate cloud storage environment that remains accessible if Zoho has an outage.

PRO TIP: Backup files are only available for download for 7 days after they are generated. If you miss the window, that backup is gone. The CRM Police should have a standing calendar reminder to download and store both files every two weeks.

The value of backups becomes real when something goes wrong: an accidental mass deletion, a workflow error that corrupts records, or a need to restore a previous state of the data. Having a recent, verified backup is the difference between a recoverable situation and a permanent loss.

Configuration 9 — Profiles and Roles

Go to: Setup → Security Control → Profiles (and Roles separately)

The default Standard profile in Zoho CRM ships with permissions that most businesses should not leave in place. Two in particular warrant attention:

Delete permissions — standard users should not have the ability to delete records. Deletion is irreversible and almost never appropriate for a frontline sales user.

Export permissions — the ability to export records is a data security risk. Employees with access to export can take a full copy of your contact database with them when they leave.

The correct approach is to clone the Standard profile, rename it to match the role (for example, Sales), and remove the permissions that should not apply. You cannot delete the default profiles, but you can avoid assigning anyone to them.

On the Roles side, the hierarchy controls visibility. A manager can see the records of everyone below them in the hierarchy. A salesperson cannot see their manager’s records. Design the hierarchy to match your actual reporting structure.

Configuration 10 — Workflow Rules

Go to: Setup → search “Workflow Rules”

The CRM Police should review every workflow in the system on a regular cadence. For each one, click the three dots and select View Usage. This shows how many times the workflow has executed successfully, how many times it has failed, and how many are currently queued.

Two patterns to watch for:

Workflows that have not run in a long period of time — either the trigger conditions are never being met, or the workflow is no longer relevant and should be deactivated.

Workflows showing failures — these are automations the business believes are running but are not. Silent failures are among the most damaging issues in a CRM system because they create a false sense of operation.

The CRM Police does not need to diagnose or fix workflow failures. Their job is to identify them and escalate to a certified Zoho consultant or internal developer. But they need to look.

Configuration 11 — Marketplace Extensions

Go to: Setup → search “Marketplace” → Installed tab

This page shows all extensions currently installed in your Zoho CRM and flags any that require attention — typically meaning an update is available or something is misconfigured.

Two things to manage here. Keep installed extensions up to date — when a developer releases an update, there is typically a reason: a bug fix, a compatibility change, or a new feature that requires updated configuration. Outdated extensions can cause silent failures or conflicts.

Audit for extensions that are no longer being used. Every installed extension adds fields, workflows, and system overhead. If a tool was tried and abandoned, removing it cleans up the system and reduces confusion for users.

ABR builds and maintains a range of purpose-built Zoho CRM extensions available on the Zoho Marketplace — each one maintained and updated on a regular cycle.

Configuration 12 — Modules and Fields

Go to: Setup → Modules and Fields

Two things to audit here.

The modules themselves. Zoho CRM ships with modules that many businesses do not use — Price Books, for example. Any module that is not part of your workflow should be toggled off. Unused modules create navigation clutter and give users more places to accidentally put data.

The fields within each module. Fields that are no longer relevant should be moved to the Unused Fields section at the bottom of the layout. They do not get deleted — they simply stop appearing on the record. Removing unused fields reduces cognitive load for your team and increases the likelihood that the fields that remain get filled in correctly.

PRO TIP: Zoho Canvas allows you to create role-specific views of a record — showing operations only the fields relevant to operations, finance only what finance needs, and so on. It takes investment to set up, but it is one of the highest-impact changes you can make to CRM adoption. When people only see what they need, they use the system better.

Configuration 13 — Pick List Values

Within each module layout, many fields are pick lists — dropdown menus with a defined set of options. Over time, these lists accumulate values that are no longer used, and they miss values that have become relevant.

The CRM Police should go through the pick list fields in each module and verify that the current values reflect how the business actually operates. Remove options that are no longer in use. Add options that are needed. Keep the lists clean.

One specific consideration for businesses using lead conversion: if a pick list field is being mapped from the leads module to another module on conversion, the values in both pick lists must be identical. A mismatch will cause the conversion to fail or the data to be dropped.

Enabling colours on pick list values adds a useful visual layer — green for positive, red for a problem, yellow for a warning, blue for neutral. Team members can assess a record’s status at a glance without reading the field value.

Configuration 14 — Layout Rules

Go to: Setup → Modules and Fields → select a module → Layout Rules

Layout rules create conditional behaviour on record forms: when a specific field value is selected, another field appears, is hidden, or becomes required. A common example is a Lost Reason field that only becomes visible when the Lead Status is set to Lost.

Layout rules that are misconfigured can block your team from completing records correctly. The CRM Police should review each rule and verify that the conditions and outcomes still reflect the intended workflow. Rules that are no longer relevant should be deactivated or removed.

Configuration 15 — Reports and Analytics

Go to: Reports or Analytics section of your Zoho CRM

Most businesses accumulate reports and dashboards over time without ever cleaning them up. The result is a reports section full of outdated, unused, or irrelevant views that nobody looks at.

The CRM Police should audit the dashboards assigned to each role and verify two things: that the dashboards each role sees contain the information they actually need, and that those team members are using them. A dashboard nobody opens is not a dashboard — it is clutter.

For each role in the business — owner, manager, salesperson — there should be a configured homepage that surfaces the metrics most relevant to their function: orphaned leads, response time averages, pipeline by stage, conversion rates by source. The data is available. The job of the CRM Police is to make sure it is organised and visible to the people who need it.

Quick Reference: 15 Configuration Checks

Configuration	What to Verify
1. Users	Active accounts match current staff; roles and profiles correctly assigned
2. Email Deliverability	All checks show green; domain is authenticated
3. Email Config Per User	All users configured; sharing set to Public
4. Email Relay	Configured if automated email deliverability is a priority
5. Calendar Integration	All users authenticated; meetings syncing to records
6. Phone Integration	Call logs automatic; recordings captured and accessible
7. Lead Conversion Mapping	All relevant fields mapped to correct destination modules
8. Data Backups	Running on schedule; files downloaded and stored externally
9. Profiles and Roles	Delete and export permissions removed from standard users
10. Workflow Rules	No silent failures; inactive workflows identified and reviewed
11. Marketplace Extensions	All extensions up to date; unused extensions removed
12. Modules and Fields	Unused modules toggled off; unused fields removed from layouts
13. Pick List Values	Values current and consistent across modules
14. Layout Rules	Conditional logic reflects current workflows
15. Reports and Analytics	Role dashboards configured and actively used

Next: The Data Side

Configuration health is one half of the equation. The other half is data quality. In the companion guide, we cover the 18 data points the CRM Police needs to verify on a regular basis to ensure that the records in the system are accurate, complete, and trustworthy.

A CRM with perfect configuration and poor data quality still produces unreliable reports and poor business decisions. Both halves matter.

Read Part 2: 18 Zoho CRM Data Quality Checks Your CRM Police Should Be Running

NOTE: Update this link to the actual Part 2 URL once published.

Need Help Building or Auditing Your Zoho CRM?

At Amazing Business Results, we are a certified Zoho Premium Partner with over 12 years of implementation experience. We build, configure, and audit Zoho CRM systems for businesses that need their CRM to actually work — not just technically, but operationally.

Our Zoho support packages include regular system health reviews, workflow audits, and a certified consultant available for exactly the kind of ongoing configuration monitoring this guide describes.

Explore our related services:

• Zoho CRM Implementation Services
• Zoho CRM Customisation
• Zoho Support Packages
• Zoho Consulting Services
• One-on-One Zoho Training

Book a free consultation

Start your free Zoho One trial (no credit card required): USA | Canada | Europe

Top Zoho Extensions: ABR on Zoho Marketplace

Zoho CRM Course: amazingbusinessresults.com/zoho-crm-course