docs(audiences): add Export sync toggle prerequisite for Salesforce write-back

[george-dilthey]

What changed

Added a prerequisite paragraph and numbered steps in the "Writing back to your CRM" section of docs/audiences.md, making clear that the Export sync toggle must be enabled before any field mapping data (including fields set to "Always write") will push to Salesforce. Also added a new FAQ entry: "My field mappings are set to 'Always write' but data isn't syncing to Salesforce — what do I need to do?" with the same steps and a note about the first-export timing.

Why

Intercom conversation #215475130065193 — Gabriel Griffith (Saviynt, Enterprise plan) had mapped Salesforce Account fields with "Always write" rules but data wasn't syncing. The human agent (Peter Johnston) had to explain that Export sync is a separate master switch, independent of field-level rules. The existing doc's setup section (step 4) explicitly tells users to "Leave Export Sync off for now" but never returns to say when or how to enable it. The "Writing back to your CRM" section describes export behavior (24-hour cadence, first export timing, etc.) but does not tell users that they must first enable the toggle, or where to find it.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/apps/w28k1kwz/conversations/215475130065193
• Slack (Peter Johnston consulting Dust bot on the same case): https://clay-hq.slack.com/archives/C0B937M5JG6/p1784304300715249
• Verifier: BETA verdict — code confirmed in /workspace/clay-base/services/audiences/src/materialization/services/export-handler.ts:3470 (isExportSyncEnabled guard skips all export processing if false, regardless of field-level write rules) and AudienceObjectSalesforceMappingSection.tsx:152-156 (separate SwitchSection bound to isExportSyncEnabled, independent of per-field MappingRule dropdowns). 24-hour schedule confirmed at audience-export-queue.ts:13. Feature is gated to Growth+ plans — plan availability is already documented at the top of audiences.md.

Uncertainties

None. All behavioral claims verified against code (BETA verdict — correct behavior, Growth+ plan gate already documented in the file).

Related observations

• The setup section's step 4 ("Leave Export Sync off for now") has no forward reference to the "Writing back to your CRM" section. A future edit could add a parenthetical — "see Writing back to your CRM when you're ready to enable it" — but this is out of scope for this trigger.
• Existing open PRs on docs/audiences.md that were reviewed and confirmed not to cover this change: docs(audiences): document signal detection-layer model and Data Hub vs. table scope #1605 (signals companion segments), docs(audiences): document archived record behavior on source re-sync #1587 (archiving and re-syncs), docs(audiences): add read-only Salesforce field types and cross-object enrichment FAQ #1585 (read-only Salesforce fields), docs(audiences): add errored-row run-condition fix, delete-row note, and field-deletion FAQ #1582 (bulk enrichment errored rows / deleting fields), docs(audiences): document Intelligence tab on company records (beta) #1569 (Claygent intelligence tab), docs(audiences): document nested sub-field mapping in bulk enrichments #1558 (nested sub-field mapping), docs(audiences): add CSV export workaround via Add to workbook #1550 (CSV export), docs(audiences): add FAQ clarifying dedup scope — Audiences only, not Clay tables #1547 (deduplication), docs(audiences): document Salesforce custom object export limitation and workaround #1528 (signal export to custom objects), docs(audiences): add field-filter warning to Snowflake and BigQuery import steps #1507 (Snowflake/BigQuery field mapping), docs(audiences): add Databricks as beta import source #1485 (Databricks import).

Closes DOC-1222

[linear-code]

DOC-1222