docs(audiences): add FAQ for why users only see Sync to ad platforms in Send menu

[george-dilthey]

What changed

Added a new FAQ entry to docs/audiences.md: "Why do I only see 'Sync to ad platforms' when I click Send on my audience segment?"

The FAQ explains:

1. The Send menu options depend on which features are enabled in a workspace — for most new workspaces, "Sync to ad platforms" is the primary option; "Send to workflow" and "Export to campaign" require additional features.
2. There is no direct "Send to table" in the Send menu. The recommended path to get audience data into a Clay table is through a bulk enrichment: Enrich → Add bulk enrich → run → click "Open enrichment" on the enrichment card to open the underlying Clay table.

Why

Intercom conversation #215475098582728: Nick Cousin (Billtrust) asked "I'm trying to 'send' an audience to a new Clay table, but my only option visible within Clay is to send it to an 'ad platform'. Is this a permissions issue?" The question required a human support agent (Peter Johnston) to answer — Fin couldn't resolve it. This confirms the docs had no FAQ covering this scenario.

Research confirmed:

• The Send menu is built from exactly four action types: Workflow, Workbook (gated), AdAudiences, PeopleCampaign — no CRM export option exists in the Send dropdown. Export sync is a background write-back setting in Settings, unrelated to the Send menu.
• "Add to workbook" is behind EnableAudiencesSendToWorkbook (default: off for new workspaces), so most new customers only see "Sync to ad platforms."
• The bulk enrichment created via Enrich → Add bulk enrich IS a Clay table, accessed via the "Open enrichment" button on the enrichment card. This is Clay's own stated recommended path for getting audience data into a table for downstream workflows.

Note: pre_pr_check flagged 12 open PRs on audiences.md. I evaluated each — all cover different sections (Salesforce field read-only rules, Databricks import, Signals, archiving behavior, etc.) and none adds a FAQ about the Send menu showing limited options or the Bulk Enrich → table path. This change is materially new to all 12.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/inbox/w28k1kwz/inbox/conversation/215475098582728
• Slack trigger thread (Peter Johnston's answer to customer): https://clay-hq.slack.com/archives/C0BCJFC328N/p1784138011758019?thread_ts=1784132799.588639&cid=C0BCJFC328N
• Slack internal confirmation (EnableAudiencesSendToWorkbook rationale): https://clay-hq.slack.com/archives/C08J4ENDYC9/p1782912488839069
• Verifier code evidence: ExportsDropdown.tsx:283–335 (Send menu has 4 actions, no CRM option); useAvailableExportActionsForSegment.ts:20–52 (only 4 action variants); AudiencesBulkEnrichmentCard.tsx:197–204 ("Open enrichment" button links to table)
• Screenshot in Intercom part fix: correct malformed markdown for crm.objects.deals.write scope #19 shows the Clay People table view with "Sync to ad platforms" tooltip visible

Uncertainties

None. Both product behavior claims verified against code. The verifier corrected an initial wrong claim (that Export sync toggle affects the Send menu) before any incorrect text was merged — FAIL on attempt 1, then corrected, then re-verified as PASS.

Related observations

• PR docs(audiences): add CSV export workaround via Add to workbook #1550 adds "Add to workbook" as a CSV export path and notes it's "currently rolling out to Growth and Enterprise workspaces." This PR addresses a different use case (CSV download); my change addresses the Send menu's limited options and the Bulk Enrich → table path for downstream workflow orchestration. A reviewer should reconcile framing of "Add to workbook" availability across the two PRs — verifier confirmed EnableAudiencesSendToWorkbook defaults to OFF for new workspaces.
• PRs docs(audiences): add Export sync toggle prerequisite for Salesforce write-back #1615, docs(audiences): document signal detection-layer model and Data Hub vs. table scope #1605, docs(audiences): document archived record behavior on source re-sync #1587, docs(audiences): add read-only Salesforce field types and cross-object enrichment FAQ #1585, docs(audiences): add errored-row run-condition fix, delete-row note, and field-deletion FAQ #1582, docs(audiences): document Intelligence tab on company records (beta) #1569, docs(audiences): document nested sub-field mapping in bulk enrichments #1558, docs(audiences): add FAQ clarifying dedup scope — Audiences only, not Clay tables #1547, docs(audiences): document Salesforce custom object export limitation and workaround #1528, docs(audiences): add field-filter warning to Snowflake and BigQuery import steps #1507, docs(audiences): add Databricks as beta import source #1485 are also open on audiences.md — all cover different sections and do not overlap with this change.

Closes DOC-1231

[linear-code]

DOC-1231