A feedback widget that looks like your product, not like ours.
Describe how it should look. See it immediately. Publish when it is right. No CSS, no redeploy, and no widget that visibly belongs to somebody else.
Teal, square, bottom left
"match our teal brand, square corners, put it bottom left"
Dark, understated
"dark panel, understated, keep it out of the way"
Editorial, high contrast
"high contrast, serif, big and confident"
Every one of these is the real widget, rendered by the code that ships to your site.
The reason widgets get removed
In-app feedback widgets get installed in an afternoon and taken out a month later, and it is usually not because they stopped working. It is because they look foreign on the page. A rounded indigo button on a site with square black buttons reads as an advert for someone else's product rather than a part of yours, and eventually somebody in a design review says so.
The usual fix is a stylesheet override, which works until it does not: the widget ships a change, your selector stops matching, and the thing looks broken instead of foreign. That is not a customization story, it is a maintenance burden with a customization story attached.
So the design lives with us instead, and what ships is white label: your own branding on the widget and no mark of ours anywhere on it. You describe what you want, it renders inside an isolated root that your CSS cannot break and that cannot break your CSS, and the look survives every upgrade because it is data rather than a patch.
How it works
- 1
Describe it
Say what you want in a sentence. "Match our teal brand, square corners, bottom left." The designer reads the colours on your own site, so the first suggestion already looks like you.
- 2
See it
The preview is the real widget, rendered by the same code your visitors get. What you approve is what ships, not an approximation of it.
- 3
Publish it
One click. The widget picks it up within a minute. Your install snippet never changes, so nobody has to redeploy anything.
- 4
Change your mind
Every published version is kept. Roll back to any of them in a click, without losing the one you rolled away from.
What it will not do
Nothing the assistant produces reaches a visitor until you press publish. Designs are checked before they are stored, anything that could load a remote resource is stripped, and the widget runs in a closed shadow root so a design can only affect the widget.
If the design service is unreachable, the widget renders its built-in styling and keeps collecting feedback. Styling is never allowed to take the thing offline.
Frequently asked questions
- Is the feedback widget white label?
- Yes. The widget carries your own branding and nothing of ours: no FeedbackFlow name, logo, or "powered by" line is shown to your visitors, on any plan including Free. The launcher label and the panel heading are yours to set, and the colours, corners, and position come from the design you publish.
- Do I need to write CSS to customize the feedback widget?
- No. You describe the look you want in plain language and the designer produces it. If you do want to hand-tune something only CSS can reach, you can, and it is scoped to the widget so it cannot affect the rest of your page.
- Does changing the widget design require a redeploy?
- No. The install snippet is pasted once and never edited again. The widget fetches its published design when it loads, so publishing a change takes effect on your site within a minute without touching your code.
- Can a bad design reach my visitors by accident?
- No. Nothing the assistant produces goes live until you press publish. Every published version is kept, so you can roll back to any earlier one in a click.
- Will the widget break the styling on my site?
- No. The widget renders inside a closed shadow root, so its styles cannot leak into your page and your page styles cannot reach it. It looks the same on every site, including ones with aggressive CSS resets.
Make it look like yours
Free to start, and the widget is on every plan.