Zoho SalesIQ live chat feeding CRM: the short answer
Zoho SalesIQ live chat feeding CRM works when you settle three things before you switch the link on. Decide which details a chat must collect, who owns the resulting record, and what source it carries. Get those right and each chat becomes one lead or contact with its conversation attached. Skip them and you get duplicates that nobody follows up.
Zoho SalesIQ is the chat and visitor-engagement product inside the Zoho suite, according to SleekAI's comparison of Zoho SalesIQ. It ships visitor tracking, lead scoring, CRM-linked routing and operator workflows. It feeds visitor sessions, lead routing and Zia AI replies back into the rest of the Zoho stack. You can read more about how we use it on our Zoho SalesIQ service page.
A lead is a person who has shown interest but is not yet a qualified customer. A contact is a person you already know and deal with. A chat from a stranger usually belongs in leads. A chat from an existing customer belongs on their contact record, not on a new lead.
This guide covers what SalesIQ captures, why duplicates appear, the decisions to make first, and how a Zobot collects the details. It then walks through one worked example, the checks to run after go-live, and what the setup means for a UK company.
What Zoho SalesIQ captures from a website visitor
Zoho SalesIQ identifies your website visitors and lets you talk to them by message, voice call or email. Acefone's overview of Zoho CRM integration describes it as an engagement platform. It interacts with visitors at different stages of the sales process through automated tools.
The useful data from a chat falls into three groups:
- Identity: the visitor's name, email address and phone number.
- Context: what they asked about, which you can store as custom information on the visitor.
- History: the conversation itself and the visitor session behind it.
Identity decides whether the chat matches someone already in Zoho CRM. Context decides who should follow up. History lets the salesperson pick up the conversation without asking the visitor to repeat themselves.
Zoho CRM brings a business's customer service, communications and information together in one place, Acefone notes. It can combine social media, live chat, voice calls and text messages on one communication platform. That only helps if each chat lands on the right record. A chat that creates a fresh, anonymous lead adds noise rather than context. If the terms lead, contact and record are new to you, our explanation of what a CRM is sets out the basics.
Why chat-to-CRM links produce duplicates and orphan leads
Duplicates appear when a chat reaches Zoho CRM without an email address or a rule for matching existing records. The CRM has nothing to compare against, so it treats every chat as a new person. A returning customer who chats three times can end up as three leads beside their real contact record.
Orphan leads are the second problem. An orphan lead is a record with no clear owner, or with an owner who never sees it. This happens when chat leads all default to one admin user, or to whoever set up the integration. The records exist, but nobody gets a task or a reminder to call.
A missing source is the third problem. When chat leads carry no lead source value, your reports cannot tell them apart from web forms, imports or trade show lists. You then cannot judge whether live chat earns its operator licences.
None of these problems is a fault in SalesIQ or Zoho CRM. Each one comes from a decision nobody made before the link went live. The fix is to make those decisions on paper first, then configure the bot and the integration to match them.
Six decisions to make before you connect SalesIQ to CRM
Settle the required fields, record type, owner, source, duplicate rule and bot-only chats before you touch any integration setting. The table lists each decision, the question behind it and a sensible default for a small sales team.
| Decision | Question to answer | Sensible default |
|---|---|---|
| Required fields | Which details must a chat have before it reaches CRM? | Email, plus name where the visitor gives it |
| Record type | Lead or contact? | Lead for unknown visitors; check for an existing contact with the same email first |
| Owner | Who follows up? | One written rule, such as the operator who chatted or the territory owner |
| Source | How will reports tell chat leads apart? | One fixed lead source value, such as "Website chat" |
| Duplicate rule | What happens when the email already exists? | Add the chat to the existing record rather than create a second one |
| Bot-only chats | Does a chat with no human operator count? | Only if the bot captured an email |
When Svennis connects SalesIQ to a client's CRM, we write the owner rule and the lead source value down and agree them with the sales manager before anyone opens the integration settings. The setups we see go wrong are almost always the ones where that conversation was skipped.
If your owner rule depends on region, set up territories in CRM first. Our guide to territory management in Zoho CRM explains how to make that assignment hold.
Collecting name, email and phone with a Zobot
A Zobot is a bot development platform on Zoho SalesIQ for building chatbots that automate customer interactions. That is how Zoho's guide to Zobot responses defines it. A Zobot is the cleanest way to make sure every chat collects the fields your CRM needs.
The Zobot features that matter for clean records are these:
- field_name: bot scripts use it to update the visitor's name, email, phone number and other details inside SalesIQ.
- Custom info: any information other than name, email and phone goes into the visitor's custom info section.
- Questions: a response type specific to SalesIQ Scripts. Each question map has the keys name, replies, input and suggestions.
- Suggestions: an array that accepts only a collection of comma-separated strings, shown as tap-to-answer options.
- Skippable: works with all input cards and shows a skip button beside the input widgets.
Use the questions response type to ask for email before anything else. Mark only the truly optional questions, such as phone, as skippable. Use suggestions for the enquiry type, because a fixed list of strings produces values you can report on later. Free text produces dozens of spellings of the same thing.
Zoho states that SalesIQ supports 30 languages for both Zobot and Answer bot. If you sell abroad, write your suggestion strings in each language you support. Keep the stored values consistent across them.
Handing a SalesIQ chat to a person with the forward action
The forward action passes a SalesIQ chat from the Zobot to a human operator who can handle the query. Zobot actions are the activities the bot performs while responding to visitors. Zoho lists seven values: reply, forward, operator_busy, context, block, pending and end.
Forward is the action that turns an automated chat into a sales conversation. Place it after the bot has collected the email address. The operator then starts with a known visitor rather than an anonymous one, and the record that reaches Zoho CRM already has its key field filled.
Two other details from Zoho's Zobot guide help here:
- context_id accepts only text, and its value must be the name of the matching context handler block. Name your blocks plainly, for example "collect_email", so the script stays readable.
- Scheduled end delays are cancelled if the visitor sends a message, an agent joins or the chat is handed to an agent. A handed-off chat will not close under the operator.
Operators also need the right tools in the console. A super admin sets up integrations in SalesIQ. The Zoho Lens integration for SalesIQ, for example, is added under Settings > Integration > Zoho Lens, and only super admins can connect it. Check you have that role before you plan an afternoon of configuration.
Worked example: one website chat becoming one owned lead
Here is a single chat followed from the website to Zoho CRM, using the settings above. The business is an imagined kitchen fitter with two salespeople. It has agreed "Website chat" as its lead source and "operator who chatted" as its owner rule.
- A visitor opens the chat on the pricing page. The Zobot greets them using the questions response type.
- The first question map has name "email", a reply asking where to send the quote, and an email input. The script writes the answer through field_name, so it updates the visitor's email in SalesIQ.
- The second question asks for a first name, also written through field_name.
- The third question offers suggestions: "Kitchen quote", "Existing order", "Something else". The visitor taps "Kitchen quote". The answer lands in the visitor's custom info section.
- The fourth question asks for a phone number. It is skippable, and the visitor skips it.
- The bot uses the forward action. Sarah, an operator, joins and books a home visit.
In Zoho CRM the result should be one lead, owned by Sarah, with lead source "Website chat". It should show the enquiry type and the chat transcript. If the email had matched an existing contact, the chat should have gone onto that contact instead.
Had the visitor picked "Existing order", the same flow would point to service, not sales. That is why the enquiry type comes before the handoff.
Checking Zoho CRM records after the SalesIQ link goes live
Run a short set of checks in Zoho CRM during the first week after the SalesIQ link goes live. Problems are cheap to fix while there are a handful of records and expensive once there are hundreds.
Work through these checks with a few test chats of your own, then with real ones:
- Every chat lead has an email address.
- Every chat lead has the agreed lead source value, spelled exactly the same.
- Every chat lead has an owner who is an active salesperson, not an admin account.
- A test chat from an existing customer's email lands on their contact, not on a new lead.
- The enquiry type from the Zobot suggestions appears on the record.
- The chat transcript is visible to the owner.
Build a simple CRM view or report filtered on the chat lead source. Sort it by created date and look for repeated email addresses. Our post on customising your CRM covers the fields and views you may need to add.
Ask the salespeople too. If they say chat leads arrive without enough context to call, the bot is asking too few questions. If visitors abandon the chat early, it is asking too many.
What a SalesIQ to CRM setup means for a UK company
For a UK company, three practical points shape the setup: operator licences, staffing hours and the chat widget version. None of them is hard, but each affects how many leads you capture and what they cost.
Operator licences
Zoho SalesIQ is priced per operator, and its AI capabilities sit on the higher tiers. Licence only the people who will actually answer chats. Let the Zobot handle out-of-hours visitors by collecting the email for a morning callback. If you are weighing Zia replies as well, our sister site's guide to AI for lead management covers where AI helps and where it does not.
Staffing hours
Most small UK sales teams cover the chat during office hours only. Design the bot so the forward action only runs when someone is available. Outside those hours, the bot should still create a clean, owned lead from the details it collected.
Widget version and personal data
Zoho announced that the old SalesIQ live chat widget would be deprecated on 15 May 2026. If your website still runs the old widget, move to the current one before you rebuild the CRM link. Chats also collect names, emails and phone numbers. Check with whoever handles data protection that your privacy notice covers chat, and decide who in CRM can see transcripts.
Next steps for connecting SalesIQ to Zoho CRM
Start with the decisions, not the settings. Use this order to get a working, clean link:
- Fill in the decision table above with your sales manager and agree the owner rule and lead source value.
- Confirm who holds the super admin role in SalesIQ.
- Check your website runs the current chat widget.
- Build the Zobot questions: email first, enquiry type as suggestions, phone as skippable.
- Add the forward action after the email question.
- Run test chats, including one from an existing customer's email, and work through the go-live checks.
If your Zoho CRM itself is new, read the basics of Zoho CRM first. A chat integration cannot be cleaner than the CRM it feeds.
If you want your own admin to run this, Zoho offers Zoho CRM classroom training. It is a 3-day instructor-led programme for CRM admins, moving from account setup to automation and module customisation. It follows a fixed outline, though, and implementation of your own CRM is not part of it.
If you would rather have the link designed around your sales process, our Zoho CRM implementation and consulting page explains how we work and how to get in touch.