How do you label speakers in a WhatsApp chat translation when the messages have no names attached?
TL;DRA bona fide marriage packet contained twenty-one Haitian Creole WhatsApp screenshots — daily conversations between a married couple. The original messages have no built-in speaker labels; bubble color and alignment are the only indicators of who sent each line. We labeled every line with markers WhatsApp itself prints in the source — '[You]' (the phone owner) and '[Hubby♥]' (the contact) — so no gender 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 pou ane 2025
- 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 PDFs assembled from phone screenshots of WhatsApp conversations with a contact saved as 'Hubby♥' (a heart emoji in the contact name). The first PDF carried eight chat screenshots arranged on a single page under monthly headings — 'Septanb,' 'Oktob,' 'Novanb,' 'Desanb' — covering September through December 2025. The second PDF covered January through April 2025 in the same layout. The third PDF, titled 'Kèk mesaj ki montre kesyon finans ak sipo nou yonn pou lot' ('Some messages showing financial matters and the support we give one another'), contained five additional screenshots from 2026.
The conversations were in Haitian Creole with frequent French and English code-switching — typical of how many Haitian-American couples write to each other day to day. The translation was needed as personal-correspondence evidence accompanying an I-130 / I-485 filing demonstrating a bona fide marriage. See our overview of <a href='/guides/bona-fide-marriage-evidence'>bona fide marriage evidence</a> for the category in context.
A first round of work on this order had been delivered without speaker labels on some screenshots, and with [Him] / [Her] labels on others — many of which were flipped relative to the actual bubble layout. The packet had to be rebuilt to be faithful end-to-end before USCIS submission.
Why This Required Special Handling
WhatsApp chat screenshots do not include the sender's name on each line. The only signals of who sent a given message are visual — outgoing messages are right-aligned with a colored (yellow on iOS) bubble; incoming messages are left-aligned with a white bubble. A flat text transcription that drops both signals leaves the reader unable to tell who said what — fatal for evidence offered to demonstrate the texture of a relationship.
The obvious workaround — labeling each line [Him] or [Her] — fails the basic principle of certified translation: the translated text must contain exactly what the original contains, nothing added, nothing inferred. Gender is not in the source; assigning it requires the translator to guess which side of the conversation belongs to which spouse, line by line. When the translator gets that wrong on even a single screenshot, the labels flip silently and the packet contradicts itself. In the first attempt on this order, that happened repeatedly.
USCIS adjudicators reading certified translations expect the rendering to reproduce — not interpret — the source. Translator-introduced labels that can be inverted by a misreading of bubble color are a structural weakness, not a stylistic one.
How We Handled It
We rebuilt the packet using only labels WhatsApp itself prints inside the source: '[Hubby♥]' is the contact name shown in each chat header and in every reply-quote box (when a message replies to an earlier one, the original sender's name appears above the quoted text). '[You]' is the label WhatsApp prints in those same reply-quote boxes whenever the quoted message was sent by the phone owner. Both labels are visible in the screenshots; neither is invented by the translator.
We then anchored every message line to one of those labels by bubble alignment alone: a right-aligned bubble is '[You]' (outgoing from the phone owner); a left-aligned bubble is '[Hubby♥]' (incoming from the contact). A second translator can verify any attribution in the deliverable by looking at the same bubble in the source — there is no translator judgment to second-guess.
Three additional structural decisions kept the rendering tight: messages that quote an earlier message (the WhatsApp 'reply' feature) are rendered as a small indented '↳ Replying to [Speaker]: <quoted text>' line immediately before the reply; system-generated lines (Voice call — N min; Missed video call — Tap to call back; Voice message — duration) are marked with a '[System]' or '[Voice message, M:SS]' prefix and italicized so the reader can tell them apart from typed messages at a glance; embedded photos and forwarded attachments are described in brackets at the speaker's position, never as plain prose.
"Translator's Note (on every deliverable in this 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 Translator's Notes accompanied the certification block on each deliverable: one documenting that the original messages mix Haitian Creole with French and English words (e.g., 'Bonjour boo,' 'Yes cherie I'm still stuck on a flight,' 'Merry Christmas, my love'), with English and French content that appears verbatim in the source preserved as written; and one documenting that 'RD' in the September chat is rendered as 'DR' (Dominican Republic), the standard English-language abbreviation for that country.
The Outcome
Three rebuilt deliverables — covering September–December 2025, January–April 2025, and the 2026 financial-conversation batch — were issued under the same order number on the same day. Roughly 1,100 translated words across twenty-one screenshots, each line attributable to its speaker by inspection of the source. The packet was delivered to the client for inclusion in their USCIS filing.
We have used this same WhatsApp speaker-label convention on subsequent foreign-language chat-translation orders for I-130 and I-751 filings without an RFE related to speaker attribution. The pattern generalizes to any messaging app whose UI prints both the contact name in the header and the phone-owner label in reply-quote boxes — WhatsApp, iMessage, Telegram. See our companion case on <a href="/cases/whatsapp-chat-embedded-attachments-uscis-i-130">handling embedded attachments inside chat translations</a> for the related rendering decisions on the same order.
What This Means for You
If you are submitting WhatsApp or other text-message screenshots as bona fide marriage evidence, the translation should not invent speaker labels the source does not contain. A <a href='/documents/personal-correspondence'>certified translation of personal correspondence</a> that anchors each line to a label already printed in the screenshot — the contact name from the chat header and the app's own 'You:' label — preserves who-said-what without asking the translator to guess gender or identity.
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-19
- I-130, Petition for Alien Relative·USCIS·Verified 2026-05-19
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.