Contacting support in another language: keep statuses and timing precise
Automatic translation can help with a report, but it may blur order closed, registration completed and account blocked. Start with a short factual description, then translate it while preserving order references and non-secret status labels.
A useful structure is what you intended, which step you performed, what appeared and what you want clarified. Include the date and time zone with timestamps. Keep the exact error wording when possible rather than replacing it with nothing works.
Read the translation before sending. Check that a code appeared but was not accepted has not turned into no code arrived. Amounts and the action sequence should remain unchanged too. Do not place active codes, passwords or payment secrets in a third-party translator.
If a term is uncertain, include the original label beside the translation and identify the screen where it appears. A good report can be several simple sentences. Polished language matters less than preserving the difference between an observation, an assumption and a request. That distinction helps support investigate the actual problem.