We utilise auto translate in workflows, and on welcome, we share a message and offer the visitor options to select based on why they contact us, these selections in turn determine the path of the flow that is followed. The issue is, The welcome message itself is sent in the detected language (browser or location, however this is being picked up), but, the choices (buttons) are displayed in the workspace default language, which is English.
This means that we are contacted from say a Spanish or German customer, we send a localised welcome message, and present the options in English, this makes no sense. Other than setting up individual workflows per language, is there a way to resolve this, if not, I would suggest that the same logic is followed for button translation and those are sent in the same language as the welcome message at the very least.
From research, the button translation comes once the language attribute is “locked in” by FIN, but that doesn’t seem to make much sense to me..