Features / Support
Chat widget
Support inside your product
A widget that sits in your app, matches your branding, and knows which customer is using it, so nobody has to ask who they are or what plan they are on.
Appearance
What it shows
AI
Need a hand? 👋
We reply in minutes
You are chatting with Tore, an AI assistant.
The checkout button does nothing on my phone.
The same capture, from a phone. Mobile is not the cut-down version.
What it does
- Drops in with one script tag
- Your colors, your logo, your wording
- Knows the signed-in customer and the product they are using
- Opens straight into a bug report when something has broken
Without it
The widget is the first thing they meet, and usually the worst
Reporting a problem means leaving your product
The help link opens a new tab, a login they do not have, and a form that asks which product they use and what plan they are on. A good number of them close the tab and just stop using the feature.
The widget does not know who is in it
They are signed in, on the Pro plan, on the billing page, and the first thing the chat asks is 'can I take your account email?'. You are asking a customer to prove they are your customer.
It looks like somebody else's software
A round purple bubble in the corner of your teal app, another company's name under the message box, and a stock greeting written by a support tool vendor. Everyone can tell it was bolted on.
How it works
One script tag, and it knows who is there
Add the snippet and list the origins allowed to load it. Sign a short-lived identity token on your backend, with the secret held server side, and Tore rejects unsigned or expired tokens rather than trusting the browser. Anonymous visitors get guest mode instead, so nothing is gated behind a login they do not have.
It takes your brand, and you watch it change
Accent color, workspace name, your logo or just its initials, font, light or dark, left or right. The header can be a solid color, a gradient, one of six background treatments (Spotlight, Minimal, Grain, Grid, White, Light gray) or an image you upload. The preview beside the settings is the real widget component, so what you see is what your customers get.
What that includes
- Accent color
- workspace name
- your logo or just its initials
- font
- light or dark
- left or right
You decide what is in it, row by row
The widget config carries 77 settings, counted from the field list in the API. Search, suggested articles, recent conversations, recent tickets, a Report a bug row, a Request a feature row, the Conversations, Tickets and More tabs, known issues, changelog, feature board, guided tours, system status, proactive messages, the greeting, the AI disclosure line, the away message. Turn on what you want and hide the rest.
You choose which teammates your customers see
The live public widget team is an explicit list. Pick people, cap the number shown at five, and Tore publishes a first name and last initial (Maya P.) plus their initials, never an email address, a role or a photo. The setting carries a plain warning that your widget sits on a public website, so anyone visiting it, including scrapers, sees the names you publish.
What that includes
- Pick people
- cap the number shown at five
- Tore publishes a first name
- never an email address
- a role or a photo
A Bug Capture tab, configured separately
Screenshot, screen recording, an always-on buffer that keeps the last thirty seconds so a bug that already happened is still captured, console, network calls, page structure, device and browser, a report-strength meter, and a link you can send when you need them to record it. Input masking runs on the device before anything is uploaded and cannot be switched off.
What it means for you
They report it without leaving the page they broke
The thing that failed is still on screen, which is why the report arrives with the evidence rather than a paragraph of recollection.
It reads as part of your product
Your colors, your logo, your wording, your font, your team's names. Nothing in it says a support vendor was involved.
The public surface stays under your control
The widget config endpoint is unauthenticated by design, so only 58 of the 77 settings are published to it, through a separate allowlist that a new operator setting cannot silently join.
The honest limit: Availability and office hours, the settings for when Tore offers a human and when your team shows as online, are a preview today: the controls are visible and labeled, but they cannot be saved yet. Voice interactions and a few other rows are stored but not yet active on the live widget, and each one says so where you set it.
Also in Support