Support and contact

Contact

You can reach us via email or Discord. If you already know where you want to go, you will find the quickest entry points for support, downloads, and help articles below.

Email support Open Discord

Discord

For quick questions, community exchange, and direct onboarding with StreamWizard.

Join the official StreamWizard server and head straight to the right channel.

Open Discord

Direct entry points

If you do not want to write right away, here are the most important public areas in the same visual language.

Open FAQ Downloads Sign in

What we can help you with

Through this contact page you can reach StreamWizard for technical and organizational questions about OBSBot, giveaway system, and the related platform features. This includes help with downloads, license activation, Discord setup, Twitch integration, update questions, and general issues when starting or operating the bots.

  • OBSBot support for setup, OBS WebSocket, media source, playlist, and ongoing 24/7 operation.
  • Giveaway-System help for giveaways, community prizes, drawings, permissions, and unlocks depending on your license model.
  • Support with API keys, protected downloads, login, dashboard access, and questions about Premium, VIP, or admin unlocks.

What a good support request should include

The more precise your request is, the faster the problem can be narrowed down. If you contact us by email, concrete details about your system, bot type, error message, and the last step before the issue are especially helpful. Discord is ideal for quick follow-up questions or orientation, while email is usually the better channel for technical details.

  • Ideally state right away whether the issue is about OBSBot, giveaway system, downloads, license access, Discord, or Twitch.
  • If possible, include screenshots, log excerpts, or the exact error message so we do not have to ask for the basics first.
  • Briefly describe what already works, where it fails, and what you did immediately before that. This saves time during setup, updates, and troubleshooting.

When FAQ, downloads, or Discord are the better first stop

Not every question needs a support ticket right away. Many common topics can already be classified through the public StreamWizard areas: the FAQ explains product roles and core concepts, the downloads page guides you through login, dashboard, and installation, and Discord helps with quick orientation when it is not yet clear whether the issue is access, setup, or concrete troubleshooting.

  • The FAQ is the best starting point if you first want to understand how OBSBot, giveaway system, license models, and the general StreamWizard workflow fit together.
  • The download and installation pages are the right place if you already have access and want to know which files, steps, and unlocks are relevant for your account.
  • Discord works well for short questions before opening a full support case, for example when you first want to clarify whether your topic is mainly about account access, setup, bot behavior, or product scope.

How support at StreamWizard usually works

Support requests are usually sorted first by whether they concern OBSBot, giveaway system, or platform access such as login, licensing, dashboard, and protected downloads. For OBSBot topics, the focus is often on setup, OBS WebSocket, scenes, media sources, playlist rotation, Twitch or Kick integration, and stability during 24/7 operation. For giveaway system questions, the focus is more on giveaways, community prizes, claims, permissions, and the Discord-backed workflows around winners and unlocks.

  • Simple access, download, or licensing questions can usually be mapped directly to an account, a plan, or a missing unlock step.
  • For technical issues, details about the operating system, OBS version, bot type, error message, and the last executed step help us avoid troubleshooting in the abstract.
  • For security reasons, you should not send passwords, full secrets, or private credentials in plain text. For diagnosis, the relevant error message, screenshots, and non-sensitive log excerpts are usually sufficient.