How do I use Receptive?

In this guide:

• Logging in to Receptive
• Creating a feature
• Updating your priorities
• Requesting Receptive features

Logging in

To login to Receptive, go to Receptive.io and click the "Log in" button in the top right corner. Once you're logged in, bookmark your dashboard page for quick access (https://receptive.io/app/#/vendor/dashboard). 

Note: Remember not to log in through your app! That's for customers only, and you'll miss out on all of your admin rights.

Creating a feature

You probably know that Receptive gives your customers a dashboard to vote & prioritize their requests. But as a team member you also have needs from your product. You can create a new feature request by clicking the "Suggest" link in the left-hand navigation.

Add a title and a description. Make sure to be as thorough and clear as possible.

Make sure you aren't submitting a duplicate idea. Use the "Browse" link on the left-hand navigation and search for ideas that are similar to yours.

If you wish, you can tag your suggestion with the relevant tags. These allows easier and more detailed reporting for your Dev Team. Learn more about tagging here.

To submit an idea on behalf of another user, click on "Requested by you" and select the relevant person.

Updating your priorities

Once you've voted/created 2+ features you can update your priorities. This way your product team will know what's most important to you and your team.

Please note that you are limited in how much weight you can distribute between ideas so that you can't say that everything is of huge importance. 

Requesting Receptive features

Have ideas for how our software could help you and your team work faster or smarter? We'd love to hear them!

Just login to your account from 
the Receptive.io homepage.

From the dropdown menu in the top right corner, select "Request Receptive feature":

You're now in our customer view (we call it "Meta-Receptive") and you can suggest, search, vote & prioritize features you'd like to see us build.

Tip: Remember to include your use case so our product team can understand the problem you're having when considering your feature.