Saved Queries and Filters

How to get there: Click All Posts in the sidebar → use the filter bar at the top → click Save to save your current filter as a query.

Learn how to save frequently-used filter combinations as reusable queries, enabling fast access to specific post segments without manually reapplying filters each time.

What are Saved Queries?

Saved queries are stored filter combinations that you can load with a single click. Instead of manually applying the same filters repeatedly (category, tags, status, date range, segments), you save the entire filter configuration and reuse it instantly.

Think of saved queries as bookmarks for specific views of your feedback data.

Why Use Saved Queries?

Time Savings:

  • Manual filtering: 2-3 minutes to apply 5 filters
  • Load saved query: 5 seconds
  • Savings: 95% faster

Consistency:

  • Same filters applied every time
  • No mistakes or missed filters
  • Team uses identical criteria

Common Use Cases:

  • Regular reviews: "Enterprise Feedback", "This Month's Submissions"
  • Segment analysis: "High-MRR Customers", "Trial Users"
  • Prioritization: "Under Review + High Votes", "Quick Wins"
  • Team workflows: "Assigned to Me", "Mobile Team Posts"

Creating Saved Queries

Step 1: Apply Filters

First, apply the filters you want to save:

Example: Enterprise Customer Requests

  • Category: Select multiple (Integrations, Security, Billing)
  • Tags: "enterprise"
  • User Segment: Plan Type = Enterprise
  • MRR: $5,000+
  • Status: Under Review, Planned
  • Date: Last 90 days

[Screenshot: Filter sidebar with multiple filters applied showing enterprise-focused criteria]

View Filtered Results:

  • Results update to show only matching posts
  • Example: 47 posts match enterprise criteria
  • Verify filters produce expected results

Step 2: Save the Query

Once filters are configured:

  • Click "Save Query" button (near filter controls)
  • Save query dialog appears

[Screenshot: Save query dialog with name input field and optional description]

Enter Query Name:

Choose a clear, descriptive name:

Good Names:

  • "Enterprise Customer Feedback"
  • "High-Value Mobile Requests"
  • "Q1 2026 Submissions"
  • "Quick Wins (High Impact, Low Effort)"

Bad Names:

  • "Query 1" (not descriptive)
  • "Test" (unclear purpose)
  • "Stuff" (meaningless)

Add Description (Optional):

Helpful for complex queries:

"Enterprise customer requests (>$5k MRR) in Integrations, Security, or Billing categories submitted in last 90 days, currently Under Review or Planned."

Save:

  • Click "Save" button
  • Query appears in Saved Queries list
  • Ready to use immediately

Step 3: Load Saved Query

Access Saved Queries:

  • Saved Queries sidebar (left panel)
  • Or dropdown menu: "Load Query"

[Screenshot: Saved queries sidebar showing list of saved queries with names and post counts]

Click Query Name:

  • All filters apply instantly
  • Results update immediately
  • Current page filtered to query criteria

Query Details Shown:

  • Query name
  • Post count matching criteria
  • Last used date
  • Edit/Delete icons

Managing Saved Queries

View All Saved Queries

Navigate to Saved Queries:

  • Settings → Saved Queries
  • Or click "Manage Queries" in filter sidebar

See all your saved queries:

  • Query name
  • Description
  • Filter criteria preview
  • Created date
  • Usage count
  • Actions (Edit, Delete, Share)

[Screenshot: Saved queries management page showing table of queries with details and action buttons]

Edit Saved Query

Modify Existing Query:

  1. Load the query (filters apply)
  2. Modify filters as needed
  3. Click "Update Query" or "Save As New"
  4. Choose:
    • Update Existing: Overwrites saved query
    • Save As New: Creates separate query

When to Update:

  • Query criteria changed (e.g., new category added)
  • Date range needs adjustment
  • Segment definition evolved

When to Save As New:

  • Want to keep original query
  • Creating variant of existing query
  • Experimenting with modifications

Delete Saved Query

Remove Unused Query:

  1. Go to Saved Queries management
  2. Find query to delete
  3. Click "Delete" icon
  4. Confirm deletion

Queries to Delete:

  • No longer relevant
  • Duplicate of another query
  • Created for one-time use

Share Saved Query

Collaborate with Team:

Share Query with Team Members:

  1. Go to query details
  2. Click "Share" button
  3. Choose team members to share with
  4. Or copy query URL to share

Shared Query Benefits:

  • Team uses same criteria
  • Consistent analysis
  • Collaborative workflows

Example:

Product Manager creates "Enterprise Pipeline" query, shares with sales team. Everyone sees same enterprise customer requests.

[Screenshot: Share dialog showing team member selection checkboxes and "Copy Link" button]

Common Saved Query Examples

For Product Managers

"Enterprise Customers"

  • Plan Type: Enterprise
  • MRR: >$5,000
  • Status: Under Review, Planned
  • Purpose: Weekly review of high-value customer needs

"Q3 Roadmap Candidates"

  • Status: Under Review
  • Votes: >20
  • Date: Last 6 months
  • RICE Score: >5.0
  • Purpose: Quarterly prioritization

"Quick Wins"

  • Tag: "quick-win"
  • Impact/Effort: High impact, Low effort quadrant
  • Status: Under Review
  • Purpose: Find easy wins between major projects

For Customer Success

"Trial User Blockers"

  • User Status: Trial
  • Tag: "blocker"
  • Status: New, Under Review
  • Purpose: Daily review to improve trial conversion

"Churn Risk Features"

  • Custom Segment: Churn Risk
  • Status: All except Released
  • Purpose: Identify features that might prevent churn

For Sales Team

"Enterprise Deal Requirements"

  • Custom Segment: Enterprise Deals Pipeline
  • Tag: "deal-blocker"
  • Status: Not Planned, Not Released
  • Purpose: Features needed to close deals

For Support Team

"Mobile App Issues"

  • Category: Mobile App
  • Tag: "bug" or "issue"
  • Platform: iOS, Android
  • Status: New, Under Review
  • Purpose: Daily mobile support monitoring

For Engineering

"Technical Debt"

  • Tag: "technical-debt", "refactoring"
  • Status: Under Review
  • Purpose: Quarterly tech debt prioritization

"API Requests"

  • Category: API & Integrations
  • Status: Planned, In Progress
  • Assigned To: API Team
  • Purpose: Track API team's work

Advanced Query Techniques

Combining Multiple Filters

Complex Query Example: "High-Value iOS Quick Wins"

Filters:

  • Category: Mobile App
  • Platform: iOS
  • MRR: >$2,000 (total voter MRR)
  • Impact/Effort: Quick Win quadrant
  • Status: Under Review
  • Votes: >10

Result: 8 posts matching all criteria - perfect for sprint planning.

Date-Based Queries

Recent Submissions:

  • Date: Last 7 days
  • Status: New
  • Purpose: Weekly moderation queue

Aging Requests:

  • Date: Older than 6 months
  • Status: Under Review
  • Purpose: Review stale feedback

Segment-Specific Queries

Plan Type Comparison:

Create separate queries for each plan:

  • "Free Tier Requests"
  • "Pro Plan Requests"
  • "Enterprise Requests"

Compare results to understand segment differences.

Query Performance Tips

Optimize Query Speed

Faster Queries:

  • Use specific filters (fewer posts to scan)
  • Limit date range (recent data)
  • Use category/status filters (indexed fields)

Slower Queries:

  • No filters (scans all posts)
  • Complex tag combinations
  • Custom field searches

Cache and Refresh

Query Results Cached:

  • First load: Computes results
  • Subsequent loads: Uses cached data
  • Cache refreshes every 5 minutes

Force Refresh:

  • Click "Refresh" icon
  • Reloads with current data
  • Useful after bulk operations

Saved Queries in Different Views

Load Query in List View

Default behavior:

  • Filters apply to list
  • See detailed post information
  • Useful for reading descriptions

Load Query in Kanban View

Filters apply to board:

  • Only matching posts appear
  • Columns show filtered subset
  • Useful for sprint planning with filtered data

Load Query in Prioritization View

Prioritize filtered subset:

  • Apply query first
  • Then run RICE/ICE scoring
  • Score only relevant posts

Example:

Load "Enterprise Requests" query → Run RICE prioritization → Focus on enterprise priorities only.

Exporting Saved Query Results

Export Filtered Data

After loading query:

  1. Results displayed
  2. Click "Export" button
  3. Choose format: CSV or Excel
  4. Download includes only filtered posts

Export Use Cases:

  • Share with stakeholders without ProductLift access
  • Further analysis in Excel/BI tools
  • Archive snapshot of query results
  • Present in executive reports

Best Practices

Name Queries Clearly

Be Descriptive:

  • Include key criteria in name
  • Indicate purpose or audience
  • Use consistent naming convention

Naming Convention Example:

  • "[Team] - [Purpose] - [Key Filter]"
  • "Product - Enterprise Feedback - Q3"
  • "Sales - Deal Blockers - Active Pipeline"

Document Complex Queries

Add Descriptions:

For queries with many filters, explain:

  • Purpose of query
  • Who uses it
  • When to use it
  • What results mean

Example Description:

"Enterprise customer requests (>$5k MRR) in core product categories (Integrations, Security, Billing) submitted in last 90 days. Used for monthly enterprise roadmap planning. Shared with product and sales teams."

Review and Update Regularly

Quarterly Query Audit:

  • Review all saved queries
  • Delete unused queries
  • Update outdated criteria
  • Rename confusing queries
  • Share valuable queries with team

Create Standard Team Queries

Establish Team Standards:

Define queries everyone uses:

  • "Weekly Review" (standard moderation queue)
  • "Sprint Planning" (standard prioritization view)
  • "Enterprise Pipeline" (standard sales view)

Benefits:

  • Team alignment
  • Consistent process
  • Faster onboarding

Troubleshooting

Issue: Query Returns No Results

Solution:

  • Filters too restrictive (relax some criteria)
  • Date range too narrow (expand dates)
  • No posts match all criteria (verify filters)
  • Click "Edit Query" to adjust

Issue: Query Results Seem Wrong

Solution:

  • Check all active filters (may have forgotten one)
  • Verify AND vs. OR logic for tags
  • Refresh query (data may be stale)
  • Test filters individually to isolate issue

Issue: Can't Find Saved Query

Solution:

  • Check Saved Queries sidebar (may be collapsed)
  • Go to Settings → Saved Queries (full list)
  • Search query by name
  • May have been deleted accidentally

Issue: Query Loading Slowly

Solution:

  • Too many posts matching (add filters)
  • Complex filter combination (simplify)
  • Database performance (contact support)

Filtering:

Workflows:

Operations: