Custom branding
Match your logo, colors, and domain so the portal feels like part of your product.
Customer support portal
A customer portal your users will actually use Self-service, tickets, and branding
Give customers a branded portal to search your knowledge base, submit tickets, and track request status, on your domain.
Last updated on 2026-07-08
Written by Malik S
Reviewed by Gandral V
Ticket tracking
Customers see status updates and reply to threads without emailing back and forth.
KB-powered deflection
Suggest articles before ticket submission to reduce volume automatically.
Overview
A portal only helps if customers can find it and finish what they came to do. Helpefi hosts a branded portal on your own domain, where people search the knowledge base, submit a request, and follow its status without sending a follow-up email. Every submission becomes a ticket in the same queue your agents already work.
Branding and custom domains
The portal carries your logo, colours, and favicon, and serves from a subdomain of your choosing, such as support.yourcompany.com. A CNAME record points the hostname at the workspace and a certificate is issued automatically. Header links can return customers to your product or documentation. Support domains are available on Professional and Enterprise plans, which is usually the point at which a portal stops looking like a vendor page and starts looking like part of the product.
Search and deflection before submission
Search sits at the top of the portal rather than behind a link, because the moment someone types a question is the moment an article can help. Suggestions appear as the customer types, and a short answer can be read without leaving the page. If the search misses, the ticket form opens with the query already in the subject, so nothing is retyped. Deflection works because it is faster than the form, not because the form is hidden.
Ticket forms that collect the right detail
A request type decides which fields a customer sees. A billing form can ask for an invoice number; a technical form can ask for a product version and offer an attachment field. Custom fields map to ticket properties, which feed routing and reporting without an agent copying values by hand. Keep required fields to what the team will actually use, since every mandatory box is a reason to abandon the form and send an email instead.
Status tracking and updates
Customers see the ticket status, the conversation, and any public replies in one thread. Email notifications link back to the portal, so the thread is readable in a browser rather than reconstructed from forwarded messages. Solved tickets can be reopened by replying, which keeps a follow-up attached to its history. Agents can also leave a public status such as waiting on a supplier, which answers the question customers ask most often.
Multiple brands and languages
Agencies and multi-product companies can run several portals from one workspace, each with its own domain, branding, and knowledge collections. Language selection changes interface copy, and articles can exist per language, so a French customer is not reading an English policy page with a translated button. Brand separation also protects content: a client portal shows only its own collections, and support staff see all of them from the agent side.
Use case: Product support portal
A SaaS team launches a branded portal with knowledge search and ticket submission, so status questions stop arriving by email.
Use case: Agency white-label portals
Each client gets its own domain and knowledge collection, managed from a single agency workspace.
Use case: Ecommerce self-service
Shipping and returns articles sit beside a return request form, so most questions end without a ticket.
Use case: Internal IT service portal
Employees submit hardware and access requests through a catalog with approvals, replacing an email inbox.
Use case: Multi-language support
Portals in several languages serve international customers in their own language without relying on email translation.
Self-service that finishes the job
Put search first, keep forms short, and give customers a status they can check without emailing. A portal that answers one question well earns the next visit.
Frequently asked questions
- Can we use a custom domain?
- Yes, on Professional and Enterprise. Add a CNAME record for your chosen subdomain and the certificate is issued automatically.
- Does the portal require customer accounts?
- Customers can search and submit with an email address. An account adds saved history and a single place to track every request.
- Can the portal serve multiple brands?
- Yes. Each brand can have its own domain, branding, and knowledge collections, all managed from one workspace.
- How does portal deflection work?
- Search suggests published articles as a customer types. If the article answers the question, no ticket is created and analytics record the result.
- Can customers track their tickets?
- Yes. The portal shows status and the full public conversation, and email notifications link back to the same thread.
- Does the portal support multiple languages?
- Interface copy can be switched per portal, and articles can be published per language so customers read approved content, not machine translation.
- Which plans include the customer portal?
- The portal is included on every plan with a shared workspace domain. Custom domains require Professional or Enterprise.
References & sources
-
Helpefi on G2 →
User reviews and ratings for Helpefi on G2.
Launch your customer portal
Publish your portal during trial setup and start deflecting tickets today.
Start free trial