✨ 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 for SupportCandy Pro: tickets, custom fields, and add-ons as tables

SupportCandy Pro keeps tickets, threads, and custom fields in dedicated wpsc_-prefixed tables, with SLA, Workflow, and Reports add-ons writing extra value tables. SleekView reads them directly and pivots every dimension into a column.

♾️ Lifetime License available

SleekView table view for SupportCandy Pro

Pro add-ons surfaced from custom tables

SupportCandy Pro builds on the v3 custom-table schema: tickets live in wp_wpsc_ticket, threads in wp_wpsc_ticket_thread, and each Pro add-on (SLA, Workflows, Reports, Knowledge Base) creates its own value tables. The default UI shows core fields well, but SLA remaining time, workflow stages, and custom-field values from wp_wpsc_cf_* tables only become first-class columns after a configuration step that most teams skip.

SleekView reads the wpsc_ tables directly, joins thread activity into the ticket row, and surfaces SLA timers, workflow stages, and every custom-field value table as a column. Filter for breached SLAs by category, save a view per agent group of awaiting-reply tickets sorted by last-thread age, or pivot by workflow stage to see where tickets are stuck without opening any of them.

Inline edits route through the SupportCandy data layer so Workflows triggers, audit history, and the Reports add-on continue to receive change events exactly as they do from the standard UI. Agent-group capability checks apply per row, so a supervisor sees their team's queue while admins see the whole helpdesk in the same saved view definition.

Workflow

From wpsc_ Pro tables to a triage-ready table

1

Detect Pro add-ons

SleekView scans for active SupportCandy Pro add-ons and registers SLA, Workflow, custom-field, and Reports value tables as available column sources alongside the core ticket schema.
2

Compose columns

Pick from ticket fields, thread metadata, custom fields, SLA timers, and workflow stages. Add a last-thread-age joined column for SLA-risk triage views.
3

Save the queue

Save per-agent or per-group queues with status, category, workflow-stage, and last-activity filters baked in. Each user loads their queue with one click.
4

Edit inline

Change status, category, agent group, or custom-field values directly from the row. SleekView writes through the SupportCandy API so Workflows, audit logs, and Reports stay consistent.

Sample columns

A typical Pro triage view

One row per ticket with SLA, workflow stage, custom field values, and agent group inline.
Source: wp_wpsc_ticket + wp_wpsc_ticket_thread + wp_wpsc_cf_* + wp_wpsc_sla_* (Pro add-on tables)
Ticket # Subject Status SLA Workflow Agent group Last activity
#9412 Stripe webhook silent Open Breached Triage Billing 30m ago
#9411 Translation missing In progress 2h left Engineering Bug 2h ago
#9410 Refund processed Resolved Met Done Billing 1d ago
#9409 Cannot reproduce Closed n/a Closed Bug 6d ago

Comparison

Default SupportCandy Pro admin vs SleekView

Default SupportCandy Pro admin

  • Custom-field columns from wp_wpsc_cf_* require per-view manual setup
  • SLA remaining time sorts only inside the SLA add-on UI
  • Workflow stage filters live behind the Workflows add-on screen
  • Reports add-on doesn't double as a triage list
  • Bulk reassignment across agent groups is limited

SleekView

  • Read wpsc_ custom tables directly without postmeta hacks
  • Surface SLA remaining time from wp_wpsc_sla_* as a sortable column
  • Inline edit status, category, and agent group from any row
  • Save views per agent group with workflow-stage filters
  • Join thread activity so last-reply age sorts in the ticket table

Features

What SleekView gives you for SupportCandy Pro

Agent-group queues

Save a view per agent group, scoped to their open tickets sorted by SLA remaining. SupportCandy Pro capability checks continue to enforce who sees what at row level.

Custom fields as joined columns

SupportCandy stores each Pro custom-field type in its own wp_wpsc_cf_* value table. SleekView joins them so every field becomes a sortable, filterable, exportable column.

Workflow-aware edits

Inline status, category, and agent changes go through the SupportCandy data layer so Workflows triggers continue to fire, audit history records the change, and Reports stays accurate.

Audience

Who uses SleekView for SupportCandy Pro

Pro support agents

Personal queues with SLA-risk filters and inline updates. One screen replaces three tabs of plugin admin during a heavy shift.

Agent supervisors

Workload-per-agent, SLA-at-risk, and reassignment in one table. Group-scoped capability checks make this safe to share with leads at every level.

Helpdesk admins

Audit tickets missing custom-field values, clean up workflow-stuck records, and check Reports inputs without writing direct SQL against wpsc_ tables.

The bigger picture

Why Pro helpdesks need pivot triage, not lists

SupportCandy Pro picks the right architecture for a serious WordPress helpdesk: custom tables, normalized custom-field storage, dedicated workflow and SLA tables. The trade-off is operational. Each add-on creates its own table, and the default UI exposes those dimensions through its own screens rather than as columns in the triage list.

Agents end up tab-jumping between the ticket list, the workflow board, the SLA add-on view, and the custom-field manager just to triage one shift's worth of tickets. A real pivot view changes the unit of work from ticket to queue. A supervisor opens one screen and sees twelve open Billing tickets with SLA remaining, workflow stage, and severity as columns, sorted by last customer message age.

That single shift removes the daily Slack roll calls about ticket ownership, makes SLA risk visible the moment it appears, and gives leads a defensible answer when they reassign across agent groups. SleekView delivers that pivot without forking SupportCandy's data layer or asking it to change.

Questions

Common questions about SleekView for SupportCandy Pro

Yes. The SLA add-on stores rules and remaining time across wp_wpsc_sla_* tables. SleekView reads them and surfaces remaining time as a sortable column. Sort ascending with status=open to get a breached-first queue you can hand a supervisor every morning.

 

Yes for the common types text, dropdown, number, checkbox. SleekView reads wp_wpsc_cf_* value tables and writes through the SupportCandy API so conditional logic and validation continue to apply. Complex types (file uploads, repeaters) edit from the ticket detail screen and surface as read-only columns.

 

Agent groups are enforced by SupportCandy's capability layer. SleekView honors those caps row-by-row, so supervisors see their group's queue, agents see their own, and admins see everything. Save the view once and the visibility rules apply per-user when each person loads it.

 

Yes. Workflows fire on SupportCandy events (ticket created, status changed, agent assigned, custom-field updated) regardless of which UI made the change. SleekView's inline edits route through the same data layer, so notifications, automations, and audit logs continue to behave normally.

 

The Reports add-on aggregates from the same wpsc_ tables. SleekView doesn't replace Reports but lets you build the underlying triage queues that feed cleaner reports: tickets with missing severity, tickets stuck in a workflow stage too long, or tickets escalated past their SLA category.

 

Most Pro installs run v3 exclusively. If you've kept v2 data in the legacy CPT, SleekView reads both schemas and exposes them as separate sources so you can migrate triage workflows to v3 at your own pace without losing visibility into the older data.

 

Internal notes are stored in wp_wpsc_ticket_thread with a private flag. SleekView filters them out of customer-facing columns by default but lets you opt into a private-notes count column for admin views. That makes it easy to spot tickets where internal collaboration is happening.

 

Yes. Any saved view exports with current columns, filters, and sort order. There's no separate export add-on to buy. Useful for monthly SLA reporting, sharing a snapshot outside WordPress, or pulling a backlog into a spreadsheet for an offsite review.

 

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