Yes. Custom Fields values are stored in postmeta and surface as filterable columns once you add them to a view. There is no separate integration to install: SleekView already reads postmeta, so any Custom Fields key registered through the add-on is available as a column the moment the add-on is active.

Yes. Select rows, change agent inline, and the standard ticket-update hooks fire so notifications go out as expected. The reassignment writes through Awesome Support's own functions, which means SLA timers, history entries, and email notifications all behave exactly as they would after a single-ticket reassignment from the ticket edit screen.

Replies are also ticket_reply posts. SleekView can build a separate replies view for moderation, or show last-reply summary inline on the tickets table so an agent sees the latest customer message without opening the ticket. Both views can coexist, and a support lead can use them side by side.

Yes. SleekView honors the role caps (view_ticket, edit_ticket, and the others Awesome Support registers) so agents only see and edit what their role allows. If a role is restricted to certain departments or products, that restriction continues to apply at the row level, even when the agent shares a queue view with a support lead who has wider access.

If you use the SLA add-on, due-dates are postmeta. Surface them as a column and filter for tickets past due. A saved view of breached tickets sorted by hours overdue gives a support lead an instant escalation list, and inline priority updates flow through the SLA add-on's own hooks so timers stay accurate.

Yes. Tickets created from email arrive as normal ticket post type records and behave the same in the table. Agents can reassign, change status, or update priority on email-created tickets exactly as they would on tickets opened through the front-end form, with the same hooks firing for outbound notifications.

Yes. Awesome Support records ticket history as a custom log, and SleekView can show a count of history entries or the most recent action as a column. A view of tickets where the last action was a customer reply, sorted by age, surfaces stale tickets that need agent attention without opening each one.

Agent assignment is stored as a postmeta value referencing the assigned user. SleekView resolves the user reference inline so the column shows the agent's display name, not a raw user ID. Inline edits use a user picker scoped to roles with the agent capability, which prevents accidentally assigning a ticket to a non-agent role through the table.