# Ticket Info

## Introduce

Some websites require you to fill in your name or email for each ticket when purchasing. At this time, you need to configure Ticket Info.

## Create Ticket Info Group

Under the wallet page, click + in the upper right corner to create a ticket info group. Here we use TTM as an example, as shown in the figure:

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

After creation, click + in the lower left corner and add your name and email information in the pop-up box, as shown in the picture:

<figure><img src="/files/3TeMvLVwY33xUg2XY77z" alt=""><figcaption></figcaption></figure>

The format is: name:email If you only need to fill in the name for drop, you only need to configure the name, for example:&#x20;

jack

guanyu

If you only need to fill in the email for drop, then configure the email, for example: 1:xxxgamil.com&#x20;

Just add a number or letter before the colon One line of information, add multiple lines, after filling in, click Save, as shown in the figure:

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

Remember to manually edit the status to ensure that the status of each message is GOOD.

&#x20;If reus is selected, each ticket info may be reused.&#x20;

If you select No for reuse, each ticket info will only be used once, and the status will become unknown.

Note: If you want to fill in the same name/email for all the tickets purchased in a sale, then please configure the same name/email with the same maximum number of tickets for an order currently on sale in the ticket info group, which means that if there is one for this sale An order can purchase up to 4 tickets, then you need to configure 4 identical name/email information in the ticket info group and select reusable.

## Configure Ticket Info in the task

Under the task page, create the corresponding website task and configure the corresponding group in the ticket info group


---

# Agent Instructions: 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:

```
GET https://kylin-inc.gitbook.io/spider-browser/other-modules/ticket-info.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.