Always-on feedback

Feedback Button

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.

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

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.

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

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