Turnkeyxgaming

Guide · Live

A translated UI is not a local dealer

Live players notice the language the dealer speaks. A client translated into Portuguese with an English-speaking dealer is an English table. Calling it a Portuguese table produces a complaint in the first minute.

7 min readUpdated By the Turnkeyxgaming team

Label the voice, not only the menu

The catalogue should tell you the dealer language where the studio provides it. Put that on the tile. UI language is a separate setting and follows the player's account. Do not infer one from the other. A Turkish interface on a Turkish-speaking roulette table is the match you want. A Turkish interface on an English table is still worth offering, and it is worth naming honestly.

Studios such as Vivo, Ezugi and the larger live brands exist partly so you can fill languages. Enable the tables that match the audience. Do not enable every language because the switch is there, or the lobby becomes a wall of tables nobody on this brand will join.

When the dealer changes mid-shift, the language on the tile has to change with the feed, or you take the language claim off until the studio states it again. A flag painted into the table art is not a statement. Studios reuse backgrounds. If the catalogue field is empty, describe the table without a language word. Guessing from the presenter's name or from the UI locale is how the first complaint is written in the opening minute.

Voice, interface, and the art on the tile

Three different signals get called 'language' in a live lobby. Only one of them is the dealer. Label that one, and do not let the others impersonate it.

SignalWhat it tells youWhat you may claim on the tile
Dealer language from the catalogueThe language the studio says the presenter is speaking.That language, as a voice label. Update it when the studio updates the field.
UI locale on the accountWhich translation of the buttons and the rules the player asked for.Nothing about the dealer. Leave the account locale alone when they sit down.
A flag baked into the thumbnailWhatever the art department drew.Nothing. Do not read a language out of a flag.
An empty catalogue fieldThe studio has not stated a voice.No language claim. Describe the table without one, or hold it back until they confirm.

Honest language labels

  1. 01

    Voice on the tile

    Show the dealer language the studio states. Do not guess from the flag in the art.

  2. 02

    UI is separate

    Keep client language on the account. Do not overwrite it to match the dealer.

  3. 03

    Edit the list

    Enable languages you have an audience for, not the full menu.

Portuguese buttons do not make a Portuguese table

Players hear the dealer before they read the chips. An English-speaking presenter with a translated interface is an English table that happens to have Portuguese chrome. Call it that.

The presenter changed and the tile kept yesterday's word

A table carried a Hindi label because the catalogue said so, and for two shifts it was true. On the third evening the studio put an English-speaking presenter on it and updated the field at 19:54. The tile kept the old label because it had been cached at 14:00 with a six-hour lifetime. Eleven players joined between 20:00 and 22:00 expecting Hindi, and two of them wrote in during the first shoe.

A label about a person is not a property of a game build, and people move. Treat the dealer language like the table limits: a catalogue value that can change during an evening, read at render or on a refresh the player can trigger, rather than a string baked into a translation file when the tile was designed. When the field is empty the tile should lose the word rather than inherit the previous one. A blank is information, because it says nobody has committed to a voice.

Record what the player was actually offered. The session row should hold the table id, the language the catalogue stated at that moment, and the time it was read. When a complaint arrives the question is not what the table speaks tonight but what the tile said at 20:07, and without that field the argument is between a player's memory and a translation file that can prove nothing about Tuesday.

What to keep when a player sits at a live table

  • Table id and studio id, since two studios can give a wheel the same display name and support will be sent to the wrong one.
  • The dealer language as the catalogue stated it when the tile rendered, with the timestamp of that read rather than of the session start.
  • Whether the value was present or empty, kept as a record. A blank is a fact, not a gap to be filled from the flag in the thumbnail.
  • The UI locale requested on the launch and the one the client reported rendering, which are two fields and often two answers.
  • The shift boundary if the studio publishes one, so a complaint about the second half of an evening can be checked against the right presenter.
  • Who last changed the catalogue value and when, because that is the first thing the studio will ask and the last thing a log will offer.

FAQ

Questions operators ask

What if the studio does not state a dealer language?

Do not invent one. Describe the table without a language claim, or leave it off until the studio confirms.

Should we overwrite the player's UI language so it matches the dealer?

No. The account language stays. A Turkish-speaking player at an English table still needs Turkish buttons if that translation exists. Matching the voice by force hides the rules they can read.

Why not enable every dealer language the studio offers?

Because the lobby becomes a wall of tables this brand's players will not join, and the language row stops meaning anything. Enable voices you have an audience for. Leave the rest off until you do.

Two tables share one thumbnail and only one has a Hindi presenter. How do we tell them apart?

With the table name and the limits, both from the catalogue, and a language label only on the table whose field supports it. Art is reused across a studio's tables, so the picture cannot be the differentiator. If the two are otherwise identical in the lobby, that is a merchandising problem the tile is papering over.

Can we call a table multilingual when the presenter changes mid-shift?

Only in the words the studio uses, and only if they state it. Describing a table as Hindi because one shift had a Hindi presenter is the error that generates the first-minute complaint. If the voice varies, say the language is not guaranteed, or leave the claim off and let players judge for themselves when they sit down.

Keep reading

Related pages

  • Product · Live dealerLive casinoRoulette, blackjack, baccarat, game shows, teen patti and andar bahar on one dealer-table wallet and one GGR report, per licensed market.Read
  • Studio · Vivo GamingVivo GamingVivo Gaming live roulette, baccarat and blackjack. Label each table with the language the dealer actually speaks, not the client's.Read
  • Studio · EzugiEzugiIntegrate the Ezugi API through one aggregator: regional live dealer tables, including teen patti and andar bahar, per market.Read
  • Guide · LiveVIP table limitsHow minimum and maximum stakes define a live table, and why a VIP wheel should not share a lobby row with a low-limit one.Read

Get a written quote and sandbox access

Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.

Telegram @turnkeyxhub WhatsApp Email Contact form