Guide · Helpdesk
What a customer portal should show, and what it shouldn’t
In short
A customer portal exists so customers stop writing “any update?”. It should show them their own requests, each one’s status and your replies, and let them answer in the same thread, with nothing to set up before they can look. It shouldn’t show your internal notes, other customers’ tickets or a password form most of them will never fill in.
Reviewed 9 November 2026. Terms used: Ticketing system, Shared inbox vs helpdesk, CSAT vs NPS.
Seven decisions for a customer portal
Whichever helpdesk you use, these decide whether customers open it.
Show every request, however it came in
A customer doesn’t remember whether they emailed, used the form or wrote on WhatsApp. List every ticket that belongs to them, newest first, each with its reference, subject and status.
Use a few plain statuses
Open, in progress, waiting on you, resolved. Customers need to know whose move it is, not your internal workflow. “Waiting on you” is the one that gets a reply.
Show the conversation, not the workings
Your replies and theirs, with dates, in one thread. Leave out internal notes, side conversations with suppliers, assignment changes and SLA timers: they belong to your team.
Let them reply in the thread
A reply in the portal should land on the same ticket as an email reply would, and move a ticket waiting on them back to your team. A closed ticket should ask them to start a new request instead.
Sign in without a password
Most customers visit once or twice. Send a one-time sign-in link to the email address on their tickets, valid for a short time, and keep them signed in for a few days.
Show only what belongs to them
Match tickets by the customer’s email address and their record, never by a reference someone can guess. An address with no tickets shouldn’t learn anything from the sign-in page.
Put help and the survey where they already are
Search your help articles from the portal’s header before they write in, and ask how you did on a resolved ticket right below its thread.
What the portal shows vs what stays with your team
Tickets
- Shows the customer
- Their own, from every channel
- Stays with your team
- Everyone’s, with the queue and assignment
Messages
- Shows the customer
- Your replies and theirs
- Stays with your team
- Internal notes and side conversations
Status
- Shows the customer
- A few plain words
- Stays with your team
- Your workflow and SLA clocks
Sign-in
- Shows the customer
- A link by email, no password
- Stays with your team
- Your team’s accounts and roles
How it works in Axonave
The helpdesk, seen from the customer’s side.
In Axonave the portal sits behind your help centre’s My tickets. Customers type their email address and get a sign-in link that works once, for 30 minutes, and keeps them signed in for 7 days; only an address that has tickets gets a mail. They see the tickets of their contact, their lead and their address, from email, WhatsApp, chat or the support form. A reply works like an email reply: a resolved ticket reopens, one waiting on them goes back to in progress and the SLA follows; a closed ticket asks them to start a new request. Once a ticket is resolved they can answer its survey right there.
- The support form embeds in your site with one snippet
- The confirmation mail carries the reference and a link to their tickets
- Help-centre search in the portal’s header
The customer portal on a phone in our demo workspace: Aisyah, signed in by link, reads TKT-1201’s thread with Hafiz Rahman’s replies, and the survey below it.
Common questions
Do customers need an account?
No. They get a one-time link by email to the address on their tickets. It works for 30 minutes and keeps them signed in for 7 days.
Can customers see internal notes?
No. The portal shows the public thread: your replies and theirs.
Does the portal need the help centre?
No. Without the help centre, Contact us and My tickets are still there.
See it working with your own customers.
We reply within one business day by email or WhatsApp.