The Zendesk Client Portal
Most Zendesk client portal builds get linked once from a footer and then quietly ignored. The fix isn't design, it's knowing what the thing can actually do.
What the Zendesk client portal shows a signed-in client
The portal isn't a separate product. It's the signed-in half of your help centre, and it appears the moment somebody with an end-user account logs in.
What they get is a short list, and it helps to be precise about it.
That is the whole surface. Everything else you have seen on a portal is either a theme change, a custom page, or something bolted on with JavaScript.
See the Zendesk customer portal guide for the enabling and registration side of the same feature.
What clients cannot do, and why it matters
This is the list that saves you an awkward call with a client who was promised more.
They cannot reassign a ticket, change its priority, or see internal notes. Good. Those are agent controls and they should stay that way.
They can't reopen a Closed ticket either. A reply to something already Closed spawns a follow-up ticket instead, which is Zendesk behaving correctly and looking, to the client, like their message vanished into a new number. Tell them that in the notification email and you'll never field the question.
And a request that gets merged into another one simply shows as Closed, with no explanation beyond whatever comment you left on it. From the client side, one of their two requests just stopped. A one-line public comment before you merge is worth the ten seconds.
The part B2B actually wants: organisations
Consumer support barely uses this. Client work depends on it.
Put your client contacts into an organisation and you can let everyone at that company see everyone else's tickets. The account manager sees what their team raised. Cover during holidays stops being a forwarded email chain. And when somebody leaves, their open requests remain visible to the people who still work there.
Two decisions come with it. First, whether the whole organisation sees everything or only a nominated set of users, since a shared view of tickets is also a shared view of complaints. Second, whether those users can comment on each other's tickets or only read them.
Neither default is right for every client. In regulated work, ask before switching it on. In a normal software account, it is usually the single change that makes the portal useful.
Four changes that get people back
Three things clients always ask for
Every B2B rollout produces the same three requests, and only two of them are reasonable.
Say yes to the first two in week one. The third is a project, and nine times in ten what the client actually wanted was a link to the system that already holds the data.
How to tell whether it is working
Two numbers, and neither of them is page views.
The first is the share of new tickets arriving through the web form rather than email. That ratio moving is the only real evidence the portal has been adopted.
The second is how often somebody replies in the portal instead of starting again. When status chasing arrives as a fresh email rather than a comment, you get two tickets for one request, and the second one usually reaches a different agent.
Frequently asked questions
What is the Zendesk my requests page?
The Zendesk my requests page is the list a signed-in customer sees in the Zendesk end user portal: their own open and solved tickets, plus their organisation's if you've switched that on.
Can clients see their colleagues' tickets in Zendesk?
Yes, if you enable organisation access on that organisation. It's deliberate rather than default, and it can be limited to nominated users rather than everyone.
Can a client reopen a closed request from the portal?
No. A Closed ticket is final, and a reply creates a linked follow-up ticket instead. Solved tickets can still be reopened by replying.
Do portal users need a paid Zendesk seat?
End users are not agents and are not licensed as agents. The portal comes with the plans that include Guide, so check your tier before designing around it.
Can I customise what the Zendesk client portal shows?
Within the theme, yes. The request list, the detail page and the form are template-level changes, which means a developer and a maintenance commitment.
Why can a client not find a ticket they know they raised?
Usually one of three things: they raised it from a different email address, they were a CC rather than the requester, or it was merged into another ticket.
Two tickets, one client, one problem
When a status chase arrives as a new email instead of a portal comment, you get a duplicate. Ticket Merger finds those and merges them automatically.
Start free trial14-day free trial. No credit card required.