Only the WordPress-side cache the Salesflare connector already writes: form-submission rows with submitted_at, form_name, email, sync_status, salesflare_account_id, salesflare_contact_id and source_page. The Salesflare cloud CRM is not duplicated.

No. Accounts, contacts, pipelines and workflows stay in Salesflare, which is the right tool for them. SleekView surfaces the WordPress half of the integration: what was submitted, when, from where and whether it reached the cloud.

No, by design. Pipeline stages live in Salesflare's cloud and Salesflare's own views are the right surface for them. SleekView records the salesflare_contact_id once a sync succeeds, which lets you jump straight to the cloud record without mirroring its state.

No. Inline edits target columns on the local cache (notes, manual review flags, local custom fields) so the table stays a WordPress audit surface. Edits to contacts and accounts themselves happen inside Salesflare.

Yes. Save a view scoped to sync_status = failed and the table narrows to the failed-sync queue. Share the view with a triage role so ops opens straight into the queue without rebuilding the filter each morning.

Yes. Any filtered set exports to CSV with the visible columns. Compliance teams use the export to archive intake records and marketing reconciles it against Salesflare reports when the cloud and the bridge disagree on counts.

When the connector starts caching submissions from a newly added form, those rows appear in the unified table because the source is the cache, not a per-form screen. The form_name column keeps the cross-form view readable and filterable.

Anything the connector has retained in its local cache is visible immediately. If the cache has been rotated or trimmed, the table shows only what is still cached, with no fabricated history, and a recurring CSV export keeps a longer archive when needed.