Am/cus 289/remove slack ctas from turnkey docs

[am-hernandez]

docs(support): add a Support page and remove Slack CTAs

Why

Turnkey Docs still pointed developers to the public Club Turnkey Slack community as a support channel. Pylon is the support surface now, so those CTAs needed to go and the docs needed a single page describing how to actually get help.

What

New Support page (solutions/support/overview.mdx, added to the Solutions nav):

• Covers the in-dashboard support chat: where the launcher is, what the panel does (new conversations, past conversations, its GitHub / status page / Contact Sales bookmarks), and how the AI first response escalates to the team.
• Notes the two prerequisites: current dashboard only, and you must be logged in.
• Documents email routing (help@turnkey.com for support, hello@turnkey.com for commercial), the Enterprise shared Slack channel, X, and the status page.
• Adds a "what to include in a support request" checklist plus a warning never to share key material.
• Four screenshots in assets/files/: launcher location, both dashboard Support CTAs, and two captioned shots of the open panel.

CTA cleanup (docs.json):

• Navbar Support link now points at /solutions/support/overview instead of the Slack invite.
• Footer slack social removed with no replacement.

Reusable callout (snippets/support-callout.mdx), replacing 18 Slack/hello@turnkey.com sign-offs across 17 files:

• SupportCallout takes an optional prompt and renders the shared "reach out through any of our support channels" sentence. It returns a fragment rather than a <Note>, so it drops into a paragraph, a list item, or an accordion without changing the visual weight of the copy it replaces.
• SupportLink is the inline anchor, for the two cases that live inside bullet lists.
• 14 network pages, reference/faq.mdx (2), features/authentication/passkeys/integration.mdx, and solutions/cookbooks/tron-gasless-transactions.mdx.

Scope and non-goals

• features/networks/others.mdx carried the same sign-off as unlinked plain text, so the ticket's URL grep missed it. It is fixed here, which makes 14 network pages rather than the 13 the ticket lists.
• Shared/dedicated Slack channel references are intentionally kept in tvc-beta-callout.mdx, time-based-policies-beta-callout.mdx, verifiable-cloud/onboarding.mdx, and manifest-sets-and-share-sets.mdx. Those are the Enterprise shared channel, not the community.
• Context-specific hello@turnkey.com asks are left alone, since they are not multi-channel support sign-offs: bespoke email templates, Python SDK prioritization, wallets.mdx, faq.mdx (2), migration-guide.mdx, and the help@turnkey.com guidance in api-reference/overview/errors.mdx, though they may warrant a folloew-up.

Testing

Verified locally: the page renders, all four screenshots resolve, and every internal link in it points at a real page (/reference/faq, /api-reference/overview/errors, /api-reference/overview/intro, /sdks/introduction).

Reviewers should check:

• The SupportCallout fragment renders inline correctly in all three positions, especially inside the FAQ accordions.
• The navbar Support link stays on localhost under mintlify dev.
• Copy accuracy on the Pylon behavior, particularly the escalation description and the launcher position.
• Consider IA and if the location of the Support doc is ideal.

Ticket

Closes CUS-289

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
turnkey-docs	🟢 Ready	View Preview	Aug 11, 2026, 10:21 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.