docs(audiences): replace non-existent Continue button with Upsert segment record instructions

[george-dilthey]

What changed

Replaced the non-existent "Continue" button steps in docs/audiences.md with the correct Upsert segment record enrichment workflow. Also fixed four downstream FAQ references that cited the same non-existent flow.

Specific changes:

1. "Sending data from Clay table" section — removed Click Continue at the bottom of the table → Save to People/Companies steps; replaced with Add enrichment → search for Upsert segment record → map columns → run
2. "People sourcing for ad platform sync" FAQ — fixed "then click Continue → Save to People from the table" to "use Upsert segment record in the table"
3. "Why doesn't my Clay table appear in the Person source filter?" FAQ — fixed "using Continue → Save to People" to "using Add data → Add source → Clay table"
4. "How do I find which Clay table a lead in Audiences came from?" FAQ — fixed "via Continue → Save to People or Save to Companies"; added note that records pushed via Upsert segment record don't create a named source entry
5. "If I delete or archive a Clay table..." FAQ — fixed "via Continue → Save to Companies / Save to People, or using Upsert Audiences Record" to "using Upsert segment record or the Add data → Add source → Clay table import flow"

Why

Intercom conversation 215475557457527 shows a Growth-plan customer (Laurent Léveillée, deck.co) who asked "how do I turn this table into an audience?" Fin replied repeatedly with instructions to click a "Continue" button at the bottom of the table — a button that does not exist in the product. The customer spent significant time looking for it before escalating. Human support agent Aamish Samotra confirmed: "There is no 'Continue' button, that was incorrect information. The right way to send your table records into Audiences is to add an Upsert Audiences Record enrichment column to your table."

The doc's "Sending data from Clay table" section was the root cause — it explicitly described Click Continue at the bottom of the table as the first step, which Fin surfaced as authoritative. This section and four FAQ references to the same fictitious flow have been corrected.

Materiality vs. existing PRs: PRs #2291 and #2288 (Webflow sync PRs from Aug 24) add Upsert segment record content to the Clay-table section. PRs #2204 explicitly adds the wrong "Continue → Save to Companies / Save to People" phrasing to the "If I delete or archive" FAQ — this PR corrects that. None of the other open PRs touch the 4 FAQ references fixed here. This is the only PR that (a) removes wrong "Continue" content rather than just adding alongside it, and (b) fixes the FAQ misinformation.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/apps/w28k1kwz/inbox/inbox/conversation/215475557457527
• Verifier evidence (action exists): /workspace/public-actions/src/upsert-audiences-record/index.ts — real action, key upsert-audiences-record; /workspace/clay-base/libs/shared/src/ActionDefinitions.ts:255 — displayName: 'Upsert segment record'
• Verifier evidence (no Continue button in tables): searched clay-base/apps/frontend/src/components/Table/ — no such component found; Continue button only exists in search wizard contexts (CPJSourceStepSidebarFooterActions.tsx, FpacContinueButton.tsx), not at the bottom of regular tables

Uncertainties

The doc retains several pre-existing references to Upsert Audiences Record (the conceptual name) throughout other sections — notably the "Using Audiences from a Clay table" section and the conflict-resolution priority table. The enrichment panel display name in the product is "Upsert segment record" (ActionDefinitions.ts:255), while the Audiences-side source label is "Upsert Audiences record" (sync-source-types.ts:45). The existing Upsert Audiences Record references were not changed in this PR (scope = fixing the "Continue" button misinformation); a follow-up pass to normalize naming throughout the doc would reduce confusion for users and Fin.

Audiences access is gated by the EnableAudiencesGA Eppo feature flag (default false). The doc already states it's available on Growth and Enterprise plans, and the customer in this ticket (Growth plan) had Audiences access — but the Eppo targeting config lives outside the repo and could not be confirmed from code alone.

Related observations

• Multiple other open PRs touch docs/audiences.md: docs(audiences): restructure Clay table section and rename Upsert/Update Audiences Record actions #2291, docs(audiences): rewrite Clay table import section and fix Upsert action name #2288, 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): document OR filter group with AND exclusion pattern #2349, 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, docs(audiences): add FAQ for Salesforce duplicate company records #2305, docs(audiences): add FAQ for time-gated audience segment membership #2303, docs(audiences): document Salesforce SOQL import for Enterprise customers #2295, docs(audiences): add FAQ for fixing existing duplicates, fix Import Record Matching scope #2280, docs(audiences): add CRM and warehouse sync cadence anchor sections #2272, docs(audiences): note that HubSpot sync time of day is not shown in the UI #2261, docs(clay-ads): add EEA consent, platform fields, delete-recreate behavior, match rate clarification #2251, docs(audiences): document Update segment record as admin-only and clarify permission error #2245, docs(audiences): document Enhanced Matching skip logic and hashed email output fields #2232, docs(audiences): document Enhanced Matching skip logic and hashed email output fields #2231, docs(audiences): add concrete use-case guidance to Audiences vs. Tables FAQ #2225, docs(audiences): clarify Find People destination when using Audience as Target companies #2224, docs(audiences): explain Clay-prefixed auto-populated fields and fix export credits FAQ #2215, docs(audiences): explain why Audiences fields have values when CRM fields are blank #2210, docs(audiences): cover archived workbook behavior in Origin source filter FAQ #2204, docs(audiences): explain signal vs bulk-enrichment relationship and fix auto-enrich timing #2203, docs(audiences): explain that archived source tables remain in Origin source filter #2202. Reviewer should reconcile at merge time. PR docs(audiences): cover archived workbook behavior in Origin source filter FAQ #2204 specifically adds incorrect "Continue → Save to Companies" phrasing to the "If I delete or archive" FAQ — this PR fixes that conflict.
• Other sections still use "Upsert Audiences Record" when describing the table enrichment panel action. The actual UI display name is "Upsert segment record" — those references should be aligned in a follow-up PR.

Closes DOC-2152

[linear-code]

DOC-2152