Immediate support, without leaving your website.
Offer your knowledge base, forms and chat right inside your site. Customers find answers without breaking their flow, and every conversation lands in the same queue as the rest of your work.
- Install it with a single script
- Publish changes from the Uppo dashboard
- Searches, chats and requests measured in one dashboard
Knowledge base, forms, chat
Self-service and human support in one widget
Combine knowledge base, request forms and live chat in the same experience. Activate only what is useful for each website and audience.
Knowledge base
Full-text search across published articles in the categories you choose, with article feedback and multiple languages.
Request forms
One or more forms with your fields. Submitting creates a ticket in the queue, and the requester receives a link to follow it.
Live chat
A real-time conversation with whoever is on shift: the chat becomes a ticket like any other, with the same queue and history.
Before the ticket
Reduce repeat requests before they reach your team
Suggest the most relevant answers before the form, while keeping a clear path to human support.
Suggestion optional
Articles stay one click away, while visitors who want to write can go straight to the form.
Articles before the form
The widget suggests relevant content before opening the form. Visitors who need more help continue with one click.
A guided path
Use a guided path for recurring requests, while keeping the way through to your team clearly in view.
Context rules
Different content on different pages
Map articles and categories to the addresses on your site. Someone on a product page or in the checkout sees suggestions that match the context, instead of a generic list.
| Where the visitor is | URL pattern | What the widget suggests |
|---|---|---|
| Product page | */products/* | Product guides and delivery times |
| Cart and checkout | /checkout* | Payment methods, discount codes, invoicing |
| Account area | */account/* | Sign-in, passwords, billing details |
The first rule that matches the address wins, so put the most specific ones at the top.
Contextual messages
Step in when the customer needs help
Show targeted messages based on the page and visitor behaviour, without interrupting the journey.
Time on page
After the number of seconds you set: useful where staying a long time usually means being stuck.
Page address
Show messages matched to the page URL, with an optional delay and content relevant to that page.
Visit count
From the third visit onwards, say: people who keep coming back to the same page are often still looking.
An event from your site
An event your own code emits, such as a failed payment or an abandoned cart.
Configuration, availability and frequently asked questions
More about this feature
Offer your knowledge base, forms and chat right inside your site. Customers find answers without breaking their flow, and every conversation lands in the same queue as the rest of your work.
You can see the effect in the same panel: searches run, articles opened, chats started and requests created over the period you choose.
- Install it with a single script
- Publish updates from Uppo
- Knowledge base, forms and chat in one interface
Knowledge base
Published articles become searchable inside the widget: the customer types and results appear straight away, without leaving the page.
- Full-text search across your published articles
- Only the categories you pick, not necessarily the whole catalogue
- Article feedback with thumbs, emoji, hearts or a numeric rating
- One default language plus the others you make available
Request forms
One or more forms with the fields you defined. Submitting creates a ticket in the queue, and the person who wrote gets a link to follow it from the portal.
- Choose which of your forms appear in this widget
- Show each form to everyone, selected groups only, or everyone except excluded groups
- Custom fields, so you collect what you need up front
- Attachments checked against type, extension and size
- The requester receives a link to follow their own ticket
Live chat
A real-time conversation with whoever is on shift. The chat becomes a ticket like any other: same queue, same rules, same history.
- Messages in real time, with no page reload
- A typing indicator while the agent writes
- You choose which agents can answer
- A dedicated message when the team is not available
The same knowledge base feeds the widget and the self-service portal: write the article once, then choose where it appears.
How the self-service portal worksMake it work for your team
Proactive message settings
Priority
When two messages could fire at once, priority decides which one appears: the visitor only ever sees one.
Once per session
Set a message to appear only once in the same session, so it does not follow the visitor from page to page.
Sender and avatar
The name and picture of whoever is writing: a person on the team, or a collective name, depending on how you want to come across.
Sound alert
Optional and off by default: turn it on only where it genuinely helps the message land.
Different content on different pages
Suggestions for groups of pages
A pattern with a wildcard covers an entire section of the site: you do not have to list addresses one by one.
Choosing the articles
For the cases you know well, you name exactly which articles should show up on those pages.
Choosing by tag
If your catalogue grows often, suggest by tag: new articles join the context without anyone editing the rule.
Live support during your team’s hours
Tie the chat to your team's hours; outside them, leave the knowledge base and the forms available.
Business hours
The chat follows a schedule with its own time zone: inside the hours it invites people to write, outside them it shows the message you prepared. You write both the title and the text.
Outside the hours
Knowledge base and forms, when enabled, stay available: someone arriving at eleven at night still finds an answer, or leaves a request that is already in the queue by morning.
Team identity and availability
Choose which agents handle this widget's chats and the identity they appear under.
Everyone, real names
Every agent appears with their own name and picture.
Selected agents, real names
Only the agents you picked answer, under their own identity.
Selected agents, under an alias
The agents you picked appear with a name and picture you choose.
One shared name
Every reply comes from a single collective name, such as "Support".
In line with your brand
In line with your brand
Match colours, header, launcher, position, typography and corner radius to your site's identity. The preview in the panel shows the real widget, not a mock-up.
Colours
Primary, secondary and accent: the three values that change the impression more than anything else.
Header
Solid colour, gradient, image or texture, with the text colour you choose for contrast.
Launcher button
A chat bubble, a question mark, a message icon or your own image, with or without a shadow.
Position
Bottom right or bottom left, with adjustable offsets so it does not sit on top of your own elements.
Typography
The system font or one of the available families: align typography, colours and style with your brand.
Corner radius
From square to heavily rounded: the detail that lines the widget up with the rest of your interface.
Size
The launcher scales. On a dense site, it is usually better to make it quieter.
Widget preview
Every change shows on the real widget before you save: you publish what you have already seen.
Add the widget to your site
Copy the snippet from the panel and paste it into the pages where you want the widget. Later changes need no further edits to your site.
- 01
Configure
Choose the experiences to enable, the categories, the forms and the look, with the preview in front of you.
- 02
Copy the snippet
The panel generates the code with your widget's identifier already in it.
- 03
Paste it into your site
In your page template, before the closing body tag. The script loads asynchronously and does not block rendering.
The snippet
<!-- Uppo Widget -->
<script>
window.UppoWidget = {
config: { widgetId: 'ID-DEL-TUO-WIDGET' }
}
</script>
<script src="https://widget.uppo.io/uppo-widget.iife.js" async></script>Copy the script once. From then on, content, forms, chat and appearance are managed from the Uppo panel.
Embedded in your site, protected by Uppo
Restrict the domains the widget may appear on, and recognise the users your site has already authenticated. Attachments go through format validation; content scanning depends on the features in your plan.
Allowed domains
You list the hosts where the widget may be embedded, with subdomains in short form (*.example.com). The panel flags a badly written entry straight away.
Users you have already authenticated
When your site has already recognised someone, your server signs their identity with the widget secret and Uppo verifies that signature before accepting it. The secret stays on your server and can be regenerated.
Attachments are checked
Documents and images, up to five files of ten megabytes each per request. Extension and declared type have to agree: archives, executables and SVG are rejected.
Attachment scanning from the Scale plan
From Scale, you can enable protection with the Uppo team. Files sent when a ticket is opened through the widget stay in quarantine until a clean scan.
Measure widget adoption and impact
Measure widget adoption and impact
Analyse opens, searches, conversations and tickets created to see where the widget helps and where content should improve.
Sessions
How many times the widget was opened over the period you choose.
Open sessions
How many conversations are running right now.
Events by type
Searches, articles opened, chats started, tickets created: what people actually do inside the widget.
Average duration
How long a session lasts, from opening to close.
Requests avoided through self-service
The share of sessions that close without a request being opened, over the period you choose.
Session list
Start, last activity, duration and the page it began on, for the sessions you want to look at one by one.
Availability by plan
Widget limits, plan by plan.
| Feature | Starter | Growth | Scale | Enterprise |
|---|---|---|---|---|
| Website widget: knowledge base, forms and chat | Included | Included | Included | Included |
| Request forms you can publish | 3 | 10 | 50 | Agreed |
| Knowledge base languages | 1 | 2 | 5 | Agreed |
| Widget attachment scanning | — | — | Included | Included |
A dash marks a feature that is not part of the plan.
Compare plans and pricingFrequently asked questions
Installation, content and conversation management.
Do I need a developer to install the widget?
Not for the install: it is a script you paste into your page template, before the closing body tag, and everything after that is configured from the panel. You need technical hands in two cases: recognising already-authenticated users, which needs a signature computed by your server, and messages triggered by an event on your site, which your own code has to emit.
Can I use the knowledge base only?
Yes. Knowledge base, request forms and chat switch on one at a time. You can start with articles only, add the form once your content holds up, and turn on chat when you have someone to staff it. Switching an experience off does not delete what you configured.
Can I show different articles on different pages?
Yes, with context rules: you map a URL pattern to the articles or tags to suggest. A product page gets the product guides, the checkout gets the questions about payments and invoicing. The first matching rule wins, so the most specific ones belong at the top.
What happens to chat outside business hours?
You tie the chat to a schedule, and outside those hours the widget shows the title and text you wrote. Knowledge base and forms, when enabled, stay available: a request left overnight is already in the queue in the morning.
Can I use my own brand?
Yes: primary, secondary and accent colours, a solid or gradient header, the icon and position of the launcher, the font family and the corner radius. The preview in the panel shows the real widget, so you try combinations before publishing them.
How do I recognise users my site has already authenticated?
You turn HMAC verification on for the widget, and your server signs the user's identity — id, email and name — with the widget secret. Uppo recomputes the signature and compares it before accepting it. The secret stays on your server, is never returned by the configuration API and can be regenerated: after regenerating, update your integration, since earlier signatures no longer apply.
Can I restrict the widget to my own domains?
Yes, by filling in the allowed-domain list. Entries are written as hosts, not as full addresses, and subdomains are covered with the short form *.example.com. While the list is empty the widget loads wherever the script is pasted, so fill it in to keep it on your own sites.
How are attachments handled?
Every file goes through a check before anything is written: extension and declared type must agree and be on the allowed list — documents and images, no archives, executables or SVG — with a maximum of five files per request and ten megabytes each. From Scale, once the Uppo team enables protection, these files also go through quarantine and malware scanning.
What if the same customer also writes by email?
Two tickets are created, one per channel. From the customer's record you merge them into a single conversation with one click, so the history stays in one place.
Read more
Knowledge base
The articles the widget searches are written here: content types, categories, languages and revisions.
See the knowledge baseSelf-service portal
The space where customers follow their tickets and read the same content, outside your own site.
See the portalSecurity and governance
SSO, IP restrictions, audit trail, data redaction and how attachments are handled.
See securityPlans and limits
What each plan includes, from publishable forms to knowledge base languages.
See the plansBring support into your website
Paste one script, then configure colours, position, hours and content from the dashboard.