# The five-question limit

Discord pop-up forms are capped at **5 components**. Each form question is one component, so the cap on a form is **5 questions per panel option**.

This applies to both ticket panels and application panels. There is no way to split a form across more than one pop-up that lets a form stretch to 6 or more questions. That option does not exist in Ticket King.

## Why this is enough for most forms

Most tickets and most applications do not need more than 5 questions to start. If you want to add a sixth, you can usually combine two questions instead.

A good form is fast for the member. Five questions take about a minute. A long form leads members to rush it or give weak answers.

## What "1 component" means

* 5 text inputs is 5 components.
* 4 text inputs and 1 dropdown is 5 components.
* 6 text inputs is over the limit.

The dashboard hides the Add Question button once you have 5 questions on an option.

## Designing within the 5: combining related questions

Ask fewer, broader questions instead of many narrow ones.

**Four narrow questions:**

1. Operating system?
2. OS version?
3. App version?
4. Build number?

**One Paragraph question instead:**

1. **Environment details.** Your OS, app version, and build number.

The member writes everything in one paragraph. Staff still get all the information, faster.

## Designing within the 5: using the opening embed

Some "questions" are really instructions to the member, not information you need them to type into the form. Move them out of the form and into the option's opening embed:

> **Before staff can help with billing, please paste:**
>
> * Your order number
> * The email on the account
> * A screenshot of the error

The member sees these once the ticket opens and provides them in their first message. This saves form slots for the questions you must have.

## Designing within the 5: using Inactive questions

Each question has an **Active / Inactive** toggle. Inactive questions stay saved but do not appear in the pop-up.

If you have drafted 8 candidate questions, set 3 to Inactive and run the form with 5. After a week, look at what staff still have to ask in tickets, then swap inactive questions in to test alternatives.

## What the cap does not mean

* It does not mean you can only collect 5 pieces of information per ticket. Once the ticket opens, staff can ask more questions in the channel.
* It does not mean applications can ask more questions than tickets. They use the same cap of 5.
* It does not change with premium. The cap is Discord's, not Ticket King's, and it applies to every plan.

## What to do if you need more

If you need 8 or more structured questions:

1. Ask 5 in the form, then ask the rest in the ticket channel after it opens.
2. Split across two panels. A first panel asks the first 5, and after acceptance you direct the member to a second one.
3. Use a form outside Discord, such as Google Forms or Tally, and have members paste a link in their ticket.

There is no way to ask more than 5 questions in a single form.

## Related

{% content-ref url="/pages/7CkCeZCrgltqb0qqKg5z" %}
[Question types](/docs/forms/question-types.md)
{% endcontent-ref %}

{% content-ref url="/pages/XQsrUSeSCzERWqbhESgi" %}
[Applications overview](/docs/applications/overview.md)
{% endcontent-ref %}


---

# 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://ticketking.xyz/docs/forms/five-question-limit.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.