Always-on feedback

Add a Feedback Button to Your Website

Let users share feedback whenever they want - without waiting to be asked.

Triggered surveys capture what you ask about. A feedback button captures everything else - bugs, feature requests, and frustrations your surveys would never surface.

Add Feedback Button Free See how it works →

Button types

Three kinds of feedback buttons

Most common

Floating feedback button

A persistent tab fixed to the edge of the screen - typically the right or bottom edge. Always visible as users scroll and navigate. The most common feedback button placement for websites and SaaS apps.

Best for: SaaS apps, product dashboards, marketing sites

Contextual

Embedded send feedback button

Placed inline within the page - inside a navigation bar, next to a feature, or at the bottom of a page section. Less intrusive than floating, but only visible when the user is in that specific area.

Best for: Feature-specific feedback, docs pages, settings screens

Minimal footprint

Give feedback widget

A compact icon or minimal button that expands into a form when clicked. Often overlaps with in-app chat placement. Best when screen space is limited and you don't want a prominent tab.

Best for: Mobile apps, constrained layouts, secondary pages

Terminology

Feedback widget vs feedback button

Same thing - different frame. The button is the trigger; the widget is the full embedded component.

Feedback button

The clickable trigger element - the tab, icon, or labeled button that users see on screen. When someone says “feedback button,” they usually mean the visible element: what it says, where it sits, what color it is.

·The persistent floating tab on the screen edge
·The "Give feedback" link inside a nav bar
·The icon that expands when clicked

Feedback widget

The full embedded component - button plus the form that appears when it is clicked. When someone says “feedback widget for website” or “web feedback widget,” they mean the whole thing: the trigger, the form, and how it is installed on the site.

·The trigger button + the feedback form together
·Installed via a single JavaScript snippet
·Configured from a dashboard - no redeploy needed

What a user feedback widget typically includes

Trigger

The visible button or tab. Configurable: label, color, position, and whether it floats or is embedded inline.

Form

The panel that opens on click. Usually includes a free-text field, optional category selector (bug / feature / other), and a screenshot tool.

Routing

Where responses go. Customer feedback widgets send submissions to a dashboard, Slack, or email - and link each response to the logged-in user who submitted it.

Placement

Where to put your feedback button on website or app

Fixed right edge

Recommended

The default for most SaaS apps and websites. Always visible without interrupting the main content. Vertical tab with label "Feedback" is the most recognizable pattern.

App navigation bar

High visibility

Placed in the header or sidebar nav for logged-in users. Catches feedback from active users who are mid-session. Good for collecting feature requests and bug reports during normal use.

Next to specific features

Contextual

A small "Give feedback" link or icon next to a specific UI element. Captures feature-specific feedback and is less likely to be ignored than a generic button. Higher-quality responses.

Bottom of long pages

Engaged users

Users who scroll to the bottom are your most engaged visitors. A feedback prompt at the end of docs pages, blog posts, or landing pages captures opinions from people who read everything.

Post-action placement

High relevance

Shown temporarily after a user completes an action - exported a report, published a survey, sent an email campaign. Captures satisfaction at the highest-relevance moment without interrupting the flow.

Avoid: bottom left

Conflicts

The bottom-left corner is where live chat (Intercom, Crisp, Drift) and cookie banners live. Placing a feedback button there creates visual conflict and reduces click rates on both elements.

Button copy

Customer feedback button labels: what to write

Two separate copy decisions: the trigger button that opens the form, and the submit button inside it.

Trigger button (opens the form)

"Feedback"

Best defaultShort, neutral, widely recognized. Works for every context.

"Give feedback"

Action-orientedThe verb makes it clear this is for sharing an opinion, not getting support.

"Send feedback"

Common variantImplies a submission action. Familiar from email-style interfaces.

"Share feedback"

Softer toneLess transactional. Works well in community products and B2C apps.

"Report issue"

Bug-focusedUse when the primary purpose is bug reports. Sets a narrow expectation.

"Take our survey"

Survey CTAUse for embedded take survey buttons that launch a specific survey rather than an open feedback form.

Submit button (inside the form)

"Submit feedback"

StandardThe default. Clear, unambiguous. Use when you have no reason to deviate.

"Send"

MinimalShort and clean. Works inside compact feedback widgets with limited space.

"Submit"

GenericUniversally understood but lowest engagement. Use as a fallback only.

"Send my feedback"

PersonalizedThe possessive "my" slightly increases completion rates in A/B tests.

"Report this issue"

Bug formsMatch the submit feedback button label to the form purpose - bug reports feel different to general feedback.

"Share with the team"

Casual toneReduces the feeling of formality. Works in early-stage SaaS where the team connection is a selling point.

One rule: match the label to the expectation

If your customer feedback buttons say “Give feedback” but the form only asks about bugs, users get confused. If the trigger says “Take our survey” and a 12-question form appears, completion rates drop. Keep the trigger label, form heading, and submit button label consistent with what you are actually asking.

Feedback button vs triggered survey

They capture different signal - run both

A feedback button captures what users volunteer. A survey captures what you ask about. The bugs and friction points that users notice but never show up in NPS scores - those come from the button.

Feedback button

·User-initiated - they choose when to share
·Unstructured - open text, screenshots, ratings
·Skews toward strong opinions (bugs, praise)
·Captures signal you didn't know to ask about
·Always-on - no setup per page or feature

Triggered survey (NPS, CSAT, CES)

·Company-initiated - you choose when to ask
·Structured - comparable scores over time
·Captures the full distribution of opinions
·Measures specific metrics at specific moments
·Requires targeting decisions per survey

Related resources

Customer Feedback Surveys →In-Product Surveys →Website Surveys →Popup Surveys →Customer Feedback Guide →Feedback Forms →NPS Survey Tool →CSAT Guide →

Frequently asked questions

Common questions about feedback buttons and widgets.

Add a feedback button to your product today

One JavaScript snippet. Floating or embedded. Works alongside your NPS and CSAT surveys. Free to start.

Start Free

No credit card required · Free plan available