SendGrid WP Pro sends mail through the SendGrid v3 /mail/send endpoint. The API key and sender config sit in wp_options under sendgrid_wp_pro_options. When local logging is on, per-send rows land in wp_sendgrid_wp_pro_log with recipient, subject, API status, SendGrid message ID, and source plugin. The plugin also caches suppression-list snapshots so bounce and unsubscribe state is queryable from WP without round-tripping to SendGrid.

The default admin separates credentials, the suppression viewer, and the send log across tabs. Saved views are not a feature; per-row retry only. Joining a send to a suppression entry, or filtering to a specific message ID for support, all require manual cross-tab navigation. The full SendGrid dashboard owns the analytics surface, which means every per-recipient support question becomes a context switch.

SleekView reads the local log and the cached suppression table directly, joining recipient to suppression status alongside the send row. Bulk retries route through the plugin's send handler so all wp_mail filters fire and the SendGrid sandbox/test modes are respected.

SendGrid's API returns a 202 for accepted mail and the actual delivery state arrives later through webhooks or sits in the suppression list. That two-stage flow makes the question "did my customer receive this?" harder than it should be, because the WP plugin's log shows acceptance and the SendGrid dashboard owns the rest. SendGrid WP Pro caches suppression snapshots locally, which means the data needed to answer that question is in WordPress, just split across two tables and two tabs.

SleekView reads both tables, joins suppression status to each send row, and exposes API code, message ID, source plugin, and template ID as filterable columns. Support gets a same-window answer. Developers can audit per-integration rejection patterns.

Deliverability ops can spot which mailboxes are entering suppression most often. The plugin still owns the API calls, the suppression sync, and the retention policy. SleekView simply joins the existing data into a workspace that does the cross-tab thinking once and saves it as a view.