Views are 'saved presets' of a combination of filters that you can use in Shipright.

You can find these filters in the top right of the app. We have several that you can use:

  • Time – filter requests on any given time period
  • Status of requests (i.e. open, under consideration, in progress, completed)
  • Visibility of requests (i.e. hidden or public on your portal)
  • Themes – labels you can add to requests as an additional layer of organization
  • User Types – tags you can add to users to capture user meta data
  • Company – to filter requests on a selection of specific companies
  • User – to filter requests on a selection of specific users

To help you easily dive into specific feedback, you can store any combination of such filters as a 'View'. Your views can later on be accessed through the left side of the overview.

How to use Views

Views are handy shortcuts to a combination of filters you, or anyone else in the company, might want to access on a regular basis.

Here are the most common use cases you can use it for:

  • Easily jump to all requests for a certain area of your product / platform that is important to you currently
  • Have a view for the different types of customers, most often related to the 'tier' they're on (e.g. free users, premium users, enterprise etc.)
  • A view to quickly look at certain feedback types (e.g. 'Bugs')
  • A view to quickly dive into a 'journey stage' that might be a priority for you at this point
  • Create a separate view for the different teams in the company, so they can quickly look at requests that are in particular relevant to them

Let's go through a few of them, so you could apply it yourself in case any of the above seems useful to you.

Creating a view for a certain product / platform area

Let's take the example of a simple to-do app. Your app may consist of several high level areas in your product: an inbox, projects, tasks, notifications, settings, billing.


Our current priority is to improve the overall experience on 'tasks', so we'd like to have a View for that to easily keep up-to-date on how requests develop in that area of our product.

For this, it's important you have set up your 'themes' correctly. This is what it would look like in this example:

When these 'themes' get added to the requests (while being submitted, or afterward in the app), it will allow you to filter your requests by these themes and store that set of filters to be easily accessible later on. Here's what that looks like:

Creating a view for a journey stage

At Shipright, we're using the pirate funnel framework to link requests to a certain stage in that funnel. It's a high-level funnel that consists of Acquisition, Activation, Retention, Revenue, Referral. The contents of what such a funnel looks like for you, depends on your preference and type of business. Let's say we're using this for our to-do app as well.

To make use of looking at requests at a certain journey stage, it's important that you set up your themes that define the journey steps, and have your requests tagged with journey stage that applies to it. In this case, our theme setup, looks something like this for our to-do app:

When you have the requests properly tagged (you can do this at the point of submission, or afterwards in the app), you can easily look at requests for a certain journey stage. In this example, we'd like to store a View that shows us how requests that relate to 'Activation' develop, because our priority is to improve the activation for our to-do app.

Creating a view for a specific customer type

Let's say our to-do app has 3 tiers: Lite, Premium, and Enterprise. If we correctly document this meta data for our users (learn more about this in the Types article), we can use this to filter our requests, and create a View so that we can easily access all requests from our Premium plan users.

Did this answer your question?