A True Story
On July 8, 2026, your team flagged the Salesforce decision as open. The feed was built read-only first as a direct result: proof without commitment.
Curated Sync Guide · Your Control Panel
Curated Sync Guide · Your Control Panel
The connection and its ledger are live. Pushing real records waits, deliberately, for your team's decision.
This guide explains the Salesforce screen in the Curated Sync control panel. Written for admins. Four minutes to read.
CURRENT AS OF JULY 16, 2026Connection status, a full event ledger, and an on-demand test button.
The screen shows whether the Salesforce link is healthy, and below it, a ledger of every Salesforce-related event the system has recorded. An explicit Test connection button verifies the link on demand. Viewing the screen never pokes Salesforce on its own.
Full visibility into the Salesforce link, with zero accidental traffic to Salesforce.
The quote feed moves website leads into Salesforce. Its switch is deliberately gradual.
The feed does nothing. This is today's position.Current
The feed reads pending quotes and previews every decision: who would be created, who matches an existing record, deduped by email. It writes nothing.
Quotes flow into Salesforce automatically, deduped by email, every write stamped with its mapping version. Requires a confirmation, and the server refuses live pushes unless the switch is truly Live.
Off today. Dry run proves it safely. Live is one deliberate, confirmed step, never a drift.
Honesty about the current state, and the reason behind it.
Your team is deciding Salesforce's future; the contract runs to the end of 2026. So pushing real records is built and switched off until you say go. The housing, the matching, and the ledger are finished and tested, which means nothing is wasted either way the decision lands.
On July 8, 2026, your team flagged the Salesforce decision as open. The feed was built read-only first as a direct result: proof without commitment.
The system respects a pending business decision. It proves itself in dry run and waits.
This is the section that changes when the decision lands.
At go-live, the feed switch moves to Live. Website quotes then flow into Salesforce automatically: matched by email first, created only when no match exists, every write stamped with the mapping version in force. The ledger records each one.
Go-live is a switch and a confirmation, not a construction project. The building is already done.
Matching is by email before any create. A quote from an existing contact updates the match instead of duplicating it.
Then the feed simply stays off. The quotes themselves live in the Curated Sync queue either way; Salesforce is an additional destination, not the system of record.
No. Live requires an explicit switch change plus a confirmation, and the server refuses live pushes while the switch is anywhere else.
Connected, ledgered, rehearsable, and patient. The Salesforce feed is ready the day your team is.