> For the complete documentation index, see [llms.txt](https://help.rafflelink.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rafflelink.com.au/getting-started/registration-guide/raffle-structure-step-7/how-to-register-a-hybrid-raffle.md).

# How To Register A Hybrid Raffle

### Overview

This guide explains how to effectively combine traditional paper ticket sales with RaffleLink's online system. Learn how to set up, manage, and conduct draws for hybrid raffles.

### Initial Setup

#### Registration Process

1. During raffle registration, indicate that you will be using paper tickets by selecting "Paper & Online Tickets" for Raffle Type
   * Note: Selecting a Hybrid Raffle Type (Paper + Online) will disable our online draw functionality and prompt a manual draw
2. Enter the total number of tickets (paper + online) in the "Total Number of Tickets on Sale" field

![](https://s3-ap-southeast-2.amazonaws.com/aus-cdn.freshdesk.com/data/helpdesk/attachments/production/51188388646/original/GRuzY17eT7zgSB4fvp95f06RsVFBTPWaBw.png?1729677846)

#### Tip:

* Assign sequential numbering: online tickets first, paper tickets last<br>
* *Example setup*:
  * Online tickets: #1 - #1000
  * Paper tickets: #1001 - #2000

Why? So you can start paper ticket sales from the end of your sequence which allows you to add more online tickets if needed

### Managing Paper Ticket Sales and Payments

#### Payment Collection

* RaffleLink does not process payments for paper tickets
* You will need to manage cash and other payment methods independently
* Consider these best practices for payment handling:
  1. Use a dedicated cash box or point of sale system
  2. Issue receipts for all transactions
  3. Maintain a separate sales log with:
     * Date of sale
     * Ticket numbers sold
     * Payment method
     * Amount received
     * Seller's initials
  4. Reconcile payments daily if possible


---

# 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://help.rafflelink.com.au/getting-started/registration-guide/raffle-structure-step-7/how-to-register-a-hybrid-raffle.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.