docs(audiences): clarify legacy plan access and add why-not-visible FAQ - #2345
Open
george-dilthey wants to merge 1 commit into
Open
docs(audiences): clarify legacy plan access and add why-not-visible FAQ#2345george-dilthey wants to merge 1 commit into
george-dilthey wants to merge 1 commit into
Conversation
Contributor
george-dilthey
marked this pull request as ready for review
August 26, 2026 20:36
This was referenced Aug 26, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Added a "Identifying your plan type" paragraph to
docs/audiences.mdimmediately after the plan availability statement, explaining what a legacy plan looks like (date-based slug visible in Settings → Billing) and that legacy non-Enterprise plans do not include Audiences. Also added a new FAQ entry "Why don't I see Audiences in my workspace sidebar?" at the top of the FAQs section — explicitly stating that joining the beta program does not grant access, that plan tier is the gate, and how to check or upgrade. Updated thedescriptionfrontmatter to reflect the legacy plan distinction.Why
Intercom conversation #215475650532754 (WorkMotion / Sergio López): a customer on a legacy Pro plan (
proApril2023) couldn't see Audiences. Fin incorrectly guided them to join the beta program and check admin permissions — two plausible but irrelevant steps. The human agent (Keane Davis) escalated and explained: "Audiences is only available for all modern plans (Launch, Growth, Enterprise). You're on a legacy Pro plan." The existing doc correctly says "legacy non-Enterprise plan workspaces do not have access to Audiences" but gives no way for a customer (or Fin) to recognize whether their plan is "legacy" — there's no guidance on what a legacy plan looks like from the billing screen, no note that beta enrollment doesn't help, and no dedicated FAQ for this very common first question.Source link(s)
apps/api/v3/featureFlags/services/featureFlags.service.ts:34-40in clay-base confirmsAUDIENCES_GA_BILLING_PLAN_TYPESdoes not includeProApril2023. Legacy Enterprise (EnterpriseApril2023) IS included — consistent with the doc's "(including legacy Enterprise)" note.proApril2023plans fail Audiences access: https://clay-hq.slack.com/archives/C08B9DAQQP3/p1782239882144419ProApril2023customer wanting Audiences, flagged as modern-plan upgrade opportunity: https://clay-hq.slack.com/archives/C08LMK5JTS5/p1785194897968279Uncertainties
None. The plan gate is hardcoded in
plan-feature-defaults.ts; both the code and Slack confirm the behavior. The existing "(including legacy Enterprise)" claim is correct per the verifier.Related observations
22 other open PRs touch
docs/audiences.md(PRs #2179, #2184, #2192, #2195, #2202–#2204, #2210, #2215, #2224–#2225, #2231–#2232, #2245, #2251, #2261, #2272, #2280, #2288–#2291, #2295, #2303, #2305, #2321, #2323). None address the legacy plan identification gap or the beta-enrollment misconception documented here — the changes are on different topics (deduplication, Salesforce/HubSpot sync specifics, Enhanced Matching, workflows, etc.).Closes DOC-2100