I am experiencing a character encoding issue with WhatsApp Flows that occurs exclusively on the WhatsApp Web/Desktop client. While the Flow renders perfectly on mobile devices, special characters (accents/diacritics) appear corrupted in the browser.

Key Observations:

• Dynamic vs. Static: The issue only affects dynamic lists (options populated via script/JSON). Static text defined directly in the Flow layout (WELJ) renders correctly on both platforms.

• Failed Workarounds: I attempted to use Unicode escape sequences (e.g., \u00f3), but the web client renders them as replacement characters (e.g., F�rmula).

• State Persistence: Interestingly, if I complete the Flow on a mobile device and later view the submitted response in the chat history on the web, the characters appear correctly.

• Environment: I am using Blip as the orchestration platform to generate the dynamic payloads.