Product feedback: Detecting an end-user's language



Posted Feb 23, 2022

Hi,

In all of our instances we have full setup of Zendesk on EN language, staff members use interface on EN language in most of the cases, but our End-users are NL, EN and DE speakers, that’s why we have all 3 languages enabled in Agent Workspace and in Guide.

However, let's imagine that we represent NL company and we need to provide support on NL language primarily, all automatic notifications sent to end-user must use NL language. 

Our concern is about how Zendesk understand end-user language and update end-user Language in end-user profile according to it.

We have many cases when NL speaker types some words that Zendesk System understands as ENGLISH language and changes it in end-user profile accordingly. This change affects CSAT surveys and they send in half-English in this case (example below):

We've found a workaround for this and we are using "employee" tag added to staff members accounts. So if staff member send a ticket - language is set to EN always, and if someone submit a ticket and there is no "employee" tag - language will be updated to NL by the trigger.

Our concern is next, we would like to have an option like to toggle on/or off and decide by ourselves if we want to have end-users language to be detected and updated and set automatically by Zendesk or no.

So ideally for us, we would like to have setting for auto detection of language toggled off or maybe to have another solution for placeholders like ones for CSAT, so they won't be auto translated and we would be able to set them in one language and make sure that they're not auto translated, as this is causing bad end-user experience .

Thanks!


7

4

4 comments

hi Jake,

 

Intelligent triage is coming with Advance AI add-on, which we do not use in our company. We need to have a solution for this use-case, without add-ons.

2


Hi everyone! Have you explored using intelligent triage in any of your workflows? This allows for routing and business rule customization based on the language the end-user uses to start the conversation. It is also dynamic in that it will match the language on each ticket, so multilingual customers will get the experience on a per ticket basis rather than based on the language set on their profile.

We're curious how this might align with the workflows you are using, and any feedback you might have from your efforts?

0


+1 on this. This will be definitely be more efficient in our use-case as well. 

3


+1 

2


Sign in to leave a comment.

Didn't find what you're looking for?

New post