> For the complete documentation index, see [llms.txt](https://alphabot-docs.gitbook.io/alphabot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alphabot-docs.gitbook.io/alphabot/use-cases/alphabot-use-cases/using-raffles-in-spaces-broadcasts-and-streams.md).

# Using Raffles in Spaces, Broadcasts & Streams

## Requirements

* In order to create a raffle on Alphabot, you'll need a "team" on our platform. Here's how to set up a team for your brand, community, or company: [Setting Up Your Team](/alphabot/for-teams/setting-up-your-team.md)
* Your team needs an active subscription to access all unlimited features (starting at $40/month) - here's how to get it: [How To Get A Subscription](/alphabot/for-teams/subscription/how-to-get-a-subscription.md).
* Something to give away, for example: a whitelist spot for an upcoming NFT project, a token allocation, an NFT, a physical item, or anything else that your viewers may be interested in.

## Creating the raffle

* Navigate to the "create raffle" page: <https://www.alphabot.app/new>
* Fill in a name for the raffle.
* In case you're giving away an on-chain reward, change the "blockchain" field if needed (default is Ethereum).
* Select a desired end date/time. The start date/time defaults to now.&#x20;
* In the case of a reward that's tied to a project, token, or brand, you can search for it in the "project data source" field. This will tie the raffle and it's winners to that project, and automatically notify winners in case of a mint date or TGE.

<figure><img src="/files/BK45vJ91yjjXLk8ERfiZ" alt=""><figcaption></figcaption></figure>

## Enabling entry requirements

* If you're giving away an on-chain reward, select the "Connect Wallet" requirement so that you collect wallet addresses from all entrants.
* The easiest way to limit entrants to your viewers/listeners is to enable the "password protected" requirement. This requires all entrants to fill in a password that you set.
* You're able to add any other entry requirements that you'd like, such as joining your Discord/Telegram, following your twitter account, or engaging with a specific tweet.

<figure><img src="/files/hj6S4l5PoPHv9oIe0uQo" alt=""><figcaption></figcaption></figure>

## You're all set!&#x20;

Click "Save & View" to publish the raffle on our platform. The raffle can now easily be **shared using the link** and is publicly accessible to everyone.&#x20;

For next steps, such as how to access entries data or winners, check out:

* [Exporting Winners Data](/alphabot/raffles/exporting-winners-data.md)
* In case of any questions, we have 24/7 support on [our website](https://www.alphabot.app/) using the live chat in the bottom right of your window.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://alphabot-docs.gitbook.io/alphabot/use-cases/alphabot-use-cases/using-raffles-in-spaces-broadcasts-and-streams.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
