TrustRadius Insights for Receptive.io (discontinued) are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Easy Integration and Navigation: Users appreciate that the product seamlessly integrates with Pendo, allowing for effortless embedding in customer environments and smooth navigation by employees. This integration eliminates the need for customers to search for ways to submit feedback and ensures that employees can access the tool without any hassle.
Effective User Feedback Tracking: Reviewers have praised the Pendo products, including Receptive, for their ability to effectively track user feedback. The search and predictive matching features are particularly commendable as they make it easy to find and analyze feedback.
Actionable Customer Feedback Collection: Users have highlighted the product's capability to collect and aggregate customer feedback in a way that is actionable. This functionality enables teams and customers to collaborate on improving existing features and adding new ones. It also helps keep the company organized and ensures proper management of thoughts and ideas surrounding development.
We use Pendo Feedback to help capture requests from customers for new features. This creates a central location where all customer feedback can be maintained and analyzed. Customers can enter in requests themselves or our tech support team can enter them in on their behalf. When we implement features that have been requested, Pendo Feedback automatically communicates the progress to the interested customers, helping to close the loop with them.
Pros
Captures feature requests from customers
Organize feature requests
Communicate progress updates to customers
Cons
Improvement could be made on easily grouping and reporting on feedback by customer parent account, not just by actual customer
Feature requests states are predefined. It would be nice if those were customizable so they could match our actual business states
The interface to update and manage the details of feedback requests could be improved and streamlined
Likelihood to Recommend
Pendo Feedback is a great addition to your product if you are already using Pendo Guidance, as it integrates nicely with the Resource Center and allows your customers to easily request feedback through there. However, if you are not using Pendo Guidance there are other feedback capturing tools that are more robust and could be a better option as a standalone product.
We use Pendo Feedback to collect enhancement requests directly from our users. My team reviews these on a regular basis and adds high-level estimates for effort. As a leadership team, we meet monthly to review all feedback requests and then determine what is going to be included in an upcoming development cycle. Not everything makes it in, of course, but this is a much better way to prioritize and expose requests that are coming through.
Pros
Easy collection of enhancement requests
Linking to Jira tickets for development priorities
Provides visibility for our customers into their priorities
Cons
Filtering in general is not easy
I would like to be able to create a leadership priority dashboard
I would like to know easily when something has been linked to Jira
Likelihood to Recommend
If you are struggling with collecting and centralizing your enhancement requests, Pendo Feedback is a really great tool. It is front and center for your customers which allows them to feel heard and close feedback loops. It also allows our customer success team to refer back to what submissions have come from a particular account. With the SalesForce and ZenDesk integrations, we are able to have requests submitted within systems that our team uses on a daily basis and doesn't require them to log in to a separate system to capture these requests.
We use Pendo Feedback as a bridge for our customers/prospects to suggest features that our software may not have or may do differently. This software is used across many departments and it helps us solve the big question of what, why, and when for building features. The tug of war of prioritizing is reduced significantly from this solution.
Pros
Organizing data from users.
Customize questions and users.
Manage priorities for our customers easily (intuitive).
Cons
Do not charge per user (we almost cancelled over that).
Get rid of or make the assumption of time and money saved more realistic.
Likelihood to Recommend
Very good for situations where you have a lot of customers and not a great way of ranking/reaching those customers with things they want and why.
Less appropriate for a fulfillment tool to be used as an ongoing communication (customers complain about getting notifications from mass comments on requests).
We use Pendo Feedback to gather enhancement ideas from our end users. Our support team directs any such ideas to Feedback, and we have a widget in our software that directs users there as well. Our product team - the product owners specifically - also use Feedback to help prioritize their work.
Pros
Allows end users to prioritize their requests - and shows them that prioritizing one de-prioritizes the others.
Provides decent reporting so I can see what users want filtered a variety of ways.
Has a great "director dashboard" I can use to show the CEO how much time it's saving us.
Cons
I wish I could customize exports; e.g. if I just want to export all items and the number of votes.
Managing my "team" users vs. end users is a little clunky.
Likelihood to Recommend
This is a great tool for getting your end-users' enhancement ideas under control. It's self serve and the users figure it out very quickly. We are not integrating it with our other tools, so your product owners have to be proactive in connecting ideas captured in Feedback to work items (we use Jira, and just insert a link to the Feedback item into the Jira ticket.) The ability to mark an enhancement as "released" and instantly email all the users who were voting for it is great. I also love the ability to customize the emails that go to "subscribed" users when an enhancement idea's status changes.
Our Customer Success and Product Management teams recently implemented Receptive with a couple of our SaaS products. Our two teams have been working in collaboration with Product Development to fully incorporate the solution, and it's gone very smoothly so far. Receptive has very much been effective in providing us the visibility we need to build a better product for our customers by telling us where their priorities lie. Not only that, but it's also assisted us in improving our customer communication and engagement, which in turn have improved our customer relationships.
Pros
Receptive organizes the masses of data on product feedback that we have into digestible, actionable items. We're able to manage a workflow in an orderly fashion and ensure that all of our information on what customers want is in one place. Receptive's Dashboard is a great place to land on without getting too overwhelmed at all the incoming requests from our customers - it shows us what items have been waiting the longest, the most valuable requests, the most popular requests, and more. The Dashboard alone has helped us focus on product feedback more strategically without getting sidetracked by the influx of data.
Receptive allows for thorough collaboration amongst our internal teams. Before we implemented it, it was sometimes a challenge to stay on the same page. Now we all have one central place to look; the activity timeline, team member tagging, and reports/metrics functionalities are all quick views into what our internal teams are doing, and we're able to easily update each other on statuses without adding to each others' email stockpiles.
Receptive's own customer success for their customers (us!) is top-notch. Our CSM Aly is a true advocate for our cause and needs within the solution. She's faithfully met with us every few weeks to check in on how we're doing, and gone extra steps to ensure that we're taken care of. They've made it very easy to be a customer of Receptive, and they've listened to our voice in our feedback for their solution, and we can clearly tell!
Cons
Receptive's user interface is generally very navigable and simple (and also looks nice)! However, we've come across a few navigation quirks that we believe could vastly be improved, particularly in their Browse column, where you can view all feature requests. We wish Receptive used webpage real estate a bit more efficiently - a lot of blank space and scrolling, as well as 'next page' clicking is necessary to browse requests. It would help if there were some sort of a preview pane for the requests, and if the filters were all at the top.
A particular functionality that we've been asking for a long time from Receptive isn't there yet: customizable feature statuses (such as Under Review, Planned, Building, Released, Declined, etc.). It looks like it has been highly requested in the past, and we're pretty sure many customers would benefit from it and love Receptive even more. We're really hoping Receptive will release it soon.
Likelihood to Recommend
Receptive is very effective for multiple internal teams/department of a single product who need to scale their product feedback management effectively. We've been leveraging it for one of our products and it was so successful, that we implemented it with a second product. The main issue we ran into situationally with that was managing 2+ modules (products) in Receptive; it was a bit more difficult to present Receptive to two different customer bases/users (we couldn't change the appearance) and slightly confusing to do within the app (lots of filtering needed). I have heard that support of multiple modules is something that Receptive will likely be working on in the near future, so that's good news.