> For the complete documentation index, see [llms.txt](https://loggix.gitbook.io/indephr-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://loggix.gitbook.io/indephr-docs/creating-surveys/question-types.md).

# Question Types

### Overview

Choosing the right question type is essential for collecting accurate and meaningful responses. Each question type is designed to capture a specific kind of input, and selecting the appropriate format helps ensure that responses are clear, consistent, and easy to analyze.

Indephr provides multiple question types to support different survey needs, from simple selections to detailed feedback.

***

### Why question types matter

Using the correct question type helps you:

* Collect structured and relevant data
* Make it easier for respondents to answer
* Improve response accuracy
* Generate clearer and more useful reports

Selecting the wrong type may lead to incomplete or unclear responses.

***

### Common question types

Below are the commonly used question types in Indephr:

***

#### Single Choice

Allows respondents to select **one option** from a list.

**Best used when:**

* Only one answer is applicable
* You want a clear and direct choice

**Example:**\
What is your primary reason for using this product?

***

#### Multiple Choice

Allows respondents to select **more than one option**.

**Best used when:**

* Multiple answers may apply
* You want to capture a range of preferences

**Example:**\
Which features do you use regularly?

***

#### Rating Scale

Allows respondents to rate something on a scale (for example, 1 to 5 or 1 to 10).

**Best used when:**

* Measuring satisfaction or experience
* Comparing performance or opinions

**Example:**\
How satisfied are you with our service?

***

#### Open-Ended (Text Response)

Allows respondents to provide a detailed written answer.

**Best used when:**

* You want qualitative feedback
* You need detailed opinions or suggestions

**Example:**\
What improvements would you like to see?

***

#### Yes / No

A simple binary choice.

**Best used when:**

* You need a clear confirmation or decision

**Example:**\
Would you recommend this product to others?

***

### Choosing the right question type

When selecting a question type, consider:

* What kind of response you need (choice, rating, or text)
* How detailed the response should be
* How easy it is for respondents to answer
* How the data will be used in reports

Choosing the right type ensures better data quality and easier analysis.

***

### Best practices

To use question types effectively:

* Keep the format simple and easy to understand
* Avoid mixing too many different types unnecessarily
* Use rating scales consistently across the survey
* Provide clear options for choice-based questions


---

# 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://loggix.gitbook.io/indephr-docs/creating-surveys/question-types.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.
