Ask for Help

Need help or want to connect? We're here for you.

Contact Kastle Support

If you run into issues or have technical questions, the fastest way to get help is through our community channels or GitHub. Our team and community members are active and ready to assist.

Telegram Support Group: t.me/kastlewallet ↗ — Join our public chat to ask questions, report bugs, or get guidance from other Kastlers and the team.
GitHub Issues: github.com/forbole/kastle/issues ↗ — For bug reports and feature requests, please open a GitHub issue so our dev team can track and address it.
X (formerly Twitter): @KastleWallet ↗ — Follow us for announcements, tips, and support DMs.
Email Us: Reach out to our team through email ↗ or in-app chat. We explain what info to include so we can help you faster.

We currently do not offer email or ticket-based support, but the channels above are monitored and responsive.

How to Get Faster Help

When asking for help, please include:

Your device and OS (e.g. iPhone 14, iOS 17.5)
Kastle version number (e.g. 1.0.5 from App Store)
Screenshots or error messages (if any)
A brief description of what you were doing before the issue occurred

Feedback and Suggestions

We value your ideas! To suggest features or improvements, feel free to message us on Telegram ↗ or open a GitHub ↗ discussion. We regularly review community input to help shape future updates.

Ask for Help

Need help or want to connect? We're here for you.

Contact Kastle Support

If you run into issues or have technical questions, the fastest way to get help is through our community channels or GitHub. Our team and community members are active and ready to assist.

Telegram Support Group: t.me/kastlewallet ↗ — Join our public chat to ask questions, report bugs, or get guidance from other Kastlers and the team.
GitHub Issues: github.com/forbole/kastle/issues ↗ — For bug reports and feature requests, please open a GitHub issue so our dev team can track and address it.
X (formerly Twitter): @KastleWallet ↗ — Follow us for announcements, tips, and support DMs.
Email Us: Reach out to our team through email ↗ or in-app chat. We explain what info to include so we can help you faster.

We currently do not offer email or ticket-based support, but the channels above are monitored and responsive.

How to Get Faster Help

When asking for help, please include:

Your device and OS (e.g. iPhone 14, iOS 17.5)
Kastle version number (e.g. 1.0.5 from App Store)
Screenshots or error messages (if any)
A brief description of what you were doing before the issue occurred

Feedback and Suggestions

We value your ideas! To suggest features or improvements, feel free to message us on Telegram ↗ or open a GitHub ↗ discussion. We regularly review community input to help shape future updates.

Ask for Help

Need help or want to connect? We're here for you.

Contact Kastle Support

If you run into issues or have technical questions, the fastest way to get help is through our community channels or GitHub. Our team and community members are active and ready to assist.

Telegram Support Group: t.me/kastlewallet ↗ — Join our public chat to ask questions, report bugs, or get guidance from other Kastlers and the team.
GitHub Issues: github.com/forbole/kastle/issues ↗ — For bug reports and feature requests, please open a GitHub issue so our dev team can track and address it.
X (formerly Twitter): @KastleWallet ↗ — Follow us for announcements, tips, and support DMs.
Email Us: Reach out to our team through email ↗ or in-app chat. We explain what info to include so we can help you faster.

We currently do not offer email or ticket-based support, but the channels above are monitored and responsive.

How to Get Faster Help

When asking for help, please include:

Your device and OS (e.g. iPhone 14, iOS 17.5)
Kastle version number (e.g. 1.0.5 from App Store)
Screenshots or error messages (if any)
A brief description of what you were doing before the issue occurred

Feedback and Suggestions

We value your ideas! To suggest features or improvements, feel free to message us on Telegram ↗ or open a GitHub ↗ discussion. We regularly review community input to help shape future updates.