Zoho SalesIQ website visitors into CRM without duplicate or junk leads

To move Zoho SalesIQ website visitors into CRM without junk, connect SalesIQ to Zoho CRM. Then let a visitor become a lead or contact only after they are identified and qualified. Zoho supports this directly. You can require approval before leads are added, score visitors by behaviour, and map visitor details to CRM fields.

A qualified visitor, in this guide, is a website visitor who has given contact details and has met a condition you defined. A lead score threshold is one such condition. A visit to your pricing page is another. Anyone who has not met it stays in SalesIQ and never touches your CRM.

The rest of this guide covers five things, in order:

• what the SalesIQ and Zoho CRM integration does
• the four routes by which a visitor becomes a CRM record
• how to qualify visitors with scoring and the Rings view
• how to gate records with approval and map visitor details to custom fields
• a worked example, troubleshooting and EU considerations

If you collect leads through web forms rather than chat, the companion guide on sending web leads into Zoho CRM with Zoho Forms covers that route.

Zoho SalesIQ is the live chat, chatbot and visitor tracking tool that sits on your website. Connecting it to Zoho CRM lets visitor details move into the CRM as leads or contacts.

The integration works in both directions. Visitors flow out of SalesIQ into Zoho CRM. CRM data flows back into SalesIQ, so operators can manage the CRM data they need inside the SalesIQ app. That means your team can prioritise visitors using CRM data without switching between the two products to check a prospect.

Three capabilities that matter for clean data

• During setup, you configure whether visitor details move to the CRM as a Lead or a Contact, including into custom fields.
• You can enable an approval step before leads are added, which Zoho positions as the way to avoid junk leads.
• The Visitor History tab can use Zoho CRM data to build custom views that filter out potential leads.

Every route you open from SalesIQ into the CRM is another source of possible records. Each route therefore needs the same qualification rules. For an overview of what the product covers, see the Zoho SalesIQ live chat and chatbot page.

A SalesIQ visitor can reach Zoho CRM through four routes, and each carries a different risk of junk records. Zoho's own description of the integration covers each of them. Knowing which routes are switched on in your account is the first step to controlling what lands in the CRM.

Route	Who decides	When the record is created	Junk risk if left ungated
Operator pushes the visitor from the chat window	A person, during the chat	When the operator chooses	Low to medium, depending on operator habits
Zobot adds the visitor as a lead	The bot's conditions	After the bot collects the required details and conditions are met	Medium, if conditions are loose
Automatic push with approval enabled	A reviewer	After approval	Low
Custom fields mapped during setup	Your integration settings	Fills fields on the lead or contact	Low for records, high for field errors

The operator route suits teams with staff watching chats. The Zobot route covers non-business hours or busy periods. Zoho explicitly suggests using Zobots to add leads when all operators are engaged. The approval route is your safety net for whatever the other two let through.

The fourth route does not create records on its own. It enriches them, so its risk is wrong or missing field values rather than extra records.

Lead scoring rules are SalesIQ rules that assign a score to a visitor when they meet a condition you define. A higher score indicates a higher probability of closing a deal. Zoho's own example adds 25 points when a visitor opens the pricing page. Scoring is how you turn "visited the site" into "worth a CRM record".

The Rings view is a SalesIQ dashboard that shows visitors on concentric rings, based on conditions you can customise. You configure filters for four rings. By default, priority drops from the inner ring to the outer ring. Visitors who match no criteria are cold visitors, shown as stars outside the rings and under the Cold Visitors tab in List view.

Building a custom preset

• Each operator can create five custom presets at most.
• You can combine conditions in each ring with AND and OR.
• One condition can hold several values, separated by commas.
• Editing the default conditions of a predefined filter makes SalesIQ treat it as a new custom preset.

The "By CRM values" filter appears only once SalesIQ is integrated with a CRM product. That filter lets you put known customers or open deals in the inner ring. Your operators then talk to them first, instead of creating fresh leads for people already in the CRM.

One caution: customisation rules set by an operator apply to that operator's account only. Agree one shared preset design, or each person will qualify visitors differently.

The approval step is the single most effective control against junk leads in the SalesIQ integration. Zoho states that you can avoid junk leads by enabling approval before leads are added to your account. You can also disable it, which is what many accounts do to save time.

Approval works because a person sees the record before the CRM does. That person can reject test chats, spam and visitors who gave a fake email address. They can also spot a visitor who is already a contact and should not become a new lead.

When Svennis sets this integration up, we keep approval switched on for the first weeks and ask one named reviewer to check each pending lead against existing CRM records. At clients, the duplicates we see usually come from operators pushing a returning customer from the chat window as a new lead.

Reducing duplicates before approval

Approval is easier when fewer duplicates reach it. Use the "By CRM values" filter so known contacts are recognisable in the visitor list. Use the Visitor History tab with CRM data to build custom views of potential leads, rather than pushing every chat. Brief operators to check whether a visitor already exists before they push them manually.

Once the reviewer rarely rejects anything, you can consider disabling approval. Keep it on for any route that still attracts spam.

Field mapping in the SalesIQ integration decides which visitor details land in which Zoho CRM field. During setup, you configure whether visitor details move to the CRM as a Lead or a Contact, and you can send them to custom fields. The mapping is what makes a pushed record useful rather than a bare name and email address.

Decide the fields before you connect the two products. Create each custom field in the Leads or Contacts module first, then choose it in the integration settings. Keep the list short. Every field you map is data someone must keep accurate, and a wrong value misleads the next person who opens the record.

Using mapped CRM data back in SalesIQ

Mapped CRM data also works in the other direction. The Visitor History tab can use Zoho CRM data to build custom views that filter out potential leads. Custom trigger actions based on Zoho CRM values can send a chat invite or show a custom banner through the invoke JS API when a known visitor lands on your website.

Give one person, usually the CRM administrator, ownership of the custom fields and their names. Any change to those fields then goes through someone who also checks the integration settings.

Take a company that sells to businesses in several EU countries and has one website with a pricing page. The team wants three things: chats during office hours, a bot at night, and only serious prospects in Zoho CRM. Here is how the settings fit together.

1. Connect SalesIQ to Zoho CRM and choose Lead as the record type for new visitors.
2. Create the custom fields "Interest" and "Branch" in the Leads module and map visitor details to them in the integration settings.
3. Add a lead scoring rule that gives 25 points for a visit to the pricing page, following Zoho's own example.
4. Build a Rings preset: inner ring for visitors matched "By CRM values", next ring for high scores, outer rings for everyone else.
5. Configure a Zobot to collect name and email outside office hours and add the visitor as a lead only when the score condition is met.
6. Enable approval, with the sales manager as the reviewer.

The result is a narrow funnel. A visitor who reads one blog post stays a cold visitor in SalesIQ. A visitor who reads pricing, chats with the bot at night and leaves an email becomes a pending lead. It carries "Branch" filled in and waits for one approval. An existing customer shows up in the inner ring, so an operator recognises them rather than creating a second record.

You can extend the same setup with custom triggers based on CRM values. These send a chat invite or show a banner through the invoke JS API when a known visitor lands on the site.

Clean data needs clear ownership: for every route into the CRM, one person or rule is responsible for the record it creates. Without that, two operators chat with the same visitor and both push a lead. Or the bot and an operator both act on the same night-time conversation.

SalesIQ gives you one direct control here. Operators can hide visitors already contacted by other operators in their department, using the toggle "Hide visitors connected to other operators". Switch it on for every operator in a sales department, so each visitor has one person talking to them.

A simple ownership split

• Operators own visitors they chat with during office hours and decide whether to push them.
• The Zobot owns visitors outside office hours or when all operators are busy, within the conditions you set.
• The approval reviewer owns the final decision on every automatic lead.
• The CRM administrator owns the custom fields and their exact names.

Once the lead is in Zoho CRM, your normal CRM rules for assignment and follow-up take over. If those rules are not yet settled, the Zoho CRM implementation page explains how Svennis approaches them. A bot that qualifies visitors is one part of wider AI-supported lead management, which the sister site covers separately.

The most common SalesIQ and Zoho CRM problems are visibility problems, not lost data. Zoho community threads show leads arriving correctly in the CRM while a visitor view inside one product stays empty. Check the points below before assuming the integration is broken.

• Visitors online view empty. One user reported new chats in SalesIQ and new leads in Zoho CRM, yet the visitors online view did not work. Confirm the tracking code is on every page, not only the chat code.
• Visitor Online widget in CRM missing for one user. Another user had two people who were administrators in both products, and the widget showed for one and not the other. Compare the two users' setups side by side.
• "By CRM values" filter missing. That filter only appears after SalesIQ is integrated with a CRM product.
• "Plan downgrade" message. It appears when you use a predefined option tied to an integrated CRM or Campaigns product whose plan has expired.
• Asked to contact your admin. Associate and supervisor roles see that message and cannot fix the setting themselves.

Also plan for the widget change. Zoho states that the old SalesIQ live chat widget will be deprecated on 30 November 2026. Test your triggers and bot flows on the current widget before that date.

For an EU company, every SalesIQ visitor you push into Zoho CRM is personal data under the GDPR. The qualification rules in this guide therefore do two jobs. They keep the CRM clean, and they limit the personal data that reaches it to people with a real business reason to be there. The tracking data SalesIQ keeps on other visitors is personal data too, which is why its retention period matters.

Agree three things with whoever handles data protection in your company before go-live. First, which visitor details move to CRM fields and which stay in SalesIQ. Second, which routes feed the CRM. Third, who approves leads and how long unqualified visitor data is kept.

SalesIQ tracking stores information on the visitor's device. Every member state requires consent for that unless it is strictly necessary, so set up your consent banner before tracking-based scoring goes live. National authorities differ on the details, so also check the guidance in each country where you run a site.

Selling across languages

SalesIQ supports 30 languages for both Zobot and Answer bot. A company selling in several member states can run the same qualification flow in each language. It can then map the country or branch to a custom CRM field, as in the worked example. One flow with a "Branch" field is easier to maintain than separate setups per country.

If you are still deciding whether Zoho CRM or a lighter tool should receive these leads, the comparison of Zoho Bigin and Zoho CRM sets out where each fits.

Start with the controls that prevent junk, then add automation. Most of the steps below take a short session each in the SalesIQ and Zoho CRM settings.

1. List which routes into the CRM are active today: operator push, Zobot, automatic push.
2. Switch on approval and name one reviewer.
3. Define your qualification condition, such as a pricing page visit plus an email address.
4. Build one shared Rings preset that uses "By CRM values" for existing customers.
5. Create the custom CRM fields, then map visitor details to them in the integration settings.
6. Turn on "Hide visitors connected to other operators" for each sales operator.
7. Review rejected leads after a few weeks and tighten the conditions that let them through.

If your CRM already holds duplicates from earlier imports, clean those first. Otherwise the "By CRM values" filter will match visitors to the wrong records. The guide on migrating to Zoho CRM without losing sales history covers that clean-up. When you are ready to set up SalesIQ itself, the Zoho SalesIQ page explains how Svennis configures it alongside Zoho CRM.

• Zoho Community: Automate lead generation using SalesIQ and CRM integration
• Zoho SalesIQ help: Visitor Tracking
• Zoho Community: Visitors online don't working
• Zoho Community: SalesIQ Online Visitor not displayed in CRM