This article explains how to use Shipright Catch and make your workflow effective. To read more about installation, read this article.

What can you use Shipright Catch for?

Whenever you encounter product feedback on a website or tool inside your browser, you can use Shipright Catch to store this feedback. That can be support and live chat tools like Intercom/Zendesk/Drift/HelpScout/Front, your favorite CRM system such as Salesforce or Hubspot, social media like Twitter / Facebook, online articles or forum comments, and any other online source.

This feedback can then be categorized and will help the product team to guide product decisions.

Submitting product feedback

Once you encounter product feedback, you just select it and press the Shipright icon next to your address bar.

You can indicate who provided the feedback as well. This will help to determine how important feedback is (what users did it come from?) later on and who to follow up with when your team wants to act upon it.

We'll automatically store the URL you found the feedback on as well, so anyone can retrieve the source from Shipright's app.

Categorizing product feedback

There are two ways to eventually categorize product feedback, so the product team will be aware of how often similar needs, requests, or improvements are expressed and by whom.

1. You just submit the product feedback through the extension. This will make sure the feedback gets stored in the Inbox in Shipright. From there, you or anyone else on the team can later on categorize feedback under Insights (the way to group similar feedback and gauge its importance)

2. You add product feedback immediately to an existing Insight (the way to group similar feedback and gauge its importance) from the Catch extension. This is optional in the extension and will avoid that you or anyone else will need to categorize the feedback later on.

Auto-complete will avoid duplication as much as possible, just as more advanced suggestions that we will support later on.

Quick Tips

We recommend you to think about and communicate your preferred workflow. The first option might be more appropriate if you're a larger team and want one or two people to control the grouping of feedback. 

Did this answer your question?