GetFeedback review

GetFeedback is website feedback software for finding out why visitors hesitate, leave, or abandon carts. Its job is to collect feedback in context, then connect responses with visitor behavior and journeys so teams can look for friction—not to replace a general-purpose analytics platform.

The product description lists two ways to invite responses: a passive form visitors can use at any time, and behavioral campaigns that show forms based on customer activity. An in-page widget keeps the feedback prompt within the website experience. Teams can target questions to particular moments, pages, or actions, then use the analysis dashboard to spot response trends. Journey insights are intended to connect what visitors say with where they are in their experience.

That makes the product most relevant when a team has a specific question about drop-off or a page-level obstacle. The published feature list does not publish details on integrations, survey response formats, or how journey data is collected, so those are worth checking before switching.

GetFeedback’s clearest strength is that it is built around feedback in context. A passive form gives visitors a standing way to comment, while behavioral campaigns can prompt them based on what they do. The in-page widget and targeting by moment, page, or action give teams options beyond sending a survey after the visit and hoping respondents remember what happened.

The combination of feedback and journey insights is useful in principle: teams can compare what visitors report with the point in their journey where friction may occur. The analysis dashboard is described as a way to spot trends and actionable insights, which gives teams a place to review responses rather than treating each comment as an isolated complaint. These are focused tools for investigating specific pages or actions, not proof that a particular change will improve conversion.

The plans also publish response allowances, which makes one part of the cost easier to assess before switching. Starter includes 1,000 responses per month and Plus includes 2,000, according to the published pricing details. Teams can compare those caps with their expected feedback volume instead of choosing on feature claims alone.

The response caps are the main published constraint. Starter allows 1,000 responses per month; Plus allows 2,000. The published pricing page details list Starter at $119 month to month or $1,190 annually, equivalent to $99 per month. Plus is $299 month to month or $2,990 annually, equivalent to $249 per month. There is no free plan, only a 7-day free trial. Seat limits are not published, so teams should confirm them before budgeting.

There is also a Salesforce caveat, though it concerns a specific survey workflow rather than the website feedback features described above. In one r/salesforce thread, a user said moving from legacy chat to Enhanced Chat removed the direct GetFeedback connection: customers had to click a link, and responses no longer went automatically to the chat case. A commenter suggested checking event timing, but the thread does not establish a confirmed fix or show that all GetFeedback setups have this problem. Teams relying on Salesforce chat should verify that workflow before switching.

GetFeedback has no free plan. The pricing page lists Starter at $119 per month, or $99 per month when billed annually at $1,190 per year. Starter includes 1,000 responses per month and a 7-day free trial. Plus costs $299 monthly or $249 per month with annual billing at $2,990 per year, and raises the cap to 2,000 responses per month.

That is a $180 monthly-billing jump from Starter to Plus, or $150 per month on the annual equivalents, for twice the response allowance. Annual billing saves $20 per month on Starter and $50 on Plus versus paying month to month, but commits you to a year. Seat limits are not published, so confirm how many team members are included before signing. The published pricing lists no add-ons. If your traffic regularly pushes past the response caps, ask about overages or a custom plan; neither is specified in the pricing details we have.

The available material does not specify migration services, supported import formats, data export options, or how long historical feedback remains accessible after cancellation. Before moving, ask GetFeedback to confirm whether responses, campaign settings, and journey data can be exported, in what format, and whether exports are available if you leave. Treat those as open questions, not included capabilities.

The review material flags reported Salesforce friction, but does not include the underlying Reddit posts or enough detail to verify what broke. Salesforce teams should confirm the exact integration behavior they need before switching, especially whether feedback and visitor context remain available in their existing workflows. For a small deployment, the main visible constraint is the monthly response cap: Starter allows 1,000 and Plus 2,000. Teams expecting higher volume should clarify pricing and upgrade options first. If leaving GetFeedback, secure an export and document any active campaigns before ending the subscription; the published sources do not say what happens to that data afterward.