SaaS churn & cancel-page feedback
Add a simple chat on your cancel page. Users tell you exactly what went wrong — right when they decide to leave. No surveys. No follow-up emails. Just honest answers.
Free to start · No credit card required
Built for product-led SaaS
Exit chat (voice or type) + offer bar on your domain · Tagged churn reasons · Billing-agnostic
On their site
Same domain as your billing UI: the chat overlay opens on cancel intent — no redirect, no mystery iframe domain. Visitors can use voice or typingin the same embed (configure in the studio). Add a matching discounts & offers strip when you want promos beside that flow. Stylized preview below.
data-breakup on this buttonSent — voice message added above.
128
this month
Pricing
34% of sessions
12
high intent
sarah@******.com
“Mostly price… looked at AcmeCharts.”
alex@******.io
“Missing CSV export on Pro.”
What you’d do next
Filter by Pricing, read transcripts (typed or voice), and route high-intent exits to win-back.
In plain English
From cancel click to tagged insight in your workspace — no extra tools required.
Same billing or account page you already have — one script, your public key, and the cancel control marked with data-breakup="trigger".
A small overlay on your site (not a redirect). Guided prompts ask what changed and make space for honest answers — optionally paired with a top or bottom offer bar from the same embed.
Transcripts plus tags (price, competitor, bugs, missing features…) land in your workspace, ready to filter or route to win-back.
Why teams use it
We don’t promise a fixed “% saved MRR” — every product is different. Here’s what founders consistently get back.
Fewer “what went wrong?” threads in Slack. Every completed exit chat is searchable with a primary reason already attached.
See which competitors and feature gaps show up in real cancellations — not only when someone remembers to reply to a quarterly survey.
Flag conversations that deserve a human touch before the story goes cold — without blasting everyone who churned.
Outcomes depend on your traffic and follow-up — Flidget’s job is to make the why legible so you can prioritize saves, roadmap, and messaging with less guesswork.
1
Embed & key
3
Steps to insight
∞
Conversations
What you get
Exit conversations, optional promo bar, and dashboard signals in one product — so your team spends time on saves, not spreadsheets.
A warm in-page conversation on cancel intent — feels human, runs on your domain beside billing, and replaces the dead-end survey link.
Optional full-width strip from the same embed: promos, codes, urgency, and CTAs — tuned in the dashboard (paid tiers: always on).
Price, competitor, missing features, bugs, and more — pulled into structured fields from every completed session.
Transcripts, filters, trends, and competitor mentions in one workspace — no more exporting CSVs to find the pattern.
Spot who’s worth a personal follow-up while the cancellation story is still fresh — without spamming every leaver.
Four straightforward steps: you ship one embed; Flidget runs the in-page chat experience and organizes what comes back into the dashboard.
Add widget.js and your public key, mark the cancel control with data-breakup="trigger", and optionally configure the discounts & offers bar in the dashboard — same embed powers both. Pass optional user email for attribution.
Flidget opens a warm in-page chat. It listens, asks light follow-ups, and wraps up when the conversation feels complete — then their original cancel flow can continue.
Each session becomes a row in your dashboard with primary reason, sentiment hints, competitor mentions, and feature asks.
Filter by reason, read the transcript, and use the win-back queue for high-potential saves — without guessing from metrics alone.
Dashboard
One workspace for founders and growth: volume, completed chats, reason mix, searchable conversations, and rollups you can share with product or success without re-copying Slack threads.
Host widget.js from your Flidget app, pass your public key, and use data-breakup="trigger" on your cancel button. The same load can surface your configured offer bar — no second snippet. Runs on your domain next to billing — no heavy iframe SDK.
Your Flidget subscription uses Paddle checkout and the customer portal when you wire production. That is separate from your own app’s payments — the widget works with any provider on your cancel page.
Straight answers about exit chat, churn tagging, and pricing — we’re building toward deeper integrations next.
No. Flidget captures async feedback at the exact moment someone decides to leave — when they’re most willing to explain.
No. The exit widget is billing-agnostic: embed it on your cancel flow whether you use Stripe, Paddle, Razorpay, PayPal, Chargebee, Apple/Google subscription flows on the web, or anything else. It never calls your payment APIs. Your Flidget subscription (paying for Flidget itself) is handled separately via Paddle checkout and portal when configured.
Two different things: (1) Your customers’ payments stay on whatever gateway you already use — Flidget doesn’t replace that. (2) Your Flidget plan is billed through Paddle checkout and customer portal after signup, linked from the in-app Billing page when your environment is configured.
Treat Flidget like any third-party conversational product: review your vendor’s data policies and terms, and use enterprise-appropriate settings where your stack allows.
Most teams embed the script on staging in minutes. Tuning copy and colors in the widget designer is a few extra clicks before you point production traffic at it.
It is an optional full-width announcement strip (top or bottom) driven by the same widget.js as exit chat. You edit copy, colors, CTA, and placement in the dashboard; visitors see it on pages where the embed loads. Free workspaces include a short daily window for the bar; paid plans can keep it on continuously.
Free to start (10 lifetime exit completions; offer bar with a short daily window on Free), then Starter, Growth, and Scale — compare limits and attribution on the pricing page.
Ship the embed on staging this week. Tune exit chat and offer bar in the dashboard, then point production traffic at your cancel flow and watch tagged reasons roll into Flidget.
Exit chat
Turn on voice mode in the dashboard: visitors can speak (browser speech-to-text where supported), send after a pause, or fall back to typing. Transcripts still land in your churn dashboard with tags and win-back queue.