diff --git a/assets/files/support-chat-launcher.png b/assets/files/support-chat-launcher.png new file mode 100644 index 00000000..b8d8571b Binary files /dev/null and b/assets/files/support-chat-launcher.png differ diff --git a/assets/files/support-chat-past-conversations.png b/assets/files/support-chat-past-conversations.png new file mode 100644 index 00000000..c09e1f1b Binary files /dev/null and b/assets/files/support-chat-past-conversations.png differ diff --git a/assets/files/support-chat-start-new-chat.png b/assets/files/support-chat-start-new-chat.png new file mode 100644 index 00000000..d1f7c464 Binary files /dev/null and b/assets/files/support-chat-start-new-chat.png differ diff --git a/assets/files/support-ctas.png b/assets/files/support-ctas.png new file mode 100644 index 00000000..a1080333 Binary files /dev/null and b/assets/files/support-ctas.png differ diff --git a/docs.json b/docs.json index d573a462..f5db02de 100644 --- 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 index 93b86234..ac98b173 100644 --- 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 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 index a15f3f3c..53669088 100644 --- 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). + diff --git a/features/networks/canton.mdx b/features/networks/canton.mdx index 9ab24dc4..bf931675 100644 --- 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). \ No newline at end of file + \ No newline at end of file diff --git a/features/networks/cardano.mdx b/features/networks/cardano.mdx index e75fdb74..5906335e 100644 --- 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). + diff --git a/features/networks/cosmos.mdx b/features/networks/cosmos.mdx index e4d5ff3d..93d04282 100644 --- 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). + diff --git a/features/networks/ethereum.mdx b/features/networks/ethereum.mdx index e48bd4cc..5f412bc7 100644 --- 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). \ No newline at end of file + \ No newline at end of file diff --git a/features/networks/iota.mdx b/features/networks/iota.mdx index 601b595d..85ec4bac 100644 --- 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). + diff --git a/features/networks/movement.mdx b/features/networks/movement.mdx index c57d1fb2..55a55e39 100644 --- 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). + ``` diff --git a/features/networks/others.mdx b/features/networks/others.mdx index 338a3f84..7dc89965 100644 --- 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. + + diff --git a/features/networks/overview.mdx b/features/networks/overview.mdx index a958c6ac..9b135920 100644 --- 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. + + For more details about each ecosystem, refer to the pages below: diff --git a/features/networks/sei.mdx b/features/networks/sei.mdx index 758f6dfc..5dcac244 100644 --- 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). + diff --git a/features/networks/spark.mdx b/features/networks/spark.mdx index 3c528fe7..2e286110 100644 --- 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). + diff --git a/features/networks/sui.mdx b/features/networks/sui.mdx index bd1e79fa..2377437d 100644 --- 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). \ No newline at end of file + \ No newline at end of file diff --git a/features/networks/tempo.mdx b/features/networks/tempo.mdx index 47a2555a..d7e68e04 100644 --- 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). + diff --git a/features/networks/tron.mdx b/features/networks/tron.mdx index 78b709ad..f1857b29 100644 --- 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). + diff --git a/reference/faq.mdx b/reference/faq.mdx index 5a942a3c..dbeb5789 100644 --- 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 @@ -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). + 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). - 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 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). 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 new file mode 100644 index 00000000..5f3a92b2 --- /dev/null +++ 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{" "} + support channels. + +); + +export const SupportLink = ({ label = "support channels" }) => ( + {label} +); diff --git a/solutions/cookbooks/tron-gasless-transactions.mdx b/solutions/cookbooks/tron-gasless-transactions.mdx index 0bcfeb1d..eef07b89 100644 --- a/solutions/cookbooks/tron-gasless-transactions.mdx +++ b/solutions/cookbooks/tron-gasless-transactions.mdx @@ -3,6 +3,8 @@ title: "How to integrate gasless transactions on Tron with Turnkey" sidebarTitle: "Gasless Tron transactions" --- +import { SupportCallout } from "/snippets/support-callout.mdx"; + Turnkey offers flexible infrastructure to create and manage private keys. By combining the secure private key infrastructure and with gas abstracted transactions, developers can easily integrate account abstraction features for any Turnkey-powered wallets. @@ -68,9 +70,4 @@ Tron’s native network token TRX staked in order to fund end-user’s transacti ### **Thinking about gasless transactions for other chains?** -If you have questions, feedback, or find yourself in need of a gas abstraction or integration that -doesn’t exist yet, please get in touch with us! You  can - -- 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) + diff --git a/solutions/support/overview.mdx b/solutions/support/overview.mdx new file mode 100644 index 00000000..e6ee6c6d --- /dev/null +++ b/solutions/support/overview.mdx @@ -0,0 +1,182 @@ +--- +title: "Support" +description: "How to reach the Turnkey team, what each support channel is for, and what to include so we can help you faster." +sidebarTitle: "Overview" +--- + +Turnkey offers several ways to get help, depending on whether you need hands-on +integration support, have a commercial question, or are tracking an active +incident. The fastest route for technical questions is the support chat built +into the Turnkey dashboard. + + + + In-dashboard chat for technical and integration questions. AI answers first, + with escalation to the Turnkey team. + + + + [help@turnkey.com](mailto:help@turnkey.com) for support, + [hello@turnkey.com](mailto:hello@turnkey.com) for plans and commercial + questions. + + + + Available to teams on an Enterprise plan, connected directly to your Turnkey + account team. + + + + Critical incidents are reported at + [turnkey-status.com](https://www.turnkey-status.com/). + + + +## Support chat in the dashboard + +The Turnkey dashboard includes a support chat widget. It is the primary channel +for technical and integration questions, and conversations you start there are +tracked so you can pick them back up later. + + + The support chat is available in the + [dashboard](https://app.turnkey.com/dashboard/v2) and requires you to be + logged in. It is not available in the legacy dashboard, so if you do not see + the widget, confirm you are on the current dashboard and signed in to your + organization. + + +### Finding the widget + +The chat launcher sits in the bottom-right corner of the dashboard and stays +available as you navigate between pages. + + + ![Turnkey dashboard with the support chat launcher in the bottom-right corner](/assets/files/support-chat-launcher.png) + + +Selecting the launcher opens the chat panel over the dashboard, so you keep your +current page and context while you ask a question. + +### Support links that open the chat + +Two **Support** entry points in the dashboard open the same chat panel rather +than sending you elsewhere. + +One is at the bottom of the dashboard side nav, available from any page. The +other is on the dashboard Home screen. + + + ![The Support link at the bottom of the Turnkey dashboard side nav and the Support call to action on the dashboard Home screen](/assets/files/support-ctas.png) + + +### What you can do in the chat + +- **Start a new conversation.** Describe your issue in the message composer to + open a new thread. +- **Reopen past conversations.** Previous threads are listed in the panel, so + you can review earlier answers or add a follow-up to an existing thread + instead of starting over. +- **Jump to related resources.** The panel contains helpful bookmarks at the bottom that link out to Turnkey's + [GitHub organization](https://github.com/tkhq), Turnkey's + [status page](https://www.turnkey-status.com/), and our + [Contact Sales](https://www.turnkey.com/contact-us) form for commercial questions. + +
+ + ![The open support chat panel with the option to start a new conversation highlighted](/assets/files/support-chat-start-new-chat.png) + + + + ![The open support chat panel with the list of past conversations highlighted](/assets/files/support-chat-past-conversations.png) + +
+ +### AI first response and escalation + +Some new conversations will receive an AI-generated first response drawn from Turnkey's +documentation. It resolves many common questions immediately, at any hour. + +If the answer does not resolve your issue, say so in the thread and the +conversation is escalated to the Turnkey support team. Some escalation is automatic. Escalated threads stay in +the same conversation, so the team sees the full history and you do not need to +restate the problem. + +## Email + +- [help@turnkey.com](mailto:help@turnkey.com) reaches the support team for + technical questions, integration help, errors, and account issues. Use this if + you cannot use the chat widget to report your issue. +- [hello@turnkey.com](mailto:hello@turnkey.com) is for pricing, plans, network + or feature requests, and other commercial questions. Teams looking for + in-depth, ongoing integration support can ask about upgrading to an Enterprise + plan here. + +## Shared Slack channel + +Teams on an Enterprise plan can have a shared Slack channel connected directly +to their Turnkey account team, which is useful during active integration work +and launches. If your organization already has one, keep using it. If you would +like one, contact [hello@turnkey.com](mailto:hello@turnkey.com). + +## Community Slack + +[Club Turnkey](https://join.slack.com/t/clubturnkey/shared_invite/zt-3aemp2g38-zIh4V~3vNpbX5PsSmkKxcQ) +is our community Slack workspace, where builders share feedback, trade notes on +their integrations, and stay up to date on the latest Turnkey features and +updates. + + + The support chat and [help@turnkey.com](mailto:help@turnkey.com) are the + primary channels for technical and integration questions, and requests there + are tracked as conversations you can pick back up. Start with the chat widget + in the Turnkey dashboard or send us an email for anything involving your + organization, an error you are hitting, or account details. + + +## Social + +Turnkey posts product updates and announcements on +[X](https://x.com/turnkeyhq/). You can also reach out there for quick, general +questions, though the support chat and email are the right channels for anything +involving your organization or account details. + +## Service status + +Critical incidents and degraded service are reported at +[turnkey-status.com](https://www.turnkey-status.com/). Check it first if you are +seeing widespread failures or elevated latency, then reach out through the +support chat or [help@turnkey.com](mailto:help@turnkey.com) with the details +below. + +## What to include in a support request + +The more of this you can share up front, the faster we can diagnose the issue: + +- Your **organization ID**, and the sub-organization ID if the issue involves + one +- The **activity ID** or **activity type** involved +- The **exact error message**, including the error ID when one is present +- The **SDK and version** or the raw request you sent, with API keys, private + keys, and other secrets removed +- **Timestamps** with a timezone, and how often the issue reproduces +- What you expected to happen versus what happened + + + Never share API private keys, wallet private keys, recovery bundles, seed + phrases, or session credentials in a support request. Turnkey will never ask + for them. + + +## Before you reach out + +Many questions are answered in the docs: + +- [FAQ](/reference/faq) covers common questions about testing, billing, + supported chains, and data policies. +- [API error reference](/api-reference/overview/errors) explains specific error + messages and how to resolve them. +- [SDK reference](/sdks/introduction) and the + [example apps](https://github.com/tkhq/sdk/tree/main/examples) in the Turnkey + SDK repository include working integrations you can compare against. +