Client Portal

Give your customers a branded, public-facing page to submit support requests and browse your knowledge base — no login required.

What is the Client Portal?

The Client Portal is a public webpage that belongs to your organization, hosted at a URL like yourcompany.fynedesk.io. Your customers visit this page to submit support requests or find answers in your knowledge base — without needing a FyneDesk account.

Every request submitted through the portal becomes a ticket in your FyneDesk queue, just like tickets created manually or via email. Your team handles them the same way.

Why use it? Instead of customers emailing you directly (which can get lost in your inbox), they use a structured form that captures their name, contact details, and a description of their issue. This means cleaner tickets and less back-and-forth.

What your customers see

When a customer visits your portal, they see a simple page with your organization name, a form to submit a request, and optionally your published knowledge base articles. There is no login wall — anyone with the link can use it.

Client portal homepage as a customer sees it

The submission form asks for:

Their name and email address
A subject (ticket title)
A description of their request

Once submitted, the customer sees a confirmation message and the ticket appears in your FyneDesk queue.

Setting up the Client Portal

You need to be an Admin to configure the portal. Go to Settings → Client Portal in your FyneDesk app.

Settings page showing the Client Portal tab with portal address field and enable toggle

1 Type a short name for your organization in the portal address field. This becomes your portal URL. For example, acme gives you acme.fynedesk.io. Use lowercase letters, numbers, and hyphens only.
2 Click Save. FyneDesk checks if the name is available and reserves it for your organization.
3 Once saved, flip the Enable Client Portal toggle on to make the portal publicly accessible. You can toggle it off at any time to take it offline without losing your address.

Choosing a good portal address Keep it short and close to your company name. Your customers will see and type this URL, so something like acme or acme-support works better than something long or random.

Enabling the Knowledge Base on your portal

If you have published articles in your FyneDesk knowledge base, you can display them on the portal so customers can find answers before submitting a request.

In Settings → Client Portal, toggle Show Knowledge Base on. Only published articles will appear — drafts stay hidden. You can turn this off at any time if you want a submission-only portal.

Sharing your portal with customers

Once the portal is enabled, share the URL with your customers. Good places to put it:

Your website's contact or support page
Email signatures
Invoices or receipts
A pinned post in any customer community or chat

The portal is public Anyone with the URL can submit a request. There is no authentication on the portal by design — the goal is to make it as easy as possible for customers to reach you. Spam is rare in practice since tickets require a name and email.

Disabling the portal

Go to Settings → Client Portal and flip the Enable Client Portal toggle off. The portal URL will stop working immediately and show a "not found" page. Your portal address is preserved — enable it again anytime to bring it back.

Frequently asked questions

Can I customize the portal's appearance?

The portal currently shows your organization name and uses FyneDesk's default styling. Custom branding (logo, colors) is on the roadmap.

Do customers need an account to use the portal?

No. Customers fill in their name and email on the form. There is no signup or login required.

Where do portal submissions appear in FyneDesk?

They appear in your regular ticket queue alongside all other tickets. You can filter by ticket source to identify portal submissions.

Can I change my portal address later?

Yes, but be careful — changing it breaks any existing bookmarks or links you've already shared. If you must change it, update anywhere you've published the old URL.