How to Manage Feedback for Multiple SaaS Products in One Inbox

To manage feedback from several SaaS websites without juggling separate tools, create a separate feedback widget for each website, approve each website’s origin, then review everything in one inbox and filter by bubble when you need to focus on a particular product. This keeps each site’s settings distinct while giving you one place to review incoming messages.

Set up one bubble per website

A bubble is the widget visitors use to send an Issue, Idea or Question. Give each bubble a clear internal name, such as “Invoice app” or “Booking tool”, and set its allowed website to the full origin where it should appear. That origin is a restriction: requests from an unapproved website are rejected.

Each bubble has its own site key, design, wording, feedback types and active status. Its site key identifies the bubble; the website check still applies. Feedback from the bubbles in your account can be managed in the same workspace and inbox. Feedback Bubble’s current public site lists support for up to five websites per account; check the live site for current plan details. Feedback Bubble’s website

A hypothetical two-product setup

Suppose you build a lightweight invoicing app and a separate booking tool. Create one bubble for each website. Name them so you can tell them apart in the dashboard, set each allowed website to the matching site, and choose wording that fits the product. For example, the invoicing widget might ask for a report when a payment status looks wrong, while the booking widget might invite ideas about managing appointments.

Install each widget on its own site

In Feedback Bubble, go to Dashboard > Bubbles > New bubble and enter the bubble name and allowed website. After activating your subscription, open Install for that bubble and add its generated code to the matching site. Repeat for the other website, using its own bubble and code.

Keep the bubble names clear. If feedback arrives from several products, the name helps you identify its source without opening every message. You can also customise each widget’s colour, icon, position, theme and form wording to suit that site. When you save ordinary design or wording changes, the existing site key picks them up, so you do not normally need to paste the installation script again.

Review all feedback, then filter by product

New submissions appear in Dashboard > Inbox > Needs review. Start with the combined view to catch messages across your products. When you want to investigate one site, filter by its bubble. You can also search message text, filter by Issue, Idea or Question, and sort by newest or oldest.

For the invoicing app, you might filter to its bubble and look for reports about failed exports. Then switch to the booking tool’s bubble to review requests about calendar settings. The submissions remain separate records, even when both products raise a similar need. If several customers describe the same problem, you can consider connecting those messages to one planned product change rather than treating each message as a separate task.

Keep useful feedback organised

A combined inbox is easier to use when each message has a next step. Keep new submissions in Needs review while you decide what to do. Move useful messages to Saved if you want to retain them without committing to product work, or use Archive when they no longer need attention. These actions organise your workflow; they do not change the customer’s original wording.

When related feedback supports a change, connect the messages to a planned change in a release. The change can move through Planned, Building and Shipped as the work progresses. A request is evidence to consider, not an instruction to build: check how well it fits your product, whether other users have the same problem, and what the work would displace.

What one inbox does and does not solve

A shared inbox reduces the need to check separate feedback tools for each website, but it does not decide which product deserves your attention first. Use the bubble filter when product context matters, and keep names consistent so messages are easy to identify.

Page and device details can help explain where a message came from, but they do not replace a clear description from the visitor. Feedback Bubble also does not combine feedback across separate accounts into one inbox, so this setup is for several bubbles managed within the same account.

If you manage more than one SaaS website, start by naming each bubble after its site and confirming the allowed website before installing its script. Then use the combined inbox for review and the bubble filter when you need to focus. See the guide to organising customer feedback