Cet article n'a pas encore été traduit. La version anglaise est présentée ci-dessous.

Running a Service Business in Two Languages Without Being Forced Into English

Pick your language once, and ToolBerry speaks it back, instead of forcing your whole crew onto one.

Par L'équipe Toolberry17 septembre 20265 Temps de lecture :

Mise à jour de l'17 septembre 2026

Pick your language once, and ToolBerry speaks it back, instead of forcing your whole crew onto one.

Picture a two-truck plumbing outfit. The owner grew up speaking English and runs the books, the schedule, the invoices in it. One of the two techs learned the trade in Spanish and still thinks in Spanish when he's under a sink. They're doing the same job, on the same app, at the same time. Most field service software has a quiet assumption baked into it: pick a language for the account, and everyone uses that one. So either the tech works in his second language all day, or the owner hands him a phone set to Spanish and hopes nothing gets lost translating it back.

ToolBerry doesn't make either of them choose. Language in ToolBerry isn't a setting on the business. It's a setting on the device.

Why "pick one language for the business" is the wrong model

Most software treats language like a company decision: someone picks it during setup, and it applies to everyone who logs in after that. That's fine if your whole crew shares a first language. It falls apart the moment they don't, which is common. . A single-language account forces someone on nearly every multi-person crew to work in their second language, every day, on top of the actual job.

How other apps handle this

Jobber and Housecall Pro both offer genuine Spanish-language support, but the scope of that support is worth looking at closely.Jobber’s Spanish experience is focused on non-admin users in the mobile app. The field crew can use the app in Spanish, while the admin experience and desktop platform remain in English. Housecall Pro takes a different approach, allowing users to switch the mobile app to Spanish, but several elements-including statuses, alerts, and user-created content such as line items, job descriptions, and checklists-remain in English unless they are manually created in Spanish.

In both cases, Spanish is primarily a localized layer over an existing English product rather than a fully bilingual experience. The system does not automatically maintain both English and Spanish versions of every piece of system-generated and user-created content.

What "per device" actually means

In ToolBerry, the language you see is tied to the device or browser tab you're using, not to your account and not to the workspace. Set your phone to English and your tech's phone to Spanish, and you're both looking at the exact same job record, the exact same schedule, at the exact same time, each rendered in your own language. Nobody's setting overrides anybody else's. There's no "admin language" that the rest of the business has to defer to.

That also means the same person can run English on their laptop at the shop and Spanish on their phone in the truck, if that's genuinely how their day splits. The app doesn't care which device asked, only what that device has picked.

The honest part: what actually re-translates, and what doesn't

This is worth being precise about, because "runs in two languages at once" can quietly overpromise if we're not careful.

Two different things are happening under the hood, and they behave differently:

The app itself, the menus, buttons, field labels, and the job types and statuses that came pre-built with your industry template, translate live, per viewer. Pick English, see English. Your tech picks Spanish, they see Spanish. Same underlying record, two renderings, because that vocabulary is on a shared translation list ToolBerry ships with.

Anything you or your crew actually type, a custom job type you name yourself, a note, a custom field's value, a renamed label, is stored exactly as typed, in whatever language it was typed in, and every viewer sees that same text. If your Spanish-speaking tech creates a brand-new job type called "Limpieza de desagüe," an English-viewing owner sees "Limpieza de desagüe," not an automatic "Drain Cleaning." It isn't translated on the fly, because it was never on the pre-built list to begin with, it's just data, the same way a customer's name or a job note is just data.

We'd rather draw that line clearly than let "two languages at once" sound bigger than it is. The structure of your workspace, the built-in vocabulary, follows each viewer's language. The things you write yourself don't get auto-translated for anyone, ever. If you want the job types your Spanish-speaking tech creates to also read in English for you, that's a naming choice on your end for now, not something the app does automatically.

How to actually start

Open ToolBerry on your own device and set your language from the profile menu, English, Español, Português, or Français.
Have your tech, or your bilingual customer-facing person, do the same on theirs. Nobody has to match.
Work the same job from both ends. The schedule, the built-in job types, the menus all read correctly for each of you.
If you name your own job types, fields, or checklist items, do it in whichever language you want the whole team to see it in, since that text is fixed once it's typed.
Missing a language your crew actually needs? Email us. Adding one to the list is cheap on our end.

Have a question?

Email us at contact@toolberry.net, especially if your crew needs a language we don't list yet.

Download the app from App Store · Get it on Google Play, or read more at toolberry.net.

Free. Works offline. Runs in the language each of you actually works in.