Yes. SLA add-on due dates and remaining time are stored as wp_postmeta against the parent ticket. SleekView reads that meta and exposes both as sortable, filterable columns. Sort by remaining time ascending and the breached or near-breach tickets surface at the top of the view.

Yes for text, select, number, and checkbox field types. SleekView writes through the Custom Fields add-on's save handlers so validation and conditional logic continue to apply. Complex types like file uploads stay read-only in the table and edit best from the ticket detail screen.

Departments are registered as a taxonomy on the ticket post type. SleekView joins wp_term_relationships and surfaces department as a filterable column. Saved views can scope to a department, and the standard role capabilities for department access still apply.

Yes. Productivity tags, snippets, and macros run from the ticket detail screen. SleekView surfaces Productivity tag values as a column so a lead can see which macros were applied without opening tickets, but the macro editor itself stays in the Productivity UI.

Yes. SleekView queries the same wp_posts and wp_postmeta indexes that Awesome Support Pro relies on, with meta-key filters pushed into the SQL layer. Installs with tens of thousands of tickets render queues in well under a second when the recommended wp_postmeta indexes are in place.

Edits route through Awesome Support's ticket-update functions, which fire the wpas_ticket_after_update hook and write a history entry. If you log changes through the Audit add-on or a custom logger, those entries continue to appear because SleekView never writes directly to the database tables for editable fields.

Yes. Email Piping tickets arrive as standard ticket post type records and behave identically in the table. Agents can reassign, change status, or update Custom Fields on email-created tickets exactly as they would on tickets opened through the front-end ticket form.

Yes. Every saved view exports to CSV with the current columns, filters, and sort order. Useful for monthly SLA reporting, sharing a backlog with a stakeholder outside WordPress, or feeding a snapshot into a spreadsheet for an offsite review.