Can we use a custom domain?

Yes. Custom domains are available on Professional and Enterprise plans. Default portal URLs (your-workspace.helpefi.com) work on every plan including trial.

Does the portal require customer accounts?

Customers can submit via email verification or optional login—you choose the friction level. Logged-in customers get ticket history and tracking; email-only submission is simpler but loses tracking capability.

Can the portal serve multiple brands?

Yes. Multi-brand workspaces support separate portals per brand with independent domains, branding, knowledge collections, and ticket routing. Database-per-tenant isolation provides data boundaries between brands.

How does portal deflection work?

As customers type their ticket subject and description, the portal suggests relevant knowledge base articles. If customers find answers, they do not submit a ticket—that is a deflection. Articles suggested based on semantic search matching intent.

Can customers track their tickets?

Yes. The ticket tracking view shows status, update history, agent replies, and allows customers to add comments or attachments. Email notifications keep customers informed without checking the portal.

What custom fields are available?

Text, dropdown, multi-select, file upload, checkbox, and date fields. Conditional logic shows fields based on prior selections. Configure fields per queue or brand for appropriate context capture.

Is the portal mobile-responsive?

Yes. The portal is responsive on mobile devices with touch-friendly forms and navigation. Test portal on mobile after configuration to verify search, form submission, and ticket tracking work correctly.

Which plans include customer portal?

Customer portal with knowledge base search and ticket submission is included on all plans including trial. Custom domains, multi-brand portals, and white-label options expand on Professional and Enterprise.

How do we migrate our portal from another platform?

Configure domain and branding during trial, migrate selected knowledge base articles, redesign ticket forms with conditional logic, and launch alongside legacy portal during parallel run before DNS cutover.

Does the portal support multiple languages?

Yes. Configure portal UI translations and knowledge base articles in multiple languages. Portal detects customer browser language or offers manual language selection.

Home
Features
Customer Portal

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.

Start free trial View pricing

Last updated on 2026-07-08 Written by Malik S Reviewed by Gandral V

Custom branding

Match your logo, colors, and domain so the portal feels like part of your product.

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 customer portal is the visible face of your support operation—it is where customers go when they need help before they email or chat. Done well, a portal deflects tickets through self-service, captures structured ticket submissions with context, and builds brand trust through a consistent, professional experience on your domain. Helpefi customer portal combines knowledge base search, ticket submission with custom fields, ticket tracking history, and AI-powered deflection into one branded experience—no separate tool needed. Portal design matters for conversion and deflection. Customers land on your portal from your website, product, or search results. A confusing portal sends them to email or chat with avoidable tickets. A clear portal helps them find answers faster than emailing you. Helpefi portal supports custom domains, logos, colors, and layout so the experience matches your brand rather than feeling like a generic ticketing interface. Ticket submission on the portal captures structured data before the ticket reaches your agents. Custom fields (account ID, product version, priority, issue category) reduce back-and-forth and let agents start resolving instead of asking basic questions. Deflection suggests knowledge base articles as customers type their subject, catching common questions before they become tickets. Post-submission, customers track status, add comments, and view history without emailing. This guide covers portal configuration and branding, knowledge base integration, ticket submission design, multi-brand portals, portal analytics, and how the portal integrates with shared inbox, AI deflection, and SLA management.

Configuring your branded portal

First impressions: your portal should look like your product, not like a helpdesk vendor. Helpefi portal supports custom domain (support.yourcompany.com), logo, favicon, brand colors, hero content, and layout customization. Configure these during setup and they apply across all portal pages—knowledge base search, ticket submission form, and ticket tracking view. Custom domains require DNS configuration (CNAME record pointing to Helpefi) and SSL certificate provisioning. Setup wizard guides DNS steps with provider-specific instructions. Test custom domain after configuration: navigate to support.yourcompany.com and verify logo, colors, and layout match brand guidelines. Hero section on the portal home page greets customers with a search bar, popular article categories, and a "Submit a ticket" call to action. Configure hero copy that matches your brand voice: "How can we help you today?" versus "Search our knowledge base for answers" sets different tones. Portal localization supports multiple languages based on customer browser settings or manual selection. Translate article content and portal UI elements for each supported language. Multi-language portals reduce friction for international customers who prefer self-service in their native language.

Knowledge base search and deflection on the portal

The search bar is the most-used portal element. Helpefi semantic search returns relevant articles based on meaning matching, not just keyword matching. As customers type their question, suggested articles appear below the search bar before they hit enter. When customers click an article, deflection is measured: if they do not submit a ticket afterward, that is a deflected ticket. Deflection effectiveness depends on article quality and placement. Publish articles that match high-volume search intents. Use article analytics to see which searches return no results—those are content gaps worth filling. Test portal search with real customer questions monthly to verify relevance. Ticket submission form includes deflection at the subject and description fields. As customers type their subject, related articles appear above the form with a prompt: "Did you find your answer in these articles?" Customers who click through and find answers never reach the ticket queue. Track deflection rate by article and by search query. High deflection on an article means it is effective; no deflection on a popular search means content gap. Share deflection analytics with content team so they prioritize writing for gaps rather than rewriting articles that already perform.

Designing effective ticket submission forms

Ticket submission forms balance information capture against friction. Too few fields and agents spend time asking basic questions; too many fields and customers abandon before submitting. Helpefi supports configurable custom fields with types: text, dropdown, multi-select, file upload, checkbox, and date. Essential fields for most portals: subject (free text), description (multi-line), priority (dropdown: low, normal, high, urgent), category (dropdown: billing, technical, account, feature request), and attachments (file upload for screenshots and documents). Add optional fields per your product needs: account ID, order number, product version, or environment (production, staging). Conditional field logic shows fields based on previous selections. If customer selects "billing" category, show invoice number and billing contact fields. If "technical," show environment, error message, and reproduction steps. Conditional logic reduces form length without sacrificing relevant context. Test form completion rates after launch. If abandonment is high, reduce field count or simplify options. If agent back-and-forth is high despite form data, add fields that capture missing context. Iterate form design monthly based on data and agent feedback.

Ticket tracking: self-service status and updates

Customers who can track their own tickets send fewer "what is the status?" emails. Helpefi portal ticket tracking shows: ticket status (open, pending, resolved, closed), last update timestamp, agent reply history, and internal notes visible only to the customer. Customers reply to tickets on the portal and their response appears in the agent workspace ticket thread. Ticket tracking reduces email volume significantly. Customers check status on the portal instead of emailing support@ for updates. Portal notifications (email or in-browser) alert customers when their ticket status changes or an agent replies. Customers configure notification preferences per ticket. Self-service actions on tracked tickets: add comment to existing ticket, attach additional files, close resolved tickets, reopen closed tickets within a configurable window, and update contact information. Each action is logged in the ticket audit trail. Portal ticket history shows all past tickets from the customer email or account. Customers looking for past solutions search their ticket history before submitting new tickets—reducing duplicate submissions for recurring issues.

Multi-brand portals and white-label operations

Agencies and multi-product companies need separate portals per brand with independent domains, branding, and knowledge collections. Helpefi supports multi-brand workspaces where each brand has its own portal with custom domain, logo, colors, knowledge base collection, and ticket queue routing. White-label portals remove all Helpefi branding so the portal feels like a custom-built support site. Custom domains on Professional and Enterprise make each portal client-ready without generic vendor URLs. Agency agreements where client support operates under the client brand benefit from complete white-label configuration. Data isolation per brand prevents cross-contamination. Database-per-tenant isolation on Enterprise gives hard boundaries between client data—critical for security reviews in regulated industries. Portal-specific SLA policies ensure each brand commercial commitments are enforced independently. Agents working across brands use team views filtered by brand. A single agent can support multiple client portals without logging into different systems. Manager dashboards show aggregate metrics while brand managers see only their brand data.

Portal analytics: understand customer behavior

Portal analytics show how customers interact with your self-service experience before reaching agents. Key metrics: search volume and top search queries, deflection rate (customers who found answers without submitting tickets), form completion rate and abandonment rate, popular articles and categories, and portal traffic by device, language, and region. Search analytics identify content gaps: search terms that return no results are candidates for new articles. High-volume searches with low deflection indicate articles exist but do not satisfy the customer intent—rewrite for clarity and completeness. Track search trend changes after product launches to anticipate new support needs. Form analytics reveal friction points: high abandonment on specific fields indicates they are confusing or unnecessary. Low form completion on mobile suggests mobile optimization needed. Compare completion rates by device and language to identify accessibility issues. Share portal analytics with product and marketing teams. Product teams see which features generate the most support traffic; marketing teams see which landing pages send customers to the portal. Cross-functional portal analytics build organizational understanding of customer support needs.

Portal with shared inbox, AI, and SLA

The portal is not a standalone tool—it is the customer-facing layer of your Helpefi operation. Portal ticket submissions flow into the same shared inbox where email, chat, and SMS tickets are handled. Agents work portal tickets alongside other channel tickets with the same assignment and SLA rules. Deflection on the portal reduces volume before tickets reach agents, but tickets that are submitted carry full context: which articles the customer viewed, their search queries, and any custom field data. Agents see what customers already tried and start from a position of context rather than asking the customer to repeat information. AI Copilot assists agents on portal tickets with the same draft suggestions and knowledge grounding as email and chat tickets. Consistent AI assistance regardless of channel means agents have the same tools for every ticket type. SLA policies apply to portal tickets with appropriate targets. Portal submissions during business hours receive standard SLA; after-hours submissions follow email SLA for next-day response. SLA compliance on portal tickets is tracked in the same reports as email and chat for unified metrics.

Migrating your portal from Zendesk, Freshdesk, or Help Scout

Portal migration involves three components: custom domain and branding setup, knowledge base article migration, and portal design configuration. Start by configuring the Helpefi portal with your domain and branding during the trial period so customers see the new portal before full cutover. Knowledge base migration from your legacy portal is the most time-consuming step. Audit articles before migration: keep high-value, recently updated articles; archive stale content in legacy system; and rebuild categories to match Helpefi collection structure. Redirect critical legacy article URLs to Helpefi equivalents. Portal form design during migration is an opportunity to improve. Review your current ticket form fields, identify which are essential and which add friction. Redesign forms with conditional logic and deflection that your legacy portal may not have supported. Launch the new portal alongside the old one during parallel run. Redirect a subset of customers to the new portal via DNS testing or beta group. Validate portal search, deflection, ticket submission, and tracking before full DNS cutover. Most portal migrations complete within two weeks when knowledge base content is well organized.

Use case: SaaS product portal

A SaaS company launches branded portal on support.product.com with knowledge base and ticket submission. Within three months, portal deflection handles thirty percent of support volume and ticket tracking reduces status-check emails by half.

Use case: Agency white-label portals

A digital agency launches separate branded portals for each client with independent knowledge collections and ticket routing. Each client has a custom domain and white-label experience, all managed from one Helpefi workspace.

Use case: Ecommerce self-service portal

An online store launches a portal with shipping policy articles, return form submission, and order tracking integration. Portal deflection handles most pre-purchase and post-purchase questions, freeing agents for order-specific issues.

Use case: Enterprise IT service portal

An enterprise IT department launches an internal service portal for employees to submit laptop requests, software access requests, and incident reports. Service catalog deflection suggests relevant articles before tickets are created.

Use case: Multi-language international portal

A global company launches portals in English, Spanish, and French with localized knowledge base content and ticket forms. International customers serve themselves in their preferred language without relying on email translation.

Your brand, your portal, your customers first choice

Helpefi customer portal combines branded self-service, intelligent ticket submission, tracking, and deflection in one experience your customers will actually use. Configure your domain and branding, publish articles that deflect common questions, design forms that capture context without friction, and let customers track their own tickets. The portal is your support operation customer-facing evidence—make it reflect the quality your team delivers.

Frequently asked questions

Can we use a custom domain?: Yes. Custom domains are available on Professional and Enterprise plans. Default portal URLs (your-workspace.helpefi.com) work on every plan including trial.
Does the portal require customer accounts?: Customers can submit via email verification or optional login—you choose the friction level. Logged-in customers get ticket history and tracking; email-only submission is simpler but loses tracking capability.
Can the portal serve multiple brands?: Yes. Multi-brand workspaces support separate portals per brand with independent domains, branding, knowledge collections, and ticket routing. Database-per-tenant isolation provides data boundaries between brands.
How does portal deflection work?: As customers type their ticket subject and description, the portal suggests relevant knowledge base articles. If customers find answers, they do not submit a ticket—that is a deflection. Articles suggested based on semantic search matching intent.
Can customers track their tickets?: Yes. The ticket tracking view shows status, update history, agent replies, and allows customers to add comments or attachments. Email notifications keep customers informed without checking the portal.
What custom fields are available?: Text, dropdown, multi-select, file upload, checkbox, and date fields. Conditional logic shows fields based on prior selections. Configure fields per queue or brand for appropriate context capture.
Is the portal mobile-responsive?: Yes. The portal is responsive on mobile devices with touch-friendly forms and navigation. Test portal on mobile after configuration to verify search, form submission, and ticket tracking work correctly.
Which plans include customer portal?: Customer portal with knowledge base search and ticket submission is included on all plans including trial. Custom domains, multi-brand portals, and white-label options expand on Professional and Enterprise.
How do we migrate our portal from another platform?: Configure domain and branding during trial, migrate selected knowledge base articles, redesign ticket forms with conditional logic, and launch alongside legacy portal during parallel run before DNS cutover.
Does the portal support multiple languages?: Yes. Configure portal UI translations and knowledge base articles in multiple languages. Portal detects customer browser language or offers manual language selection.

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