Support

Use support when the product behavior does not match the documented flow and you cannot resolve it with Troubleshooting.

When to Ask for Support

Support is appropriate when:

• the product flow does not match the documentation
• the same error repeats after you already checked the basic causes
• the campaign or token state looks inconsistent
• you are blocked from a critical step such as funding, launching, or claiming

Useful Context to Share

• The product flow you used
• The action that failed
• The visible error message
• The network and wallet context
• The transaction signature or explorer link, if the action created a transaction
• A screenshot, if the issue involves a UI state or wallet prompt

A Good Support Report Includes

1. The page you were on when the issue happened
2. The exact button or action you clicked
3. The token mint or campaign address involved
4. The error text shown in the UI or wallet
5. The transaction signature or explorer link, if a transaction was created
6. A screenshot if the issue involves UI state, claim status, or a wallet prompt
7. Whether the issue happened once or every time

Contact Support

• Join the Bonkit Discord  for product support and issue reports.
• Join the Bonkit Telegram  for updates and support.
• For CLI issues, include the package version (npm view @bonkit/airdrop-studio version) and the relevant .bonkit/activity-log.json excerpt.
• For SDK issues, include the package version and a minimal reproduction snippet.

Before You Send the Report

• check Troubleshooting once
• confirm you are on the correct wallet, network, and RPC endpoint
• note whether the issue is about the CLI studio, the generated claim site, or the SDK
• collect the transaction signature or explorer link if the issue happened after signing
• capture a screenshot or terminal log excerpt if the issue involves UI or CLI output