Saved Searches

Updated 1 week ago by Sofia Quintero

Bookmarking your search results with saved searches

When you are researching a specific topic and find useful search results you may want to save them and read them later. Saved searches help you do just that. You can use save searches to track a group of tags, keywords or any properties value associated with your customer feedback.


To create your first saved search take the following steps:

  1. Build your search query. Remember you can build very specific queries using a variety of filters.

      
  2. Once you are happy with the search results. Click on the saved searches icon next below the search bar. 

      
  3. Name your saved search and that’s it! Now you have a quick access to your report in the dashboard and also in your search area.

      

With NomNom you can search across multiple sources of feedback using a variety of powerful filters. User properties filters are a very useful way to segment feedback easily. It helps you answer questions like:

  • Which enterprise customers reported bugs in the last 7 days?
  • What are the new features requested by freemium customers in the last 30 days.?
  • Do we have feedback from NPS Detractors who used feature X in the last 2 weeks.?
  • What is the feedback from customers who churned in the last 24 hours.?

Saved searches give you the flexibility to track feedback that matters to you easily. 

Examples of common saved searches are Bug reports in the last 7 days, feature requests from a specific segment of customers, UX issues reported in the last 2 weeks.

Tracking processed and unprocessed feedback

Tracking processed state via feedback attributes

You can quickly find documents which haven't been classified in any way by using "has" query term. For example, you can decide that documents which are not part of any project and have no highlights are treated as not processed. You can use the following query in a saved search to quickly check out the feedback which hasn't been classified:

Tracking processed state via custom property

If you want to track processed/unprocessed feedback manually you can do that by combining saved searches and document properties. You can add a property called "status" to each piece of feedback you work on (either individually, or via batch editing):

Because properties can be assigned to highlights or documents you can be very granular in terms of how and what is marked as processed.

After assigning the "status" property you can create two saved searches with the following queries:

Unprocessed feedback

Processed feedback

From now, whenever you can quickly see which feedback has been dealt with or not, by using both saved searches.


How Did We Do?