Article summary
Keep WhatsApp avatar observations completely separate from user language preference in a multilingual Luxembourg +352 workflow.
A Luxembourg +352 phone, name and avatar together still cannot reliably choose the language a customer prefers. Language routing must follow user choice or evidence from an actual conversation.
Priority of language evidence
| Evidence | Usability |
|---|---|
| Explicit user selection | High |
| Confirmed support conversation | High, dated |
| Content preference | Supporting |
| Name/avatar/+352 | No automatic assignment |
Avatar checking does not return language
It may return phone, business-account observation, avatar and mapped phone. Language labels remain a separate business-system concern.
Offer a choice when language is unknown
Use a neutral entry that lets the customer select and later change preference. Sales should not inspect an image and decide.
+352 supports numbering only
Preserve phone_raw and country evidence. The code does not prove residence, citizenship or language.
A blank avatar does not mean communication difficulty
Keep not_observed, visibility_limited and task_unknown separate, and do not lower customer priority.
Separate TXT and preference tables
Upload one phone per line while language_preference stays internal. Returned Excel cannot overwrite a confirmed choice.
A mapping does not copy language
When a new phone relates to a customer, language still comes from the customer record, not phone country or avatar.
Minimise access in an EU context
Agents needing language routing do not access images. The operating organisation assesses purpose, transparency, retention and rights.
The simple Luxembourg answer
Ask the customer rather than guess. An avatar may have a limited use; language selection is not one.
