Feature Requests

Pipedrive has a 'powered by Pipedrive' link that makes it easy for people interested in using that service/product to quickly jump in and take a look. This idea could be used on existing Engagements to make it easier for users to look into Social Asking when they are already visiting an embed or page with SA content. Premium plan holders could choose to eliminate this link if they want to stay focused on their brand.

Alternative formats for the image that accompanies the 'swipe' style gauges. The square format doesn't work well for some images, and other formats won't work well for square style formats. Recommended options: Portrait style (taller and narrower than square) Banner style (short and wide) Circle View (square, but with circular view)

Implementing the ability to choose from a selection of icons for their gauges allows owners to guide the angle of feedback they're looking for from their audience, or simply customize their page to best fit their theme or preferences. Examples include: A thumbs-up/thumbs-down set for users who prefer not to use the existing heart/heart-outline set. A bright lightbulb/dark lightbulb set for owners seeking feedback on how 'smart' a proposed change or product is. A '#1'/'#2' set to allow customers to choose between 2 critical options and denote how strongly they feel about it all on one gauge A handful of color variations for the above, so owners can avoid using colors that clash with their color scheme.

Favoriting/Hiding Topics Allow engagement owners to favorite and hide unlimited topics and filters to customize the public view of the filters shown Favoriting would pin topics to the top of the list. Hiding would completely remove topics from public view. The goals are to: Provide engagement owners more control over the filters provided Allow hiding sensitive topics from public view Showcase key topics

On the dashboard, in addition to seeing your saysos, be able to access a list of all shared with you.

From any engagement you own, assign a botId to your sayso to link the data from that sayso to one of our bots. On report generation, populate the bot. Provide a link to this bot from the sayso as a small chat icon in the bottom corner. Bots should have access to all data from the engagement and be ready to assist users with a variety of tasks.

When on a page, if new comments are found, create a special notification if any are replies.

For users that didn't sign up but finished to 100%, pop up something to encourage them to create an account to enter the giveaway before they leave.

Report generation outputs a single format of size and complexity, regardless of the pool of customers or data. This can work scaling upward, but when using a smaller pool of comments/consumer data, the report can look very sparse. The existing report type can be called 'intermediate'. It handles everything fairly well with a reasonable sized pool of data. A 'simple' report format could help to provide focused (and satisfying) data when using smaller amounts of data or less comments than normal engagements. A 'comprehensive' format could potentially help with engagements on a scale we haven't seen before - additional data or ways to view it may help engagement owners sort through the massive volume of data that comes with thousands or tens of thousands of comments or ratings. The report generation can check for the number of comments, in a similar fashion to how it already does. Instead of a simple 'ok' at 50 comments or 'fail' at less, the check can determine which of the three proposed types of reports will be generated based on available data. 15-75 for 'simple' reports, 76-150 for 'intermediate' reports, and 151+ for 'comprehensive' reports (these numbers are only suggestions based on currently available data and may change). Additionally, a check may be used to determine the number of anonymous comments, which could support a 'value' system. The owner of the engagement could set the value of anonymous comments to 0 (don't count anonymous data), 1 (anonymous is just as welcome as verified user data), or a value in between like 0.25 (anonymous comments only have 1/4 the normal impact on the report that verified users do).