HomeChat Widget
Get startedThe launcher and panel across every page of your portal, styled down to the token — two palettes, your typography, your copy — with the real embed bundle rendering beside the controls as you change them.
Book a demo →Two palettes
A light and a dark set on every style, edited independently.
Fourteen tokens
Each one named for what it paints, not for where it sits in a file.
Live embed
The preview is the real bundle, not a picture of one.
Preview
Most theme editors show you an approximation and let you find out later. This one renders the real embed bundle in the panel next to the settings, so what you are looking at while you pick a colour is what a customer gets when the page loads.
Colour
Not a primary and a secondary and a hope. Every colour the widget uses is listed by the thing it actually colours — the send button, the icon on an accent card, the wash behind the header, the floating launcher — so matching your product is a matter of reading down a list rather than guessing.
Shape
Put the launcher in whichever corner your product has room for. Turn off the tabs you are not using — and if only one is left, the bar goes away rather than sitting there with a single item in it.
Voice
The greeting, the line under it, the name on the header and the questions offered up as chips are all copy you write. A widget that opens with your own four most-asked questions is doing more work than one that opens with a blinking cursor.
Who uses it
For product teams
The reason support widgets look cheap is that they are themed with two colours and a logo slot. Fourteen named tokens and two full palettes is enough to make it look like a part of the product rather than a visitor.
For designers
The panel beside the controls is the real bundle, so there is no publish-and-check loop. Pick the accent, see the send button and the active tab move with it.
For support leads
Put your most-asked questions on the home tab as chips. The ones people tap are the ones worth writing an article about.
Connected
Every module writes to the same customer graph, so data captured here shows up wherever it is useful — no connectors to authorize, no sync to babysit.
See all integrations →AppGram modules
FAQ
Yes — the panel beside the settings renders the real embed bundle rather than an illustration of it, so the greeting, the cards, the tab bar and the launcher you are looking at are the ones a visitor gets.
Every style carries both. You edit the light palette and the dark palette separately, and set whether the widget always renders one, always renders the other, or follows whatever the visitor's system is set to. There are helpers to copy one palette across to the other or invert it as a starting point.
Fourteen colour tokens, each named for what it paints — the accent, the icon on an accent card, the panel background, the wash behind the header, card backgrounds, text and muted text, borders, the user message bubble and its text, the launcher and its icon, the tab bar, and the glow. Then the font family, the base size, a background image with a texture over it, the panel blur, and the corner it launches from.
Yes. Home, Messages, Help and Changelog are each on or off, and you choose which one opens first. If you leave only one on, the bottom bar hides itself rather than showing a single item.
Yes. Styles are a library — the built-in presets plus any you build — and one is live at a time. That makes it safe to work on a new look without touching the one your customers are currently seeing.
Get started
Everything you were bolting together — feedback, roadmap, changelog, help, support, status, forms — in a single workspace with one API and one bill.
Cancel anytime. Yours to test on real customers.
