Both. Triage state like Investigating and Resolved writes to the local event mirror table. The Suppressed lane calls the Mailgun API to add the recipient to the account suppression list so future sends skip that address everywhere, not just inside WordPress. Same drag, two consistent writes, one to the mirror and one to Mailgun.

Use delivery_status for the primary lanes since it carries the exact values Mailgun emits including accepted, delivered, failed, bounced, complained, and unsubscribed. For more granular triage, compose the group-by from delivery_status plus a custom triage_state column so the same board shows both the Mailgun-side state and the in-house workflow state.

Each lane paginates and only loads card data for the slice currently in view. Delivered comfortably holds millions of historical rows because the lane lazy-loads as you scroll. The Failed and Bounced lanes that actually need real-time accuracy stay snappy because they only carry the small slice of events from the recent window.

Yes. Set permissions so the support role can drop into Investigating and Resolved but not into Suppressed. The Suppressed lane becomes a non-drop target for that role and the card snaps back. Ops engineers and admins keep full access to all lanes, so suppression stays a privileged action.

The local mirror flag rolls back and the card returns to its previous lane with an inline error toast showing the API response. SleekView treats the API write as the source of truth so the kanban never drifts from the Mailgun account state. The failure is logged for audit and can be retried with another drag.

Yes. Add a domain filter to the kanban view so the board scopes to only sends from the chosen domain. Save the filtered URL for each domain and the team responsible for that domain gets a focused triage board. The same Mailgun account drives multiple boards without any data duplication.

It replaces it for the day-to-day triage work that ops teams actually do, like spotting failed receipts and suppressing bounced addresses. The Mailgun dashboard still has account-level analytics, domain reputation graphs, and webhook configuration that live outside the kanban scope. Most teams check the dashboard weekly and live in the kanban daily.

No. The kanban only queries the event mirror table when the board is open, and even then it only pulls the lanes currently in view. There is no background polling, no extra cron, and no admin-init queries. Sites running the Mailgun for WordPress plugin already write the mirror table, so SleekView simply reads from rows that exist.