Help Center
Docs

The Customer Ticket Portal

Give contacts a sign-in page where they can view and reply to their support tickets

What the Portal Is

A private ticket view for your customers, fed by the same Inbox your agents work.

The customer portal is a signed-in page where a contact sees their own support tickets: status, priority, your public replies, and attachments. They can reply from the portal, and a reply to a resolved ticket reopens it, so a customer is never stuck on a closed thread. Internal notes never appear in the portal. Only the replies your team sends as a public reply do.

A Business plan feature
The portal comes with tickets on Business and above, beside the other public support surfaces (your Help Center and live chat). A portal reply lands on the ticket like any other customer message, so response targets, assignment and notifications work as they do for email.

Sharing the Portal Link

The sign-in link is on the Channels page, ready to copy.

Open Service → Configuration → Channels and find the Customer portal row. When your Help Center is published on a plan with tickets, the row reads Available and Customers confirm their email with a sign-in code first. It shows the sign-in link with Copy, Open and Test as a customer. If the row reads Not available or Needs a plan, it names what is missing, such as Publish your Help Center first.

Reply emails link to the portal when it can show the ticket
A reply your team emails to a customer carries a View your request button that opens the portal sign-in page, but only when the portal will list that ticket for that reader: the ticket is linked to a contact, the email goes to that contact's address, your plan includes tickets and your Help Center is on. Any other reader would sign in to an empty list, so their email has no button.

Inviting a Contact

Send a portal link from the contact's record.

1

Open the contact and find Customer portal

Go to People, open the contact, and switch to the Related tab. The Customer portal card sits with the contact’s tickets. You need permission to edit tickets to see it, and the contact needs an email address on file.

2

Send the invite

Choose Invite to portal, then Send invite. The contact receives an email with a personal sign-in link that stays valid for 30 days. The link is theirs alone: the app never shows it, so it cannot leak from an agent’s screen.

3

Resend when needed

Resend link sends a fresh link and retires the previous one, so a contact only ever has one live link. Resends have a short limit, which protects the customer’s mailbox from an accidental double send.

Signing In with an Email Code

Customers can also sign themselves in, no invite required.

Where the sign-in page lives
Your portal sign-in page sits at /portal/login/your-business, under the same public address as your Help Center pages and your website widgets. Only a workspace admin can change that address, and the addresses your workspace used before keep opening the sign-in page, so a customer who saved the link does not lose it in a rename. See Your Help Center Address.

A contact who is already in your CRM can reach the portal without an invite. On the sign-in page, Sign in to your support requests, they enter their email address and choose Send code. A 6-digit code arrives that is valid for 5 minutes. They enter it and choose Sign in, which starts a 30-day portal session. Resend code sends a new one after a short wait. A code works once and stops after 5 wrong guesses. The page answers the same way whether or not it knows the address, so nobody can use it to find out which of your contacts exist.

One credential per contact
An invite and a code sign-in do not add up to separate live links. Signing in with a code refreshes the contact’s existing credential and keeps any visibility your team set, so a routine sign-in never resets a support decision.

Company-Wide Visibility

Choose how much of their company's ticket history a contact can see.

By default a contact sees only their own tickets. For a champion or account admin at a customer company, you can widen that from the same Customer portal card once an invite exists, with the What they can see selector:

  • Own tickets: the default. The contact sees only tickets filed by or for them.
  • Company view: the contact also sees every ticket from their company, read-only. They can still reply on their own tickets.
  • Company view and reply: the same visibility, plus replies on colleagues’ tickets.

The setting belongs to the contact, not to one link: it stays through resends and new code sign-ins until your team changes it. Company visibility follows the company on the contact’s CRM record, so keep that link current to keep the portal view right.

Revoking Access

Cut off a contact's portal access immediately.

Revoke access on the Customer portal card deletes the contact’s portal credential and cancels any sign-in codes they asked for and did not use. Every portal link they received stops working at once. Revoke access when a contact leaves the customer company or an inbox may be compromised. It is not a permanent ban: the contact can sign in again later with an email code, which starts them back at Own tickets.

Requests Awaiting Email Confirmation

A request from the Help Center form stays in pending verification until the sender confirms their email.

Anyone can type any email address into your Help Center request form, so every form request waits for a confirmation. The customer sees Check your email, and a confirmation link goes to the address they typed. The link works once and stays valid for 7 days. Opening it confirms the request, and the page reads Request confirmed. A request sent from inside the portal needs no such step, because the contact already proved the address when they signed in.

What your team sees before the customer confirms

  • Email not confirmed: a muted label on the ticket's row in the Inbox and in its header.
  • The reply box opens on Internal note, and Public reply is off with the line Waiting for the customer to confirm their email. You can reply after they confirm. Internal notes work as usual.
  • Resend confirmation email: sits beside that line for people who can edit tickets. It sends a new link and retires the old one, once every 10 minutes on a ticket. The result reads Confirmation email sent again., Wait a few minutes before you send it again. or We could not send the confirmation email. Try again in a few minutes.
What pending means in practice
A pending ticket starts no response targets and notifies nobody, so nobody is paged for a request that may never be real. In the portal, a pending ticket is visible only to the contact who filed it. It never appears in a colleague’s company-wide view, so nobody can see someone else’s ticket by claiming their address. Once the sender confirms, the label goes away, response targets start and your team is notified as usual.