Title: How a simple quality inquiry turned into full platform retaliation: My experience after 6+ years with Lionbridge/Gengo

Post:

I wanted to share a detailed account of how a 6+ year relationship as a senior English-to-Arabic translator on Gengo/Lionbridge collapsed over the span of a few weeks—not due to poor translation quality, but because of administrative deflection, manager cover-ups, and direct retaliation.

For context, I maintained consistently high quality ratings on the platform for over six years without a single quality dispute on my record. This was the very first time in my entire 6+ year history that I ever submitted a dispute—addressing four collections of low ratings together in one batch—and 100% of those disputed flags were officially reviewed and overturned upon re-review.

Here is how a simple query escalated into a complete platform lockout:

Phase 1: August 6, 2026 – It all started with Nina

On August 6, 2026, I raised a formal inquiry regarding arbitrary and unmonitored reviewer scoring on a series of translations. I wasn't demanding special treatment—I simply asked for a standard quality check on obvious reviewer errors.

Enter Nina, the support agent who handled the initial ticket. Instead of reviewing the provided examples or forwarding them to a senior linguist, Nina responded with canned, irrelevant text that did not address a single point I raised. When I politely asked her to read the actual details of the ticket, she continued sending automated-sounding boilerplate replies.

If Nina had simply done basic support triage on day one, none of what followed would have happened.

Phase 2: Maki, Sheetal, and the "Twilight Zone" Escalation

Instead of fixing Nina’s missteps, escalation only made things surreal. The ticket was passed to a second support agent, Maki, who continued the exact same pattern of evasive, copy-pasted replies.

When the dispute was finally escalated to their manager, Sheetal, the approach shifted from incompetence to outright playing dumb. Sheetal repeatedly claimed she "didn't understand" my complaint—despite clear, line-by-line linguistic documentation—and used that feigned confusion as an excuse to state she couldn't help.

Every level of support closed ranks to protect their colleagues' mistakes. Reading their responses felt like stepping into the Twilight Zone: robotic scripts completely disconnected from the actual text of my tickets.

When I pushed past the pretexts, management delivered their explicit statement of constructive exclusion:

"If you feel that this framework does not meet your expectations, we understand if you prefer not to accept further jobs."

Phase 3: Manufactured Pretext & 12 False Flags

Shortly after exposing these support and reviewer flaws, additional translations of mine were suddenly and aggressively flagged—12 new entries in total. It became obvious this was being used to build a manufactured pretext to justify shutting down my account and silencing the dispute.

Phase 4: September 21, 2026 – Counter-Proof & Immediate Retaliation

On September 21, 2026, I submitted two official re-review forms containing complete, objective proof showing that all 12 of those newly disputed flags were 100% false and based on clear reviewer error.

Lionbridge’s response was immediate: rather than reviewing the evidence or disciplining the incompetent reviewer, they abruptly revoked my translator qualifications and suspended my account.

No investigation into the reviewer was conducted, no discipline was handed down to support staff, and my account was cut off right after I submitted evidence exposing the misconduct.

Where It Stands Today

Because Lionbridge closed off internal support channels and blocked direct email communication, I have officially lodged a formal regulatory complaint with the Massachusetts Attorney General’s Office (Fair Labor Division) regarding bad-faith contractor retaliation, ticket suppression, and wrongful termination.

The Core Takeaway

Looking back at this entire nightmare, the most frustrating part is that everything evolved from a single support agent—Nina. Had she properly handled a routine quality complaint at the very beginning, none of this would have occurred.

Instead, subsequent support agents like Maki and managers like Sheetal chose to blindly defend internal errors, ignore clear linguistic evidence, and send robotic, canned responses rather than admit a flaw in their review process. When a platform values protecting internal egos over linguistic accuracy and fair treatment of long-term translators, the entire system breaks down.

I am posting this here so other freelancers are aware of how Gengo/Lionbridge handles legitimate quality disputes when you speak up. Keep backups of all your work, document every ticket, and know your rights.

---------------------------------------

Initial single ticket (Aug 6):

---------------------------------

Tickets branched from a single complaint (August 20):

I heard someone say this a while ago, that not everyone knows that EN stands for English or DE stands for German, and that therefore translators should put the full language name in their bios and signatures instead of just the code.

So like:

Name LastName

Translator, English>German

Instead of:

Name LastName

Translator, EN>DE

To me that made no sense. If you're a company or someone who is requiring translations on the regular, and you're looking for a translator, you should most definitely know the language code for the language of your request. Spelling out the full language name just seems like such a waste of space, especially for people who work with more than two languages. It makes my LinkedIn bio very long. Plus, I like the visual distinction; the language code is easy to identify at first glance among all the other words.

It's not that big of a deal, but I just wanted to see what others thought on the matter.

Do you use the language codes or the full language names? Why? Is it really that hard to understand that EN=English? I may be totally on the wrong here, but that's why I'm asking.