# Chatbot - How to disambiguate selections across multiple drop downs

**URL:** <https://devforum.zoom.us/t/chatbot-how-to-disambiguate-selections-across-multiple-drop-downs/41385>\
**Category:** API and Webhooks\
**Created:** [January 24, 2021, 4:19am UTC](https://devforum.zoom.us/t/chatbot-how-to-disambiguate-selections-across-multiple-drop-downs/41385 "2021-01-24T04:19:54Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![breynoldszoom](https://avatars.discourse-cdn.com/v4/letter/b/a88e57/32.png) [@breynoldszoom](https://devforum.zoom.us/u/breynoldszoom)\
**Post date:** [February 23, 2021, 4:39am UTC](https://devforum.zoom.us/t/chatbot-how-to-disambiguate-selections-across-multiple-drop-downs/41385/7 "2021-02-23T04:39:19Z")

</div>

Thanks for the feedback Max,  
I understand the desire to keep the chat name.  
I’ve written up a feature request with some suggestions that ties this together with some other issues I ran into. Hopefully it will be useful in whatever you all come up with down the road.

> [@Better NLS and Backend Widget Processing Suggestion](https://devforum.zoom.us/t/better-nls-and-backend-widget-processing-suggestion/41538):
>
> Is your feature request related to a problem? Please describe. The “key” field in the API design for widgets is doing double duty as a label. This leads to an unnecessary burden on develpers of NLS aware systems. Describe the solution you’d like Add an ‘internalKey’ field to better enable National Language Support (NLS) and disambiguate values in the backend. For example, the page at has an example which includes this field, { “editable”: true, “value”: “Zoom”, “key”: “Company” } (…

---

_[View the full topic](https://devforum.zoom.us/t/chatbot-how-to-disambiguate-selections-across-multiple-drop-downs/41385)._
