One campaign can have two vocabularies
The visitor needs questions, explanations, validation errors, consent language, and next-step expectations in the language of the route. Intake, however, may depend on a shared set of picklist values, tags, and workflow conditions.
In Case Growth Solutions' multilingual injury implementation, English and Spanish dog-bite flows maintain language-specific summaries while the English answers are translated back to the exact values expected by the shared GoHighLevel fields.
Normalize the system without erasing context
A canonical CRM value makes reporting and automation dependable. A readable case summary in the submitted language helps intake understand what the person saw and how the answer was phrased.
Both are useful. The structured value supports routing; the localized summary preserves the human context. Neither should be reconstructed later from an ambiguous free-text note.
The technical handoff must be language-safe
Phone and email validation, server-owned tags, attribution capture, assignment IDs, consent timestamps, and CRM error handling should behave consistently across routes. A language switch must not drop campaign parameters or change which workflow receives the contact.
When both routes share a CRM location, field options and mappings need an explicit compatibility test. A translated label that does not match the accepted picklist can otherwise turn a valid inquiry into a delivery error.
QA each route as a complete funnel
Review mobile layout, long labels, error copy, keyboard behavior, privacy and terms links, disqualification screens, and the final CRM record in each language. Do not approve one route by assuming the other is structurally identical.
The practical standard is simple: every language path should preserve meaning for the visitor and produce an intake record that the receiving team can route without guessing.