tkhq · am-hernandez · Aug 14, 2026 · Aug 11, 2026 · Aug 11, 2026 · Aug 11, 2026
diff --git a/assets/files/support-chat-launcher.png b/assets/files/support-chat-launcher.png
diff --git a/assets/files/support-chat-past-conversations.png b/assets/files/support-chat-past-conversations.png
diff --git a/assets/files/support-chat-start-new-chat.png b/assets/files/support-chat-start-new-chat.png
diff --git a/assets/files/support-ctas.png b/assets/files/support-ctas.png
diff --git a/docs.json b/docs.json
@@ -264,6 +264,12 @@
                 ]
               }
             ]
+          },
+          {
+            "group": "Support",
+            "pages": [
+              "solutions/support/overview"
+            ]
           }
         ]
       },
@@ -1070,7 +1076,7 @@
     "links": [
       {
         "label": "Support",
-        "href": "https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ"
+        "href": "/solutions/support/overview"
       },
       {
         "label": "Blog",
@@ -1091,7 +1097,6 @@
     "socials": {
       "x": "https://x.com/turnkeyhq",
       "github": "https://github.com/tkhq",
-      "slack": "https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ",
       "linkedin": "https://www.linkedin.com/company/turnkeyhq/"
     }
   },

diff --git a/features/authentication/passkeys/integration.mdx b/features/authentication/passkeys/integration.mdx
@@ -2,6 +2,8 @@
 title: "Integrating Passkeys"
 ---
 
+import { SupportLink } from "/snippets/support-callout.mdx";
+
 ## Passkey flow
 
 A typical passkey flow is composed of 4 main steps, depicted below:
@@ -68,8 +70,7 @@ Regardless of whether you use our helpers and abstractions, take a look at [our
 If you have questions, feedback, or find yourself in need of an abstraction or integration that doesn't exist yet, please get in touch with us! You can
 
 * Create an [issue on our SDK repo](https://github.com/tkhq/sdk/issues)
-* Join our slack community [here](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ)
-* Contact us at [hello@turnkey.com](mailto:hello@turnkey.com)
+* Reach out through any of our <SupportLink />
 
 We're here to make this as easy as possible for you and your team!
 

diff --git a/features/networks/aptos.mdx b/features/networks/aptos.mdx
@@ -3,6 +3,8 @@ title: "Aptos support on Turnkey"
 sidebarTitle: "Aptos"
 ---
 
+import { SupportCallout } from "/snippets/support-callout.mdx";
+
 ## Address derivation
 
 Turnkey supports Aptos address derivation with `ADDRESS_TYPE_APTOS`. Aptos addresses are derived from the Ed25519 curve, which Turnkey fully supports.
@@ -208,4 +210,4 @@ Aptos utilizes the Move programming language for smart contracts. When developin
 - Executing Move functions
 - Managing account resources
 
-If you're building on Aptos and need assistance with your Turnkey integration, feel free to contact us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+<SupportCallout prompt="Building on Aptos and need help with your Turnkey integration?" />
diff --git a/features/networks/canton.mdx b/features/networks/canton.mdx
@@ -3,6 +3,8 @@ title: "Canton support on Turnkey"
 sidebarTitle: "Canton"
 ---
 
+import { SupportCallout } from "/snippets/support-callout.mdx";
+
 ## Address derivation
 
 Canton identities are derived from the Ed25519 curve, which Turnkey fully supports. Rather than deriving a single chain-specific address, Canton uses a two-step process: Turnkey generates an Ed25519 key pair (using `ADDRESS_FORMAT_COMPRESSED` with `CURVE_ED25519`), and the resulting public key is then registered with a specific Canton network node. Registration creates a new **Party** and returns its `PartyId` along with a Canton-internal fingerprint of your public key. The party participates in network activity by identifying itself with its `PartyId` and fingerprint. Note that a party is not a global concept (unlike e.g. ENS) — it lives only on the node where it was registered.
@@ -197,4 +199,4 @@ Canton applications are written in the Daml smart contract language. When buildi
 - Executing commands on Daml contracts
 - Managing external party identities
 
-If you're building on Canton and need assistance with your Turnkey integration, feel free to contact us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+<SupportCallout prompt="Building on Canton and need help with your Turnkey integration?" />
diff --git a/features/networks/cardano.mdx b/features/networks/cardano.mdx
@@ -3,6 +3,8 @@ title: "Cardano support on Turnkey"
 sidebarTitle: "Cardano"
 ---
 
+import { SupportCallout } from "/snippets/support-callout.mdx";
+
 ## Address derivation
 
 Cardano support is at the **curve level**: Turnkey holds an Ed25519 key pair (`ADDRESS_FORMAT_COMPRESSED` with `CURVE_ED25519`) and returns the public key, from which you derive the Cardano address **client-side** (the payment credential is the Blake2b-224 hash of the public key). The example below uses [MeshJS](https://meshjs.dev/), but any Cardano library works.
@@ -142,4 +144,4 @@ A Cardano address encodes only a **network id** — `1` for mainnet, `0` for *an
 - **Developer-Friendly**: Integrate with existing Cardano development workflows (MeshJS, CSL, Lucid)
 - **Multi-network Support**: Use the same code across mainnet and the preprod/preview testnets
 
-If you're building on Cardano and need assistance with your Turnkey integration, feel free to contact us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+<SupportCallout prompt="Building on Cardano and need help with your Turnkey integration?" />
diff --git a/features/networks/cosmos.mdx b/features/networks/cosmos.mdx
@@ -3,6 +3,8 @@ title: "Cosmos support on Turnkey"
 sidebarTitle: "Cosmos"
 ---
 
+import { SupportCallout } from "/snippets/support-callout.mdx";
+
 ## Address derivation
 
 Turnkey supports Cosmos address derivation. The address formats we support follow the [Cosmos SDK](https://docs.cosmos.network/) standard for bech32 addresses.
@@ -122,4 +124,4 @@ Turnkey supports various Cosmos ecosystem chains for address derivation and sign
 - **Secure Signing**: All private keys remain secure in Turnkey's infrastructure
 - **Policy Control**: Apply custom signing policies to control transaction approvals
 
-If you are using a Cosmos chain we do not explicitly support, feel free to contact us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+<SupportCallout prompt="Using a Cosmos chain we don't explicitly support?" />
diff --git a/features/networks/ethereum.mdx b/features/networks/ethereum.mdx
@@ -3,6 +3,8 @@ title: "Ethereum (EVM) support on Turnkey"
 sidebarTitle: "Ethereum (EVM)"
 ---
 
+import { SupportCallout } from "/snippets/support-callout.mdx";
+
 ## Address derivation
 
 Turnkey supports EVM address derivation with `ADDRESS_TYPE_ETHEREUM`. This address format is valid across all EVM chains and L2s.
@@ -300,4 +302,4 @@ Turnkey supports the EVM chains below for address derivation and signing arbitra
 - zkSync
 - Zora
 
-If you are using an EVM chain we do not support, feel free to contact us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+<SupportCallout prompt="Using an EVM chain we don't support yet?" />
diff --git a/features/networks/iota.mdx b/features/networks/iota.mdx
@@ -3,6 +3,8 @@ title: "IOTA support on Turnkey"
 sidebarTitle: "IOTA"
 ---
 
+import { SupportCallout } from "/snippets/support-callout.mdx";
+
 ## Address derivation
 
 Turnkey fully supports IOTA addresses derived from the Ed25519 curve.
@@ -153,4 +155,4 @@ Turnkey supports:
 - **Signing Policies**: Apply custom policies to control transaction approvals
 - **Multi-user Support**: Manage multiple IOTA addresses under a single organization
 
-If you're building on IOTA and need assistance with Turnkey integration, feel free to contact us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+<SupportCallout prompt="Building on IOTA and need help with your Turnkey integration?" />
diff --git a/features/networks/movement.mdx b/features/networks/movement.mdx
@@ -3,6 +3,8 @@ title: "Movement"
 description: "Movement support on Turnkey"
 ---
 
+import { SupportCallout } from "/snippets/support-callout.mdx";
+
 ## Address derivation
 
 Turnkey supports Movement address derivation. Movement is built on the Move VM and uses Ed25519 cryptography, which Turnkey fully supports.
@@ -204,5 +206,5 @@ Movement leverages the Move VM for smart contracts. When developing Move smart c
 * Executing Move functions
 * Managing onchain resources
 
-If you're building on Movement and need assistance with your Turnkey integration, feel free to contact us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+<SupportCallout prompt="Building on Movement and need help with your Turnkey integration?" />
 ```
diff --git a/features/networks/others.mdx b/features/networks/others.mdx
@@ -3,6 +3,8 @@ title: "Others"
 mode: "wide"
 ---
 
+import { SupportCallout } from "/snippets/support-callout.mdx";
+
 **Can't find your preferred network?**  
 Turnkey is chain-agnostic, and our flexible infrastructure is built to
 support underlying cryptographic curves, instead of specific chains and assets. If your chain isn't mentioned, check if the underlying curve is compatible – we support signing for all chains and assets on the **Ed25519, Secp256k1, and P256** curves.
@@ -42,6 +44,5 @@ following multichain capabilities, powered by Turnkey:
 
 **Want more support?**  
 We are continuously evaluating and adding support for emerging assets and protocols.
-If there are specific networks you'd like to see us offer deeper support for, or
-if you're looking for more code examples, please let us know by contacting us at
-hello@turnkey.com, on X, or on Slack.
+
+<SupportCallout prompt="Want deeper support for a specific network, or more code examples?" />
diff --git a/features/networks/overview.mdx b/features/networks/overview.mdx
@@ -5,6 +5,7 @@ mode: "wide"
 ---
 
 import { NetworkLinks } from "/snippets/shared/networks-links.mdx";
+import { SupportCallout } from "/snippets/support-callout.mdx";
 
 ## Multichain support at Turnkey
 
@@ -43,7 +44,9 @@ At our highest level of support, Turnkey offers the ability to parse transaction
 | Tier 3 | SDK construction and signing     | ✓ | ✓ |                                               |                                               |                                               |                                               |                                               |                                               |                                               |                                               |
 | Tier 4 | Transaction parsing and policies | ✓ | ✓ | ✓ |                                               | ✓ |                                               |                                               |                                               |                                               |                                               |
 
-We are continuously evaluating and adding support for emerging assets and protocols. If there are specific cryptocurrencies you'd like to see us offer deeper support for, please let us know by contacting us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+We are continuously evaluating and adding support for emerging assets and protocols.
+
+<SupportCallout prompt="Want to see deeper support for a specific cryptocurrency?" />
 
 For more details about each ecosystem, refer to the pages below:
 

diff --git a/features/networks/sei.mdx b/features/networks/sei.mdx
@@ -3,6 +3,8 @@ title: "Sei support on Turnkey"
 sidebarTitle: "Sei"
 ---
 
+import { SupportCallout } from "/snippets/support-callout.mdx";
+
 ## Address derivation
 
 Turnkey supports Sei address derivation. Sei is part of the Cosmos ecosystem and uses the bech32 address format with the `sei` prefix. Addresses are derived using the SECP256k1 curve.
@@ -121,4 +123,4 @@ For DApp developers looking to integrate with Sei, you can use Turnkey as a secu
 - **Policy Control**: Apply transaction policies to control what can be signed
 - **Multi-environment Support**: Use the same code across testnet and mainnet
 
-If you're building on Sei and need assistance with your Turnkey integration, feel free to contact us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+<SupportCallout prompt="Building on Sei and need help with your Turnkey integration?" />
diff --git a/features/networks/spark.mdx b/features/networks/spark.mdx
@@ -3,6 +3,8 @@ title: "Spark support on Turnkey"
 sidebarTitle: "Spark"
 ---
 
+import { SupportCallout } from "/snippets/support-callout.mdx";
+
 [Spark](https://www.spark.money/) is a Bitcoin Layer 2 that uses FROST threshold signing across a collective of operators to enable fast, low-fee transfers and Lightning payments without giving up self-custody of the underlying BTC. Turnkey provides enclave-based key management for Spark: your identity key, leaf keys, deposit keys, and Lightning preimages are generated and used inside the Turnkey enclave. None of this key material ever leaves it, with the lone exception being the [static deposit flow](#static-deposits-export-a-key-from-the-enclave). This flow, by necessity, exports one deposit key so a Spark Service Provider can process deposits while your wallet is offline, and that key stops mattering once you claim the deposit.
 
 If you don't know the protocol, read [Spark core concepts](https://docs.spark.money/learn/core-concepts) and [Sovereignty](https://docs.spark.money/learn/sovereignty) first. This page covers what Turnkey adds to a Spark integration.
@@ -176,4 +178,4 @@ If you're integrating Spark, start with the SDK example and refer back to this p
 - [Spark identity-key derivation](https://docs.spark.money/wallets/identity-key-derivation)
 - [BIP-340: Schnorr Signatures for secp256k1](https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki)
 
-If you're building on Spark and have questions about integrating with Turnkey, contact us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+<SupportCallout prompt="Building on Spark and need help with your Turnkey integration?" />
diff --git a/features/networks/sui.mdx b/features/networks/sui.mdx
@@ -3,6 +3,8 @@ title: "Sui support on Turnkey"
 sidebarTitle: "Sui"
 ---
 
+import { SupportCallout } from "/snippets/support-callout.mdx";
+
 ## Address derivation
 
 Turnkey supports Sui address derivation with `ADDRESS_TYPE_SUI`. Sui addresses are derived from the Ed25519 curve, which Turnkey fully supports.
@@ -150,4 +152,4 @@ Turnkey supports:
 - **Signing Policies**: Apply custom policies to control transaction approvals
 - **Multi-user Support**: Manage multiple Sui addresses under a single organization
 
-If you're building on Sui and need assistance with Turnkey integration, feel free to contact us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+<SupportCallout prompt="Building on Sui and need help with your Turnkey integration?" />
diff --git a/features/networks/tempo.mdx b/features/networks/tempo.mdx
@@ -3,6 +3,8 @@ title: "Tempo support on Turnkey"
 sidebarTitle: "Tempo"
 ---
 
+import { SupportCallout } from "/snippets/support-callout.mdx";
+
 Tempo is a general-purpose blockchain optimized for payments. Tempo is designed to be a low-cost, high-throughput blockchain with user and developer features targeting modern payment systems including first-class stablecoin support. More on [Tempo here](https://docs.tempo.xyz/).
 
 ## Address derivation
@@ -46,4 +48,4 @@ Turnkey supports:
 - **Developer-Friendly**: Integrate with existing Tempo development workflows
 - **Multi-environment Support**: Use the same code across testnet and mainnet environments
 
-If you're building on Tempo and need assistance with your Turnkey integration, feel free to contact us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+<SupportCallout prompt="Building on Tempo and need help with your Turnkey integration?" />
diff --git a/features/networks/tron.mdx b/features/networks/tron.mdx
@@ -3,6 +3,8 @@ title: "Tron support on Turnkey"
 sidebarTitle: "Tron"
 ---
 
+import { SupportCallout } from "/snippets/support-callout.mdx";
+
 ## Address derivation
 
 Turnkey supports Tron address derivation with `ADDRESS_TYPE_TRON`. Tron addresses are derived from the same SECP256k1 curve that is used for Ethereum addresses, but with a different address encoding format.
@@ -111,4 +113,4 @@ Turnkey can be integrated with popular Tron development tools such as:
 - **Simplified Key Management**: No need to manage private keys in your application code
 - **Multi-signature Support**: Enable quorum-based approvals for transactions
 
-If you have any questions about using Turnkey with Tron or need assistance with integration, feel free to contact us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+<SupportCallout prompt="Building on Tron and need help with your Turnkey integration?" />
diff --git a/reference/faq.mdx b/reference/faq.mdx
@@ -2,6 +2,8 @@
 title: "FAQ"
 ---
 
+import { SupportCallout, SupportLink } from "/snippets/support-callout.mdx";
+
 ## Authentication and credentials
 
 <AccordionGroup>
@@ -111,7 +113,7 @@ title: "FAQ"
 
     We have deeper support for [Ethereum](/features/networks/ethereum), [Solana](/features/networks/solana), and [Bitcoin](/features/networks/bitcoin).
 
-    If there are specific ecosystems or chains you'd like to see us offer deeper support for, please let us know by contacting us at [hello@turnkey.com](mailto:hello@turnkey.com), on [X](https://x.com/turnkeyhq/), or [on Slack](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ).
+    <SupportCallout prompt="Want to see deeper support for a specific ecosystem or chain?" />
   </Accordion>
   <Accordion title="Do you support transaction construction and broadcast?">
     Turnkey's [Transaction Management](/features/transaction-management) supports  gas sponsorship, transaction construction, broadcast, nonce management and monitoring capabilities, down to just a few API calls. 
@@ -155,7 +157,7 @@ title: "FAQ"
     For more information about pricing and billing, check out the [pricing page](https://www.turnkey.com/pricing).
   </Accordion>
   <Accordion title="Where else can I get help with my Turnkey implementation?">
-    Join our slack community [here](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ) to get support with your integration, share product feedback, and connect with other crypto builders. Or, reach out directly to [help@turnkey.com.](mailto:help@turnkey.com.) Teams that are looking for more in-depth integration support can upgrade to an Enterprise plan via [hello@turnkey.com](mailto:hello@turnkey.com).
+    See <SupportLink label="Support" /> for every way to reach us, including the support chat in the dashboard and email. Teams that are looking for more in-depth integration support can upgrade to an Enterprise plan via [hello@turnkey.com](mailto:hello@turnkey.com).
   </Accordion>
   <Accordion title="What is your data deletion policy?">
     To request the deletion of your parent organization from our records, please email us at [privacy@turnkey.com](mailto:privacy@turnkey.com).

diff --git a/snippets/support-callout.mdx b/snippets/support-callout.mdx
@@ -0,0 +1,12 @@
+export const SupportCallout = ({
+  prompt = "Need help with your Turnkey integration?",
+}) => (
+  <>
+    {prompt} Reach out through any of our{" "}
+    <a href="/solutions/support/overview">support channels</a>.
+  </>
+);
+
+export const SupportLink = ({ label = "support channels" }) => (
+  <a href="/solutions/support/overview">{label}</a>
+);