Zoho Support Services

Yes, and for what it exists to do it is genuinely competent. Zoho support handles platform faults, outages, billing and account questions — and if something is broken in their service they are the only ones who can fix it. The limits are practical rather than a criticism. They start from nothing each time, so you re-explain your configuration at the beginning of every conversation. They will tell you what a setting does but not which one your business should use. Custom functions, widgets and third-party integrations are your implementation rather than their product, so they generally fall outside scope. And anything that is not Zoho's fault at all — your DNS, your payment gateway, your data — is not something they will look at, which is where a good share of real problems live.

Support is what you call when something is wrong: a workflow that stopped firing, a function throwing errors, an import that created duplicates, an invoice the portal rejected. Administration is the standing work that stops most of those calls happening — provisioning starters, deactivating leavers cleanly, keeping roles and sharing rules current, reviewing the licence count before renewal, making sure integration credentials belong to the company rather than to an employee. There is a third category people tend to fold into support and should not: enhancement, which is the new reports, new automation and new processes the business needs as it changes. Charging for those as though they were incidents is how a support arrangement quietly turns into an open-ended bill.

A 30-minute response SLA, 24×7. Response means a person who can see your account replying — not an automated acknowledgement with a ticket number. Resolution time depends entirely on the problem: a permission fix is minutes, a failed integration may be an hour, and a data repair after a bad import is honest work that takes as long as it takes. What we commit to is that you are never waiting on silence.

Yes, and it is a common engagement. It starts with an audit of what is actually configured — modules and custom fields, automation, blueprints, functions, roles and sharing rules, integrations and who owns their credentials. That is not a formality. It is what stops us diagnosing your setup and your problem simultaneously the first time something breaks. The findings are yours whether or not you go ahead, and where the audit turns up work that has to happen before any response commitment is realistic, we scope that separately rather than folding it into a retainer.

Zoho includes a basic level of its own support with paid editions and sells higher tiers — Premium and Enterprise — priced as a percentage of licence spend. Check Zoho's current terms directly, because the tiers and their inclusions change. Partner support is a different product and is scoped and quoted separately from licences, so you can see what each part costs rather than finding support folded invisibly into a per-user rate. Having a partner does not remove your access to Zoho's own support either — it means somebody else raises the case, with the diagnosis and evidence already assembled.

That is a large share of what support actually is. Mail from CRM landing in spam is usually a domain authentication or reputation issue. A payment that did not reconcile is often the gateway's settlement file rather than Zoho Books. A WhatsApp automation that stopped may be the provider's template approval. None of these are Zoho faults and all of them stop your business working, which is the only definition of a problem that matters.

No. An annual arrangement makes sense where Zoho is load-bearing — invoicing runs through it, the sales team lives in it, several integrations depend on it. Where usage is lighter, ad-hoc support against an agreed rate is more honest than a retainer you use twice a year. We would rather tell you which one fits than sell you the larger one.

Only what you want us to keep. The super-admin account is yours throughout and always has been. Standing access is faster when something is wrong, because the first twenty minutes of an incident are not spent arranging permissions. Granting access only when there is something to do is entirely workable, and we will say so rather than pretending otherwise.

Usually, yes. The practical obstacle is rarely technical — it is access. If the org's super-admin is an address nobody controls, or an integration was authorised under a personal account that has been deactivated, recovering ownership is the first piece of work and occasionally involves Zoho directly. Once ownership is back with you, the audit tells us what we have inherited and what needs repairing before a response commitment means anything.

Answering how something works is support and we do not meter it. Structured role-based training for a new intake, or retraining a department after a process change, is scoped work — it needs preparation, materials and someone's undivided day. The distinction is not about being strict; it is that folding real training into an incident SLA means it gets done badly, between tickets.