Skip to main content

How to add a support widget to your crypto app

Templ
Templ
Notes from the Templ team

The install prompt asks your coding tool to add the widget to your app. Review the files before accepting the change.

Prefer a manual install? Follow the manual quickstart. It provides the same complete support module without an AI coding tool.

Give the tool your app​

Open the app with your manager's EVM wallet. Sign in to a workspace or create one. Copy its install prompt from Widget into your coding tool inside your app's code.

The prompt asks the tool to use the widget reference and inspect your app's wallet connection. It asks for a small adapter that opens Help.

The tool should reuse your wallet connection. It should save failure details for the user to review before sharing.

Review the files​

Check the widget loader, wallet adapter and Help button the tool adds. The failure handler should save current details with captureSupportFailure. The Help button calls openSupport.

The app can pass the action, network, visible error and public transaction hash. The user sees the details and chooses what to share.

A failed action should keep its normal result and error handling. Opening Help should not repeat the transaction.

Review the wallet adapter's sign-in message and selected network. Ethereum and Base cover the EVM pilot path. Solana follows its separate release checks.

Test the site​

Use your workspace's install prompt.

The widget works on public HTTPS websites without website approval. Add a test account before sending the test question.

Load the page, open Help and send a question. Read the case in your team's inbox. Reply and check that the user sees the answer.

Use Check my install In testing to review the install checks.

Sample setupRun dateLocal checks
Next.js, wagmi and RainbowKit2026-09-29Type check, build and integration tests

These local runs check sample installs. They do not prove hosted availability or the current prompt's full acceptance checks.

Other stacks: not tested yet.

Remove the widget​

Remove the Help adapter and the widget loader. Remove the call from each failure handler.

Stop loading the hosted widget module. Check the page and its failure paths after the change.

Never share a private key or recovery phrase.

In testing means the feature is built and not yet open to every workspace. See availability.

Sources​