Apxor vs. Receptive.io (discontinued)

If you want to analyze the user funnel, eg. how many users signed up-> then how many clicks "Button 1" etc. then Apxor is a good tool. But as I mentioned earlier, until they fix the issues, we can not rely on it for accuracy.

Incentivized

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.

Incentivized

• It is possible to creates users funnel for specific time range and for specific event.
• You can customise your dashboard and keep saved multiple dashboards.
• Support is also good, you get telephonic support.

Incentivized

• Captures feature requests from customers
• Organize feature requests
• Communicate progress updates to customers

Incentivized

• There are lots of bugs in data capturing.
• Since data is not captured properly hence we can not rely on metrics provided by Apxor. I tracked it for a test run, there is a mismatch of more than 20%.
• SDK not available for Cordova.

Incentivized

• 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

Incentivized

I have not had a lot of contact with support, but when I do it's quick and accurate info.

Incentivized

Firebase is good for accuracy, also it has more features.

Incentivized

We had UserVoice prior to Receptive but it was just too clunky and extensive for our needs. It was less about automation and still very manual work to process feedback. It also didn't provide collaboration levels that we needed for our internal teams to work together. ProdPad was a very clean tool but also didn't enable us to automate the process like Receptive does.

Incentivized

• Overall it's a positive impact, because you can always improvise if you know where your customers are dropping.
• Also, it gives clear idea which part of your app users are using.

Incentivized

• We were managing these enhancements in our support ticketing system, using spreadsheets, and it was TERRIBLE. Being able to tell a user "Great idea! Submit it to Feedback!" has saved my support team hundreds of hours.
• We have reduced incoming support requests when the request is really an enhancement - the ability to have a "Suggest Features" widget in our software sends users straight to Feedback.
• Because we can make some fields required, we can cut down on the need to reach back out to our users for clarification.

Incentivized