---
title: "Ticket Reservation"
description: "Set up sales in reservation mode with a participation request"
url: https://help.meetingapplication.com/en/articles/9497438-ticket-reservation
collection: "Ticket sales and participants registration"
updated: 2026-10-22
language: en
alternates: [pl]
---

# Ticket Reservation

Set up sales in reservation mode with a participation request

## Ticket reservation

In the Meeting Application, you can run open ticket sales and distribute entry passes, or limit the ability to get a ticket only to selected participants. We know that sometimes you need to organize an event where the number of spots is limited, or you need to verify who’s allowed to come.

For these types of events, **ticket reservation** is perfect — this mode lets you consider each request individually. You don’t have to worry anymore about competitors checking out your ideas or guests from outside your target group showing up 😏 Thanks to our solutions, you’ll always be ready and informed!

## Ticket reservation mode

To enable ticket reservation mode, in the Admin Panel, go to the tabs **CREATE → ACCESS → TICKETS**, then click Payment Methods in the top right corner — there you’ll find the _PARTICIPATION REQUESTS_ option. Flip the switch next to the sales mode with participation request so that it turns blue, which means it’s enabled.

Configure available [tickets](https://help.meetingapplication.com/pl/articles/9497436-bilety.md), add [discount codes and coupons](https://help.meetingapplication.com/pl/articles/8006066-kody-rabatowe-i-znizki.md) if needed, [registration forms](https://help.meetingapplication.com/pl/articles/8031756-formularze-zbierania-danych-podczas-rejestracji.md), connect [payment methods](https://help.meetingapplication.com/pl/articles/8032127-wybor-bramki-platnosci.md), [set up invoices](https://help.meetingapplication.com/pl/articles/9497435-faktury.md) and necessary [regulations and consents](https://help.meetingapplication.com/pl/articles/9497434-zgody-dla-uczestnikow-wydarzenia.md), adjust [email contents](https://help.meetingapplication.com/pl/articles/8031592-komunikacja-mailowa-z-uczestnikami-wydarzenia.md), then publish the tickets. From this moment, anyone who wants to get a pass (paid or free) will need to be approved by you, the Organizer.

![](https://staticfiles.gleap.io/ghelparticle/gzGztFaE1CXpilApHlnIqAQgjaGIjW4udREO1SFs9mE9jNff5GtmqwnxD3Q51s2ldwoNIvjxK5t.png)

![](https://staticfiles.gleap.io/ghelparticle/tVNmOKFp7pE9ouMsPzNTEvsowczgTEM5zPQTsHaFntI0HLhgbLcCUBGlQ5CcCJxOOPdHFZpstn0.png)

## Participation requests

All participation requests sent on behalf of potential participants can be found in the **MANAGE → PARTICIPATION REQUESTS.**

![](https://staticfiles.gleap.io/ghelparticle/ByTiJZ8s9A5iWo7Y6K1B3WzImuDdfIZlUwly0Btx6rYzHIe7TGZ5phq12e0uMEM5uyjgOsIWdYt.png)

Here you'll see all requests with their current **statuses**:

-   **New**: new request, waiting for approval from the Event Organizer
    
-   **In progress**: request reviewed by the Organizer, waiting for payment/action from the Participant
    
-   **Completed**: request processed, successfully finished → Participant got a ticket
    
-   **Rejected**: request processed, rejected by the Organizer → Participant cannot get a ticket
    

In the **Buyer** column, you'll see the first and last name (if the ticket is personalized) and the payer's email address, plus the total gross amount of the order right next to it.

**Order contents** can be viewed by clicking on individual **item packages** (set of tickets, add-ons).

Inside the window with the order contents, you can also preview the answers to the **registration forms** attached to specific tickets.

![](https://staticfiles.gleap.io/ghelparticle/IQbHTZ4m7m8gXZXgrQ6Oy1haIxsAQpPojmGawm1orw2zLrmVCh7RJ648UdzDxTAVTFrZ6dLvo3h.png)

If the buyer selects the option ☑I want an invoice, you'll see the entered company details here.

![](https://staticfiles.gleap.io/ghelparticle/S4evtZoPoqaXD5wB55GiG0WrIQqIaIgjrSYd0XEw8rQYvbcCwiXUJEkMjsB252HHrmvwgcSuNvE.png)

## Actions

### Accept or Reject

When a new participation request for the event comes in, the system lets you **accept** the request or **reject** it. Both actions are available in the **Participation Requests** table in the **Actions** column.

![](https://staticfiles.gleap.io/gattachments/qsLYrAw3IbLkEeh1zRZJnJgMeOUXIOQJVlhi7AKVXRHzTtvQoCnrvBQnneQQr9pPxzZ8o1bj8Qc.png)

When you reject a participation request, a window will pop up letting you add a note, so you can check at any time why this particular participation request was rejected.

![](https://staticfiles.gleap.io/gattachments/1Q23HJSS33GysVP8YkYZUT5xQGxbXsvnSqXtsZuFqPSnE6CLbVq1ttwcoub2g0Udd4KnCW2apIC.png)

### **Change from Accepted → Rejected**

This option is available **only for paid tickets**, until the tickets are paid.

Reversing an acceptance cancels all pending transactions, and the administrator can add a reason for the decision, which will be saved in the history in the Admin Panel.

> **Info:** The note with the reason for rejecting the request is only visible to the system administrator.

### **Change from Rejected → Accepted**

This option is possible **during the active timeout period** (3 days from submitting the request or from the last canceled payment). After that time, changing your decision is no longer possible.  
After accepting participation, the system will automatically send an email with a payment link to the user.

> **Warning:** Changing from YES to NO is possible until the ticket is paid for.
> For free tickets, changing your decision from YES to NO won't be possible.

![](https://staticfiles.gleap.io/gattachments/EvVh5uDAfVdARfHKgV1TWoulvvXzwlzOTL8JcQwZ5HUAt07J21Yc9Z7fTIADXVyc1wp9lTVgdt9.png)

## Participant's Action and Submission History

> **Success:** The action history is assigned to the email address of the participant wanting to get a ticket. Thanks to this, in any future submissions by the same person, the history will show all previous actions by the Administrator who accepted or rejected the participation request.

In the **MANAGE → PARTICIPATION REQUESTS** tab, there's an extensive history of submissions, thanks to which you can check at any time all actions taken for a given email address. When you hover over the icon in the **History** column, the system displays a full activity log: all acceptances, rejections, cancellations, and additional notes left by administrators. This way, you get instant insight into the participant's previous submissions and can make informed decisions about further processing.

The history feature and the ability to change your decision let you efficiently manage submissions, keeping full transparency and control over the registration process for events that require participant verification.

![](https://staticfiles.gleap.io/gattachments/Aj2bHbmglt3QLOMmd04ANKfeZBCCv3kH5pN7EITcN4bYrJ0Np6jwL0dxYhENJWE6dIKcM5RIjga.png)

## Filtering and sorting

Want to see only a specific range of records? You can sort and filter all requests however you like using the arrows next to the column names and filter attributes.

An up arrow next to a column means records are sorted in that column in ascending order - the lowest value will be first, and the highest last. Similarly, a down arrow means the record with the highest value in that column will be first.

Filtering is available in the top right corner after you click the **Filters** button. You can show records for a selected date range (from → to, from, or to) and by request status. The order and display of individual columns can be edited - you can adjust which information you want to see to match what you need right now.

If you use the same filter parameters repeatedly, save your settings for later by clicking **Save filter** - system and your saved filters can be found in **Loaded filters**.

![](https://staticfiles.gleap.io/ghelparticle/8yx4gIL3qb1shRSTZm7uiv0VB8ANgOuHQODx8PsWWZxYBRWmxBZeaC7GEpgpIZGyrv6UOd9sM0b.png)

## User Path

A Potential Participant of your event will go through the payment path just like a standard ticket buying process—the only difference is that instead of getting straight to the payment and receiving a confirmation email with a ticket, they’ll see a message saying the ticket purchase is limited by the Organizer’s verification.

![](https://staticfiles.gleap.io/ghelparticle/L8zwmbdLnILtpAQskKBVkVtWFceLdAOFPZWYCOT4oSaeu7etooD3ygJgKmf7BcUWh58GN8BQCy0.png)

![](https://staticfiles.gleap.io/ghelparticle/t88r2PGROhlNnV4cimtpAW2unPJBIzi5ffT5An1yZBL3KJLbWxCvjv1lBlOTrFxw0JIhlRQHhbS.png)

### **Emails sent during participation request handling**

Depending on the admin’s decision and the payment status, the system automatically sends the right email messages to participants. That way, the user is always up to date on the status of their request and knows what to do next.

The system sends [m.in](http://m.in).:

-   **mail about submitting a participation request** – confirmation that the application has been sent to the Organizer,
    
-   **mail about accepting the request** – with a link to start or complete the payment,
    
-   **mail about rejection** – information about not being able to participate,
    
-   **mail about starting payment** – with the option to retry the transaction if the user interrupted the process,
    
-   **mail about changing the request status to rejected** – informing about the decision changing from YES to NO
    
-   **mail about changing the request status to accepted** – informing about the decision changing from NO to YES, with a link to payment
    

You can edit and customize the content of individual emails in the **MANAGE → Custom E-mails**, so the communication matches the tone of voice of your event.

You can find more details about configuration and types of messages in [**THIS ARTICLE.**](https://help.meetingapplication.com/pl/articles/8031592-komunikacja-mailowa-z-uczestnikami-wydarzenia.md)

> **Success:** Remember to change the banner in all system emails that might be sent for your event to the one dedicated to your event.

![](https://staticfiles.gleap.io/ghelparticle/XWpJxwc8Db4ejeU2QnyUi1yRNH6XU3bOf5gceHBNIRBevkxqvqhA1P4QSJakjw01Hx3K1cXRYdg.png)

### **User journey - tl;dr**

1.  the user selects a ticket,
    
2.  fills out the registration form,
    
3.  sees a message: “Reservation is waiting for confirmation”,
    
4.  gets an email confirming the request was sent,
    
5.  after acceptance – an email with a payment link,
    
6.  option to retry payment multiple times,
    
7.  after a successful payment – the ticket gets assigned,
    
8.  after a failed payment – retry option,
    
9.  after timeout – the request expires, ticket goes back to the pool.
    
10.  to get a ticket, you need to go through the cart process again.
     

## **Ticket payment in Reservation mode**

After receiving participation approval, the system sends the Participant a confirmation email with the payment link.

> **Info:** The participant has 3 days to pay for the ticket. After 3 days, the system will automatically cancel the transaction and the ticket will return to the pool of available entries.

To get a paid ticket, you need to make the payment within 3 days of your participation request being accepted.

### **3-day timeout and expiration rules**

Timeout is the period in which the participant has to pay for the ticket after the request is accepted.

**Timeout = 3 days (first session at midnight).**

We count the timeout:

a) from the moment of **request acceptance** – if the participant hasn't started the payment,  
b) from the moment a webhook is received from the gateway: **canceled / failed** – if the user started the payment but didn't finish it (returns to payment method selection; closes the payment gateway page).

After the time limit is exceeded:

-   the system changes the status to _Overdue_ or _Rejected, overdue_,
    
-   tickets are automatically returned to the pool,
    
-   no possibility for re-acceptance.
    
-   from the cart after returning from the payment gateway (LP scrolls to the top automatically),
    
-   from the **MyOrders** tab (separate tabs: Orders and Participation requests),
    
-   from links in emails sent when:
    
    -   payment is started (new email),
        
    -   payment fails,
        
    -   participation request.
        

### **Change of payment method**

The participant can switch between gateways:

**PayU** ↔ **Stripe** ↔ **Autopay**

Exception:

-   after selecting **proforma invoice** the payment method is blocked,
    
-   if the organizer **rejects the payment for the proforma** → the ticket goes back to the pool → the user has to start the process again.
    

**Have a great event with Meeting Application!**