Older SupportCandy stored tickets as a CPT, while v3 moved everything to custom tables. SleekView checks the schema your installation uses and reads from the right place automatically. You don't need to flip a switch or pick a mode — it works on both, with v3 getting the richer joins because the data is properly normalised.

Yes for the common field types — text, dropdown, number, checkbox. SleekView reads the wpsc_cf_* value tables and writes through the SupportCandy API so your conditional logic, validation, and audit trail stay intact. More complex field types (file uploads, repeaters) edit best from the ticket detail screen and surface as read-only columns.

SleekView respects the agent-group capabilities exactly as SupportCandy enforces them. Supervisors see their group's tickets, agents see their own, and admins see everything. You build a saved view once and the visibility rules apply per-user when each person loads it. No separate permission layer to maintain.

If you use the SLA add-on, the remaining-time field becomes a sortable column. Build a view that sorts by SLA-deadline-ascending with status=open, and you have a real-time at-risk queue. Combine with category or product-area filters to scope it to a specific team.

Yes. Workflows fire on SupportCandy events — ticket created, status changed, agent assigned — not on which UI made the change. Inline edits from SleekView go through the same data layer, so notifications, automations, and audit logs all run normally. We tested this against the common Workflows recipes, including auto-reassign and tag-based routing.

Yes. Any saved view exports to CSV directly from the table header, with the columns and filters you've set. There's no separate export add-on to buy. Useful for monthly reporting, sharing a snapshot with a non-WP stakeholder, or pulling a backlog into a spreadsheet for an offsite review.

Yes. Add a joined column counting prior tickets from the same email or user ID. Sorting by that column surfaces repeat customers quickly, which is useful for support leads triaging escalations or VIP queues. The aggregate query runs server-side so the table stays fast even with large ticket histories.

Internal notes are stored in the same thread table with a private flag. SleekView filters those 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 without exposing note content to agents who shouldn't see it.