> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-forms/builder/question-types/choice-fields.md). # Choice fields: Single, Multiple, Dropdown Single choice, Multiple choice and Dropdown questions in Dapta Forms: List vs Cards layouts, the Label / Value / Points / Icon option row, the emoji, letters and image icon picker, importing options f Choice questions give respondents a fixed set of options. They are the questions that carry points, drive branching and map cleanly to CRM properties, so they do most of the work in a lead qualifier. This page explains every control in the **Options** section, plus what each of the three types looks like to respondents. | Type | Gallery hint | Respondent behaviour | | ------------------- | ------------ | ------------------------------------------------------------------------------------------------ | | **Single choice** | Pick one | One option. In the **Slides** layout the form advances as soon as they tap; no button needed. | | **Multiple choice** | Pick several | Any number of options. They confirm with the button (or Enter). | | **Dropdown** | Compact list | One option from a compact, searchable list. Best for long lists such as countries or industries. | Single choice and Multiple choice are the same question with a different selection mode, so you can switch between them from the **Question type** select without losing options, points or icons. *** ## Add options **Step 1:** Click **Add question** and pick **Single choice**, **Multiple choice** or **Dropdown**. Type the question text on the canvas. **Step 2:** Type the option labels directly on the canvas (each new question starts with **Option 1**) and click **Add option** to add more. Or use the **Options** section in **Question settings**, which shows the full editor for every option.

The Options section of Question settings with the Show options as control and three option rows, each with Label, Value, Points and Icon — The **Options** section: layout switch on top, then one editable row per option.

You can drag the handle on the left of each row to reorder options, and click the trash icon (**Remove option**) to delete one. *** ## The option row: Label, Value, Points, Icon

One option row with Label Starter, Value starter, Points 1 and the Icon picker button — Each option has four fields. Hover the ⓘ next to a label to read its help text.

| Field | What it does | | ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Label** | What respondents read on the option. Safe to reword at any time. | | **Value** | What gets stored in the response and sent to HubSpot or a webhook. It is generated from the label (`Starter` becomes `starter`) but you can edit it. Keep it stable: changing it breaks past answers and any mapping that points at it. | | **Points** | Added to the score when this option is picked. Use a negative number to subtract. Integers only; `0` means the option is neutral. See [Scoring](/dapta-forms/logic/scoring.md). | | **Icon** | An emoji, one or two letters, or an image shown next to the label. Empty falls back to the label's initials. | New options are seeded as **Option 1** / `option_1` / 0 points. Below the rows, the **Scoring** switch decides whether this question counts toward the score at all ("Counts this question toward the score. Points from the selected option add to the total; set ranges in Results."). *** ## List or Cards At the top of the **Options** section, **Show options as** switches the layout for Single and Multiple choice questions: * **List** (default): a vertical list of rows. Options can carry an emoji or initials in a circle. * **Cards**: options laid out in a centred grid of tiles with the icon on top. Cards are the only layout that can show a logo (an image icon).

Cards on the canvas. The canvas is what respondents see, icons included.

The canvas updates live when you switch, and the dashed **Add option** tile stays at the end of the grid in Cards mode. Dropdown questions have no layout switch: they always render as a compact list. > **💡 Tip:** Cards work well for 2 to 6 short options with a recognisable icon or logo (plans, industries, tools you integrate with). For longer lists, stay on **List** or switch to **Dropdown**. *** ## Pick an icon **Step 1:** Click the **Icon** button on an option (**Pick an icon**). A small picker opens with tabs at the top.

In the List layout the picker offers Emoji and Letters.

| Tab | What you get | | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | **Emoji** | A curated set in seven groups: Reactions, People, Business, Tech, Communication, Status, Places. Click one to apply it. | | **Letters** | Up to two letters, e.g. HS for HubSpot. Empty falls back to the label's initials. | | **Image** | Only in the **Cards** layout. Paste an `https://` image URL. Logos keep their shape: they are fit inside a box, not cropped to a circle. | | **Clear** | Removes the icon; the option falls back to its initials. | **Step 2:** Switch the question to **Cards** if you want logos, then open the picker again: the **Image** tab appears.

The Image tab takes an https:// URL. Other protocols are refused.

Emoji and letters show in a circle; images get a box they fit inside, so a wide logo is not cropped. If you switch a question with image icons back to **List**, the images are not shown (the option falls back to initials) but the URLs are kept, so switching back restores them. *** ## Import options from a spreadsheet Typing twenty industries by hand is slow. Under the option rows, click **Import options** to paste them from a sheet.

The Import options from a spreadsheet dialog with pasted rows, the Replace options and Add to the end switch, and a preview table with ok, duplicate and invalid score statuses — Paste one or two columns. The preview tells you exactly what will be imported.

**Step 1:** Copy one or two columns from your sheet and paste them in the box. Column 1 is the option, column 2 (optional) is its score. A header row is detected automatically (the summary line says **header skipped**). **Step 2:** Choose a mode: * **Replace options** clears the current list and imports the paste. Note: **Replacing removes the icons your current options carry.** * **Add to the end** keeps the current options and appends the new ones. **Step 3:** Check the preview table (**Option**, **Score**, **Status**) and the summary line (for example **3 valid · 3 with score · header skipped**): | Status | Meaning | | ------------------ | -------------------------------------------------------------- | | **ok** | Will be imported. | | **duplicate** | Same label as an earlier row (or an existing option); skipped. | | **invalid score** | Column 2 is not a number; the row is skipped. | | **rounded to {n}** | A decimal score was rounded to the nearest integer. | **Step 4:** Click **Import {n} options**. Values are generated from the labels (`SaaS B2B` becomes `saas_b2b`) and scores land in **Points**. If your paste has no second column, the dialog says **No scores in this paste. This question keeps its current points.** *** ## Dropdown: searchable for respondents A **Dropdown** uses the same option editor (labels, values, points, import), minus the layout switch and image icons. On the public form it renders as a compact control with a **Type to search…** box: respondents filter the list as they type and pick one entry; an empty filter shows **No results found**. It is the right choice for long, well-known lists where scrolling a card grid would be tedious. Dropdown also accepts a **Placeholder** in **Question settings** (ghost text before a selection is made). *** ## Choice fields and the rest of the form * **Logic:** in **Edit logic**, choice answers use **Matches any of** to show or hide later questions, and **If answer is … then jump to** rules to branch. See [Show & hide conditions](/dapta-forms/logic/conditions.md) and [Branching & jumps](/dapta-forms/logic/branching.md). * **Scoring:** each option's **Points** feed the score; the per-question **Scoring** switch can exclude a question. See [Scoring](/dapta-forms/logic/scoring.md). * **HubSpot:** the **Value** is what is written into a mapped property; use [Value maps](/dapta-forms/connect/hubspot/value-maps-and-static-properties.md) to translate values into the property's internal options. * **Prefill:** `?plan=growth` preselects the option whose value is `growth`. See [Hidden fields & URL prefill](/dapta-forms/builder/hidden-fields-and-url-prefill.md). * **Dynamic questions:** a choice answer can change the wording of a later question. See [Dynamic questions (variants)](/dapta-forms/builder/dynamic-questions.md). ## What's next * [Text & scale fields: Short text, Long text, Website, Slider](/dapta-forms/builder/question-types/text-and-slider-fields.md) * [Scoring](/dapta-forms/logic/scoring.md) * [Question settings](/dapta-forms/builder/question-settings.md) --- # 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.dapta.ai/dapta-forms/builder/question-types/choice-fields.md?ask=&goal= ``` `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.