How to Use Zoho CRM to Capture and Route Website Leads

The short answer: sign up from the right country so your data lands in the right data centre, import the leads you already have, build a web-to-lead form with a hidden source field and a captcha, create an assignment rule that hands each lead to a rep by source, add a scoring rule and a workflow rule that alerts the owner when a score rises, then embed the form and check the first week's leads, by hand or through Zoho's read-only MCP server.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

The job here is a common one for a marketing lead: a contact form on the website sends email to a shared inbox, someone forwards it, and a lead waits until a rep notices. Zoho CRM can take that form over, decide who owns each lead and tell the owner. For what the product is and costs, see the Zoho CRM glossary entry.

Before you build anything:

• Price the edition the routing needs. Zoho's own use case for routing by lead source is marked Professional and above. For example, four reps and you on Professional cost 5 x $23 = $115 a month billed annually, on the pricing page, checked on 24 October 2026.
• Start from the form you already have. List its fields and every page it sits on. Each field needs a matching CRM field, and each page becomes a value in a hidden field.
• Write down today's number. Pick one figure to beat, such as hours from form submission to a named owner, and measure the current process for a week before you switch.

What you need

• An account in the right region. Zoho assigns the data centre from the country chosen at sign-up, per its data centre page; for Europe that is Amsterdam, with Dublin as the secondary.
• Two permissions: Manage Webform for the form, per the webforms guide, and Assignment Rules & Threshold for routing, per the assignment rules guide.
• A consent basis for each field you collect. The form can carry a privacy policy checkbox and double opt-in; what you must ask for depends on your own legal advice.

Step 1: Import the leads you already have

Bring the existing list in first, so new form leads land beside it rather than duplicating it. In the Leads module, click the arrow next to Create Lead and choose Import, then upload a CSV, XLS, XLSX or VCF file of up to 25 MB, per Zoho's import guide. Choose Add as new and select a unique field, usually Email, so rows that match existing records are skipped. Map each column, or use Auto Map and check it. Import a small subset before the full file, and keep the original untouched by importing a copy.

Step 2: Build the web-to-lead form

Go to Setup, Channels, Webforms, choose the Leads module and click New Form, as the webforms guide describes. Last Name, Email and Phone are there by default, and Last Name cannot be removed. Drag in the fields your current form has.

Then add three things the old form probably lacked. A hidden field, such as Lead Source set to the page name, so you know which page produced each lead. A reCAPTCHA v2 checkbox, available on paid editions, registered with Google for the same domain as the form. And a privacy policy checkbox, which the form will not submit without.

Step 3: Set the form's details

Enter the form location URL, the page where the form will live; Zoho accepts submissions only from the listed domains, which keeps out spam. Add a landing page URL for after submission. Turn on double opt-in if you want visitors to confirm their email before the record is created, which needs the primary email field on the form. If your site already runs a cookie banner, the guide explains that you can connect it through Zoho's cookie APIs instead of showing Zoho's banner.

Step 4: Route each lead to an owner

Go to Setup, Automation, Assignment, and click Create Assignment Rule for Leads. The use case article builds one rule entry per lead source, each naming an owner and a follow-up task for that owner, and notes that ownership can rotate round robin instead. Each entry takes up to 25 criteria. Then return to the form and select this rule as its record assignment rule.

Step 5: Score the leads

Go to Setup, Automation, Scoring Rules. A rule adds or subtracts points when a field or behaviour matches. Zoho's scoring guide gives its own B2B illustration: 7 points for opening an email, 15 for clicking a link within the last 3 days, 10 for attending a training. Start with three or four criteria you can defend, such as company size and the page the lead came from.

Step 6: Tell the owner when a lead heats up

Create a workflow rule in Setup, Automation, Workflow Rules. Zoho's workflow guide lets a rule fire when a record is created or when its score increases, and the instant actions include an email notification, a task, or a message in Slack or Cliq. A score trigger suits this job: the rep hears about a lead once it is worth a call, not with every form.

Step 7: Embed the form and go live

Copy the code from the form's final screen as HTML source, embed code or an iFrame, and place it on the pages you listed. With an iFrame, the webforms guide says reCAPTCHA domain validation has to be disabled. Submit a test lead from each page and check that the hidden source, the owner and the follow-up task all arrived.

Step 8: Review the first week with an agent

Zoho publishes four MCP servers for AI agents. Connect only the read-only Data Insights server to an MCP client such as Claude Desktop, following Zoho's setup page, and sign in through the OAuth prompt. Then ask a question the routing has to answer, such as how many leads were created last week by lead source and owner.

The agent drafts the summary; a person checks it against the Leads list view before changing any rule. The agent inherits your permissions, per Zoho's MCP page, and its calls spend the account's API credits like any API call. Leave the Data Operations server off for this job: its documented actions include deleting records in bulk.

Mistakes Zoho's guides warn about

• Testing routing with leads you typed in. Assignment rules apply to records from import, web forms and the API only, not to records created by hand, per the assignment rules guide. An unconfirmed user is never assigned a lead either.
• Choosing the wrong workflow trigger. The trigger cannot be changed after the rule is saved, so a wrong choice means a new rule.
• Gaps in the import file. More than ten consecutive empty rows end the file, and rows after them are not imported.
• Updating instead of adding. The import guide says added records can be undone but updates to existing records cannot be reverted.
• Self-managed cookie consent without the API calls. Zoho treats that as a rejection of consent, so form analytics stay empty.

A help centre exists to get more of the product switched on, and every feature it teaches is one more reason to stay a tier up. Read the edition line at the top of an article, where it has one, before you plan a step around it.

FAQ

Which edition do I need for this?

Web forms with captcha need a paid edition, and Zoho's routing use case is marked Professional and above, so plan on Professional. The free edition can still hold a test run of the import and the form.

Can one form feed several reps by region?

Yes. Add a country or region field to the form and create one assignment rule entry per region, each with its own owner, as the use case article does for lead sources.

How do I see what an import changed?

Go to Setup, Data Administration, Import, Import History, and open the import to see which rows were added, updated or skipped, per the import guide.