What Zoho CRM help actually means
Zoho CRM help comes in several forms, and most businesses reach for the wrong one first. When your sales process changes and the CRM no longer matches it, a support ticket will rarely solve the problem. Support explains how the product works. It does not redesign your setup around the way you now sell.
The fixes usually fall into three groups. Configuration changes what the CRM does using its built-in tools. Integration connects it to the other systems your team relies on. A custom extension adds behaviour the product does not provide out of the box.
Each of the three has a different cost, a different owner and a different level of risk. Picking the right one early saves you from paying for code when a layout change would do, or from bending your process around a setting when you actually need an integration.
This post sets out what Zoho's own support and onboarding cover, where they stop, and how to tell which fix you need. If you are new to the product, the basics of Zoho CRM is a better starting point.
Signs your setup no longer fits
A CRM rarely breaks all at once. It drifts out of step with the business as you add products, markets or team members. The signs are usually visible in daily work before anyone raises them.
- Sales staff keep a spreadsheet alongside the CRM because the record does not hold what they need.
- Deals skip stages, or stages no longer describe how a sale really moves through your sales pipeline.
- People copy data by hand between the CRM and your help desk, finance or quoting tool.
- Managers do not trust the reports, so they ask for updates in meetings instead.
- Follow-ups depend on memory rather than on rules the system enforces.
- Different teams sell in different ways, but everyone works in the same layout.
Write these down with an example for each. A concrete list such as "renewals are tracked in a spreadsheet by one person" is far more useful to whoever helps you than a general sense that the CRM is not working. It also shows you which of the three fixes each problem points to, which we cover below.
What Zoho's own support covers
If you pay for Zoho CRM, you get Classic Support by default. According to Zoho's support plans page, you can reach the support team by email, call or chat, or schedule a remote assistance session. Those sessions run through Zoho Assist, and you can revoke access once the session is over. Users on the free edition get Basic Support, with email questions answered within 1-2 business days.
Two paid tiers sit above Classic. Here is how they compare.
| Tier | Cost | Availability | Initial response |
|---|---|---|---|
| Classic | Included with a paid subscription | 8 hours, 5 days a week | 8 hours |
| Premium | 20% of your subscription fee | 24 hours, 5 days a week | 3 hours |
| Enterprise | 25% of your annual subscription fee, minimum 50 user licences | 24 hours, 7 days a week | 1 hour |
Enterprise adds a dedicated Technical Account Manager and quarterly reports on feature usage with recommendations. Zoho lists Zoho CRM on the G-Cloud framework at £16 to £52 a user a month, so the percentage uplift scales directly with your licence count and edition.
You can also contact support at support@zohocrm.com, and Zoho's support knowledge base explains support access, which grants a developer or support agent temporary access to your account to diagnose issues.
Where support and onboarding stop
The support tiers buy you faster answers. They do not buy you a redesigned CRM. Zoho is explicit about this, and it is worth reading the fine print before you upgrade a plan in the hope it fixes a process problem.
Onboarding
New subscriptions include 4 onboarding sessions of 60 minutes each, within 15 days of the date of subscription. Zoho states that your onboarding specialist may guide you through setup, but they will not implement Zoho CRM for you.
Technical Account Manager
On Enterprise Support, the Technical Account Manager acts as a liaison between your stakeholders, Zoho and any implementation partners. Zoho notes that the TAM will not implement the CRM or customise solutions, and that implementation is not covered by the cost of Enterprise Support.
Jumpstart and Enterprise Business Solutions
Zoho also sells setup services. Jumpstart gives you a dedicated expert to set up and configure the product, but it covers built-in features only and excludes custom developments. Enterprise Business Solutions is aimed at mid-sized to large businesses and covers planned implementation of custom solutions across multiple Zoho apps, third-party tools and homegrown systems, including data migration and team onboarding.
The practical point is simple. If your problem is "how does this feature work", support is the right route. If it is "this CRM does not match how we sell", you need design and build work, whoever does it.
Fix one: configuration
Configuration is the cheapest and lowest-risk fix, and it solves more problems than most teams expect. It uses tools already in the product, so there is no code to maintain and upgrades from Zoho do not break it.
The features Zoho lists for this kind of work include:
- Page Layouts, which let you design distinct layouts for each sales process, with conditional fields and rules.
- Canvas, for arranging fields and structuring record pages without code.
- Blueprint and approval processes, which turn a sales process into structured steps people must follow.
- Cadences, which automate a branching sequence of follow-ups that reacts to each lead response.
- Duplication management, import, export and audit logs for keeping data clean.
Configuration fits when the data and the systems are right but the CRM is set up for an older way of selling. A second product line with its own stages is a layout and Blueprint job. Missed follow-ups are usually a Cadences or workflow job. For more on these building blocks, see how to customise your CRM and our sales automation glossary entry.
The risk with configuration is sprawl. Every layout, rule and field someone adds without a plan makes the next change harder, so decide who owns it.
Fix two: integration
Integration is the right fix when the CRM itself is fine but the information your team needs lives somewhere else. Manual copying between systems is the clearest symptom.
Some integrations are ready-made. Zoho CRM offers a two-way help desk integration with Zoho Desk and other help desk tools. Relevant tickets appear under each lead and contact, and CRM contact details appear in each ticket. Support staff can see potentials, activities, lead scores and lead sources for every recorded ticket. Setup means finding the integration in Zoho's marketplace and authenticating the two systems. Zoho CRM can also synchronise contacts and tasks from common office applications your team may already use.
Where no ready-made connector exists, the REST APIs support create, read, update and delete operations. Two limits matter for planning:
- Real-time streaming is not available out of the box, so near-instant sync needs extra design.
- API calls use credits, and your credit allowance depends on your number of users and your CRM edition.
A busy integration can therefore push you towards a higher edition or more careful call design. Estimate call volumes before you build, not after. Zoho's CRM resources page links to a developer guide on integrating with third-party applications through the APIs.
Fix three: a custom extension
A custom extension is the right fix when the behaviour you need does not exist in the product and cannot be assembled from settings. It costs more to build and carries a maintenance duty, so it should be the last of the three you reach for, not the first.
Zoho CRM gives developers several tools, described in Zoho's CRM documentation:
- Functions, formerly Custom Functions, for programming custom actions the CRM does not provide natively.
- Client Script, which runs event-driven actions in the user interface with custom JavaScript and can call the CRM APIs and serverless functions.
- Connections, which call third-party REST APIs and give functions or widgets access to authenticated data.
- A Developer Edition, a complete edition for building and testing away from live data.
Some needs recur across many businesses, and packaged extensions exist for them. Svennis has published five Zoho Marketplace extensions for gaps of this kind, and every one is rated 5 out of 5. Checking for a packaged extension before commissioning bespoke code is often the quickest saving you can make.
If you do build, insist on documentation, a test environment and a named owner. Code nobody understands becomes the next reason the CRM no longer fits.
Limits to know before you decide
A few product facts shape which fix is realistic. They come from Zoho's own G-Cloud listing and documentation, and they catch teams out when discovered late.
- Cloud only. Zoho CRM is offered as a public cloud deployment with no on-premise option. Any plan that assumes local hosting will not work.
- Administration is desktop work. Administrator-level customisation and configuration cannot be done in the mobile app. Budget desk time for whoever owns the setup.
- Dormant accounts are deleted. If a paid subscription ends without renewal, users move to the free edition. An account with no activity for over 120 days is deleted with its data, and you cannot export it afterwards.
- Uptime. Zoho states a monthly service uptime of 99.9%.
- Data location. Zoho's listing gives the European Economic Area as the data storage and processing location.
Zoho is also adding AI tools. Zia is the AI feature inside the CRM, and Zoho MCP lets AI agents carry out tasks across more than 950 Zoho and third-party services. If you are weighing AI automation as part of a fix, treat it as another integration, with the same questions about data access and ownership.
How to tell which fix you need
Take the list of problems you wrote earlier and sort each one using the table below. Most businesses find that the majority of their issues are configuration, a few are integration, and only one or two genuinely need code.
| What you see | Likely fix | Why |
|---|---|---|
| Stages or fields do not match how you sell | Configuration | Layouts and Blueprint can reshape the process with built-in tools |
| Follow-ups are missed | Configuration | Cadences and workflow rules automate them |
| Data is retyped from another system | Integration | A connector or API link removes the manual step |
| Support cannot see sales history | Integration | The two-way help desk sync shows it on each ticket |
| A calculation or check the product cannot do | Custom extension | Functions or Client Script add missing behaviour |
| You do not understand a feature | Zoho support | This is what the support tiers are for |
Ask whoever advises you to classify each item the same way and explain why. A good adviser will steer you away from code where settings would do. For more on what a partner does, see what is a Zoho partner. Teams further along may also find the intermediate Zoho CRM guide useful.
Practical next steps
You can make real progress on this in a week without spending anything. The aim is to arrive at any conversation, with Zoho or with an adviser, knowing what you need and why.
- List the problems. Ask each team for three examples where the CRM gets in the way. Keep them concrete.
- Classify each one. Use the table above to mark it as support, configuration, integration or custom extension.
- Check your support tier. If most items are "how does this work" questions, Classic may be enough. If response time is the issue, compare the 3-hour Premium and 1-hour Enterprise responses against their cost.
- Estimate integration load. For each system you want to connect, note how often data must move. This tells you whether API credits or the lack of real-time streaming will matter.
- Look for packaged extensions before commissioning custom code.
- Name an owner. Decide who approves changes to the setup, so configuration does not sprawl again.
With that list in hand, you can judge whether you need a support upgrade, a short configuration project or a larger build. Our Zoho CRM implementation page describes how that kind of project is usually scoped, if you want a reference point.