Totally agree. Since we have no reasonable* way to collect country in a chatbot conversation**, we created almost 25 workflows to take IP country and populate in the Country property, e.g. If IP Country is CA then set property Country to Canada. This is a bit of a show stopper for us if the bot can’t identify the IP country.
* We can’t present the user with 100+ buttons to choose from their country and we can’t ask them to type it in since that free text field might not match exactly the country value in the country picklist e.g. United States, vs USA vs US or even typo.
**We need this for routing leads to the correct regional Sales teams, but from the user perspective there is no need to provide the country he is in as it’s totally irrelevant to what he wants. This is why we have no other option to than to use IP country.