In order to send SMS bulk uploads you have to add an to-email address even though they are sending to text messages. We should be able to bulk upload for SMS without the email address field.

Either add metadata to the review/survey request history file that includes the survey metadata associated with the request OR improve response rate reporting to show the response rate by certain meta data fields, such as the associate who the customer interacted with. We ask our team members to encourage their customers to fill out their survey, but have no way to measure who is successful. We want to establish a minimum response rate, but cannot get to the metric other than at the location level.

We would like to see the to-name in the user interface under request history. Currently it is on hover email/phone number, but it would be great to have it in its own column. We know we can export it, but it would be more convinient to have it in the UI.

As a user responsible for sending and monitoring review and survey requests, I would like to be able to see and act upon the failed requests. I would like the ability to have the platform create tickets in actions from failed requests. I would then like the ability to resolve what ever issue caused the failure and have the requests resent with the corrections. This would allow me to correct bad or missing email addresses and achieve a higher delivered rate for my requests.

We have Region ID and location ID for our locations. I would like the ability to sort by Region ID either in the report itself, or in the CSV I download. Currently I can group by Region ID, but that then loses the granular detail within the Region ID.

Thanks!

Please provide a review request via text and email through your app

Currently our DRIP functionality only sends a follow up if the user has not clicked the link. It would be useful to have a DRIP functionality that sends a reminder to the customer asking them to finish a survey for a link they previously clocked.

On our surveys we see multiple responses per request. The link stays open and we are seeing customers who share inboxes respond multiple times. We'd like to restrict them to one response per request.

Create a plan to schedule when the requests have to be sent automatically.

I want to be able to define what roles are able to view and send templates, while still allowing for the user to see the corresponding metrics. I want to essentially control what templates are able to be seen within the quick request tab, but still allow for the user to be able to view the template metrics within request history/metrics.

As a user of the Reputation.com platform, I would like to see a breakdown of how many reviews are organic and how many reviews are attributed to Reputation.com review requesting. Currently the request leaderboard by location shows the attributed reviews as "Total number of reviews collected for your location". Instead, I would like to see the number of reviews that are attributed to a review request, the number of reviews left organically, and the total number of reviews for the location.

Bulk upload is not clear when there are errors, and when successful does not provide confirmation of what was sent. I want more information after a bulk upload, such as:

• number of requests successfully sent


• any other errors and which line they occurred on

The ability to send an alert if an automated request has not been sent in 7-14 days.

Almost all of our request templates contain a question to one of our surveys. While we have the ability to add these within the WYSIWYG editor, we cannot style the questions within the HTML editor (style sheets). It would be great if we could get add that flexibility.

I would like to be able to search for a review request recipient from the Request History page. I would like to be able to search for an email, phone number, or name and have related review requests come up. Currently users need to download the request history in order to search for a specific recipient.

We would like to see the "to-name" in the UI under request history. Currently it is on hover over email/phone number, but we would like to see it within the user interface not just within reporting.

I would like more explanation/detailed reasons as to why review requests fail. Currently, we show a status of bounced or not delivered, but I would like to see a specific reason why the request bounced or was not delivered so that I can understand and address delivery issues.