Salesforce Form Connector pushes form submissions from WordPress forms into Salesforce as Leads, Contacts, or Cases, recording the sync result on the underlying form entry. Sync status moves through Pending, Synced, Failed, and Skipped depending on whether the Salesforce API call succeeded, failed, or was excluded by sync rules. The default form admin shows the entry as a row but loses every signal about which entries are stuck in pending sync, which failed silently, and which were skipped by conditional rules.

SleekView reads the form storage table directly, joins to the Salesforce sync meta written by the connector, and exposes the sync status as a primary grouping axis. The natural one is the sync result with Pending, Synced, Failed, and Skipped columns. You can also group by Salesforce object type (Lead, Contact, Case), by Salesforce record ID once synced, or by sync error reason on failed entries to drive diagnostic work.

Dragging a card writes the new value back through the form's standard update path, firing the standard hooks so Salesforce Form Connector can re-evaluate sync rules for the entry. A drag from Failed back to Pending can trigger a fresh sync attempt through the connector. Skipped entries are filtered out of active sync boards by default but can be exposed on a dedicated audit board so the team can verify sync rules are excluding only the entries that should be excluded.

Salesforce Form Connector is excellent at pushing form submissions into Salesforce, but the default form admin shows nothing about whether each entry actually made it into Salesforce. That works when sync rarely fails. It stops working the moment Salesforce starts throttling, dedup rules begin rejecting entries, or authentication expires on the connector.

A kanban board fixes the part the connector was never designed to fix: sync health visibility. Each column shows how many entries are in each sync state per Salesforce object type, so sales ops can spot when syncs are failing silently before pipeline integrity is at risk. Status changes happen with a drag instead of writing custom retry scripts, and dragging from Failed back to Pending triggers a retry through the standard connector path.

Because every column maps back to real Salesforce sync meta on the form entry, the board is not a parallel system that drifts from Salesforce. Everything you see is exactly what reconciliation feeds, sales dashboards, and the Salesforce side itself already see through the connector. The end result is a form admin that finally matches how revenue ops teams actually monitor Salesforce sync.