Over the first six months or so of using Receptive, you'll likely see a lot of changes in terms of the data you collect and the engagement you see from your customers.
Most Receptive users see similar patterns early on, and so we thought we'd share with you what to expect.
At first, you may feel like you're inundated with new requests, as your customers flock to your Receptive dashboard and give their opinions.
Want more feedback? Find out how to get more engagement here.
But don't panic!
Over time, as more of your customers use Receptive, the new request activity will start to dial down. This is because your dashboard will now be populated with a lot of different requests, and most bases will already have been covered.
Over time customers will login and simply vote on the already existing feature requests, which brings us neatly on to...
Voting & Prioritizing
At first, it will seem like your customers aren't prioritizing much at all. But that's just because you don't have that many requests populating your dashboard.
Not to worry!
As the months go by, and your dashboard becomes more populated, your customers will have far more requests to browse through, and so they'll begin prioritizing and voting more.
The following trend chart shows the average number of new requests (green), votes on existing requests (purple), prioritizations (yellow) and pageviews (including your release log and roadmap, blue).
You'll begin to see engagement increase a lot as you start building and releasing requests, especially if you use the techniques we recommend here.
Now, this might seem like it's going to put a lot of work on your plate, but that brings us perfectly on to...
More Engagement, Less Work
At first, you'll have a lot of new requests to review. So when we tell you that engagement will increase drastically over time, it's natural for you to bury your head in the sand.
You see, as time passes, and you receive fewer new requests but more overall engagement, all of that data doesn't translate to more work.
In fact, the opposite is true. Receptive aims to automate most of the trivial tasks, and so you'll end up collecting more and more data, without any of the manual effort.
So let's finish with a...
Essentially, as we've explained through our number crunching, the amount of effort and work you put in at the start mirrors the spike of feature requests you'll receive.
But as those feature requests start to level off, so too does your workload.
At the same time, you'll see customer engagement increase as they begin prioritizing and voting on more of the requests which now populate your dashboard.
This means that you end up collecting more and more data, with less and less work on your part. Sounds like a win-win!