What Zia lead scoring is and when it helps
Zia lead scoring for a UK sales team is a feature in Zoho CRM that gives each lead and each deal a score showing how likely it is to convert. Zia is Zoho's AI-powered sales assistant for Zoho CRM. Zoho describes it as providing "interpretations, solutions, and predictions for salespeople".
Lead scoring itself is an old idea. You rank prospects by how likely they are to buy, so reps spend their time on the ones most worth calling. The difference with Zia is that you do not write the rules. Zia works out a score from the information already held against each record.
That is also its weakness. A score learned from your own history is only as good as that history. If leads are closed without an outcome, stages are skipped and calls are never logged, Zia learns from gaps. The score then looks precise and means very little.
This guide covers how the score is built, who can use it, the data it needs, how to switch it on, how to use it in your pipeline, and how to check whether it agrees with what your reps see. If you want the wider picture of the assistant first, read our post on what Zia actually does for a small sales team.
How the Zia score is built
Zoho's announcement of the feature defines the Zia score as "an AI based scoring methodology where Zia takes into account all of the information related to that particular record and calculate a score for that record". The result represents "the likelihood of conversion of a particular lead/deal".
What goes into it
Zoho lists four inputs:
- Record information: the fields on the lead or deal itself.
- SalesSignals: a feed that records when prospects open and reply to your emails, interact with you on social media, and other time-based activity.
- Related data: the activities, notes and linked records attached to it.
- Integration data: information from other products you have connected to the CRM.
What comes out
The score runs from 0 to 100 and is expressed in percentile format. Zoho groups it into three bands: Need improvement, Good and Excellent. Each score is saved in a custom field labelled Zia Score, so you can sort, filter and report on it like any other field.
On the record detail page, a score card shows "What went wrong" with the record, "What went right" and the overall score. That card matters more than the number. It is how you find out why Zia rates a lead highly, and whether the reason makes sense to the person who owns the account.
How it relates to manual scoring
Zoho CRM also has manual scoring rules, where you set positive and negative points against criteria you choose. Zoho states that "Zia scoring and manual Scoring rules under Automation will behave independently". One does not overwrite the other.
Who can use it: editions, licences and modules
Check this before anything else, because it rules many small teams out. Zoho's announcement says Zia Scores "is released for all Enterprise, Ultimate and above edition customers with more than 20 user licenses in all the DCs". A DC is a Zoho data centre, so the limit applies wherever your account is hosted. Availability can change, so confirm it in your own account settings.
Zia scoring is also limited in scope. Zoho says "it is currently available only in Leads and Deals module". The main CRM modules are Leads, Contacts, Accounts and Deals, so contacts and accounts get no Zia score.
If you do not qualify, manual scoring rules remain an option. Zoho's release notes list lead scoring "with positive and negative scoring" as available for Standard edition and above.
| Point of comparison | Manual scoring rules | Zia scoring |
|---|---|---|
| Who sets the logic | You write the rules and points | Zia derives it from record data |
| Edition | Standard and above | Enterprise, Ultimate and above, more than 20 user licences |
| Modules | Leads and other records you set rules for | Leads and Deals only |
| Existing records | Scored with the Run Scoring Rules for all Records button | Analysed after switching on, within a few minutes to 24 hours |
| Explanation | The rules you wrote | Score card: what went wrong, what went right |
| Minimum data | None | 200 records |
Other CRM vendors gate predictive scoring in a similar way. A roundup by Sybill notes that HubSpot offers rules-based scoring on Professional plans and AI predictive scoring on Enterprise.
The data Zia needs before its scores are worth reading
Zoho states that "Zia will need a minimum of 200 records to start scoring". If that is not met, you see a "Waiting for data" error. Reaching the minimum only means Zia will produce a score. It does not mean the score reflects how your team sells.
Time matters as well as volume. Sybill's roundup observes that "predictive models typically need at least six months of conversion outcomes to learn meaningful patterns". A CRM that went live last quarter, or one imported from spreadsheets with no outcomes, has little for Zia to learn from.
| Check | Why it matters | What to look for |
|---|---|---|
| Record volume | Below 200 records, Zia does not score | Count open and closed records in Leads and in Deals separately |
| Outcomes recorded | Zia needs to see which records converted and which did not | Old leads converted or marked lost, not left open indefinitely |
| Deal stages used honestly | Skipped or back-dated stages teach the wrong pattern | Closed deals that moved through your real stages |
| Activities logged | Calls, meetings and emails form part of the related data | Reps logging calls and meetings in the CRM, not in personal diaries |
| Integrations connected | Integration data and SalesSignals feed the score | Email, telephony and calendar linked to the CRM |
| Consistent fields | Inconsistent values hide real patterns | Picklists used instead of free text for source, industry and region |
Zoho CRM's standard lead layout has 22 fields. Most teams add their own on top. If your layouts have grown untidy, our post on how to customise your CRM covers trimming fields before you rely on them for anything automated.
How to switch it on: a worked example
Take a Manchester distributor on Zoho CRM Enterprise with more than 20 user licences. Its Leads module holds well over 200 records going back beyond six months, and lost leads are marked as lost. The sales manager wants a daily list of the leads most worth calling.
- Open the setting. Go to Settings > Zia > Recommendation > System recommendation, the path Zoho gives in its announcement.
- Enable Zia scoring. Switch it on from the System recommendation page.
- Wait for the analysis. Zoho says it "typically takes a few minutes to 24 hours for Zia to analyse your data". If you see "Waiting for data", the minimum criteria are not met yet.
- Open a few leads. Check that the Zia Score field is filled and read the score card on each one.
- Add the field to a list view. Put Zia Score next to lead owner, source and last activity, so reps see it where they already work.
The distributor already had manual scoring rules for web form leads. It left them running. Because the two behave independently, the manager now has two numbers on each lead: the points total from the rules they wrote and the Zia band. Where the two disagree is often where the most useful conversations with reps start.
Do not build automation on the score in the first weeks. Look at it, compare it and understand it first.
| Step | Where or how long |
|---|---|
| 1. Open the setting | Settings > Zia > Recommendation > System recommendation |
| 2. Enable Zia scoring | Switch it on from the System recommendation page |
| 3. Wait for the analysis | A few minutes to 24 hours |
| 4. Check a few leads | Confirm the Zia Score field is filled on each record |
| 5. If Waiting for data appears | Minimum criteria are not met yet, so recheck your record count |
Using the score in your pipeline view
Zoho CRM lets you view records in tabular view, kanban view or canvas view. The Zia Score field works in all of them as a sortable field, so the first change is simply to sort open leads by score in the view reps already use.
Views and filters
Zoho states that the Zia Score field "can be used as a criteria or input in other features like: when creating a smart filter, creating a custom view, validation rules, layout rules, review process, workflow rules, Blueprint". In practice, start with one custom view per band, for example open leads rated Excellent and owned by the current user. That gives each rep a short list without changing any process.
Because Deals are scored too, add the same field to your deal pipeline. A deal in a late stage rated Need improvement is worth a question at the weekly review.
Automation, later
Once the scores have earned trust, workflow rules can act on them. In Zoho CRM a workflow rule sends email alerts, assigns tasks and updates fields when its trigger criteria are met. A sensible first rule is an alert to the lead owner when a new lead lands in the Excellent band.
Blueprint, the feature for building and running a set sales process inside the CRM, can also take the score as a criterion. Use that with care. Blocking a deal from moving because of a score nobody fully understands will frustrate reps quickly. For more on views, workflows and Blueprint, see our intermediate Zoho CRM guide.
Checking whether the scores match what reps see
A score is only useful if it agrees with good judgement most of the time and explains itself when it does not. Test it before you rely on it.
A simple comparison
- Pick a set of recent open leads across several owners.
- Ask each rep, without showing them the scores, to sort their leads into three groups: chase now, keep warm, unlikely.
- Put the reps' groups next to Zia's bands: Excellent, Good, Need improvement.
- For every lead where the two disagree, open the score card and read "What went wrong" and "What went right".
The score card usually tells you which side is wrong. Sometimes the rep knows something the CRM does not, such as a phone call that was never logged. Sometimes Zia has spotted a pattern the rep has missed. Often the cause is a field filled in inconsistently, which you fix in the data rather than in the score.
At Svennis, when we switch Zia scoring on for a client, we run this comparison with the sales manager before any view or workflow depends on the score. Where the disagreements trace back to unlogged activity, we fix the logging habit first and repeat the comparison later, because rescoring bad data gives the same answer.
Repeat the check after a few weeks. Zia keeps learning as new outcomes are recorded, so agreement should improve if the data does.
| Reps' judgement | Zia score | |
|---|---|---|
| Who ranks the leads | Each rep, for their own leads | Zia, from each record's history |
| Groups used | Chase now, keep warm, unlikely | Excellent, Good, Need improvement |
| How the test is run | Reps sort without seeing any scores | Scores stay hidden until reps finish |
| What it draws on | Calls and context the rep knows about | Record fields, SalesSignals, related and integration data |
| Where to look on disagreement | Ask the rep what was never logged | Score card: What went wrong, What went right |
When the score misleads a small team
Zia scoring is designed for teams with volume. A smaller team should know where it falls short.
You may not have it at all
The release terms require more than 20 user licences. A team of eight reps on Enterprise may simply not see the setting. Manual scoring rules are the realistic choice there.
Too few outcomes
Two hundred records is a floor, not a comfort zone. If a handful of large wins dominate your history, Zia will favour whatever those wins had in common, even if that was chance. Treat scores from a thin history as a hint, not a ranking.
Activity is not intent
SalesSignals records email opens and replies. Sales Force Europe makes the point plainly in its guide to lead scoring in the UK: "Opening emails doesn't meet the criteria for a qualified lead." If the only signal on a lead is opens, a high score deserves scepticism.
Stalled leads
The same guide describes degradation, where a promising lead stalls because the buyer lost interest or got buried in work. A score built on past activity can lag behind that change. Leads that have gone quiet need a human look, whatever their band.
If your volumes are too low for predictive scoring, other approaches to lead management may suit you better than waiting for Zia to have enough to work with.
What this means for a UK sales team
Most of what decides whether Zia works is internal: your data, your stages and your licence count. The UK market adds a few practical points.
Sales Force Europe's UK director of accounts, James Smith, describes the value of scoring this way:
"For a sales and marketing team, it gives indicative timelines from prospects, how far along that buying journey they are."
He adds that "the UK can be a tough nut to crack when it comes to European expansion, cutting to the buyers that are further down that sales cycle can be your quickest route to ROI". If you sell into the UK from elsewhere, that is a reason to rank leads carefully rather than work them in date order.
The same guide stresses personalised outreach in the UK and knowing your ideal customer profile from the start. It also notes that scoring is usually done by the business development reps who generate the leads, while taking account of the sales reps and the end client. For a Zia rollout, that means the people who create leads must log them properly, because their records become the training history.
Many UK teams rely heavily on outbound calling. Outbound activity only reaches Zia if calls are logged in the CRM, which is where telephony integration earns its keep. Finally, Zia builds a profile of each lead from personal data, so check that your lawful basis under UK GDPR covers it, that your privacy notice tells prospects you score them, and that you record it where you document your processing.
Practical next steps
Work through these in order. Each one is quick, and together they tell you whether Zia scoring is worth switching on or whether manual rules will serve you better for now.
- Check eligibility. Confirm your edition and licence count against Zoho's terms: Enterprise, Ultimate or above, with more than 20 user licences.
- Count your history. Check that Leads and Deals each hold at least 200 records and that closed records carry a clear outcome.
- Clean the obvious gaps. Close or mark lost the leads that have sat open for months, and agree with reps that calls and meetings are logged.
- Connect your sources. Link email and telephony so SalesSignals and integration data reach the score. If open tracking relies on a tracking pixel, PECR requires the recipient's consent first, so check how your email tracking works before you switch it on.
- Switch it on. Go to Settings > Zia > Recommendation > System recommendation, then allow up to 24 hours.
- Run the comparison. Set Zia's bands against your reps' own ranking and read the score card wherever they disagree.
- Add one view, then one rule. Start with a custom view by band. Add a single workflow alert only once the scores have held up.
If your CRM needs work before any of this makes sense, that is a normal finding, not a failure. Our Zoho CRM implementation and consulting page explains how we help UK firms tidy the data, stages and layouts that Zia depends on.