create event event visibility ticket types ticket sales RSVP share event Start with an event: the page people visit for the date, location and event details. Choose ticketed entry or RSVP, then decide how people can register.

## Start with your usual ticket provider {#start-with-your-usual-ticket-provider}

BASH helps you manage access for your community alongside your normal ticketing setup. Connect a supported ticket provider first. If your provider is not listed, contact support to request an integration and ask whether one is planned.

Ticketing and audience sync are separate choices. Connecting a provider for an event does not by itself make every ticket holder an email or WhatsApp subscriber. To add provider ticket-holder history to **Audience**, follow [Sync a ticket provider audience](/help/import-and-sync-your-audience#sync-a-ticket-provider-audience).

For example, you can keep an event with its connected provider while setting up a presale or giving a member group access to a specific sale, without moving the whole event's ticketing to BASH.

If connecting your provider is not possible, you can sell your community tickets directly through BASH. For those tickets, you can check people in through BASH or export the ticket QR codes for a compatible scanner. See [Plan check-in for community tickets](/help/sell-directly-through-bash#plan-how-people-will-enter) and [Choose your ticketing setup](/help/sell-tickets).

## How events and tickets fit together {#how-events-and-tickets-fit-together}

| Part | What it controls | Example |
| --- | --- | --- |
| **Event** | The event page, date, location, visibility and entry method. | A recurring event with its own date, location and entry method. |
| **Ticket type** | An admission option with its own price, stock and settings. Find these under **Tickets**. | Free admission and Workshop admission. |
| **Ticket sale** | Which tickets an audience can obtain and when. A ticket can appear in several sales, with shared stock. | Regular tickets on the event page, or a member sale for an existing member group. |

Use **Tickets** for free or paid ticketed admission. Choose **RSVP** when people should respond to an invitation without obtaining a ticket. An RSVP event does not need a ticket catalogue or ticket sale.

Event visibility and sale access are separate decisions. Making an event public does not give everyone access to a members-only sale. Sharing a link does not remove a sale's access rules.

## Enter the event details {#enter-the-event-details}

You need permission to create events for your organisation. Have the event name, date and location ready.

1. Open your organisation dashboard and select **Create** → **Event**.
2. In **Event details**, enter the event title and description.
3. Set **Location**, **Date** and the start time. Check the time zone beside **Date**. Use **Add end date** if you want to show an end time.

[![An unsaved event with its title, visibility, location and date fields](/images/help/proposals/events/create-details.png "Enter the event details and check the date and time before continuing.")](/images/help/proposals/events/create-details.png)

4. Set **Event visibility** to **Public** or **Anyone with the link**. Use the link option for an unlisted event you plan to share directly.
5. Add event media or adjust **Page appearance** if needed, then select **Next**.

[![The Event visibility menu with Public and Anyone with the link](/images/help/proposals/events/create-visibility.png "Choose event visibility independently of who can access individual ticket sales.")](/images/help/proposals/events/create-visibility.png)

## Choose how people enter {#choose-how-people-enter}

1. Open the **Entry: Tickets** menu and choose **Tickets** or **RSVP type event**.
2. For ticketed entry, check the ticket provider and select **Add tickets** to configure admission. If the tickets are not ready, select **Set up tickets later** to continue without them.
3. For RSVP, review the registration settings, then select **Next**.

[![The unsaved event Entry menu offering Tickets and RSVP](/images/help/proposals/events/create-entry-modes.png "Choose ticketed admission or RSVP. You can also continue a ticketed event with Set up tickets later.")](/images/help/proposals/events/create-entry-modes.png)

If you defer ticket setup, attendees cannot obtain tickets until you configure them and make them available in a sale. Connect your supported provider first. If you need the community-ticket fallback, follow [Sell tickets directly through BASH](/help/sell-directly-through-bash) for its ticket fields and saving steps.

## Review and create the event {#review-and-create-the-event}

1. In **Review**, check the title, date, location, visibility and entry settings. Select **Change** beside a row that needs correcting.
2. Check **Regular tickets**. In this example, **Set up tickets later** means the event has no tickets ready to offer.
3. When the details are ready to go live, select **Create event**.
4. Check the saved event's **Overview** and open its attendee page to review what people can see.

[![An unsaved event Review with Set up tickets later and Create event](/images/help/proposals/events/create-review.png "This is the final review before creation, with ticket setup deferred. The example has not been created.")](/images/help/proposals/events/create-review.png)

## Share the saved event {#share-the-saved-event}

1. Open the saved event's **Overview** and select **Share**.
2. Select **Copy event page link** to copy the event link for sharing.
3. Check the page and its ticket availability before sending the link to attendees.

[![An existing event with the Share menu open](/images/help/proposals/events/event-share-menu.png "Share offers Copy event page link and Share in post. This is an existing saved event.")](/images/help/proposals/events/event-share-menu.png)

To announce it in a post, select **Share in post** and review the post's content, audience and delivery settings before publishing. See [Publish a post](/help/publish-a-post).

## If people cannot get tickets {#if-people-cannot-get-tickets}

1. Open **Tickets** and check that the intended ticket belongs to a sale.
2. Open **Ticket sales** and check that sale's dates, stock and access rules.
3. If you used **Set up tickets later**, complete ticket setup before sharing a ticket purchase invitation.

For an event or control you cannot find, check the selected organisation and ask its administrator to confirm your access. If the problem remains, use **Need more help? Message support** below this article and include the event name and the exact message shown, without private ticket links or attendee details.

Understand events, ticket types and ticket sales, then create an event and share its page.

Events and ticket sales

event ticket sales selling directly through bash ticket shop weeztix paylogic price Connect your usual ticket provider to BASH first. The provider choices currently shown are **Weeztix (link your Weeztix event)** and **Paylogic (link your Paylogic event)**. Saving a provider choice is separate from connecting its account and selecting the event.

For example, you can keep an event with its connected provider while using BASH to manage a presale or community access.

If your provider is not listed, contact support to request an integration and ask whether one is planned. When a provider connection is not possible, **Sell directly through BASH** is the fallback for your community tickets. You can check people in through BASH or export the ticket QR codes for a compatible scanner. [Plan check-in for community tickets](/help/sell-directly-through-bash#plan-how-people-will-enter).

## Before you start {#before-you-start}

You need permission to manage the event’s ticketing. An **Entry manager** can check people in but cannot set up ticket sales. If another organisation manages ticketing, follow the event’s ticketing message.

## Open your event’s tickets {#open-your-event-s-tickets}

1. Open the correct organisation in your dashboard.
2. Open **Events** and select the event.
3. Select **Tickets** to open the event’s ticket catalogue.

The empty catalogue shows **No tickets yet**. The **Set up ticketing** action opens the provider choice.

[![An empty Tickets catalogue with the Set up ticketing action](/images/help/screenshots/sell-tickets/ticket-catalogue.png "Set up ticketing is available when ticketing has not been configured.")](/images/help/screenshots/sell-tickets/ticket-catalogue.png)

## Choose your ticketing setup {#choose-your-ticketing-setup}

1. Select **Set up ticketing**.
2. Open **Select provider**, or the button showing the current provider choice.

[![The ticketing setup dialog with BASH, Weeztix and Paylogic options](/images/help/screenshots/sell-tickets/ticket-setup.png "Choose where tickets for this event will be managed.")](/images/help/screenshots/sell-tickets/ticket-setup.png)

3. Choose **Sell directly through BASH**, **Weeztix (link your Weeztix event)** or **Paylogic (link your Paylogic event)**.

### Link a provider event {#link-a-provider-event}

1. If the account is not connected, select **Connect Weeztix** or **Connect Paylogic** and complete the connection in the provider window. To connect or manage the account separately, open **Settings → Integrations** and choose the provider.
2. Select the matching provider event. Check that it is the intended event in the provider account; do not rely on its name alone.
3. Follow the remaining setup messages. If **Save** is disabled, the provider choice is not ready to save.
4. Select **Save** when the setup is ready.

Connection, event selection and sales readiness are separate stages. Check sales readiness before sharing a sales link.

Connecting a ticket provider makes its ticketing data available. Adding its audience has separate choices. See [Sync a ticket provider audience](/help/import-and-sync-your-audience#sync-a-ticket-provider-audience).

Provider account connection requires the external provider’s setup. If you cannot complete it:

1. Select **Cancel** to leave the event’s saved ticketing unchanged.
2. Contact support with the provider and the message shown, using the support steps below.

### Sell directly through BASH {#sell-directly-through-bash}

1. Select **Save** in the provider dialog.
2. Continue with [adding tickets in BASH](/help/sell-directly-through-bash#add-your-tickets).

If you made the ticketing choice while creating an event, it is part of that event’s working copy:

1. Complete **Review**.
2. Select **Create event** to save the event and its tickets.

For the full ticket procedure and the difference between creating a ticket and offering it for sale, see [Sell tickets directly through BASH](/help/sell-directly-through-bash).

## Check the saved result and attendee page {#check-the-saved-result-and-attendee-page}

When selling directly through BASH, **Tickets** lists the saved tickets, their status, stock and the sales that include them. A ticket with **Add to sale** is not yet included in a sale. See [Add a ticket to regular sales](/help/sell-directly-through-bash#offer-a-ticket-on-the-event-page).

[![A configured Tickets catalogue showing ticket stock and the In sale column](/images/help/screenshots/ticket-catalogue/configured-catalogue.png "The In sale column shows where each saved ticket is offered.")](/images/help/screenshots/ticket-catalogue/configured-catalogue.png)

1. Open the event’s **Overview**.

[![The organiser’s event Overview with Share and the Open icon beside the event name](/images/help/screenshots/sell-tickets/ticketed-event-overview.png "Open leads to the attendee page. Share contains the event page link options, including **Share in post**.")](/images/help/screenshots/sell-tickets/ticketed-event-overview.png)

2. Select **Open**, shown as an arrow leaving a square, to inspect the attendee page.
3. If you already hold a ticket, select **Get more tickets**.
4. Check the event name, date, time and ticket availability.

[![An existing attendee’s event page with Get more tickets expanded, a free ticket and a €10 workshop ticket, both almost sold out](/images/help/screenshots/sell-tickets/attendee-ticket-availability.png "The event is almost sold out. Both ticket options have quantity controls; neither is selected in this view.")](/images/help/screenshots/sell-tickets/attendee-ticket-availability.png)

5. To copy the event page link, select **Share**, then **Copy event page link**.
6. Check that this is the type of link you intend to share. A personal or restricted sale link can grant different access from the event page link.

### Check payout setup {#check-payout-setup}

For paid tickets, resolve payout setup before charging attendees:

1. Open **Settings** → **Ticketing** → **Sell directly through BASH**.
2. Inspect the payout status and follow any setup instructions.
3. Review the current fee information for your organisation and the amount shown in checkout.

## If tickets are unavailable {#if-tickets-are-unavailable}

Check the following:

- The ticket has been added to the intended sale.
- The sale dates allow purchases.
- Stock remains.
- The visitor meets any access requirement.

A ticket’s **Open** status in the catalogue does not by itself mean it has been added to a sale.

Your ticketing choice can become fixed after tickets are added or sold. If BASH says it can no longer be changed, contact support before moving ticketing. Connected-provider tickets use that provider’s check-in system.

If you cannot continue:

1. Select **Need more help? Message support** below this article.
2. Include the organisation, event, provider, step reached and exact message.
3. Select **Open support message**, then review and send the draft.

Keep payment details and personal access links private.

Connect your ticket provider, or use direct BASH ticketing for community tickets when a connection is not possible.

Start selling tickets for an event

sell directly through bash event ticket sales free tickets paid tickets ticket types shops Connect your usual ticket provider to BASH first where it is supported. If your provider is not listed, contact support to request an integration and ask about the available route.

Selling directly through BASH is the fallback for the tickets you want to offer your community when a provider connection is not possible. For example, you could offer a community ticket allocation this way while keeping the wider event ticketing with your usual provider.

## Plan how people will enter {#plan-how-people-will-enter}

Before you open sales, choose how you’ll check in people with BASH-issued tickets.

- [Check in directly through BASH](/help/check-in-attendees). Scan tickets with the BASH mobile app or check people in manually in the dashboard.
- [Export ticket QR codes](/help/export-ticket-qr-codes) if your external scanner can import the codes from a CSV file.

## How the tickets are made available {#how-the-tickets-are-made-available}

When selling directly through BASH, create tickets in the event’s **Tickets** catalogue, then add them to a sale so attendees can obtain them. Creating an unassigned ticket does not put it on the attendee page.

## Before you start {#before-you-start}

You need permission to manage the event’s ticketing and **Sell directly through BASH** selected in its ticketing setup. See [Choose your ticketing setup](/help/sell-tickets#choose-your-ticketing-setup).

Free tickets can be created before payouts are set up. If **Price** is disabled and **Add payout details to charge for tickets** appears, complete payout setup before charging attendees. That link opens **Settings** → **Ticketing** → **Sell directly through BASH**, where **Set up payouts** starts the payment-account setup.

## Add your tickets {#add-your-tickets}

1. Open the event and select **Tickets**.

[![The event Tickets catalogue with the New action and In sale column](/images/help/screenshots/ticket-catalogue/configured-catalogue.png "Use New to create a ticket; the catalogue also shows the sales using existing tickets.")](/images/help/screenshots/ticket-catalogue/configured-catalogue.png)

2. Select **New** to open **New ticket**.

[![The New ticket drawer with Ticket name, Price, Total stock and More settings](/images/help/screenshots/ticket-catalogue/new-ticket-editor.png "Price is disabled in this example because payout details have not been added.")](/images/help/screenshots/ticket-catalogue/new-ticket-editor.png)

3. Enter **Ticket name** and **Total stock**. Stock is shared across all sales that use this ticket.
4. Set **Price** if paid tickets are available. Leave it at zero for a free ticket.
5. Open **More settings** if you need **Ticket dates**, **Ticket-specific questions**, **Require approval**, **Only verified attendees**, **Ticket type**, **Group tickets** or **Max. tickets per person**.

6. Select **Create ticket**.

The drawer closes and the ticket appears in the catalogue with its price and stock. If it shows **Add to sale**, it has been saved without a sale. You can find tickets without a sale under **Unassigned**.

### Add tickets while creating an event {#add-tickets-while-creating-an-event}

When adding a ticket during event creation, the drawer’s action is **Add ticket** and the message says **Created when saving the event.**

1. Select **Add ticket** to add it to the event’s working copy.
2. Continue to **Sales dates** and check **Opens**. If it is **On save**, regular sales open when the event is saved.
3. Continue to **Review** and check the event and tickets.
4. Select **Create event** to save them.

## Offer a ticket on the event page {#offer-a-ticket-on-the-event-page}

Adding a ticket to **Regular tickets** offers it on the event page when its sale dates allow purchases.

1. In **Tickets**, select **Add to sale** beside the unassigned ticket.
2. Open **Sale** and choose **Regular tickets**.
3. Review the list, then select **Add to regular tickets**.
4. Read the confirmation, then select **Save and add**.

The ticket’s **In sale** column now shows **Regular tickets**.

### Check the attendee page {#check-the-attendee-page}

1. Open the event’s **Overview** and select **Open**, shown as an arrow leaving a square.
2. If you already hold a ticket, select **Get more tickets**.
3. Check the intended ticket and its availability on the attendee page.

[![An existing attendee’s event page with Get more tickets expanded, a free ticket and a €10 workshop ticket, both almost sold out](/images/help/screenshots/sell-tickets/attendee-ticket-availability.png "The event is almost sold out. Both ticket options have quantity controls; neither is selected in this view.")](/images/help/screenshots/sell-tickets/attendee-ticket-availability.png)

For other audiences, use the event’s **Ticket sales** page. See [Set up a presale](/help/set-up-a-presale) or [Create a custom ticket sale](/help/create-private-ticket-access). Tickets can be used in several sales, so inspect the **In sale** column before changing a shared ticket’s name, price or stock.

## Ask a question for one ticket type {#ask-a-question-for-one-ticket-type}

Use **Ticket-specific questions** when only people obtaining a particular ticket should answer, such as a question for Workshop admission. These questions belong to the ticket type, so check which sales use that ticket before changing them. They are separate from general event registration and personal-information questions.

### Open the ticket question settings {#open-the-ticket-question-settings}

1. Open the event's **Tickets** catalogue.
2. Open the actions menu beside the intended ticket and select **Edit ticket**.
3. Expand **More settings**, then **Ticket-specific questions** and select **Add question**.

[![The ticket catalogue with Free admission and Workshop admission](/images/help/proposals/events/ticket-settings.png "Choose the ticket type that should ask the question, then use its actions menu to open Edit ticket.")](/images/help/proposals/events/ticket-settings.png)

### Write and add the question {#write-and-add-the-question}

1. Enter the question, for example, “What would you like to learn at the workshop?”
2. Choose **Question type**. Use **Text** for a written answer, or select the appropriate answer format and complete any options it requires.
3. Turn **Required** on if an answer is necessary; leave it off for an optional question.
4. Select **Add question** to put it into the ticket's working copy.

[![An unsaved optional Text question for Workshop admission](/images/help/proposals/events/ticket-question-filled.png "Choose the answer format and whether the question is required. Adding the question is separate from saving the ticket.")](/images/help/proposals/events/ticket-question-filled.png)

### Save and check the ticket {#save-and-check-the-ticket}

1. Check that the question appears under **Ticket-specific questions**. Open it again if you need to correct it before saving.
2. Select **Save changes** in **Edit ticket** to persist the ticket changes.
3. Reopen the same ticket and check that its question is still listed.

[![The new question listed in the unsaved Workshop admission editor above Save changes](/images/help/proposals/events/ticket-question-staged.png "The question is staged in this example. Save changes has not been selected.")](/images/help/proposals/events/ticket-question-staged.png)

To abandon the ticket changes, select **Cancel** and follow any discard confirmation. If the question text or answer format is locked when editing an existing question, do not assume it can be rewritten; check the available controls before changing the ticket.

### Export answers to a ticket question {#export-answers-to-a-ticket-question}

1. Open a ticket question and select **Export answers** in the answers list.
2. Select **Export as CSV** or **Export as Excel** to download the answers.

## Export attendee data for an agreed import {#export-attendee-data-for-an-agreed-import}

If your provider has asked for a list of attendees, use the **People** export. For scannable codes, [export ticket QR codes](/help/export-ticket-qr-codes).

1. Open the event’s **People** page. Check that the list and filters cover the people you want to export.
2. Open **More options** and select **Export as CSV** or **Export as Excel**.

[![The event People menu showing CSV and Excel options and a separate QR code export](/images/help/screenshots/ticket-qr-export/event-people-export-menu.png "Choose Export as CSV or Export as Excel to download attendee data.")](/images/help/screenshots/ticket-qr-export/event-people-export-menu.png)

3. Check the downloaded file against your provider’s requirements and follow its import process.

The file contains attendee data. Keep it private and share it only with the team handling the import.

## Review what attendees pay {#review-what-attendees-pay}

1. When payout setup is complete, open **Settings** → **Ticketing** → **Sell directly through BASH** and check the fee information. Fee controls depend on your organisation’s payment setup.
2. Open checkout for the intended sale and check the amount shown.
3. To investigate an amount, compare the actual order and invoice.

For the default VAT setting for new tickets:

1. Open **Settings** → **Ticketing** → **Ticket VAT**.
2. Check the setting and ask your accountant to confirm the rate that applies. See [Check VAT and ticket invoices](/help/ticket-vat).

## If the ticket does not appear for attendees {#if-the-ticket-does-not-appear-for-attendees}

1. Check **In sale**.
2. If it shows **Add to sale**, follow the regular-sales procedure above.
3. If it names a sale, check that sale’s opening and closing dates, ticket stock and access requirements.

If **Price** is disabled:

1. Select **Add payout details to charge for tickets**.
2. Resolve the setup status before changing the price.

If saving shows an error, keep the entered details and read the message before trying again.

If you cannot continue:

1. Select **Need more help? Message support** below this article.
2. Include the organisation, event, ticket name, step reached and exact message.
3. Select **Open support message**, then review and send the draft.

Do not include payment credentials or private ticket links.

For entry management after sales, see [Check in attendees at your event](/help/check-in-attendees).

Offer community tickets when you cannot connect your provider, and plan how attendees will enter.

Sell tickets directly through BASH

scan tickets qr code guest list check in entry manager door hosts When selling directly through BASH, check ticket holders in manually from the event’s **People** page. To scan QR codes, use the BASH mobile app. The browser’s **Scanner** action shows you how to download the app.

If your door team uses a compatible external scanner, [export the ticket QR codes](/help/export-ticket-qr-codes).

## Before you start {#before-you-start}

You need access to the event’s attendees and check-in controls. An **Entry manager** has access to event attendees, answers and check-in, without event editing or the full organiser dashboard.

These controls apply when you are selling directly through BASH. For tickets issued by your connected provider, use that provider’s check-in system. An RSVP event has no ticket QR codes to scan.

## Check in manually {#check-in-manually}

1. Open the correct organisation and event in your dashboard.
2. Select **People**.
3. Open **More options** beside the list controls.

[![The event People menu with Start check-in](/images/help/screenshots/ticket-qr-export/event-people-export-menu.png "Open More options beside the list controls to find Start check-in.")](/images/help/screenshots/ticket-qr-export/event-people-export-menu.png)

4. Select **Start check-in**. Entry managers open in check-in mode.

[![The People list in check-in mode with Search list, Done and checked-in ticket counts](/images/help/screenshots/check-in-entry/check-in-mode.png "Check-in mode shows each person’s checked-in and total ticket counts.")](/images/help/screenshots/check-in-entry/check-in-mode.png)

5. Use **Search list** to find the attendee.
6. Check their name and ticket type before admitting them.
7. Select **Check-in** on the person’s row. The button also shows the checked-in and total ticket counts, for example **Check-in (0 / 1)**.

A successful update changes the button to **Checked-in**, for example **Checked-in (1 / 1)**. The person’s ticket summary also shows how many tickets are checked in. For several tickets, read both counts: **Checked-in (1 / 2)** means one ticket still needs check-in. The main button checks in all of that person’s available tickets sold directly through BASH for the event.

### Check in individual tickets {#check-in-individual-tickets}

For a person with several tickets:

1. Select the arrow beside the check-in button.

[![The individual ticket menu with two checked ticket choices and Save](/images/help/screenshots/check-in-entry/individual-check-in-tickets.png "Two ticket choices are already checked. This view has not changed the attendee’s check-in state.")](/images/help/screenshots/check-in-entry/individual-check-in-tickets.png)

2. Select the tickets to check in.
3. Select **Save**. Choosing boxes alone does not save the changes.
4. Check that the checked-in count matches the tickets you selected.

### Finish manual check-in {#finish-manual-check-in}

1. Select **Done** above the list.
2. Check that the normal **People** list is shown.

## Correct an accidental check-in {#correct-an-accidental-check-in}

For a person whose tickets are all checked in:

1. Select **Checked-in** to undo their check-in.
2. Check that the count returns to the intended state before continuing.

To correct only one ticket for a person with several tickets:

1. Select the arrow beside the check-in button.
2. Update the individual ticket choices.
3. Select **Save**.
4. Check that the count matches the intended state.

## Scan tickets with the app {#scan-tickets-with-the-app}

### Open the download guidance {#open-the-download-guidance}

1. Select **Scanner** on **People**. The **Check in attendees** guidance explains that scanning is available only in the app.

[![The Check in attendees dialog explaining that the scanner is available only in the app](/images/help/screenshots/check-in-entry/web-scanner-guidance.png "The browser opens download guidance. Ticket scanning takes place in the BASH app.")](/images/help/screenshots/check-in-entry/web-scanner-guidance.png)

2. Select **Download BASH** to open the app download route.

### Use the scanner on a phone {#use-the-scanner-on-a-phone}

1. Install the BASH app.
2. Sign in with an account that has access to the correct event.
3. Open the event’s scanner in the app.
4. Allow camera access when requested.
5. Read each scan result before admitting the attendee.

A browser window does not provide camera scanning.

If a scan is rejected:

1. Find the attendee in **People**.
2. Check that it is the correct event and ticket before using manual check-in.

Do not admit someone based only on a QR code image when the scan result indicates a problem.

## Give your door team access {#give-your-door-team-access}

You need permission to manage the organisation’s team. **Entry manager** is an organisation role, so check the organisation and intended access before inviting door staff.

1. Open **Settings**, then **Team & access**.
2. Select **Invite team members**.
3. In **Search or enter email**, find the person or enter their email address.
4. Open the role button, initially **Admin**, and choose **Entry manager**.
5. Review the people and role, then select **Invite** to send the invitation.

Before the event:

1. Ask the invitee to accept the invitation and sign in with that account.
2. Check their access on a door-team device before entry starts.

## If check-in controls are missing or a ticket will not scan {#if-check-in-controls-are-missing-or-a-ticket-will-not-scan}

- Check that you opened the correct organisation and event.
- In the normal **People** list, use **More options** → **Start check-in** to reveal the manual controls.
- Use the provider’s own scanner for tickets issued by your connected provider.
- Inspect the attendee’s ticket and current check-in state before making a manual correction.
- If **Start check-in** or the event is unavailable, ask the organisation manager to check your role and event access.

If you cannot resolve the issue:

1. Select **Need more help? Message support** below this article.
2. Include the organisation, event, device, step reached and exact error.
3. Select **Open support message**, then review and send the draft.

Keep QR codes and personal ticket links private.

Check in attendees when selling directly through BASH, and give your door team the right access.

Check in attendees at your event

QR codes barcodes ticket export external scanner check-in CSV If your scanner can import ticket codes from a CSV file, you can use it to check in people with BASH-issued tickets. You can also [check in attendees directly through BASH](/help/check-in-attendees).

## Download the ticket codes {#download-the-ticket-codes}

For a simpler check-in, close ticket sales first and export shortly before doors open.

You need permission to manage the event. Downloading locks ticket forwarding, cancellation by ticket holders and renaming until you unlock tickets.

1. Open your event and select **Tickets**.
2. Open **More options** and select **Export ticket QR codes**.

[![The Tickets menu with Export ticket QR codes](/images/help/screenshots/ticket-qr-export/tickets-export-menu.png "Open More options in Tickets to find Export ticket QR codes.")](/images/help/screenshots/ticket-qr-export/tickets-export-menu.png)

3. Select **Export QR codes** to download the full list as a CSV.

[![The export dialog with Customise columns, the lock notice and the Export QR codes button](/images/help/screenshots/ticket-qr-export/full-export-dialog.png "Select Export QR codes to download the CSV.")](/images/help/screenshots/ticket-qr-export/full-export-dialog.png)

4. Import the CSV into your scanner and check that it recognises the codes.

Keep the CSV private. Check-ins made with your external scanner stay in its system.

### Choose which columns to include {#choose-which-columns-to-include}

1. In the **Export ticket QR codes** dialog, open **Customise columns**.
2. Keep the columns your door team needs. **Code** is always included. **Ticket name** is selected by default, and you can also include **Name**, **Email** or **Phone**.
3. Select **Export QR codes** to download the CSV.

## Update your scanner list {#update-your-scanner-list}

If sales stay open or tickets are removed after you export, check the event banner for changes.

1. Select the action for new or removed tickets and confirm in the dialog. If both actions appear, download both files.
2. Add the new codes and delete the removed codes in your scanner.

## Unlock tickets {#unlock-tickets}

1. On **Tickets**, open **More options** and select **Unlock tickets**.
2. Select **Unlock**.

[![The Unlock tickets confirmation with the Unlock button](/images/help/screenshots/ticket-qr-export/unlock-dialog.png "Review which actions become available again, then select Unlock.")](/images/help/screenshots/ticket-qr-export/unlock-dialog.png)

Ticket holders can forward and cancel tickets again, and you can rename tickets. Update your scanner after making changes. Your next export locks tickets again.

## If you cannot export ticket QR codes {#if-you-cannot-export-ticket-qr-codes}

This option is for tickets issued directly through BASH. It is unavailable for connected-provider events and events that issue tickets using external codes.

1. Select **Need more help? Message support** below this article.
2. Include the event and the message you see. Keep ticket codes and attendee files out of the support message.
3. Select **Open support message**, then review and send the draft.

Download a CSV of your BASH-issued ticket codes and keep your scanner’s list up to date.

Export ticket QR codes for an external scanner

vat tax invoice service fees booking fees payout Find an original buyer’s ticket order and prepare its invoice in BASH. Ticket invoices, BASH service invoices and payout records describe different parts of a transaction; a payout alone does not provide the full sales and fee breakdown.

## Before you start {#before-you-start}

You need event-management access and must be a manager of the organisation receiving the payment to generate its ticket invoice.

When selling directly through BASH, ticket invoices are available for eligible completed paid orders processed with Stripe. Free, external-provider, unpaid or refunded orders can be ineligible. The order view explains why an invoice is unavailable. For Weeztix or Paylogic orders, use the provider’s invoice process.

## Check your organisation’s ticket VAT setting {#check-your-organisation-s-ticket-vat-setting}

1. Open the organisation’s **Settings**, then **Ticketing**.

[![Ticketing settings with Ticket defaults and the Ticket VAT row showing Not set](/images/help/screenshots/ticket-vat-settings/ticket-defaults.png "Ticket defaults show the current currency and VAT setting.")](/images/help/screenshots/ticket-vat-settings/ticket-defaults.png)

2. Under **Ticket defaults**, select **Ticket VAT**.
3. Check the percentage. This is the default for new tickets.

[![The Ticket VAT editor with a percentage field, Cancel and Save changes](/images/help/screenshots/ticket-vat-settings/ticket-vat-editor.png "Review the default VAT rate. This example is unchanged; Save changes has not been selected.")](/images/help/screenshots/ticket-vat-settings/ticket-vat-editor.png)

To leave the default unchanged:

1. Select **Cancel**.

To change the default:

1. Enter the rate you have confirmed.
2. Select **Save changes**.
3. Check the **Ticket VAT** row for the saved percentage.

The **Ticket VAT** row shows the saved percentage, or **Not set** if no default has been entered. Check the relevant order’s actual VAT details when preparing its invoice; do not assume a later default change describes an earlier purchase.

To check fee information:

1. Return to **Ticketing** and open **Sell directly through BASH** under **Ticket providers**.
2. Check the fee information and payment setup. The information and controls depend on that setup. If the page shows **Set up payouts**, payment-account setup is still required before accepting ticket payments.

The applicable VAT treatment depends on your organisation, event and the service being supplied. For Dutch sales, consult the [Belastingdienst’s VAT guidance](https://www.belastingdienst.nl/wps/wcm/connect/bldcontentnl/belastingdienst/zakelijk/btw/tarieven_en_vrijstellingen/) and ask your accountant to confirm the treatment. This article does not prescribe a VAT rate.

## Find an attendee’s ticket invoice {#find-an-attendee-s-ticket-invoice}

1. Open the event’s **People** page and search for the original buyer. The buyer may be different from the current ticket holder.
2. Select the person, then select **Tickets** in their details.

[![The person’s Tickets tab with Orders placed, order numbers and View order](/images/help/screenshots/ticket-vat-settings/buyer-orders.png "The paid status shown belongs to an example order and does not confirm a real payment.")](/images/help/screenshots/ticket-vat-settings/buyer-orders.png)

3. Under the relevant event’s **Orders placed**, locate the order number and select **View order**.

4. Check the order’s event, ticket lines and total, then select **Generate invoice**. If an invoice already exists, the action is **View invoice**.
5. Check **Invoice name (person or company)** and **Invoice email**, then complete **Street and house number**, **Postal code**, **City** and **Country**. **Address line 2 (optional)** and **VAT number (optional)** are available if needed.
6. If BASH asks for a missing **VAT rate (%)**, enter the rate used for that purchase for each affected line.

[![Unsaved billing form for an example €10 Workshop ticket, with fictional billing details, 21% VAT and Preview invoice](/images/help/screenshots/ticket-vat-settings/seeded-invoice-billing.png "This example uses fictional billing details and an illustrative 21% rate. Check the buyer’s actual details and the rate for their purchase before previewing.")](/images/help/screenshots/ticket-vat-settings/seeded-invoice-billing.png)

### Preview and generate the invoice {#preview-and-generate-the-invoice}

1. Select **Preview invoice**.
2. Check the billing details, issuer, line amounts, VAT and **Total paid**.

[![Preview for an example €10 Workshop ticket with fictional billing details, 21% VAT and Generate invoice](/images/help/screenshots/ticket-vat-settings/seeded-invoice-preview.png "This is an unissued example preview with fictional billing details and an illustrative rate. Generate invoice has not been selected; no actual payment or invoice delivery is shown.")](/images/help/screenshots/ticket-vat-settings/seeded-invoice-preview.png)

If any details need correction:

1. Select **Back**.
2. Correct the details.
3. Select **Preview invoice** again and check the updated preview.

When the preview is correct:

1. Select **Generate invoice**. This starts invoice creation; billing details become fixed once generation starts.

### Download or send a completed invoice {#download-or-send-a-completed-invoice}

When creation completes, use the invoice view to download the invoice:

1. Select **Download PDF** when the PDF is available.

To email the invoice:

1. Check the displayed recipient.
2. Select **Send invoice** to email the invoice to that recipient.

Creating an invoice and sending it are separate actions.

## If Generate invoice is missing {#if-generate-invoice-is-missing}

1. Read the reason in **View order**.
2. Confirm that you opened the original buyer’s order.
3. Check that your account can manage invoices for the organisation receiving payment.

Do not change an order’s payment or refund state to make it eligible.

If invoice generation reports a problem after starting:

1. Keep the saved billing details and follow the error shown.
2. If you are unsure whether creation completed, contact support before creating another invoice for the same purchase.

## Reconcile sales with payouts {#reconcile-sales-with-payouts}

- Compare the same organisation, currency and period across orders, service invoices and payout records.
- Review refunds and adjustments separately.
- Check each document’s issuer and amounts before using it for accounting.

For a missing invoice or discrepancy:

1. Select **Need more help? Message support** below this article.
2. Include the organisation, event, order number, step reached and error or amount in question.
3. Select **Open support message**, then review and send the draft.

Keep payment credentials and personal ticket links private.

Open the original buyer’s order, preview its invoice details, and check why an invoice may be unavailable.

Check VAT and ticket invoices

audience people communities memberships subscribers import contacts sync audience Brevo Mailchimp ticket providers Your audience brings together the people connected to your organisation. Use **Audience** to bring in existing contacts, keep connected sources updated, find someone, combine related event audiences or manage a group with ongoing member access. Start with the part that matches your need; you do not need to set up every part first.

For example, you could find someone in **People**, group audiences from related events in a **Community**, and offer **Memberships** for access to selected quests or ticket sales. Email and WhatsApp subscriptions are checked separately from those groups.

## Choose what you need {#choose-what-you-need}

| You want to… | Start with… |
| --- | --- |
| Find someone or inspect your audience | **Audience → People**. |
| Download a CSV or Excel file of selected people | [Export people from your organisation](/help/personal-data-privacy-cookies#export-people-from-your-organisation). |
| Bring existing contacts or event audiences into BASH | **Add people**, then choose a file, ticket provider or email-list source. |
| Manage the audiences of related events together | **Audience → Communities**. |
| Give a group ongoing member access | **Audience → Memberships**. |
| Send an announcement | **Posts**, where you choose access and notification channels separately. |

Someone can appear in several of these groups. Being in your audience does not itself make them a member or mean they have subscribed to email or WhatsApp updates.

## People and subscriptions {#people-and-subscriptions}

**People** is where you find individual audience records. **Audience → Overview** shows **All people**, **Email subscribers** and **WhatsApp subscribers** separately. These counts answer different questions; they do not need to match.

1. Open **Audience** in the organisation you want to work with.
2. Select **All people**, **Email subscribers** or **WhatsApp subscribers** to open the corresponding list.
3. Use the search field to find a person. Open their record to inspect the available details.

[![Audience overview with Add people and separate All people, Email subscribers and WhatsApp subscribers cards](/images/help/screenshots/audience-sync/audience-overview.png "The overview shows 42,680 people, 31,240 recorded email opt-ins and 18,760 recorded WhatsApp opt-ins. Subscriber groups can overlap; these counts do not indicate deliverability.")](/images/help/screenshots/audience-sync/audience-overview.png)

## Bring existing audiences into BASH {#bring-existing-audiences-into-bash}

1. Select **Add people** from **Audience** or **People**.
2. Open **Select source**. Choose **Import list** for a one-time CSV or Excel import, a connected ticket-provider account for event audiences, or **Brevo** or **Mailchimp** for ongoing email-list updates when available.
3. Follow [Import and sync your audience](/help/import-and-sync-your-audience) for the source-specific choices, permission review and result checks.

[![Add audience starts with Select source, including Import list and disconnected ticket providers](/images/help/screenshots/audience-sync/source-selection.png "Choose the source first. Connection and review choices depend on that source.")](/images/help/screenshots/audience-sync/source-selection.png)

A file import is a snapshot. Connected ticket-provider audiences and selected email lists can keep updating. Choosing a community, adding an event audience and joining a membership remain separate actions.

Check the source of any subscription information you import. A contact record, a ticket purchase and an agreement to receive updates are different things. Before sending a post, check the eligible recipients and subscription controls for each channel.

## Communities {#communities}

A **Community** brings together people from related events, such as a recurring event series. Use it when you need to manage that audience separately from the rest of your organisation.

For example, you could organise several events in a recurring series within one community. This is a grouping of audiences, rather than a ticket sale or a membership.

The organisation's **Community page**, managed under **Settings → Community page**, is its wider public page. It is separate from an individual community created in **Audience → Communities**.

1. Open **Audience → Communities**.
2. Select **Create community** on an empty list, or **New** when communities already exist.
3. In **Details**, enter a dashboard **Name** and optional **Description**, then select **Next**.
4. In **Visibility**, choose **Public with identity** or **Internal-only**. A public community has its own public name and logo, lets people sign up and can be the sender of posts. An internal community groups people within your dashboard.
5. Select **Next** and check **Review** before selecting **Create**.

[![An unsaved community's Visibility step offers Public with identity and Internal-only.](/images/help/proposals/audience/community-visibility.png "An unsaved example shows the choice between a public identity and an internal audience group.")](/images/help/proposals/audience/community-visibility.png)

Creating the community does not choose its events:

1. Open its saved page and select **Add**.
2. Choose **Event audience**, select the related events and select **Next**.
3. Review the people and any subscription choices. Complete the open choices before confirming with **Add people**.
4. Check the community's **Events** and **People** counts afterwards.

## Memberships {#memberships}

A membership lets people join an ongoing group that you can use for access. For example, you can select an existing member group when setting up a quest or member sale. A Community groups related audiences; a membership identifies the people who have joined that member group.

Creating a membership does not create a quest or ticket sale. Choose the group separately when setting up access to those features.

1. Open **Audience → Memberships** and select **New membership**, or **Create member group** on an empty list.
2. In **Details**, enter a **Name** and optional **Description**, choose a dashboard **Colour**, then select **Next**.
3. In **Access**, choose **Membership visibility**. **Link only** keeps the group unlisted; **Public** lists it on your community page.
4. Review **WhatsApp updates**, **Send confirmation to people who join** and the selected confirmation channels. Open **Customise form** to review the questions and **Require approval**.

[![Unsaved membership Access shows visibility, join confirmations and Customise form.](/images/help/proposals/loyalty/member-access-unsaved.png "Check discovery, joining requirements and confirmations separately.")](/images/help/proposals/loyalty/member-access-unsaved.png)

5. Select **Next**, check **Review** and select **Create** when ready.
6. Open the saved group in **Memberships**. Check its **Members** count and use **Share** when you are ready to invite people to join.

[![Saved membership shows its Members count and Share action.](/images/help/proposals/loyalty/member-saved-detail.png "The saved example has 1,240 members. Sharing its sign-up link is a separate action.")](/images/help/proposals/loyalty/member-saved-detail.png)

A membership controls member access. It does not replace checking the recipients and subscription requirements when sending an update.

## Choose a next step {#choose-a-next-step}

- For an event announcement, [publish a post](/help/publish-a-post).
- For ticket availability, [choose how people get ticket access](/help/community-activation).
- For participation tasks or points rewards, [use quests, points and rewards](/help/ambassador-programme).

If you cannot find the right audience or access setting, contact support with the organisation, the group or event, and the step reached. Do not include a full contact export or private access links.

Bring existing audiences together and understand people, communities, memberships and subscriptions.

Your audience in BASH

import contacts sync audience CSV Excel Weeztix Eventix Paylogic Brevo Mailchimp email lists reconnect duplicates Use **Add people** to bring existing contacts and ticket-provider audiences into your organisation. Choose a file for a one-time import, or connect a supported source for ongoing updates. Adding people does not send them a notification.

## Before you start {#before-you-start}

You need permission to manage your organisation's audience. Connecting an external account also requires access to the intended provider account. Check the organisation and account before continuing.

A contact record, an event ticket and permission to receive updates are separate. Check the source of imported subscription information. A stored phone number does not give someone WhatsApp permission.

## Choose your source {#choose-your-source}

1. Open **Audience** in the organisation dashboard.
2. Select **Add people**.
3. Open **Select source** and choose the source you want to use.

[![Add audience with Select source open, showing a file import and ticket-provider choices](/images/help/screenshots/audience-sync/source-selection.png "Choose from the sources available to your organisation. Not connected means the source needs an account connection.")](/images/help/screenshots/audience-sync/source-selection.png)

| Source | What you add | What keeps updating |
| --- | --- | --- |
| **Import list** | Contacts from CSV or Excel, added to your audience or an event audience. | This is a one-time import. Later edits to your file do not update BASH. |
| **Weeztix** or **Paylogic** | Ticket-provider event audiences and the people who signed up for updates. | Event audiences continue updating. Automatically adding new events is a separate choice. |
| **Brevo** or **Mailchimp** | Contacts from the lists you select, with their email subscription information. | Changes from those lists update BASH automatically while the connection remains active. |

The sources available depend on the connections enabled for your organisation. If an expected source is missing, contact support with its name and the organisation you are using.

## Import a CSV or Excel file {#import-a-csv-or-excel-file}

1. Choose **Import list** under **Select source**.
2. Select **CSV template** if you need an example of the supported columns. Your file needs an email column. You can add names, phone numbers and other supported details when available.
3. Under **Upload file**, choose a CSV or Excel file. You can add several files, up to 20,000 rows in total. Alternatively, select **Insert as text**, paste your list and select **Use list**.
4. Check the destination beside each list. Keep **Audience** for organisation contacts, or choose **Event audience** and the intended event. Use **Add event** if you need to enter a new event's name and date.
5. If BASH recognises events in a ticket-provider export, review the proposed events before choosing **Add as event audiences**. Check their names and dates, including any match to an existing event.

[![A parsed list with three rows and the Audience destination beside it](/images/help/screenshots/audience-sync/file-ready.png "Check each list's destination before selecting Next. Upload file and Insert as text are alternative ways to supply a list.")](/images/help/screenshots/audience-sync/file-ready.png)

6. Select **Next** to prepare **Review**.

In **Review**:

1. Check the total people, email permissions, phone numbers and people already in your audience. Open any details for rows BASH could not read; correct the file or download those rows to inspect them.
2. Answer any email or WhatsApp permission questions using the information you actually hold. A **Yes** answer records your confirmation; uploading a number or buying a ticket is not itself evidence of that permission.
3. Complete any missing event dates. Check recognised corrections and existing-event matches before continuing.
4. Select the final **Add people** button with its displayed count when the review is complete. Answer any open questions before confirming. If there is nothing to add or update, select **Done**.
5. If you started an import, [check its progress](#check-progress-and-fix-problems) once the dialog closes. After it completes, open **People** or the intended event audience to inspect the result.

[![Review of three contacts with zero email permissions recorded and an unanswered permission question](/images/help/screenshots/audience-sync/file-review.png "Review separates people found from email permission. This example is a preview; neither permission answer nor Add people has been selected.")](/images/help/screenshots/audience-sync/file-review.png)

BASH matches existing people rather than creating another person for every row. Overlapping files, existing contacts and skipped rows can make the number added smaller than the number uploaded. Existing contact details and conflicting rows need review; an import does not replace every saved field.

## Sync a ticket-provider audience {#sync-a-ticket-provider-audience}

The **Add people** route brings in the selected Weeztix company or Paylogic merchant's event audiences. This is separate from choosing the provider event and tickets used for a ticket sale. For that task, follow [Sell tickets at your event](/help/sell-tickets#link-a-provider-event).

1. Open **Add people**, then choose your **Weeztix** company or **Paylogic** merchant under **Select source**.
2. If the account is not connected, choose the provider's connection option and follow its setup. For Paylogic, check the Reporting connection. Return to **Add people** when the account is available.
3. Check **Automatically add new event audiences**. Keep it on to add future events from that account automatically, or turn it off to stop future events being added after this import. This route adds all available current event audiences from the chosen account.
4. Choose a community if you also want these event audiences grouped there. This is optional; it does not create a membership.
5. Select **Add people** to prepare the import, then wait for **Review**. Provider exports can take time to prepare.
6. Check the audience counts and answer any permission questions before selecting the final **Add people** action.
7. [Check the import's progress](#check-progress-and-fix-problems) once the dialog closes. After it completes, inspect the resulting events and their audiences in BASH.

[![Disconnected Paylogic integration with connection guidance and Connect Paylogic merchant](/images/help/screenshots/audience-sync/paylogic-connection.png "The provider's page in Settings → Integrations explains the connection requirements. This example has no connected account or imported provider audience.")](/images/help/screenshots/audience-sync/paylogic-connection.png)

Ticket holders join their event audience. People recorded by the provider as having signed up for your updates can also become email subscribers. These groups overlap, so the event audience count and subscriber count can differ.

Provider subscriber syncing and event audience syncing are separate. Weeztix can pass updates through its connection; Paylogic checks for new data daily. Do not expect a newly changed provider record to appear immediately.

Automatically imported events stay hidden until you set them up. Turning off automatic new-event additions leaves the events already added updating and keeps the people already imported.

## Sync Brevo or Mailchimp lists {#sync-brevo-or-mailchimp-lists}

This connection reads selected email lists into your organisation audience. BASH does not send contact edits or subscription changes back to Brevo or Mailchimp. It does not add those contacts to an event audience or member group.

1. Open **Add people**, then choose **Brevo** or **Mailchimp** under **Select source**.
2. If prompted, connect the intended provider account and approve the requested access in that service. Return to BASH when the connection is complete.
3. Select the lists you want to add. A list marked **Already syncing** is already connected.
4. Select **Next** to start fetching contacts. The dialog closes once the sync starts.
5. Open **Settings → Integrations**, then the provider, to check each list's imported count, **Last synced** information and status. Check **People** for the imported contacts.

[![Disconnected Mailchimp integration with Connect Mailchimp and its audience-sync help link](/images/help/screenshots/audience-sync/mailchimp-connection.png "Connect Mailchimp starts account authorisation. Lists are chosen after connection; this example has not connected an account or started syncing.")](/images/help/screenshots/audience-sync/mailchimp-connection.png)

After the initial import, changes from the selected lists continue updating BASH. Names, phone numbers and addresses can fill missing details. These updates do not create WhatsApp permission.

Contacts can appear in **People** without being email subscribers. BASH uses the source's subscription information alongside existing BASH preferences. If someone appears in several connected lists, their email eligibility reflects those sources and their recorded choices. Removing a contact from a provider list does not by itself delete their BASH record.

Before sending, check the eligible email and WhatsApp counts in the post's **Send** step. [Publish a post to your audience](/help/publish-a-post#choose-notification-channels) explains those controls.

## Check progress and fix problems {#check-progress-and-fix-problems}

The dialog closes once BASH accepts a file or ticket-provider import.

1. Check the **People** tab for a progress indicator while the import runs. If you see a completion notification, it shows how many people were added.
2. Open **Audience → People** and select **Imports** to find the import later. Open its entry to inspect what was added, what already existed and what was skipped.

If **People** shows a notice about the import, use **Check status** when BASH can't confirm the result. Select **Retry** only if the notice offers it for that import.

For a Brevo or Mailchimp connection:

1. Open **Settings → Integrations** and select the provider.
2. Check the list status: **Importing** means the initial import is running; **In sync** means it is active. **Stopped syncing** needs attention.
3. Check **Last synced** alongside the status. If the connection was lost, select **Reconnect** and complete the provider's connection process.
4. Return to the provider page and check that the lists resume updating.

If no lists appear, check that you connected the intended account. If a source, list or import remains unavailable, use **Need more help? Message support** below. Include the organisation, provider, list or event name, step reached and error shown. Keep credentials, full contact exports and private access links out of the message.

## Stop syncing {#stop-syncing}

For Brevo or Mailchimp, disconnecting stops BASH reading the provider's lists. People already imported remain in **People**, with their recorded email preferences.

1. Open **Settings → Integrations** and select the provider.
2. Open the connected account's options and select **Disconnect**.
3. Read the confirmation, then select **Disconnect** if you want syncing to stop.

For automatic ticket-provider event additions:

1. Open **Settings → Integrations** and select **Weeztix** or **Paylogic**.
2. Open the intended account's settings.
3. Turn off **Sync ticket buyers** to stop adding new events automatically. Events already added keep updating, and imported people stay.

Stopping a sync is separate from deleting a person's data. For a data request, follow [Personal data, privacy and cookies](/help/personal-data-privacy-cookies#request-a-copy-correction-or-deletion).

Add contacts from a file, sync ticket-provider audiences or keep selected Brevo and Mailchimp lists updated in BASH.

Import and sync your audience

community early access private shop ticket access Use a ticket sale to decide which audience can obtain an event’s tickets and when. Choose the access route that matches your invitation: sign-ups, selected people, a member group or another eligible audience. The event and its ticket types remain separate from the sale’s access rules.

For example, you could collect sign-ups for a presale, give selected people access through a **Custom sale**, or offer a **Member sale** to an existing member group. Choosing a group for a sale does not add people to that group or subscribe them to updates. Start by comparing the options below, then open the chooser for your event.

## Choose a ticket sale {#choose-a-ticket-sale}

| Choose | When to use it |
| --- | --- |
| **Regular tickets** | Offer tickets on the event page, subject to the sale dates and ticket availability. [Sell tickets directly through BASH](/help/sell-directly-through-bash). |
| **Presale** | Collect sign-ups through a form, then make tickets available to those people. [Set up a presale](/help/set-up-a-presale). |
| **Custom sale** | Give selected people access, or create an unlisted sale for anyone with its link. [Create private ticket access](/help/create-private-ticket-access). |
| **Loyalty sale** | Give ticket holders from another event access, with optional ticket-type and check-in filters. [Set up a loyalty sale](/help/set-up-a-loyalty-shop). |
| **Member sale** | Give a specific member group access to tickets. |
| **Ambassador sale** | Give ambassadors personal links to share with buyers. [Set up an ambassador sale](/help/set-up-ambassadors). |

You may know these as private shops, custom shops or loyalty shops. The dashboard now calls them ticket sales.

## Open the chooser {#open-the-chooser}

You need an event and permission to manage its ticket sales. For ticketing setup, start with [Sell tickets for your event](/help/sell-tickets).

1. Open **Events** in your organisation dashboard and select the event.
2. Open **Ticket sales**.
3. Select **New**. If the event has no ticket sales yet, select **Create ticket sale** instead.

[![The event ticket sale dropdown with five sale types](/images/help/screenshots/ticket-sale-chooser/ticket-sale-dropdown.png "New opens the sale types for the event you are already managing.")](/images/help/screenshots/ticket-sale-chooser/ticket-sale-dropdown.png)

4. Select the sale type. The event is already fixed by the page you opened; there is no second event selector in this menu.

## Continue with the selected sale {#continue-with-the-selected-sale}

The setup flow opens for that event and type. Selecting a type does not publish the sale. Follow the linked guide for the sale type you chose.

1. Complete its access rules, tickets, dates and messages.
2. Check **Review** before creating the sale.

### Keep an unfinished setup {#keep-an-unfinished-setup}

1. Select **Save draft**.
2. Check the saved draft that opens. You can also return to it from **Ticket sales**.

## Set up a member sale {#set-up-a-member-sale}

Use a member sale when an existing member group should be able to obtain tickets. Create the group first if it does not exist; see [Memberships](/help/your-audience#memberships). Choosing a group for this sale does not add people to that group.

### Choose the group and tickets {#choose-the-group-and-tickets}

1. In the chooser, select **Member sale**.
2. Under **Member access**, select **Select group** and choose the intended member group.
3. Decide whether to enable **Show sale publicly with lock**. This controls how the sale is displayed; membership still controls access. Select **Next**.

[![An unsaved Member sale with a member group selected](/images/help/proposals/events/member-access-selected.png "Check the member group and the Show sale publicly with lock setting before continuing.")](/images/help/proposals/events/member-access-selected.png)

4. In **Set up sale: Tickets**, enter the **Sale title** people should see.
5. Select **Add tickets**, select the existing ticket types to include, then select **Done**. Check the selected list, **Personal plus ones** and **WhatsApp updates at checkout**, then select **Next**.

[![General admission selected in an unsaved Member sale ticket setup](/images/help/proposals/events/member-tickets-selected.png "The selected ticket belongs to the event. Adding it here does not create a separate stock allocation.")](/images/help/proposals/events/member-tickets-selected.png)

### Set the dates and review messages {#set-the-dates-and-review-messages}

1. In **Availability dates**, check **Opens**, **Closes** and **Visible from**, then select **Next**.
2. In **Messages**, review **Email** and **WhatsApp**. Turn both off if you do not want to send a sale link through either channel.
3. Review **Reminder settings** separately, then select **Next**.

[![An unsaved Member sale with Email and WhatsApp off and reminders disabled](/images/help/proposals/events/member-messages.png "Both sale-link message channels are off and reminders are disabled. Review your own settings before creating the sale.")](/images/help/proposals/events/member-messages.png)

### Create and check the sale {#create-and-check-the-sale}

1. In **Review**, check the tickets, member group, personal plus ones and timeline. Use **Change** to correct a setting.
2. With both message channels off, select **Create sale** when you are ready. If you enabled messages, review the final action and its recipient information before confirming.
3. Check the saved sale and its **Access** group, then review the attendee preview before sharing it with members.

[![The unsaved Member sale Review with a member group and Create sale](/images/help/proposals/events/member-review.png "This is an unsaved creation review, not a saved sale. The selected membership and ticket are ready for a final check.")](/images/help/proposals/events/member-review.png)

If **Next** is unavailable, check that you selected a group and at least one ticket. To stop before creation, use **Save draft** and return to the draft from **Ticket sales**.

## If the event or creation control is missing {#if-the-event-or-creation-control-is-missing}

Check that you opened the organisation that manages the event. If you cannot manage its ticket sales, ask the organisation's administrator to check your access before continuing.

If you still cannot continue:

1. Select **Need more help? Message support** below this article.
2. Include the organisation, event and missing control or error shown.
3. Select **Open support message**, then review and send the draft.

Keep private ticket links and attendee details out of the message.

Compare ticket access options and set up a member sale for an existing group.

Choose how people get ticket access

presale preregistration sign up early access A presale lets people sign up before buying tickets. You choose the sign-up window separately from the ticket sale's opening and closing dates.

## Before you start {#before-you-start}

You need an event and permission to manage its ticket sales. You also need to choose where the event's tickets are managed before adding tickets. See [Sell tickets for your event](/help/sell-tickets).

## Set up the sign-up form {#set-up-the-sign-up-form}

1. Open the event from **Events**, then open **Ticket sales**.
2. Select **New**, or **Create ticket sale** if this is the first sale.
3. Choose **Presale** from the dropdown for this event.

[![The event-scoped New dropdown lists the five ticket sale types.](/images/help/screenshots/ticket-sale-chooser/ticket-sale-dropdown.png "New opens sale types for the event you are already managing. Choose Presale.")](/images/help/screenshots/ticket-sale-chooser/ticket-sale-dropdown.png)

4. In **Sign up**, check **Form visibility**. Choose **Public** to list the form on your community page, or **Link-only** to leave it unlisted.
5. Check **WhatsApp updates** and **Send confirmation to people who sign up**. If confirmation is on, choose its **Email** and **WhatsApp** channels. These confirmations are separate from the message announcing ticket access.
6. Open **Customise form**. Check **Public title**, use **Description** if needed, and review **Personal information** and any **Custom question**.

[![Existing presale Sign up editor shows Form visibility, WhatsApp updates, sign-up confirmation, Customise form and a form preview.](/images/help/screenshots/presale-detail/presale-edit-sign-up.png "Shown while editing a saved presale: sign-up visibility, confirmation and form settings.")](/images/help/screenshots/presale-detail/presale-edit-sign-up.png)

7. Open **Availability date** and set **Sign up opens** and, if needed, **Sign up closes**. **On save** opens the form when you create the presale.
8. Select **Next** to open **Tickets**.

## Add tickets and choose when buying opens {#add-tickets-and-choose-when-buying-opens}

1. In **Tickets**, enter the **Sale title**.
2. Use **Add ticket** to create a ticket or **Select ticket** to use an existing event ticket. Finish the ticket editor with **Add ticket**, or the selector with **Done**. These changes are saved with the presale.
3. Check **Personal plus ones** and **WhatsApp updates at checkout**, then select **Next**.
4. In **Availability date**, set **Opens** and **Closes** for buying tickets. Check **Visible from**, which controls when the sale becomes visible before it opens.

[![Existing presale Availability date editor shows separate Opens, Closes and Visible from controls beside the ticket-sale preview.](/images/help/screenshots/presale-detail/presale-edit-availability.png "Shown while editing a saved presale: ticket-sale dates are separate from sign-up dates.")](/images/help/screenshots/presale-detail/presale-edit-availability.png)

5. Select **Next** to open **Messages**.
6. Choose the **Email** and **WhatsApp** channels for the access message, check **When?**, and add a personal message if needed.
7. Open **Reminder settings** and check the closing reminder separately. Turn off both channels for each message you do not want to send.
8. Select **Next** to open **Review**. Check the timeline, **Sign up form visibility**, **Sign-up confirmation** and **Presale tickets**. Use the relevant **Change** control to correct a setting.

[![Presale Review shows separate sign-up and ticket-sale opening times, with sign-up confirmation off.](/images/help/screenshots/presale-detail/create-presale-review.png "Presale Review separates the form opening from the ticket-sale opening.")](/images/help/screenshots/presale-detail/create-presale-review.png)

9. Check the final button and message settings before creating the presale. Creating it activates the saved schedule; a form set to **On save** can accept sign-ups immediately. Enabled messages and reminders follow their configured timing. A final button containing **and send link** and a recipient count also sends access messages to those recipients.
10. Select **Create presale** when you are ready, or **Save draft** if you are not ready to activate it.
11. On the saved presale's detail page, check the timeline for the separate sign-up and sale openings. An open form shows **Sign-ups open**. Use **Share sign-up** when you are ready to share the form.

[![Saved presale detail shows Sign-ups open, the ticket-sale countdown, the timeline and Share sign-up.](/images/help/screenshots/presale-detail/presale-detail.png "The saved presale separates sign-up status from the ticket-sale opening.")](/images/help/screenshots/presale-detail/presale-detail.png)

**Send preview** sends a message to the chosen preview recipients.

## Export presale sign-ups and answers {#export-presale-sign-ups-and-answers}

1. Open the presale from **Ticket sales**.
2. Select **Presale sign-ups** in the **Access** section.
3. Open **More** and select **Export sign-ups with answers (CSV)** or **Export sign-ups with answers (Excel)**.

[![The presale sign-ups menu with CSV and Excel export options](/images/help/screenshots/ticket-qr-export/presale-export-menu.png "Choose the file format for sign-ups and answers.")](/images/help/screenshots/ticket-qr-export/presale-export-menu.png)

Your browser downloads the sign-ups and their answers. Keep the file private and share it only with people who need it.

## If you cannot continue or people cannot buy {#if-you-cannot-continue-or-people-cannot-buy}

- **Next** is disabled in **Tickets**: the ticket must be added or selected and its editor completed. The ticket steps above cover both options. **Set up ticketing** means the event's ticketing setup is still required; follow [Sell tickets for your event](/help/sell-tickets). **Set up later** is for creating the form before finishing its ticket setup.
- Registrations are closed: check **Sign up opens** and **Sign up closes** in **Sign up**.
- Someone registered but cannot buy: check the sale's **Opens** and **Closes**, ticket availability, remaining stock and **Personal plus ones**. Visibility and access do not make tickets available before their opening date.
- A message is missing: check the relevant confirmation, access-message or reminder settings. WhatsApp delivery also depends on [your WhatsApp connection](/help/connect-whatsapp) and recipient eligibility.

Use **Need more help? Message support** below if these checks do not resolve it. Include your organisation, event, presale name, step reached and error shown. Do not include private access links or verification codes.

Create a sign-up form and choose when registered people can buy tickets.

Set up a presale

private tickets personal link custom shop selected people Use a **Custom sale** to give selected people access to event tickets. You can also make an unlisted sale available to anyone with its link.

## Before you start {#before-you-start}

You need an event, permission to manage its ticket sales and the intended recipients available in your organisation's audience. Choose where the event's tickets are managed before adding tickets. See [Sell tickets for your event](/help/sell-tickets).

## Choose who gets access {#choose-who-gets-access}

1. Open the event from **Events**, then open **Ticket sales**.
2. Select **New**, or **Create ticket sale** if this is the first sale.
3. Choose **Custom sale** from the dropdown for this event.

[![The event-scoped New dropdown lists the five ticket sale types.](/images/help/screenshots/ticket-sale-chooser/ticket-sale-dropdown.png "New opens sale types for the event you are already managing. Choose Custom sale.")](/images/help/screenshots/ticket-sale-chooser/ticket-sale-dropdown.png)

4. In **Access**, keep **Selected people** and open **Select people…**.

[![Existing custom sale Access has Selected people chosen with a one-person selection and offers Anyone with the link.](/images/help/screenshots/custom-sale-detail/custom-edit-access.png "Shown while editing a saved custom sale: Selected people and Anyone with the link.")](/images/help/screenshots/custom-sale-detail/custom-edit-access.png)

5. In **Select recipients**, use **Search events, groups, people...** to find and select your recipients or audience.
6. Check the selection and choose **Done**.
7. Check the count shown in **Access**, then select **Next**.

**Anyone with the link** is the alternative when everyone holding the sale link should have access. That sale is unlisted; the link still grants access to whoever receives it.

## Add tickets, dates and messages {#add-tickets-dates-and-messages}

1. In **Tickets**, enter the **Sale title**.
2. Use **Add ticket** to create a ticket or **Select ticket** to choose an existing event ticket. Finish the editor with **Add ticket**, or the selector with **Done**.
3. Check **Personal plus ones** and **WhatsApp updates at checkout**, then select **Next**.
4. In **Availability date**, check **Opens**, **Closes** and **Visible from**. **On save** opens the sale when you create it.
5. Select **Next** to open **Messages**.
6. Choose the **Email** and **WhatsApp** channels for sending access, then check **When?** and the eligible recipient counts.
7. Open **Reminder settings** and check the closing reminder's channels and timing. Turn off both channels for each message you do not want to send.
8. Select **Next** to open **Review**. Check **Access**, **Tickets**, **Personal plus ones** and the timeline. Use the relevant **Change** control to correct a setting.
9. Check the final button and message settings. Creating the sale grants the configured access and activates its schedule. Enabled access messages and reminders follow those settings. A final button containing **and send link** and a recipient count also sends access messages to those recipients.
10. Select **Create sale** when you are ready, or **Save draft** if you are not ready to activate it.
11. On the saved sale's detail page, check **Access**. For a selected audience, it shows **Selected people** and the number of people with access. Check that count before distributing access.

[![Saved custom sale detail shows Open, People with access and Selected people under Access.](/images/help/screenshots/custom-sale-detail/custom-sale-access.png "Check the selected audience and access count on the saved custom sale.")](/images/help/screenshots/custom-sale-detail/custom-sale-access.png)

**Send preview** sends a message to the chosen preview recipients.

## If access or sending does not work {#if-access-or-sending-does-not-work}

- **Next** is disabled in **Access**: the recipient selection must be completed with **Done** and show a selected-person count. Follow the selection steps above.
- **Next** is disabled in **Tickets**: the ticket must be added or selected and its editor completed. The ticket steps above cover both options.
- A recipient cannot buy: check the sale's dates, ticket availability, stock and **Personal plus ones**.
- Access exists but a message did not arrive: check its channels and eligible counts before creating another sale. For WhatsApp, check the [connection status](/help/connect-whatsapp).

Treat personal access links as private. For membership-based access, choose **Member sale**. For referral links, see [Set up an ambassador sale](/help/set-up-ambassadors).

Use **Need more help? Message support** below if you still need help. Include your organisation, event, sale name, step reached and error shown. Do not include personal access links or verification codes.

Use a custom sale to give selected people access to event tickets.

Create private ticket access

loyalty returning guests previous event checked in A **Loyalty sale** gives ticket holders from another event access to tickets for your next event. You can filter access by ticket type or recorded check-in.

## Before you start {#before-you-start}

You need permission to manage the new event's ticket sales and access to the source event's ticket audience. Choose where the new event's tickets are managed before adding tickets. See [Sell tickets for your event](/help/sell-tickets).

Ticket holders are not automatically subscribers to email or WhatsApp updates. If the source event uses a connected ticket provider, check that its ticket-holder audience is available in BASH before creating the sale. See [Sync a ticket provider audience](/help/import-and-sync-your-audience#sync-a-ticket-provider-audience). If the sync is still running or reports an error, follow [Check progress and fix problems](/help/import-and-sync-your-audience#check-progress-and-fix-problems).

## Select the previous audience {#select-the-previous-audience}

1. Open the new event from **Events**, then open **Ticket sales**.
2. Select **New**, or **Create ticket sale** if this is the first sale.
3. Choose **Loyalty sale** from the dropdown for this event.

[![The event-scoped New dropdown lists the five ticket sale types.](/images/help/screenshots/ticket-sale-chooser/ticket-sale-dropdown.png "New opens sale types for the event you are already managing. Choose Loyalty sale.")](/images/help/screenshots/ticket-sale-chooser/ticket-sale-dropdown.png)

4. In **Access**, open **Select event…** beside **Ticketholder of...**.
5. Use **Search event**, **Recently selected**, **Coming up** or **Past events** to find the source event and select it.
6. Under **Ticket types**, keep **All types** or select the relevant ticket types.
7. Enable **Give access only to people who have checked in at the event.** only if recorded attendance is required. Check the resulting selected-person count.

[![Existing loyalty sale Access editor shows the source event, Ticket types, check-in switch, collapsed Lock access and selected-person count.](/images/help/screenshots/loyalty-sale-detail/loyalty-edit-access.png "Shown while editing a saved loyalty sale: source event, ticket types and check-in filter.")](/images/help/screenshots/loyalty-sale-detail/loyalty-edit-access.png)

This saved sale editor’s **Save changes and send link (7,680)** action also sends the access link to those recipients; do not treat it as a save-only control.

8. Open **Lock access** and check **Require WhatsApp subscription for access**. If enabled, eligible people must agree to WhatsApp updates about the event to unlock access. This is separate from sending them a message.
9. Select **Next** to open **Tickets**.

## Add tickets and review the schedule {#add-tickets-and-review-the-schedule}

1. In **Tickets**, enter the **Sale title**.
2. Use **Add ticket** to create a ticket or **Select ticket** to choose an existing ticket for the new event. Finish with **Add ticket** or **Done**.
3. Check **Personal plus ones** and **WhatsApp updates at checkout**, then select **Next**.
4. In **Availability date**, check **Opens**, **Closes** and **Visible from**. Review the suggested dates after choosing the source event; do not assume they match your intended sale.
5. Select **Next** to open **Messages**.
6. Choose **Email** and **WhatsApp** for sending access, then check **When?** and the eligible recipient counts.
7. Open **Reminder settings** and check its channels and timing separately. Turn off both channels for each message you do not want to send.
8. Select **Next** to open **Review**. Check **Access**, **Tickets**, **Personal plus ones**, **Lock access** and the timeline. Use the relevant **Change** control to correct a setting.
9. Check the final button and message settings. Creating the sale activates the access rules and schedule. Enabled access messages and reminders follow their configured timing. A final button containing **and send link** and a recipient count also sends access messages to those recipients.
10. Select **Create sale** when you are ready, or **Save draft** to keep an unfinished setup.
11. On the saved sale, check **Access** for the source audience and the number of people with access. Check the timeline for its opening and closing dates.

[![Saved loyalty sale detail shows Open, People with access and the source event under Access.](/images/help/screenshots/loyalty-sale-detail/loyalty-sale-access.png "The saved loyalty sale shows which event audience has access.")](/images/help/screenshots/loyalty-sale-detail/loyalty-sale-access.png)

**Send preview** sends a message to the chosen preview recipients. A past ticket does not itself make someone eligible for WhatsApp delivery.

## If the audience is missing or someone cannot buy {#if-the-audience-is-missing-or-someone-cannot-buy}

- The source event is missing: check that you have access to the organisation and its event audience.
- No people are selected: check **Ticket types** and the check-in switch. A check-in filter excludes people whose attendance is not recorded.
- An eligible person cannot buy: check the new sale's dates, ticket stock, **Personal plus ones** and any **Lock access** requirement.

For a provider event, **Add event audience** may be offered before its audience is ready:

1. Select **Add event audience** if it is offered, then wait for the audience to finish loading.
2. If it fails and **Retry** is offered, select **Retry**.
3. Check that the source audience is available before continuing. Contact support if it remains unavailable.

Use **Need more help? Message support** below if these checks do not resolve it. Include the organisation, source event, new event, sale name and error shown. Keep personal ticket links and attendee details private.

Give ticket holders from another event access to your next ticket sale.

Set up a loyalty sale

messages send update email audience notifications presale invitation exclude sign-ups Use a post to invite people to a presale, share a ticket link or publish practical event information. Choose the audience, add a clear action and check who can receive the message before sending.

Choose a page destination when people should be able to find the post there, or **Send-only** for a message to selected people without a page listing. You need permission to manage posts for the organisation you are working in.

## Choose where the post appears and who receives it {#choose-where-the-post-appears-and-who-receives-it}

A post has three separate choices:

| Choice | What it controls |
| --- | --- |
| Post type | Whether the post appears on your community page (**General post**), an event page (**Event post**), or has no page listing (**Send-only**). |
| Access | Who can read the post. A public page does not make a members-only post readable to everyone. |
| Notifications | Whether eligible people receive an email, a WhatsApp message, both or neither. |

Your community page is your organisation’s page. Choosing named communities under **Audience** sets the audience scope; it does not create a separate post on each group’s page. See [Your audience](/help/your-audience#communities) for the difference.

For an arrival update, attendees could read the information on the event page without another notification. If the team wants to send an update, it checks the eligible recipients for each channel separately from read access.

Creating a post does not connect WhatsApp, grant membership or make someone a subscriber. Use the recipient counts and any warnings in **Send** to check the people BASH can reach.

To use contacts from a Brevo or Mailchimp list as post recipients, add that list to BASH first. Follow [Sync Brevo or Mailchimp lists](/help/import-and-sync-your-audience#sync-brevo-or-mailchimp-lists). An imported phone number does not record WhatsApp consent; check the eligible count for that channel in **Send**.

## Invite people to a presale {#invite-people-to-a-presale}

Start with an existing presale sign-up form. If you still need one, follow [Set up a presale](/help/set-up-a-presale). You choose whom to invite; sharing the presale does not choose the audience for you.

1. Open the presale in your organisation dashboard.
2. Open **Share sign-up**, then select **Share sign-up link in post**. The composer opens with starter text and a presale sign-up action.
3. Add your announcement, subject and artwork in **Content**. Keep the sign-up action so recipients can open the matching form.
4. Under **Audience**, if shown, choose the relevant communities or **Entire audience**. For a targeted invitation, choose **Send-only** under **Post type**, then **Select people** to build the audience using your event audiences, groups or individual contacts.
5. Review the suggestion about people who have already signed up for the linked presale. Applying it to a page post switches the post to **Send-only**, so it will have no page listing. The exclusion changes who can read the post. Select **Exclude** if you want to leave those people out.

[![Audience selection with a suggestion to exclude existing presale sign-ups](/images/help/screenshots/posting-presale/choose-audience.png "Review the suggested exclusion for your chosen audience. This example uses demo data.")](/images/help/screenshots/posting-presale/choose-audience.png)

The suggestion appears when BASH finds existing sign-ups in the chosen audience and can identify one relevant action. If it is missing, check the selected audience and sign-up action. Several unrelated actions can prevent a suggestion. Adding the action alone does not exclude anyone.

6. Select **Next** to check **Schedule**, then continue to **Send** and choose email, WhatsApp or both.
7. Check each channel’s eligible recipients, then continue to **Review**. Follow [Review and publish](#review-and-publish) to check your audience, delivery and schedule before confirming.

For a ticket reminder, the same flow can suggest excluding existing ticket holders when the action links to the event, or buyers of a particular ticket sale when it links to that sale. Review and apply the suggestion yourself; it is not an automatic exclusion.

### What recipients see when they sign up {#what-recipients-see-when-they-sign-up}

The presale action opens the matching sign-up form. When a recipient’s personal link or signed-in account lets BASH recognise them, the form can show their known identity instead of asking for those details again. If all required details are already available and there are no extra questions to answer, they can sign up in one tap.

A visitor may still need to enter missing details, answer the organiser’s questions or complete verification. A previous visit alone does not establish their identity. The post’s access rules also do not override the presale’s own sign-up access or opening time.

## Open Posts {#open-posts}

1. Open your organisation dashboard and select **Posts**.
2. Select **New**. The composer opens at **Content**.
3. Check the organisation and the sender shown in the preview before writing.

[![Posts list with New and seven existing entries under Recent](/images/help/screenshots/posting-20261030/posts-index.png "Start in Posts and select New. The existing Recent entries are separate from this walkthrough.")](/images/help/screenshots/posting-20261030/posts-index.png)

## Write your content {#write-your-content}

1. If **Audience** is shown, select the intended communities or **Entire audience**. Check the sender and recipients after changing the scope.
2. Under **Post type**, select how to share the post:
   - **General post** publishes on your community page. Use it for an update to your whole audience or the communities selected under **Audience**.
   - **Event post** publishes on an event page. Select the intended event.
   - **Send-only** sends to selected people without listing the post on a page.
3. Check the access control for the selected post type. For example, a General post offers **Visible to anyone** or **Members-only** when memberships are available.
4. If you choose members, select the intended member group. Access determines who can read the post; it does not guarantee notification delivery.
   For **Send-only**, use **Select people** to choose the audience. Review any suggested exclusion before applying it. The selected people are fixed when the message is sent; a scheduled send uses the people matching your selection at that time.
5. Enter a **Subject**, then write your message in the editor. Use **Insert** if you need to add an image or action.
6. Check the post preview and open any action destinations before publishing. On desktop, select **Full screen editor** for more writing space, then select **Done** to return.
7. Select **Next** to open **Schedule**.

[![Content in an existing saved draft, with General post, access, subject and message controls](/images/help/screenshots/posting-20261030/post-content.png "Check the post type, access and message. This is an existing saved draft; no content was changed.")](/images/help/screenshots/posting-20261030/post-content.png)

The short hint beside **General post** shows its scope, such as **Whole audience**, **Chosen communities** or **Members only**. When available, the compact number in brackets shows the size of that audience under the selected access rules. It is not a delivery count. Check the eligible recipients for each channel in **Send**. Open the **Post type** menu for descriptions of the available types.

## Choose the publication time {#choose-the-publication-time}

1. In **Schedule**, check **Opens**. Keep **Now** for immediate publication, or open the date control and choose a future date and time.
2. If you choose a date and time, select **Done** in the picker. To return to immediate publication, use **Now** in that picker.
3. Select **Next** to open **Send**. Check the selected time and time zone again in **Review** before confirming publication.

[![Schedule in an existing draft with Opens set to Now](/images/help/screenshots/posting-20261030/post-schedule.png "Set the publication time in Schedule. No date was changed in this example.")](/images/help/screenshots/posting-20261030/post-schedule.png)

## Choose notification channels {#choose-notification-channels}

1. In **Send**, check the **Email** and **WhatsApp** switches. Turn off any channel you do not want to use. With both off, publishing sends no notification. A Send-only post needs a delivery channel.
2. Read the eligible recipient count for each selected channel. Review whether **Only send to people who signed up for email updates** should be on, if the option is shown. The selected audience and reachable recipients can differ.
3. If you enable **WhatsApp**, check its connection status and choose **Send link to post** or **Send WhatsApp version**. The latter has a separate **Review message** and Meta approval step. Follow [Send a post through WhatsApp](/help/send-whatsapp-updates) before continuing.
4. Select **Next** to open **Review**.

[![Send in an existing draft with both channels off, 31,240 people available for email and zero available for WhatsApp](/images/help/screenshots/posting-20261030/post-send.png "Both channels are off. Check recipient availability for each channel; this example has not linked a WhatsApp account.")](/images/help/screenshots/posting-20261030/post-send.png)

## Review and publish {#review-and-publish}

The final action applies your publication time and selected notification channels. Check these settings before confirming.

1. Check the subject, message and actions in **Content**. **Review** summarises publishing settings; it does not replace checking the message.
2. In **Review**, check **Post type**, **Allow comments and reactions** and **Schedule**. Check **Sender** if shown and the displayed time zone for a scheduled post.
   - For **General post** or **Event post**, check **Who can read** and **Sending to**.
   - For **Send-only**, check **Recipients** and **Delivery**. **Delivery** appears after you select a channel in **Send**.
3. Use **Change** beside a setting to correct it. For publication timing, **Change** beside **Schedule** returns to the **Opens** control.

[![Review of an existing draft showing Post type General post, Sender, Schedule Now and Sending to No notification](/images/help/screenshots/posting-20261030/post-review.png "Check the post type, access, timing and delivery before confirming. Post has not been selected; the draft has not been published or sent.")](/images/help/screenshots/posting-20261030/post-review.png)

4. Select the final action that matches your intention: **Post** for publication without notifications, **Send & Post** for publication with notifications, **Send** for Send-only, or **Schedule post** for a future time.
5. Return to **Posts** and check the saved post and its status before creating another copy or sending again.

A scheduled or published post does not confirm that every notification was delivered.

## Save and reopen a draft {#save-and-reopen-a-draft}

1. Select **Save draft** to save and return to **Posts** without publishing.
2. Open the **Drafts** tab.
3. Select the post to continue.
4. Check that the saved subject and message are present before making more changes.

## If you cannot publish {#if-you-cannot-publish}

- A missing-content or access issue: return to **Content** and complete the highlighted field or selection.
- The post changed to **Send-only** after **Exclude**. In **Content**, check **Post type** and the selected audience before sending.
- **WhatsApp approval required**: select **Review message** and complete the approval step, or turn WhatsApp off in **Send** if you do not intend to use it.
- **Not linked** beside WhatsApp: use **Set up**, or turn that channel off. See [Connect WhatsApp](/help/connect-whatsapp).
- **Check status** after an uncertain result: use that action and check **Posts** before creating another copy or sending again.

If you still need help:

1. Select **Need more help? Message support** below this article.
2. Include the organisation, post subject, step reached and error shown.
3. Select **Open support message** and review the draft before sending it. Do not include private attendee links.

Invite a relevant audience to your presale, or publish an update on a page. Check access, exclusions and delivery before sending.

Publish a post to your audience

whatsapp business facebook meta set up integration opt in existing whatsapp existing business account business number migration Connect WhatsApp to use it as a notification channel for your organisation. You need permission to manage the organisation's communication settings and access to the Meta business account you intend to use.

## Find your WhatsApp connection {#find-your-whatsapp-connection}

1. Open your organisation dashboard.
2. Open **Settings → Email & WhatsApp**.
3. Under **WhatsApp notifications**, select **Connect** or **Manage** beside **WhatsApp** to open the integration page.

[![The WhatsApp notifications section showing Connect and the separate WhatsApp consent setting](/images/help/screenshots/connect-whatsapp/communication-whatsapp.png "Open the integration from the WhatsApp row. Consent stays on Email & WhatsApp.")](/images/help/screenshots/connect-whatsapp/communication-whatsapp.png)

4. Under **Connection status**, check **Connection**. **Not linked** means you can start setup with **Set up**.

[![The WhatsApp integration showing Connection status, Not linked and Set up](/images/help/screenshots/connect-whatsapp/integration-whatsapp.png "Check the connection on the integration page before starting setup.")](/images/help/screenshots/connect-whatsapp/integration-whatsapp.png)

## Use an existing account or number {#use-an-existing-account-or-number}

New and existing accounts start from the same **Set up** action. Account and number selection take place in Meta's window; BASH has no separate form for choosing an existing number.

Before starting:

- Check that your Meta account can manage the intended business assets and keep access to the number available for verification.
- If the number is used in the WhatsApp Business app or through another provider, read the connection or migration requirements presented for that account. Stop and ask BASH support if the effect on your current service is unclear.
- Keep your existing service in place until the connection route is clear. Do not delete or disconnect it to make a missing account or number appear.
- If BASH already shows a linked connection, follow [the connection status guidance](#understand-your-connection-status) before attempting setup again.

## Start setup with Meta {#start-setup-with-meta}

Meta controls the account and number choices after the handoff. Have access to the intended business account and to any number Meta asks you to verify.

1. Beside **Not linked**, select **Set up**. BASH shows **Linking WhatsApp** and opens a Facebook signup window. Allow the popup and keep the BASH tab open.
2. Sign in using the Meta account that can manage the intended business.
3. Choose or create the business account offered by Meta. For an existing account, select the intended business account and number where Meta offers them. Check both before confirming; the options depend on the account.
4. Complete the number, verification and billing requirements shown by Meta. Stop and ask support before accepting a migration you do not understand.
5. Return to BASH and read **Connection** again. Use the status guidance below if another action is required.

Starting signup or closing the Facebook window does not mean the connection is ready. BASH's connection status, account restrictions and message approval determine whether you can send.

## Understand your connection status {#understand-your-connection-status}

- **Not linked**: select **Set up** to start linking.
- **Inactive**: select **Activate** to enable the existing connection.
- **Waiting for Meta...**: setup is awaiting Meta approval. Wait for the status to change before relying on WhatsApp for an announcement.
- **Action needed**: select **Review** and resolve the requirements shown.
- **Error**: use **Retry** to check the current status. Contact support if the error remains.
- **Active**: the connection is linked. Check **Message limit:**, any **Daily limit reached** notice and the approval status of the message you want to send.

An active connection is separate from recipient consent and message approval. For the sending workflow, follow [Send a post through WhatsApp](/help/send-whatsapp-updates).

## Choose how to collect consent {#choose-how-to-collect-consent}

1. Return to **Settings → Email & WhatsApp**.
2. Under **WhatsApp notifications**, open **WhatsApp consent**.
3. Select **Collect** or **Don’t collect** for the organisation default. Collecting consent requires a mobile number on sign-up and checkout forms. Individual forms can override this default.
4. Check the selected value. Your choice saves when you select it.

Changing this default does not subscribe existing contacts. Check the eligible recipient count when preparing a notification.

An imported mobile number is contact information, not WhatsApp permission. A ticket holder or email subscriber is not automatically eligible for WhatsApp. Check the channel's eligible recipient count in **Send** before publishing; see [Send a post through WhatsApp](/help/send-whatsapp-updates).

When connection details are available:

1. In **Email & WhatsApp**, open **WhatsApp replies**.
2. Choose **Reply in Messages** or **Send an automatic reply**. If you choose an automatic reply, enter the message.
3. Select **Save** and check that **WhatsApp replies** shows your selected option.

For current Meta charges, check [WhatsApp's pricing page](https://business.whatsapp.com/products/platform-pricing).

## If the account or number is not offered {#if-the-account-or-number-is-not-offered}

1. Check that the Meta account you signed in to can manage the intended business assets.
2. Read the available account and number choices, including any connection or migration requirements.
3. If the intended option is still missing, stop and contact support using the action below. Include the organisation, step reached and missing option. Keep your existing service in place and do not share verification codes or credentials.

## If setup does not open or finish {#if-setup-does-not-open-or-finish}

- **Popup blocked**: allow popups for BASH, then select **Set up** again.
- **Browser blocking connection**: check whether tracking protection, an ad blocker or a VPN is blocking Facebook for this site. Select **Try again** after resolving the block. You can also reopen the integration page in another supported browser and select **Set up**.
- **Linking WhatsApp** remains open: check the Facebook window. Use **Cancel** to leave the BASH loading dialog if you want to stop the attempt, then read **Connection** before starting again.
- **WhatsApp setup couldn't complete**: return to the connection status and check the account used for setup. If the error says no number was linked, check that the number-selection step was completed. Ask support if the error repeats.

If you need help:

1. Select **Need more help? Message support** below this article.
2. Include the organisation, connection status and error shown.
3. Select **Open support message** and review the draft before sending it. Do not share passwords, verification codes or account tokens.

Connect a new or existing WhatsApp business account and check its status, consent and reply settings.

Connect WhatsApp to your organisation

whatsapp messages consent message limit templates billing Send a post as a WhatsApp notification to eligible contacts. You need permission to manage posts, a ready WhatsApp connection and people who have agreed to receive WhatsApp updates in the selected audience.

## Check the connection and recipients {#check-the-connection-and-recipients}

1. Open **Settings → Email & WhatsApp** and find **WhatsApp notifications**.
2. Select **Connect** or **Manage** beside **WhatsApp** to open the integration page.
3. Check that **Connection** shows **Active**. If setup or another action is required, follow [Connect WhatsApp](/help/connect-whatsapp).

[![The WhatsApp integration showing Not linked and Set up under Connection status](/images/help/screenshots/connect-whatsapp/integration-whatsapp.png "This connection needs setup before the organisation can send through WhatsApp.")](/images/help/screenshots/connect-whatsapp/integration-whatsapp.png)

4. Open **Posts → New**.
5. In **Content**, check **Audience**, if shown, then choose **General post**, **Event post** or **Send-only** under **Post type** and check access. Follow [Publish a post to your audience](/help/publish-a-post) for those choices.
6. Enter a **Subject** and write the message in the editor.

[![A saved demonstration post in Content, with General post, access and message fields](/images/help/screenshots/posting-20261030/post-content.png "Prepare the post content before choosing its delivery channels.")](/images/help/screenshots/posting-20261030/post-content.png)

7. Select **Next** to open **Schedule**. Keep **Opens** set to **Now** to send immediately, or choose a future date and time and select **Done**. For a scheduled send, check the time zone again in **Review**.

[![Schedule in an existing draft with Opens set to Now](/images/help/screenshots/posting-20261030/post-schedule.png "Choose the post's publication time before its delivery channels. No date was changed in this example.")](/images/help/screenshots/posting-20261030/post-schedule.png)

8. Select **Next** to open **Send**.
9. Turn **WhatsApp** on and check the eligible count and connection notice before continuing. Use this count to check WhatsApp recipients. The compact count beside **General post** shows audience size under the access rules.
10. Turn **Email** off if you do not also want an email.

[![Send in an existing draft with both channels off, 31,240 people available for email and zero available for WhatsApp](/images/help/screenshots/posting-20261030/post-send.png "The account has not linked WhatsApp. Recorded subscriptions alone do not make the channel ready to send.")](/images/help/screenshots/posting-20261030/post-send.png)

A zero available count does not mean there are no recorded WhatsApp opt-ins. In this example the account is not linked and the phone numbers are not routable; resolve connection and recipient requirements before relying on the channel. A ticket holder or email subscriber is not automatically a WhatsApp subscriber, and importing a phone number does not record WhatsApp permission. If you need to sync ticket-holder history into **Audience**, see [Sync a ticket provider audience](/help/import-and-sync-your-audience#sync-a-ticket-provider-audience).

## Choose the WhatsApp message {#choose-the-whatsapp-message}

The dropdown beneath **WhatsApp** offers two delivery choices:

- **Send link to post** sends a link to the post. Check the **WhatsApp** preview tab to see the link message.
- **Send WhatsApp version** sends a separate version of the message and requires Meta approval. Complete the review below before publishing or scheduling.

For **Send WhatsApp version**:

1. Select **Review message**. The **Review WhatsApp message** dialog shows the original post and the WhatsApp message.
2. Read the WhatsApp message and check its buttons. If it needs changing, select **Edit**, make the changes and select **Save**. These edits change the WhatsApp version, not the original post.
3. Select **Submit for approval** when the version is correct. A changed or rejected version can show **Submit again**. This requests Meta review; it does not send the update to your audience.
4. Check the approval status back in **Send**. If the review dialog is still open, **Done** closes it.
5. Wait for the required approval before publishing or scheduling. If it is pending, follow the draft steps below.

Do not treat a saved draft or a submitted approval request as a sent message.

To leave the post while approval is pending:

1. Select **Save draft**.
2. When you want to continue, open **Posts → Drafts**.
3. Select the post and check the WhatsApp approval status again.

## Review and confirm the send {#review-and-confirm-the-send}

Sending can incur charges. Check the eligible count, cost estimate and your current account limits before confirming.

1. Check the final subject, message and actions in **Content**.
2. In **Schedule**, check **Opens** and choose the publication time. In **Send**, confirm WhatsApp is on and the required approval is complete.
3. Open **Review** and check **Post type**, **Sender** if shown, and **Schedule**. For **General post** or **Event post**, check **Who can read** and **Sending to**. For **Send-only**, check **Recipients** and **Delivery**. For a scheduled send, check the displayed time zone and use **Change** beside **Schedule** if you need to adjust the time.
4. Select **Send & Post** to send and publish now, **Send** for a Send-only post, or **Schedule post** for the selected future time.
5. Return to **Posts** and check the post's status. Publishing or scheduling does not confirm delivery to every recipient.

## Check consent, limits and cost {#check-consent-limits-and-cost}

1. Open **Settings → Email & WhatsApp**.
2. Find **WhatsApp consent** and check whether the organisation default is **Collect** or **Don’t collect**. Individual sign-up and checkout forms can override it. Importing a phone number does not subscribe someone to WhatsApp updates.
3. Select **Connect** or **Manage** beside **WhatsApp**. On the integration page, check **Message limit:** and any reset notice if shown.

Meta's charges depend on the recipient's market and message category. Check [WhatsApp's current pricing](https://business.whatsapp.com/products/platform-pricing) and the billing requirements for your account rather than relying on an old fixed rate or allowance.

## If you cannot send {#if-you-cannot-send}

- **Not linked**: select **Set up** on the WhatsApp integration page and complete the connection first.
- **WhatsApp approval required**: select **Review message**. The final send action stays unavailable until the required approval is complete.
- **Inactive**, **Waiting for Meta...** or **Action needed**: use the [connection status guidance](/help/connect-whatsapp#understand-your-connection-status).
- **Schedule paused** after editing a scheduled WhatsApp version: wait for the required approval, then check **Schedule** and confirm your publication timing again.
- **Daily limit reached**: check the reset notice on the WhatsApp integration page before planning another send.
- No eligible recipients: check the intended audience and WhatsApp subscriptions. The connection alone does not create consent.
- An uncertain publish result: use **Check status** and check **Posts** before sending again.

If the problem remains:

1. Select **Need more help? Message support** below this article.
2. Include the organisation, post subject, status and error shown.
3. Select **Open support message** and review the draft before sending it. Do not include private access links or verification codes.

Check your connection, recipients and message approval before sending a WhatsApp update.

Send a post through WhatsApp

loyalty quests tasks submissions proof points rewards ambassadors Use **Loyalty → Quests** when you want people to do something, such as share an announcement, and submit their work for review. A quest defines the tasks, who can take part and when submissions are open. You can offer points for completing tasks if points are enabled; a quest does not have to award points.

Use **Loyalty → Rewards** to offer items people can claim with points. Decide what people can earn and what those points can buy before inviting them. A task submission still needs review, and a reward claim still needs fulfilment by your team. Creating a quest or reward does not complete those later steps.

Ambassadors are one use case. You can give an ambassador member group access to a quest. For personal ticket referral links, follow [Set up an ambassador sale](/help/set-up-ambassadors) separately. A quest is not a ticket sale.

## Before you start {#before-you-start}

You need permission to manage the organisation. Prepare clear task instructions, the evidence you will accept and who will review submissions. If you plan to offer rewards, agree the points costs, stock and collection or delivery arrangements.

The screenshots show unsaved setup forms and separate saved examples. Counts in saved examples illustrate access, submitted work and recorded claims; they do not confirm approval or fulfilment.

## Create a group for member access {#create-a-group-for-member-access}

If participation should depend on membership, [set up the group in Audience](/help/your-audience#memberships) first. Use that same group in the quest's **Access** settings. A membership alone does not create a quest, referral sale or points reward.

## Quests {#quests}

A quest turns an activity into tasks people can complete and submit for review. Use one when you need clear instructions, an audience and a place to review the work. For example, you could ask a member group to share your announcement and submit a screenshot.

Points are optional. The organiser reviews the submission; submitting work is separate from approval and any points credit.

### Set up your first quest {#set-up-your-first-quest}

1. Open **Loyalty → Quests**. Select **New**, or **Create quest** if the list is empty.
2. In **Access**, choose **Member groups** and select the relevant group. Alternatively, choose **Selected people** or **Anyone with the link**. Select **Next**.

[![Unsaved quest Access with a member group selected and the other access choices visible.](/images/help/proposals/loyalty/quest-access-unsaved.png "Choose who can participate. The selected member group has 1,240 members.")](/images/help/proposals/loyalty/quest-access-unsaved.png)

3. In **Details**, enter the **Quest name** and optional description, then select **Next**.
4. In **Tasks**, select **Add task**. Enter **Task name** and **Instructions**, including what people should submit for review.
5. Set **Maximum per person** if needed. If points are enabled, set **Points per completion**; leave it at **0** for a task without a points award.
6. Select **Add task** in the task panel to add it to the working copy. Repeat for other tasks, then select **Next**.

[![Unsaved Add task panel with task instructions, Maximum per person and Points per completion.](/images/help/proposals/loyalty/quest-task-unsaved.png "An illustrative task offers 100 points and asks for a screenshot. Nothing has been submitted or approved.")](/images/help/proposals/loyalty/quest-task-unsaved.png)

7. In **Availability**, check **Quest opens**, **Quest closes** and the displayed time zone, then select **Next**.
8. In **Message**, choose whether to send the link by **Email** or **WhatsApp**. Check any displayed WhatsApp cost. Turn both channels off if you do not want an access message. Access messages are unavailable for **Anyone with the link**. Select **Next**.
9. In **Review**, check the tasks and access. Select **Save draft** to continue later, or **Publish Quest** when ready. Publishing uses the availability and enabled message settings you have chosen.


### Check access and submissions {#check-access-and-submissions}

1. Return to **Loyalty → Quests** and open the quest.
2. Check **People with access**, **Access**, the task list and **Submissions**.
3. Open **All submissions** to inspect submitted work. Check the person, task instructions and proof before making a review decision. A submission count is not a count of approved work.

[![Saved quest detail with one task, 1,240 people with access and 930 submissions.](/images/help/proposals/loyalty/quest-saved-detail.png "The saved example has 930 submissions, including 200 awaiting review and 620 approved. A submission count is separate from approval.")](/images/help/proposals/loyalty/quest-saved-detail.png)

## Rewards {#rewards}

A reward gives people something to claim with points, such as an item to collect from your team. Use rewards when you have a points-earning activity and can fulfil what you offer. Adding a reward does not give anyone points.

For example, a task could offer **100 points** for an approved completion, and a pin badge could cost **100 points**. This illustrates how earning and spending can fit together; the setup screenshots do not show a points award or claim. Quest points are optional, and points can also be configured through ambassador sales.

### Offer a reward for points {#offer-a-reward-for-points}

1. Open **Loyalty → Rewards**. If points are off and the catalogue is empty, select **Set up rewards**. Review the confirmation explaining that points will turn on and the reward form will open, then select **Turn on points and continue**. Points stay on if you close the form without adding a reward.
2. If the form is not already open, select **New**, or **Add reward** when points are on and the catalogue is empty. With an existing catalogue, **New** also works when points are off and does not turn them on.
3. In **New item**, enter the **Name**, **Description** and **Points** cost. Explain collection or delivery in the description.
4. Set **Max. per person** and **Total available** if you need claim limits. Select **Add reward** when ready.

[![Unsaved New item reward form with a 100-point cost and example claim limits.](/images/help/proposals/loyalty/reward-form-unsaved.png "An unsaved example: one per person and 25 available are illustrative limits, not stored stock.")](/images/help/proposals/loyalty/reward-form-unsaved.png)

5. Check that the item appears under **Available rewards** with its points cost and claimed count.
6. Open the item to check **Claimed** and **Claimed by**. Arrange collection or delivery separately; a recorded claim does not confirm fulfilment.

[![Saved reward showing its 100-point cost, 186 claims and Claimed by.](/images/help/proposals/loyalty/reward-saved-detail.png "The saved reward has 186 recorded claims. Arrange fulfilment separately.")](/images/help/proposals/loyalty/reward-saved-detail.png)

## If people cannot take part {#if-people-cannot-take-part}

1. Open the quest and check its **Access** and availability. For member access, check the group in **Audience → Memberships** in the same organisation.
2. For a missing reward, check **Loyalty → Rewards** and whether the item is under **Available rewards**. The catalogue and claims remain manageable when points are off; existing balances may still be usable for eligible rewards.
3. If the issue remains, contact support with the organisation, quest or reward name and the step reached. Do not include private links or submitted personal information.

Invite people to complete tasks, review their submissions and offer rewards for points.

Quests, points and rewards

ambassadors ambassador shop ticket sale referrals points referral discount An ambassador sale gives members of a selected group personal promotional links to share with ticket buyers. This guide is for organisers setting up ticket referrals. For member groups, tasks and rewards, see [Quests, points and rewards](/help/ambassador-programme).

## Before you start {#before-you-start}

You need access to manage the organisation and event, a member group for the ambassadors and an event with ticketing set up. [Set up ticketing](/help/sell-tickets) before adding a sale. You can create the member group in **Audience → Memberships**.

## Create the ambassador sale {#create-the-ambassador-sale}

1. Open the event from **Events**, then open **Ticket sales** and select **New**, or **Create ticket sale** for its first sale.
2. Select **Ambassador sale** from the dropdown for this event.

[![The event-scoped New dropdown lists the five ticket sale types.](/images/help/screenshots/ticket-sale-chooser/ticket-sale-dropdown.png "Choose Ambassador sale for the event you are already managing.")](/images/help/screenshots/ticket-sale-chooser/ticket-sale-dropdown.png)

3. In **Access**, choose **Member group** and select your ambassador group.
4. Check **Show sale publicly with lock**: turning it on makes the sale publicly visible with a membership lock. Select **Next**.

[![Existing ambassador sale Access editor shows Member group, the selected group and Show sale publicly with lock.](/images/help/screenshots/ambassador-sale-detail/ambassador-edit-access.png "Shown while editing a saved ambassador sale: member group and public visibility lock.")](/images/help/screenshots/ambassador-sale-detail/ambassador-edit-access.png)

5. In **Ambassadors**, enter the **Title** and **Description** shown to ambassadors.
6. Open **Max referrals per ambassador** to set the cap on tickets bought through each ambassador’s link, including their own purchases.
7. If points are enabled, open **Referral points** and set **Points per referral**. Select **Next**.

[![Existing ambassador sale Ambassadors editor shows Title, Description, Max referrals per ambassador and Referral points.](/images/help/screenshots/ambassador-sale-detail/ambassador-edit-referrals.png "Shown while editing a saved ambassador sale: ambassador copy, referral cap and points.")](/images/help/screenshots/ambassador-sale-detail/ambassador-edit-referrals.png)

8. In **Tickets**, enter the buyer-facing **Sale title**.
9. Use **Select ticket** to choose existing tickets, then select **Done**. To create a ticket instead, use **Add ticket** and finish its editor with **Add ticket**.
10. Check the ticket prices and capacity, **WhatsApp updates at checkout** and, when available, **Referral discount**. Select **Next**.
11. In **Availability date**, check **Opens**, **Closes** and **Visible from**. **On save** opens the sale when you create it. Select **Next**.
12. In **Messages**, choose whether to send the sale link by **Email** or **WhatsApp**, and check **When?** for access-message timing.
13. Open **Reminder settings** and review reminders separately. To avoid notifications, turn off both access-message channels and disable reminders.
14. Select **Next** to open **Review**. Check the timeline, **Access**, tickets, referral cap and discount.

[![Ambassador sale Review shows the selected member group, ticket count, referral cap and Create sale button.](/images/help/screenshots/ambassador-sale-detail/create-ambassador-review.png "Review the ambassador group, referral cap and timeline before creating the sale.")](/images/help/screenshots/ambassador-sale-detail/create-ambassador-review.png)

15. Select **Create sale** when ready, or **Save draft** to keep working later. Creating the sale can open access and send any messages you enabled.
16. On the sale’s management page, check its status and the group under **Access**. A sale opening on save shows **Open**. The page also shows **People with access** and **Tickets sold**.

[![Saved ambassador sale detail shows Open, People with access, Tickets sold and the ambassador group under Access.](/images/help/screenshots/ambassador-sale-detail/ambassador-sale-access.png "Check the ambassador group and sale status on the saved sale.")](/images/help/screenshots/ambassador-sale-detail/ambassador-sale-access.png)

Access and notification delivery are separate: creating a sale with messages off does not send an access message.

## Check discounts and points {#check-discounts-and-points}

- **Referral discount** changes the buyer’s ticket price. Its availability depends on the ticket provider’s capabilities.
- **Referral points** sets the points an ambassador can earn per ticket sold. The section appears when points are enabled for your organisation.
- Reward items are managed separately in **Loyalty → Rewards**. Adding points to a sale does not add items to the reward catalogue.

## If something is missing {#if-something-is-missing}

- **Next** is unavailable in **Access**: an ambassador group is required. If no suitable group exists, follow [Create a group for member access](/help/ambassador-programme#create-a-group-for-member-access).
- **Next** is unavailable in **Tickets**: at least one ticket must be selected and the selection completed with **Done**.
- Points controls are missing: open **Loyalty → Rewards** to check whether points are enabled.
- A link no longer allows purchases: check the sale status, referral cap, availability dates and ticket capacity before sharing it again.

For a setup or access problem you cannot resolve, use **Need more help? Message support** below. Include the organisation, event, step reached and error shown. Do not include personal promotional links.

Give a member group personal referral links to share an event’s tickets.

Set up an ambassador sale

GDPR data request export delete account data controller data processor cookie consent This guide explains where to find BASH’s privacy information and how to make a request about personal data. The linked policies contain the full terms.

## Find the relevant policy {#find-the-relevant-policy}

- [Privacy Policy](https://bash.social/privacy): what personal data BASH processes, why it is processed, retention and your privacy rights.
- [Cookie Notice](https://bash.social/cookienotice): cookies, consent and browser controls.
- [Terms & Conditions](https://bash.social/terms): the terms for using BASH, including data processing for organisers.

## Understand who handles the data {#understand-who-handles-the-data}

When BASH processes event data on an organiser’s instructions, the organiser is the data controller and BASH acts as a processor. BASH also acts as a controller for some of its own services and purposes. The Privacy Policy explains these roles.

If your request concerns an event, you can contact its organiser or BASH. BASH may need to help the organiser handle the request or forward it to them.

## Request a copy, correction or deletion {#request-a-copy-correction-or-deletion}

1. Email [legal@bash.social](mailto:legal@bash.social).
2. Explain what you want to receive, correct or delete.
3. Include the email address you use with BASH and the relevant event or organisation, if applicable.

BASH can then assess your request and may ask for information needed to identify the relevant data. Do not send passwords, verification codes or private ticket links.

Deleting an account or ending a service does not mean every record can be removed immediately. The Privacy Policy explains retention requirements and exceptions.

## Export people from your organisation {#export-people-from-your-organisation}

You need permission to manage the organisation’s audience.

1. Open **Audience**, then **People** in your organisation dashboard.

[![The People list in a synthetic organisation, with search and selection controls](/images/help/screenshots/privacy-people/people-list-controls.png "Find the intended people before using the selection controls.")](/images/help/screenshots/privacy-people/people-list-controls.png)

2. Select the people you want to export using the list’s selection controls. Check the selection before continuing.
3. Open the selection’s **More options** menu and select **Export as CSV** or **Export as Excel**.

[![The selection menu with Export as CSV and Export as Excel](/images/help/screenshots/ticket-qr-export/audience-people-export-menu.png "Choose a format in More options after selecting people.")](/images/help/screenshots/ticket-qr-export/audience-people-export-menu.png)

4. Check that your browser downloads a file for the people you selected.

Treat the file as personal data and share it only where needed. If the export is unavailable or you need a different data copy, use the support steps below and describe the scope you need. Privacy requests can be sent to [legal@bash.social](mailto:legal@bash.social).

## Stop syncing a provider audience {#stop-syncing-a-provider-audience}

To stop importing updates from a Brevo or Mailchimp list, disconnect that provider from **Settings → Integrations**. People already imported to **Audience** and their email preferences remain. See [Stop syncing a list](/help/import-and-sync-your-audience#stop-syncing) for the steps.

## Manage cookies {#manage-cookies}

1. When BASH shows a privacy banner, read it and the linked [Cookie Notice](https://bash.social/cookienotice).
2. Choose the option you want:
   - On the website, select **Decline** or **Accept all**.
   - In the dashboard, select **Accept essential cookies only** or **Accept all cookies**.
3. Check that the banner closes after you choose.

[![The website privacy banner with Cookie Notice and Privacy Policy links, Decline and Accept all](/images/help/screenshots/privacy-people/website-cookie-banner.png "Read the notice before choosing. Website and dashboard cookie buttons use different labels.")](/images/help/screenshots/privacy-people/website-cookie-banner.png)

If you have already made a choice and need help changing it, use the support steps below.

You can also delete or block cookies in your browser settings. This may sign you out or affect saved preferences and features. Removing cookies does not delete your BASH account or the personal data held for it.

For help using a control:

1. Select **Need more help? Message support** below this article.
2. Add the step reached and error shown.
3. Select **Open support message** and review your draft before sending it. Use the privacy email above for a personal data request.

Find BASH’s privacy documents and ask for a copy, correction or deletion of personal data.

Help with BASH

Tickets and entry