Self-service portal

A central place for your customers

Bring guides, requests and updates into a portal with your identity. Customers can find information, open tickets and follow conversations with your team.

  • Knowledge base, tickets and updates in one place
  • Custom domain with a managed certificate
  • Public, private or mixed access, portal by portal
A central place for your customers

From search to resolution

Stay in the same channel

Customers find an answer, submit a request when needed and follow every update from the same branded portal.

Control and identity

The portal adapts to the person signing in

Create contact groups to make knowledge base content and forms available to the right people.

Manual or dynamic groups

Select contacts or define groups by company and customer category. They update when the data changes.

Inherited restrictions

Content cannot widen access denied by its folder. Rules remain combined when you move or republish it.

Preview as a contact

Before publishing, check the result for a real contact or an unauthenticated visitor.

Your domain and your brand

Each portal has its own public name, logo, favicon, colors, languages and footer.

End users under control

Email invitations, explicit statuses, per-portal access and bulk user operations.

Company identity

On Enterprise, end users sign in through their existing identity provider, without another password.

Multiple portals

Manage multiple brands and audiences from one account

Create separate portals for brands, products or customer groups, each with its own identity, content and settings. The same article can appear on several portals or just one.

Example portal list
PortalAddressStatusContent published
Customer supportsupport.example.comActive · DefaultGuides, FAQs, downloads
Reseller arearesellers.portal.uppo.ioActive · PrivatePrice lists, contracts, tutorials
New productbeta.portal.uppo.ioNot activeRelease notes

Illustrative example. All portals are configured within the same Uppo company, with the same team and queues.

Configuration, availability and frequently asked questions
Access, groups and contact preview

Create contact groups and use them to make knowledge and web forms available only to the right people. Rules apply to both visibility and submission, not just navigation.

Every portal starts on a portal.uppo.io subdomain. You can also configure a custom domain, depending on your plan.

Manual or dynamic groups

Select contacts or define groups based on their company and customer tier. Dynamic groups update as the underlying data changes.

Content and forms for customer groups

Include only selected groups or exclude them. The same model applies to folders, individual content and web forms.

Inherited restrictions

Content cannot broaden access denied by its folder: rules combine and stay protected when content is moved or republished.

Preview access by contact

Before publishing, check the result for a real contact or an anonymous visitor and inspect the effective rules.

Your domain and your brand

Customise identity, header, layout, navigation, languages, ticketing and footer. You can use a custom domain with a managed certificate, depending on your plan.

Control who gets access and what they can see

Invite customers, decide which portals they get into and revoke access when you need to, from a single list.

Preview access by contact

Access rules also protect search, attachments and form submissions.

Make it work for your team

Manage multiple brands and audiences from one account

One portal per brand

Public name, logo, favicon, colours, languages and footer belong to each portal. Changing one leaves the others alone.

Different audiences, different catalogues

Categories and content are published on the portal that needs them: the same article can sit on several portals, or on just one.

Central administration

Every portal is configured from the same Uppo account, with the same team, the same queues and the same assignment rules.

Prepare it, open it when you want

A portal can be prepared quietly and switched on when it is ready; switching it off loses neither content nor settings.

Every customer follows their own requests

From the portal, customers see the history of their tickets, filter by status, priority, topic or date, read the replies and answer without going through email.

Signed in to the portal

  • They only see the tickets they are linked to, on the portals you granted them.
  • They filter by status, priority, topic or date and find the right request straight away.
  • They reply and attach files in the same conversation your team is working in.
  • This is the recommended path for confidential conversations.

Or from the link received by email

Someone without an account opens a single ticket from the link: the one it was generated for, and nothing else belonging to your company. The link gives access without signing in and should be kept confidential. Every visit is recorded, with the date of the last access and the number of openings.

Public content, private requests
Access

Open the knowledge base to everyone, keep conversations for signed-in customers, or combine the two.

Public

Anyone can read the knowledge base and raise a request without signing up. The right shape when support doubles as a shop window and answers need to be reachable from search engines.

Private

Access is by invitation: end users only see the portals you have granted them.

Mixed

The knowledge base stays public, while the ticket area requires signing in: open content and private conversations in the same portal.

What each person can see

Those three shapes come out of separate settings you can combine however you need.

  • Knowledge base: public or restricted, with or without the author's name, with or without comments and article feedback.
  • Submitting tickets: open to anyone, or to signed-in users only.
  • Ticket access: configure who can read requests separately from submission permissions.
  • Customer dashboard: choose whether it is available on each portal.
  • Published forms: choose which of your forms appear on this portal.
  • Sections: the knowledge base and the ticket area are switched on and off one at a time, portal by portal.

Corporate identity

On the Enterprise plan, end users sign in with the identity they already have instead of managing another password: authentication goes through your provider, and the user record shows which external identity it is linked to.

SSO, IP restrictions and audit trail
Control who gets access and what they can see
End users

Control who gets access and what they can see

Invite customers, decide which portals they get into and revoke access when you need to, from a single list.

Invitation

You invite someone by email; until they complete the process they stay pending, and the invitation can be sent again.

Explicit statuses

Active, pending, inactive or revoked. The status shows in the list, can be filtered on, and is changed from the user's record.

Access per portal

Access is granted per portal, not per company: the same person can be let into one and kept out of another. Who granted it and when stays on record.

Bulk actions

Grant or revoke access for a group of selected users in one go, instead of opening one record at a time.

External identities

With single sign-on the user is created on first login, and the record shows the external identifier they are linked to.

Activity

First sign-in, last sign-in and number of sign-ins, so you know who actually uses the portal.

Your domain and your brand
Customisation

Your domain and your brand

Customise identity, header, layout, navigation, languages, ticketing and footer. You can use a custom domain with a managed certificate, depending on your plan.

Identity

Public name and internal name, logo, favicon, and the address the logo links back to.

Header

Title, subtitle and the text inside the search box: the first three lines a customer reads.

Layout and colours

Pick one of the available layouts and set the primary, secondary and accent colours.

Languages

One default language plus the active ones, portal by portal.

Ticketing

Page titles, permissions for submitting and reading, available filters, personal signature and published forms.

Knowledge base

Titles, visibility, author name, comments and article feedback collection.

Footer

Text, your own links, legal name, company details and the privacy, cookie and terms addresses.

Domain

A portal starts on a portal.uppo.io subdomain. Depending on your plan, you can replace it with your own domain.

Publish on your own domain

Custom domains are available depending on your plan. We handle the certificate: what you need is two DNS records.

  1. 01

    Add the domain

    Enter the full name, for example support.yoursite.com. Uppo returns the records to create.

  2. 02

    Create the DNS records

    One CNAME proves the domain is yours and allows the certificate to be issued; the other routes traffic to the portal.

  3. 03

    Go live

    The domain's status stays visible, with the validation and rollout dates. You can have the records checked again without starting over.

Until your own domain goes live, the portal keeps answering on its original address: there is no moment when it is unreachable.

See what customers search for and which answers are missing
Analytics

See what customers search for and which answers are missing

Analyse searches, missing results and most-read articles to improve self-service continuously.

Most frequent searches

The words customers actually type, ranked by volume, over the period you choose.

Searches with no results

The list of questions the portal could not answer: your content backlog, already prioritised by customers.

Most read articles

Which content carries the traffic, with views over the period and where readers came from.

Articles to revisit

Content opened often and rated unhelpful, or never opened at all: the pieces to rewrite or retire.

Searches against tickets

How much demand the knowledge base absorbs and how much still turns into a request.

Article feedback

Turn it on for a portal and customers say whether an article helped, with room to explain why.

These are your portal’s own numbers. A newly published portal fills up with its first visits.

Availability by plan

Availability by plan

Compare portals, private-portal monthly active users, languages and customisation options.

Portals you can publish

Starter
1
Growth
2
Scale
5
Enterprise
Scalable

Public portal users and views

Starter
Unlimited
Growth
Unlimited
Scale
Unlimited
Enterprise
Unlimited

Monthly active private portal users (MAUI)

Starter
25/month
Growth
100/month
Scale
250/month
Enterprise
1,000/month

Knowledge base languages

Starter
1
Growth
2
Scale
5
Enterprise
Scalable

Custom domain with managed certificate

Starter
—
Growth
Included
Scale
Included
Enterprise
Included

Full white-label

Starter
—
Growth
—
Scale
—
Enterprise
Included

SSO and SCIM provisioning for end users

Starter
—
Growth
—
Scale
—
Enterprise
Included

Logo, favicon and colours can be customised on every plan. A dash marks a feature that is not part of the plan.

Compare plans and pricing

Frequently asked questions

Access, content, domains and managing multiple portals.

Can I create more than one portal?

Yes. How many depends on the plan: one on Starter, two on Growth, five on Scale, an agreed number on Enterprise. Each portal has its own settings, content and authorised users, and can be switched on or off without touching the others.

Can I use my own domain?

Availability depends on your plan. Every portal starts on a portal.uppo.io subdomain; to replace it you add your domain and create two CNAME records at your DNS provider, one so the certificate can be issued and one to route traffic. Until it goes live, the portal keeps answering on its original address.

Does the customer have to create an account?

It depends how you set the portal up. The knowledge base can stay open to everyone, and raising a request can be left open or restricted to signed-in users. Anyone who receives the link to a ticket by email can read it and reply without registering.

Can I show different content on different portals?

Yes. Each piece of content is published on the portals where you want it: the same library feeds a portal open to customers and a private one for resellers, with different catalogues and one editorial team.

Does the portal support multiple languages?

Yes. For each portal you pick a default language and the active ones. How many knowledge base languages you get depends on the plan: one on Starter, two on Growth, five on Scale, and an agreed number on Enterprise. Content is shown in the language requested, so translate the sections you want published in that language.

How are customer tickets protected?

Data is separated per company, and an end user only sees the tickets they are linked to, on the portals you granted them. The link sent by email opens a single ticket without signing in, so it should be kept confidential. Every visit is recorded. For confidential conversations, the recommended path is the signed-in portal.

What happens when a search returns nothing?

The visitor stays on the portal and can raise a request from there. The search lands in the list of searches with no results, which you can review by period: the most direct way to learn which content is missing.

Read more

Knowledge base

How the content your portal publishes is written, organised and translated.

Go to the knowledge base

Widget

The same content and the same form inside your own site, without sending the visitor away.

Go to the widget

Plans and limits

Compare portals, languages, custom domains and white-label options across plans.

See the plans

All features

Tickets, SLAs, automations, workflows, analytics and security: the full picture.

See the features

Several brands, SSO or unusual access requirements?

If you serve more than one brand, have an identity provider to connect or your own rules about who sees what, the Enterprise plan is agreed around your numbers.

Open your customer portal

Public content, private requests: you decide what each audience can see.