TallyT
Tally
Jul 12

"Other" option

- Add an "Other" option for multi-select, checkboxes... - Automatically show a short answer field if user chooses "Other" - Keep "Other" at the end and do not randomize it
CompletedCompleted

Mar 28, 2025

An amazing addition,thanks

Apr 9, 2024

Introducing the "Other" option! Now available for multiple choice, dropdowns, checkboxes, and multi-select questions. Simply activate it in the :: menu, customize the text, and start gathering free text responses alongside your predefined choices. Additionally, we've added "Lock options in place" setting, which is available only when "Randomize options" is enabled. This setting keeps important choices like "None of the above," "Don't know," or "Not applicable" fixed in their original positions while randomizing the rest of the options to prevent bias in responses. It also allows you to use your custom "Other" text input while locking its position at the bottom of the list. Hope you like it. All feedback is welcome! ☺️

Apr 9, 2024

Filip Minev 👏🏻👏🏻 an amazing addition, thanks!

Apr 18, 2024

Filip Minev Nice addition, but is there a way to require that the user fill in the text box? Right now, as far as I can tell, if the field the Other option belongs to is required, a user can select "Other" and leave the box blank, and that passes validation.

Apr 18, 2024

Ryan Masuga Not for the moment. It would be best if that's added as a separate feature request, so we can gauge the interest for it. Right now, if you use the manual Other field setup, you can make the free text input required or not: https://tally.so/help/how-to-create-an-other-option#362bda02…

Mar 18, 2024

I'm in favour of this feature, but one caveat: Please also keep the current way of doing this for those who like to keep the freeform answer field responses separate from our structured / set responses. It can make some data analysis use cases cleaner and faster, this way.

Jan 11, 2024

Because this feature is not built-it, the options can't be randomized.

Dec 23, 2023

The main problem with the proposed workaround is when moving questions, you have at least x2 more blocks to move. And because bulk block movement isn't supported, it's x2 more work.

Aug 3, 2023

Hi Van Ngo, I've edited you're suggestion and merged it with an other one :)