Support usually can’t see the sale. That’s the whole reason a customer has to explain their own history to the person meant to be helping them. The support side of Zoho One, built around Zoho Desk, exists to close that specific gap.

You’ve been the customer in this. You phone about something you’ve already emailed about. The agent asks for your account number, then your order number, then what the problem is. You explain it again. Somewhere in your file is every detail you’re being asked for, and the person on the phone can’t see it.

That isn’t bad service. It’s a data problem wearing a service problem’s clothes.

The agent is doing their best with what’s on screen. What’s on screen is a ticket system that knows about tickets. It doesn’t know you bought three months ago, that your invoice is disputed, or that a salesperson is mid-renewal with you this week. Each of those lives somewhere else.

What does the support side of Zoho One cover?

Three applications, doing three genuinely different jobs.

Zoho Desk is the helpdesk. Tickets arrive from email, a web form, chat, phone or social, land in one queue, get an owner and a clock, and are resolved and recorded. It’s the backbone, and it’s where most companies start. Zoho’s own Zoho Desk page covers the channel list.

Zoho Assist is remote support. An agent takes control of a customer’s screen with permission, or reaches an unattended machine. If your product is physical or your customers need someone to look at their actual computer, this is the piece that stops the twenty-minute description of what’s on a screen you can’t see.

Zoho SalesIQ is the website layer: who’s on your site, what they’re reading, and live chat or a bot to talk to them. It’s usually sold as a sales tool, which is why support teams miss it. Plenty of support conversations start on a website rather than in an inbox.

The overlap between SalesIQ and Desk confuses people constantly. Simplest way to hold it: SalesIQ is the conversation while someone’s on your site, Desk is the case that outlives the conversation. A chat that needs a resolution becomes a ticket.

Why does shared customer history change support?

Because the agent stops guessing, and the customer stops repeating themselves.

When Desk and CRM are connected, the agent opening a ticket sees the customer as the rest of the business sees them. What they bought. What it cost. Which deal is open right now. Whether they’ve complained twice this month already. That’s a single view of the customer instead of a ticket in isolation.

It runs the other way too. A salesperson about to call for a renewal can see four unresolved tickets sitting on that account. That call goes differently, and it should.

Now the precision, because this claim gets overstated everywhere. A standalone helpdesk will talk to your CRM readily enough; what it won’t do is read the same customer your salespeople do, and that difference is where the money leaks.

The link between Desk and CRM inside the Zoho platform is native. It’s still something somebody switches on and configures. It isn’t magic and we won’t pretend it is.

Where should a support team start?

With the queue, almost always. Not with the clever parts.

Get every channel landing in one place first, with an owner and a response expectation attached to each ticket. That single change usually does more for a support team than anything that follows it. Only then connect CRM, so agents see context. Then look at self-service and knowledge bases, because the cheapest ticket is the one the customer resolves alone at eleven at night.

Automation comes last. Automating a process nobody has agreed on just makes the wrong thing happen faster. We see that mistake more than any other on support projects. A team buys the product, switches on every rule in week one, and spends month two unpicking it. Sequence is most of the work.

Where this doesn’t fit is worth saying plainly. A business with a handful of support emails a week doesn’t need a helpdesk. A shared inbox and a rule about who checks it will serve you better, and anyone selling you a ticketing system at that volume is selling you admin. If your volumes justify voice queues and workforce planning rather than tickets, that’s contact centre work and a different conversation again.

The short version

The support side of Zoho One is Desk for cases, Assist for hands-on help, SalesIQ for the website. What makes them worth having together is that support can see the sale, so the customer doesn’t explain themselves twice. Start with one queue. Add the context, then the self-service, then the automation, in that order. Most support projects fail on that order, not on the software.

Next in the series: Zoho Desk in depth, including the honest bit about its learning curve and what it really costs to get a team productive on it.

CUSTOMERS EXPLAINING THEMSELVES TWICE?
We’ll walk your actual support flow and show you where the context gets lost, including when the answer is that you don’t need a helpdesk yet.
Show me where support loses the customer