AI Themes are now live! Available on Standard and Advanced plans only.
Use your company's own mission statements to craft AI powered analysis based off of all existing Response data. Themes no longer need to be manually maintained.
Reply Template Control
We have made it easier to manage reply templates in order to help our customers who are multi-location, multi-team, and even multi-brand.
Users with permissions to reply to Contacts can now create Reply Templates and select the Visibility level of the template.
By default all customers have the Private and Everyone options.
Customers with locations can also select a specific location(s).
Go to Settings > Account > Settings to create a whitelist of allowed hashtags. This will control the visibility of hashtags when adding a tag and when filtering.
should now be able to map the main comment to a field in Zendesk.
Filtering now shows up to 100 filter values when adding a filter (up from 5). In addition, the list is scrollable and the cancel/apply buttons move with the scroll.
Workflow tags - added keyboard shortcuts and UX improvements when adding workflow tags. Also all tags will remain visible when filtering on specific tags.
Frontline Engagement report can now be filtered on custom date ranges
App 3.0: users can now add hashtags using the new message composer
App 3.0: Locked the Overview page to always show the last 30 days on all components. The Teams page will correctly respect the user’s chosen time filter.
App 3.0: We will now always show the topic for a response on the Feedback page. Previously we would show “No Topic Selected” if the user’s selected scorecard did not match the scorecard of the response.
Web: Custom NPS Labels now correctly update between editing and previewing the survey.
Web: Fixed a display issue on the Case Management report where the tooltip on far left/right bars was not visible.
General: fixed a bug where Smart Notifications were not respecting user filters and sending notifications for feedback that wasn’t related to the user
Mobile: Sending an internal note was creating duplicate notifications for users, specifically on the new app.