> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/parametrage-produit/personnalisation-de-la-fiche-client-participant/demander-les-informations-concernant-le-participant-a-posteriori-de-la-commande.md).

# Request information about the participant after the order

The post-order participant information request feature is a valuable option to simplify the online purchasing process while ensuring that you collect the necessary information about the participants of an activity. This approach helps optimize the conversion rate by minimizing the fields required at the time of ordering and then requesting additional information via a personalized email. Here’s how to use it effectively.

### Steps to use the feature

#### Access product configuration

1. Log in to your Yoplanning.pro back office.
2. Navigate to the **Products** section under the **Administration** tab.
3. Select the product for which you want to configure this option.

#### Configure the product

1. In the product sheet, look for the "participants" tab
2. Answer **No** to the question: "Do you want the details of each participant?".
3. Just below, determine which fields you want your customers to fill out for this product when booking.

**Note:** If you answer **No** to the question about the details of each participant and you define at least one field as optional or mandatory, this will automatically trigger requests for information after the order.

#### **Configure the information to ask participants**

1. Access settings

* In the **"Administration"** menu, click on **"Configuration"**.
* Go to the **"Personalized Data"** section.

1. Add a custom criterion\*\*

* Click on **"Customer File"**, then on **"Add"**.
* Enter and save.

1. Associate criteria with products

* Once the criterion is created, it will appear in the **list of available data**.
* You can then activate it in the **"Participants"** tab when editing your product.

#### **Access the functionality of the data entry of participants at the counter**

At the counter, you have the option to **manually enter participant data**:

1. Go to the **relevant session**.
2. Click on the **participant name**.
3. Select **"Edit"**, fill in the required information, then click **"Save"**.

This feature allows you to easily manage and update participant information according to your needs.

#### Customize the email template

1. Go to the **Online Sales** section of the product sheet.
2. Edit the post-booking message template to include a specific tag, along with some explanatory text, that will insert a link for customers to provide the missing information. Here's the tag: `%participant_details_url%`.

#### Automate a reminder

1. If you want to send a reminder to customers who have not yet completed this information, use the **Activity Reminder** message template.
2. Check that in the template, you have correctly integrated the following tag: `%post_booking_message%` which allows you to include the link in activity reminders.
3. Schedule this reminder in the product sheet to be sent, for example, 24 hours before the activity.

### Usage tips and best practices

* **Message Clarity:** Make sure the explanatory text preceding the tag in your emails is clear and actionable, encouraging your customers to fill in the missing information.

### Common Problems and Solutions

* **Issue: Customers not filling out information** **Solution:** If some customers are not providing the requested information after multiple reminders, consider contacting them directly via phone or text message to ensure you have all the necessary data.
* **Issue: Email Tag Errors** **Solution:** Please verify that the tag inserted in your emails is correct and functional. An incorrect tag could prevent customers from accessing the form to enter their information.

### Update: Counter Use

We have removed the limitation that did not allow this feature to be used at the counter. Now, when you simply register a quantity for a customer, the system will ask for the information of each participant.

#### Example scenario

* Initially, you have for example Patricia Martin with a quantity of 5.
* As Patricia's colleagues fill out the form with their own details (name, first name, height, weight, shoe size, etc.), they are created in the system.

This feature is essential to combine efficiency and quality of service by reducing barriers to purchase while ensuring that the necessary information is collected on the participants in an activity.


---

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

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

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

```
GET https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/parametrage-produit/personnalisation-de-la-fiche-client-participant/demander-les-informations-concernant-le-participant-a-posteriori-de-la-commande.md?ask=<question>&goal=<endgoal>
```

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

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

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