How do you label speakers in a WhatsApp chat translation that has no names in the text?
TL;DRA client submitted a year of WhatsApp chat screenshots in Haitian Creole, with French and English code-switching, as bona fide marriage evidence. The original messages carried no speaker labels in the text. We attributed each line to either '[You]' or the saved contact name '[Hubby♥]' — both labels the app itself prints in its reply-quote boxes. No gender or identity was inferred by the translator. The certified translation was delivered for the client's USCIS filing.
Case Specifications
- Document
- Personal correspondence — WhatsApp chat screenshots
- Foreign Name
- Konvèsasyon chak jou (Haitian Creole)
- Country
- Haiti
- Languages
- Haitian Creole, French (code-switching), English (code-switching) → English
- Submitted To
- USCIS (I-130 / I-485, bona fide marriage evidence)
What We Received
A client submitted three batches of WhatsApp chat screenshots, photographed onto single pages by month. The chats were in Haitian Creole, with frequent French and English code-switching. The contact in every chat was the saved name of the client's spouse, including a heart emoji. The translation was needed as personal-correspondence evidence for an I-130 / I-485 filing.
The packet was a <a href='/documents/text-message-translation'>certified text-message translation</a> spanning more than a year of daily messages. Each line had to be attributed to its sender — but the source carried no name on each line.
Why This Required Special Handling
WhatsApp screenshots have no speaker labels in the text — the only built-in signals are visual (bubble color and alignment). A flat transcription drops both, and the reader cannot tell who said what.
Adding '[Him]' or '[Her]' labels breaks a core rule of <a href='/documents/certified-translation'>certified translation</a>: the translated text must reproduce, not infer. Gender is not in the source, and a label that requires a guess can silently flip when applied across hundreds of bubbles in a multi-batch order.
How We Handled It
We labeled every line with only the markers WhatsApp itself prints in the source. Right-aligned outgoing bubbles became '[You]' — the exact label the app uses in its reply-quote boxes for the phone owner's messages.
Left-aligned incoming bubbles took the contact name from the chat header, including the heart emoji. Both labels are visible inside the source, so a second translator can verify any attribution against the same screenshot.
We added one more rendering rule. WhatsApp's reply feature became '↳ Replying to [Speaker]: <quoted text>' indented before each reply. System rows — voice calls, missed calls, voice messages — were marked '[System]' or '[Voice message, M:SS]' and italicized. Embedded photos, forwarded files, and Status reshares were described in brackets at the speaker's position.
"Translator's Note (used on every deliverable in the order): Speaker labels are taken directly from how the source app itself labels the parties. '[Hubby♥]' is the contact name shown in each chat header and in the source's reply-quote boxes. '[You]' is the label the source app itself uses for the phone owner's outgoing messages (visible in the gray reply-quote boxes labeled 'You:'). No gender or identity has been inferred by the translator; '[You]' corresponds to the right-aligned (outgoing) bubbles and '[Hubby♥]' to the left-aligned (incoming) bubbles in each screenshot."
Two supporting standing notes accompanied the certification block on every batch. One documented the language mix — Haitian Creole bodies with French and English insertions preserved verbatim. The other documented bracket conventions for non-text elements so an adjudicator could distinguish voice messages, system rows, and shared media from typed text at a glance.
The Outcome
Eight deliverables were rendered under the same order number, each using the same convention. The packet was delivered to the client for inclusion in their USCIS marriage-based filing.
We have since used this convention on other foreign-language chat orders covering <a href='/immigration/i-130'>I-130 evidence</a> and I-751 evidence, with no RFE related to speaker attribution. The pattern works on any messaging app whose UI prints both the contact name in the header and a phone-owner label in reply-quote boxes.
What This Means for You
If you submit chat screenshots as evidence, the translation should not invent speaker labels. Use markers visible in the source — the contact name and the app's own 'You:' label. Any reader can then verify each attribution by re-reading the screenshot.
Have a similar situation?
We handle multi-month WhatsApp, iMessage, and Telegram chat translations for I-130, I-485, and I-751 evidence packets.
Related Cases & Resources
Sources & References
- Meet Translation Requirements·USCIS·Verified 2026-05-23
- I-130, Petition for Alien Relative·USCIS·Verified 2026-05-23
Explore the Hub
Languages
Immigration
Accepted By
All identifying information has been removed from document images. Case details are shared with client permission. No personal data is stored or displayed on this page.