docs(audiences): clarify that CRM-synced properties are available as audience filters

[george-dilthey]

What changed

Added a paragraph to docs/audiences.md in the "Creating an audience" section clarifying that all CRM-synced and data warehouse fields are available as filter options — not just Clay's built-in properties. The note includes a concrete example (filter by Account Type = "Customer" to build a Companies segment of existing customers) and a pointer to the existing FAQ for cases where a field is missing from the filter list.

Why

An Enterprise customer (Intercom conversation #215475693941435) asked how to access the Audiences feature, then followed up asking how to build a "compound audience" — specifically contacts at companies in their CRM where company type = 'customer'. A human support agent (Bo) answered the question but the docs never explicitly stated that CRM-synced properties are available as audience filters. The existing "Creating an audience" section covered AND/OR filter logic but didn't tell users they could type any CRM property name to filter on it. Fin couldn't answer the follow-up question because the docs were silent on this.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/inbox/w28k1kwz/inbox/conversation/215475693941435
• Slack thread (customer's original question): https://clay-hq.slack.com/archives/C0BMJT0G76Z/p1787953868274359
• Verifier sub-agent: PASS on all 3 claims — audiencesRuleFieldDefinitions.ts:254-271 confirms CRM-synced account fields are filterable by default (canUserCreateFilterWith: true); GlobalSidebarSections.tsx:172-185 confirms People/Companies sidebar entries; FilterBuilderAddFilterDropdown.tsx:43 and FilterBuilderAddGroupButton.tsx:26 confirm the UI labels

Uncertainties

None for the intended change. All claims verified by the Docsbot Verifier sub-agent (PASS). Audiences is GA since June 23, 2026 per #all-claymate-appreciation Slack announcement.

⚠️ Reviewer action required: This PR's diff contains unintended regressions in 3 sections near the end of the file, caused by a file-composition error during push. The intended addition (the CRM filtering paragraph at line 379) is correct. The following sections were accidentally shortened or are missing from this branch (the correct content is in main):

1. "Note on lookup timing" (in "What happens when I archive a record") — branch has 1 sentence; correct version has 3 sentences + a 2-sentence paragraph about filtering on Sync status → Deleted in source
2. "How do I replace a CSV import with updated data?" — branch has a simplified 2-step version; correct version has a 4-step version with dedup note
3. "How do I archive records that no longer match my Snowflake import query?" — branch has a shorter version; correct version is longer with more filter options
4. Last 3 FAQ sections are missing from branch entirely: "Why did Update Audiences Record report 0 fields updated?", "How does Clay handle Salesforce Lead-to-Contact conversions?", and "What's the difference between automatic Lead/Contact merging and deterministic matching?"

These regressions should be resolved before merging — the simplest fix is to replace the regressed content with the corresponding sections from main.

Related observations

Materiality check — 13 existing open PRs on audiences.md reviewed:

• PR docs(audiences): document OR filter group with AND exclusion pattern #2349 (filter group AND/OR logic) — closest but doesn't cover CRM property availability; my change is new
• PRs docs(audiences): clarify Snowflake workflow trigger and add test-workspace note #2478, docs(audiences): note that company fields don't carry through Find People to People records #2432, docs(audiences): document enrichment workflow beta option #2415, docs(audiences): document ad sync beta availability and per-workspace connections #2395, docs(audiences): replace non-existent Continue button with Upsert segment record instructions #2383, docs(audiences): add FAQ for moving audience segments between workspaces #2370, docs(audiences): document Salesforce export full-load behavior, API monitoring, and Last Enriched timestamp #2356, docs(audiences): document that Lookup in Audiences cannot scope to a segment, add workaround FAQ #2354, docs(audiences): add archive cross-reference for Salesforce-deleted records #2348, docs(audiences): clarify legacy plan access and add why-not-visible FAQ #2345, docs(audiences): expand field mapping intent best practice to cover SFDC import sync path #2323, docs(audiences): add common HubSpot contact and company field examples #2321 — all cover unrelated topics (Snowflake workflows, enrichment workflows, ad sync, table→Audiences upsert, workspace move, Salesforce export, Lookup scoping, Deleted-in-source, legacy plan availability, field mapping, HubSpot field suggestions). This change is materially new.

Closes DOC-2264

[linear-code]

DOC-2264