Suggest allow users of your website (including your own team) to leave very quick feedback about any aspect of their experience. The feedback will be attached to a session replay showing all the relevant context, making it easy for a developer or product owner to understand what happened and how to reproduce a problem.
Getting started
To enable feedback by rage-clicking on your website, you need to initialize the installation snippet with quadClickForFeedback: true. If enabled, Pavior will detect rage-clicks (quadruple-clicks that don't have any effect) and bring up the feedback box. Users often rage-click when frustrated, and this enables you to collect feedback at exactly the point of frustration.
If you want to enable Suggest for just your internal team members to give feedback, use something like:
Pavior('init', {
...,
doTimeTravel: user.isInternalTeamMember,
quadClickForFeedback: user.isInternalTeamMember
})Note: Time travel must be enabled on the session if you want to use Suggest.
Customization
If you don't like the default rage-click behavior, you can customize it by manually triggering the feedback workflow using our client API:
Pavior('feedback', 'saved_moment')For example, you might use the following snippet to open the feedback box whenever Ctrl + Shift + F is pressed:
document.addEventListener('keydown', (event) => {
if (event.ctrlKey && event.shiftKey && event.key === 'F') {
Pavior('feedback', 'saved_moment');
event.preventDefault();
}
});Responding to feedback
When a user leaves a suggestion, it will create a saved moment, the same as when you save one from the session viewer. The feedback will appear in your support inbox. You can respond to the user, the same as any other conversation. They will receive a notification in their live chat widget (if enabled on your site), and an email (if the user is identified). If the user is anonymous and you don't have live chat enabled, there's no way for the user to see your response.
Just like saved moments, the link to a user feedback is permanent. You can paste the link in your issue tracker to give developers a high-fidelity history of exactly what happened.