✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Feedback for Awesome Support Pro

Awesome Support Pro stores tickets, custom fields, and reply threads. SleekView Feedback reads those rows, picks a vote column and a status column, and renders an upvote board so customers can promote the requests they actually care about without leaving your site.

♾️ Lifetime License available

SleekView Feedback board for Awesome Support Pro

Surface the Awesome Support Pro queue your users vote on

Awesome Support Pro keeps every ticket, reply, and custom field in wp_wpas_tickets and its companion meta tables. The data is rich, but a public roadmap or feature request board is not part of the core experience. Customers email duplicate ideas, agents triage the same bug twice, and the loudest user wins the priority instead of the most affected one.

SleekView Feedback connects directly to the same ticket rows. Pick a numeric meta field for votes, the status taxonomy for badges, and the ticket category for tags. The view renders one card per ticket sorted by votes, with an upvote button that writes back to the same meta key. Authors, status pills, and category pills come straight from the ticket record, so the board never drifts from the support queue.

You can filter to one ticket type (feature requests only, or open bugs only), expose a clean public URL, and embed the board on a roadmap page. Internal notes stay private because only the columns you map are rendered. The result is a transparent backlog that your existing Awesome Support Pro install already has the data for.

Workflow

From ticket queue to public roadmap

1

Connect the ticket source

Point SleekView at the Awesome Support Pro ticket post type. Filter to the request category or status you want to surface. Internal-only tickets stay hidden, and replies remain agent-side, so the public view only ever shows the fields you opt in to.
2

Pick your vote and status fields

Map a numeric custom field (or create one) to votes, the built-in ticket status to the status pill, and the request category taxonomy to the tag. SleekView reads those columns live so changes inside Awesome Support reflect on the board on the next page load.
3

Embed the Feedback view

Drop the SleekView block on a Roadmap page, set the layout to Feedback, and choose the card style. The cards render in vote order with title, author, status, and tag. Visitors browse without an account and submit upvotes with a single click.
4

Sync votes back to tickets

Each upvote increments the numeric meta field on the underlying ticket, so the same value is visible to agents in the Awesome Support Pro admin. Sort tickets by votes in the WP list table to prioritise the next sprint based on real customer demand.

Sample board

Sample Awesome Support Pro roadmap board

A live preview of how Awesome Support Pro feature requests and bug reports render in the Feedback view, sorted by upvotes from highest to lowest with status and category pills.
412 votes
Add canned reply variables for ticket custom fields
Diana M. Feature request Planned soon
287 votes
Bulk reassign tickets by department in admin list
@helpdesklead Feature request In progress
196 votes
Time tracking widget breaks on Safari 17
Marcus T. Bug report Open ticket
164 votes
Allow file attachments larger than 32MB on replies
Priya R. Feature request Open ticket
138 votes
Email replies sometimes attach to wrong ticket thread
@supportops Bug report In progress
72 votes
Native dark mode for the agent dashboard
Kenji S. UX polish Open ticket

Comparison

Default Awesome Support vs SleekView Feedback

Awesome Support default

  • Tickets live behind login, so there is no public roadmap surface visible to prospects
  • Customers cannot upvote or promote a request without opening a brand new duplicate ticket
  • Status and priority changes are visible to agents only, never reflected in a public list
  • Building a board view requires custom code on top of the wpas ticket post type
  • No card layout, no vote sort, and no badge styling out of the box for end users

SleekView Feedback

  • Reads Awesome Support Pro tickets straight from the wpas_ticket post type with no copy
  • Vote button increments a numeric meta field, visible to agents in the admin list table
  • Status badges map directly to the built-in Awesome Support status taxonomy values
  • Filter by department, product, or ticket category before rendering the public board
  • Upvotes are rate limited per IP and per user so no script can inflate a single ticket

Features

What SleekView Feedback gives you for Awesome Support Pro

Real upvotes on real tickets

Each card maps one-to-one to an Awesome Support Pro ticket. Votes write back to a numeric meta key on that ticket, so the priority signal shows up directly in the agent backend without any sync job or external service in between.

Filter the queue before publishing

Restrict the board to a single ticket type, status, or department. Bug reports get one board, feature requests get another, and internal triage tickets never reach the public view because only the rows you opt in to are queried.

Status and category styling

Pick a colour per status value and per category term, then SleekView renders consistent pills across every card. Open, In progress, Planned, Shipped, and Declined each get a distinct badge so the queue scans cleanly at a glance.

Audience

What Awesome Support Pro teams build with this view

Public feature request board

Expose only the Feature Request ticket category as a roadmap page. Customers vote on the ideas you have already captured instead of emailing duplicates, and product gets a ranked queue from the same data.

Known issues page

Surface open bug tickets on a status page. Visitors see the same issue is being tracked, upvote to signal impact, and the agent admin reads the same count from the meta column, so triage stays in one place.

Shipped log

Filter by Shipped status to render a changelog of resolved tickets in reverse vote order. It doubles as social proof and reduces follow up questions about whether a request was ever addressed.

The bigger picture

Why a Feedback view beats a separate roadmap tool

Most support teams running Awesome Support Pro end up bolting on a second tool for public feedback. The team subscribes to a roadmap SaaS, exports requests, copies them into the external tool, and then tries to keep two systems in sync as agents triage. The result is duplicate work and stale boards.

SleekView Feedback removes that gap. The ticket data inside Awesome Support Pro is already structured: votes, status, category, and author live in fields you can map. Rendering them as upvote cards is just a different view of the same rows, not a parallel database.

Customers still get the public, vote-driven, transparent experience they expect from a modern feedback board, and agents still work in the same WordPress admin they already use for replies, attachments, and time tracking. When a status flips from Open to Shipped inside Awesome Support, the badge on the public card updates on the next request. When a customer hits upvote on the board, the count is immediately readable in the ticket meta column.

One source of truth, one tool to maintain, and a roadmap that is always backed by the real queue.

Questions

Common questions about SleekView Feedback for Awesome Support Pro

The Feedback view works with both versions. As long as the ticket post type and the custom fields you want to map exist, SleekView reads them. Awesome Support Pro adds more meta fields and statuses, which gives you richer mapping options for status badges and category pills.

 

Yes. Votes are stored as a numeric meta value on the ticket itself. You can add a column to the ticket list table to show the count, sort by it, and use it inside Awesome Support reports. The board is just a public view of the same number.

 

Yes. The SleekView source filter only queries tickets that match the conditions you set, for example a specific category, a status that is not Closed, or a custom field flagged as public. Anything outside that filter never reaches the front end.

 

Only the columns you map are rendered. Replies, internal notes, attachments, and private custom fields stay in the Awesome Support Pro admin. The Feedback card shows title, vote count, author label, status pill, and category pill, nothing else.

 

By default they can vote without logging in, with rate limiting per IP. If you prefer authenticated voting, switch the source to require a logged in user and SleekView will gate the upvote button so only registered customers can submit.

 

Yes. The status badge reads the taxonomy term assigned to each ticket. Any custom status you defined inside Awesome Support is available in the badge mapping screen, where you assign a colour from the SleekView palette.

 

SleekView paginates results and queries only the columns you map, so a board of hundreds of tickets renders without pulling reply threads or attachments. Vote writes are debounced server side to protect the database during a traffic spike.

 

No. SleekView runs entirely on your WordPress install. The ticket rows, the vote increments, the status badges, and the rendered cards all live on your own database and server. No third party SaaS is involved at any step of the pipeline.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView