Your Feedback Widget Can Now Talk Back
SeggWat now has live chat built into the same feedback widget. Real-time conversations with your users, on your own stack, EU-hosted, with no third-party chat vendor in the middle.
A feedback widget is a one-way door. Someone hits the button, types out a bug or a request, clicks send, and then nothing. They don't know if a human saw it. You don't get to ask the obvious follow-up ("which browser?", "can you send a screenshot?"). The most useful moment, when the user is right there and still annoyed, slips away.
So I built the missing half. SeggWat now has live chat, and it lives inside the same widget you already embed.
Same button, no second vendor
This is the part I care about most. Live chat isn't another script tag, and it isn't Intercom bolted onto the corner of your site. It's a module inside the feedback widget you already have. The same button that collects bug reports now opens a conversation. It's one embed and one widget, the same place your users already go.
The chat code only loads when you turn chat on, so if you don't use it, your users never download it. No bloat for the projects that just want the feedback button.
On your own stack, in the EU
Most "add live chat" stories end with you piping your customer conversations through a third party in another jurisdiction. I didn't want that for SeggWat, and I suspect you don't either.
SeggWat's chat runs on the same Rust and Axum server as everything else. Messages stream over Server-Sent Events, backed by MongoDB change streams, so a reply lands on the other side in real time without anyone polling. Your conversations live in your SeggWat data, EU-hosted, under the same GDPR terms as the rest of your feedback. There's no extra data processor to add to your privacy policy.
Nobody around? It becomes an email
Real-time is great when someone's watching the inbox. When they're not, the message can't just vanish. If no one picks up a conversation, it turns into an email thread for your team, and the user gets the reply by email too. The conversation survives the gap instead of dying in a widget nobody had open.
Chat is for identified users, the people you already know who are signed in on your site. That keeps it real conversations with real customers, not a drive-by spam channel.
It plugs into the rest of SeggWat
A chat is rarely just a chat. Sometimes it's a bug, sometimes it's a feature request. From the chat inbox you can turn a conversation into a feedback item or a board idea in one click, and the transcript comes along, so nothing gets lost in the hand-off. And because it's all one system, your median first-response time shows up in Insights right next to your feedback and rating stats.
Try it
Live chat is part of Pro, and it's included in the 14-day trial. If you're already on SeggWat, switch it on in your project's feedback channel settings and it appears in the widget you've already shipped. There's no new embed to add.
EU-hosted, GDPR-friendly, screenshot annotation, surveys, an ideas portal, an MCP server, and now live chat. 14-day free trial.
Related Posts
Reward Survey Completers with a Discount Code
Pair a targeted survey with a discount code on the thank-you screen — incentivize the feedback you actually asked for, at the moment it matters.
In-App Surveys Are Here: Ask Users the Right Question at the Right Moment
SeggWat now ships in-app surveys — NPS, CSAT, CES, and custom multi-question forms that fire on the right page, at the right moment, from one script tag.
Why I Built an MCP Server Into My Feedback Tool
How SeggWat exposes feedback, ratings, and NPS data to AI assistants via the Model Context Protocol, and why MCP is becoming table stakes for dev tools.
