Most businesses set up Zoho CRM with the default fields, add their contacts and leads, and then wonder why the team is still using spreadsheets on the side. The default Zoho CRM is a starting point, not a finished system. The power comes from customisation — and four features do most of that work: custom fields, custom buttons, workflow rules, and workflow actions.

This post explains each one, how they connect, and shows real examples from systems we have built for clients.

Custom Fields — Capturing What Matters for Your Business

Zoho CRM comes with standard fields: Name, Phone, Email, Company, Lead Source, Stage, and so on. These work for everyone, which means they work perfectly for no one. Your business has data points that are specific to how you sell and operate. Custom fields let you capture those.

Custom fields can be added to Leads, Contacts, Accounts, Deals, and all other modules. The field types available include:

  • Single line text — for short values like GST Number, PAN, registration number
  • Multi-line text — for notes, addresses, or longer descriptions
  • Picklist (dropdown) — for fixed options like Industry Type, Customer Category, Region
  • Multi-select picklist — where more than one value applies, like Product Lines Interested In
  • Date and datetime — for trial end date, contract renewal date, last site visit
  • Number and currency — for credit limit, annual turnover, outstanding balance
  • Checkbox — simple yes/no fields like Is Key Account, GST Registered
  • Lookup — to link records across modules, like linking a Deal to a specific branch

Real example from a manufacturing client: The standard Zoho CRM Contact record had no place to capture the GST number, the credit limit approved, or whether the customer was on 30-day or 60-day payment terms. We added three custom fields to the Account module: GST Number (single line), Credit Limit (currency), and Payment Terms (picklist: 0 days / 15 days / 30 days / 60 days). Once these were in CRM, the sales team could see payment terms before quoting, and the accounts team stopped having to call sales to ask the same question every month.

Where Custom Fields Live

Custom fields are added under Settings → Customisation → Modules and Fields → [Module Name] → Fields. You can drag and drop them into the layout so they appear in the correct position on the record screen. Fields not needed for most records can be placed in a collapsed section so they are available but do not clutter the default view.

One important design decision: do not create a custom field for every piece of information that exists. Create custom fields for information that will be used to filter, segment, trigger automation, or make decisions. Information that is only ever read by one person in one context belongs in a note, not a field.

Custom Buttons — Trigger Actions Without Leaving the Record

A custom button is a button that appears on a CRM record and does something when clicked. That something can be opening a URL, running a script, calling an API, or executing a Deluge function. Custom buttons make Zoho CRM feel like it was built for your business rather than a generic tool.

Custom buttons are created under Settings → Customisation → Modules and Fields → [Module] → Links and Buttons.

When creating a button, you choose:

  • Where it appears: List view (applies to selected records), Record detail view (appears on a single record)
  • What it does: Open a URL, run a Deluge script, or execute an SDK action

Real example — Send WhatsApp from a Deal record: A client's sales team was opening WhatsApp manually, copying the customer phone number, and typing follow-up messages after every deal update. We added a custom button called "Send WhatsApp Update" on the Deal detail view. When clicked, it opens a pre-filled WhatsApp web link with the customer's phone number and a message template that includes the deal name and current stage. One click instead of four steps. The team now uses it for every follow-up.

How to build it

WhatsApp Button on Deal Record

Button type: Open URL • Trigger: Detail view • URL: https://wa.me/${Mobile}?text=Hi%20${Account_Name},%20your%20deal%20${Deal_Name}%20is%20currently%20in%20the%20${Stage}%20stage.%20We%20will%20update%20you%20shortly.
Zoho substitutes the merge fields automatically when the button is clicked.

Real example — Generate PDF quotation: For a robotics leasing client, we built a custom button on the Deal record called "Generate Lease Quote." It calls a Deluge function that pulls the deal fields (customer name, asset type, lease term, monthly amount) and generates a formatted PDF using Zoho Writer template merge, then attaches it to the deal and sends it to the customer's email. What used to take 20 minutes of manual work in Word now takes one click.

Workflow Rules — When Something Should Happen Automatically

A workflow rule defines the trigger and condition for an automation. It answers the question: when should something happen, and under what conditions?

Workflow rules are created under Settings → Automation → Workflow Rules → Create Rule.

Every workflow rule has three parts:

  1. Module — which module does this rule apply to (Leads, Contacts, Deals, etc.)
  2. Trigger — when does the rule fire
  3. Condition — optional filter to limit which records trigger the rule

The Four Triggers

When a record is created — fires once when a new record is added. Use this for onboarding sequences, welcome emails, or assigning leads to sales reps based on territory.

When a record is edited — fires when a specific field changes. This is the most commonly used trigger. Use this when a deal stage changes, a lead status changes, or an approval field is updated.

When a record is created or edited — fires on both. Useful when the condition matters more than the moment of creation versus edit.

Based on date and time — fires at a scheduled time relative to a date field. Use this for renewal reminders, follow-up sequences, or escalations when no action has been taken within a time window.

Conditions

Conditions narrow down which records the rule applies to. Without a condition, the rule fires for every record in the module. With a condition, it only fires when the condition is met.

Example condition: Trigger = record edited • Condition = Stage changed to "Proposal Sent" AND Deal Amount is greater than ₹5,00,000 • Action = Notify sales manager by email with deal details.

Without the condition, the manager would get a notification for every single deal edit. With the condition, they only hear about high-value proposals — which is all they actually needed.

Workflow Actions — What Actually Happens

The workflow action is what Zoho does when the rule fires. There are six types of actions available:

1. Email Notification

Send an email to the record owner, a specific user, or the contact/lead themselves. Emails use templates you create in advance with merge fields pulled from the record. Use this for welcome emails, follow-up reminders, or internal alerts.

Real example

Lead assigned email

Trigger: Lead created • Condition: Lead Source = Website • Action: Email notification to assigned sales rep with lead name, phone, and the specific page they enquired about. The sales rep gets a formatted alert the moment the lead comes in, not when they next log into CRM.

2. Field Update

Automatically update a field on the record when the rule fires. This is one of the most underused features in Zoho CRM. Use it to stamp a date when a stage changes, set a priority level based on deal size, or update a status field when an action is completed.

Real example

Stamp the date a lead was qualified

We added a custom field called Qualified On (date field) to the Leads module. Workflow rule: when Lead Status changes to "Qualified", action = field update: set Qualified On to today's date. This gives the sales manager a clear record of how long each lead took to qualify, without anyone remembering to fill it in manually.

3. Task

Create a follow-up task assigned to a CRM user. Use this to ensure no lead or deal falls through without a next action. Every deal moving to a new stage can automatically create a task for the assigned rep.

Real example

Auto-create follow-up task after demo

Trigger: Deal stage changed to "Demo Done" • Action: Create task assigned to deal owner, due in 2 days, subject: "Follow up after demo — send proposal or close loop." The sales rep never has to remember to create this task. It appears in their task list automatically.

4. Tag

Add or remove a tag on the record. Tags are useful for segmentation — grouping records for bulk actions, reports, or campaigns without changing the main fields on the record.

5. Webhook

Send data from Zoho CRM to an external system via HTTP. Use this to trigger actions in other tools when something happens in CRM — like notifying a Slack channel, pushing data to a custom system, or triggering a Zoho Flow automation.

6. Function (Deluge)

Execute a custom Deluge script. This is the most powerful action type — it can do almost anything: create related records, call external APIs, send WhatsApp via API, update multiple fields at once, or perform calculations. If the other action types cannot do what you need, a function can.

Real example — auto-create a Zoho Books invoice when a deal closes: Trigger: Deal stage changed to "Closed Won" • Action: Deluge function that looks up the Account in Zoho Books, creates an invoice with the deal amount and product line items, and posts a comment on the CRM Deal record with the invoice number and link. The accounts team sees a Books invoice appear without the sales team doing anything. No handoff required.

How the Four Features Work Together

The real power is not in any one of these features alone. It is in how they connect.

Here is a complete example from a distribution client. The goal was to stop losing leads that needed a credit check before the first order could be placed:

  1. Custom field: Added Credit Check Status (picklist: Pending / Approved / Rejected) and Credit Limit (currency) to the Account module.
  2. Workflow rule trigger: When Account is created.
  3. Workflow action 1 — Field update: Set Credit Check Status to "Pending" automatically so no new account is ever overlooked.
  4. Workflow action 2 — Task: Create a task for the accounts team: "Complete credit check for [Account Name]" due in 24 hours.
  5. Second workflow rule: When Credit Check Status changes to "Approved".
  6. Action — Function: Deluge script that updates the credit limit field and sends an email to the assigned sales rep telling them the account is cleared and they can proceed with the first order.
  7. Custom button: A button on the Account record called "View Credit History" that opens the company's internal credit tracking sheet filtered by that account name.

The result: every new account goes through a credit check without anyone having to remember to initiate it. The sales rep knows the moment an account is approved. The accounts team has a task that cannot be missed. And the button gives instant access to the history without leaving CRM.


Want Zoho CRM configured for how your business actually works?

We implement and customise Zoho CRM for businesses across India, USA, UAE and Australia. If your team is still working around the system instead of through it, that is a configuration problem we can fix.

Talk to an Expert →