# Radio

### Use Cases: 

✅ Exclusive choices: Use the "Radio" component when you want users to select a single option from a predefined list of choices. It ensures that users can only select one option among the available ones.

✅ Multiple-choice questions: "Radio" components are suitable for presenting multiple-choice questions or scenarios where users need to pick one answer from a set of options.

### Not to Use Cases:

 ❌ Single-option scenarios: Avoid using "Radio" components when there is only one option available, as it unnecessarily adds complexity to the user interface. In such cases, consider using other input methods like checkboxes or buttons.

❌ Multi-selection needs: Do not use "Radio" components if you need to allow users to select multiple options from the list. In such cases, checkboxes or multi-select components would be more appropriate.

<br>


---

# 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://2600hz.gitbook.io/sds/sds-3.0/sds-components/components/radio.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.