A business chooses a piece of software for its features, its price and its fit with existing systems. Language rarely makes the list. Yet in a country with many spoken languages, the language of the screen, the template and the automated message decides who can use the tool and who can be understood by it. Customer follow-up shows this most clearly, because it is where the business has to be understood by someone who did not choose the software.
This piece looks at how language barriers enter through software choices, and what a business can check before it commits. It is a hypothesis drawn from general guidance on internationalisation and accessibility, not a finding about any particular South African employer.
Where language hides in a software choice
South Africa has several official languages, and most workplaces use several in daily speech even when one is used on paper. The tools a business adopts usually assume a single one. That assumption shows up in at least four places.
- The interface. Staff who are fluent in conversation may be slower and less certain in a second or third language on screen, particularly with technical menu terms.
- The templates. Reminders, quotes, confirmation messages and survey requests arrive in the tool's default language unless someone sets up alternatives.
- The data fields. Names, addresses and notes may not accept the characters, word order or honorifics that customers use.
- The support material. Help pages, training videos and error messages are often available in only one or two languages.
None of these is a defect in the tool. They are choices made by the vendor for its largest market, and the business inherits them when it buys.
What the standards and vendor guidance say
The World Wide Web Consortium's introduction to internationalisation and localisation explains that internationalisation means designing a product so that it can be adapted to different languages and regions without engineering changes, and that localisation is the adaptation itself. The distinction is useful for a buyer. A tool that was designed for adaptation can add a language through settings. A tool that was not may require expensive customisation or may never support it.
The same body's guidance on declaring the language of content and on text size in translation shows how much detail is involved: character encoding, text direction, the ability to mark which language a passage is in, and the ability to expand text, since translated text is often longer than the original. A buyer does not need to master these topics, but a vendor that cannot answer simple questions about them is giving an answer of its own.
Customer-facing messages carry a second concern. Private businesses are generally free to choose the languages they use with customers. That freedom is exactly why the choice is worth making consciously instead of letting the software choose by default.
An illustrative case
Consider an illustrative example, not a real case: a Polokwane dental practice with two practitioners and a reception team that speaks Sepedi, English and Afrikaans between them. The practice adopts an appointment and follow-up tool that sends reminders and recall messages in English only, with no option to switch.
The receptionists end up retyping the important reminders by hand in the patient's language, because several older patients ignore the English ones. The work is invisible, falls on the staff who speak the other languages, and stops entirely when they are away. Patients who would have answered a message in their own language instead miss appointments, and the practice reads this as indifference when it is, at least in part, a language problem.
The human tax: access and dignity
The first cost is access. A customer who cannot easily read a message cannot easily act on it, whether it is a reminder, a quote or a request for payment. The barrier is not the customer's failure to understand. It is the business's decision, usually unintended, to speak in only one voice.
The second cost is dignity. Being sent an automated message in a language you do not read well can feel like being treated as an afterthought. For staff, the cost is similar but internal: working all day in a second language on screen, translating on the fly for customers and being quietly expected to do it without recognition. Those staff often become the human interface that the software never was, and the burden falls on them unevenly.
There is also a quieter cost to the business's picture of its own customers. If follow-up messages in one language get a response and those in another do not, the results can look like differences in customer quality when they are differences in access.
What could realistically change
Language support is not an all-or-nothing demand. A small business cannot translate everything into every language. It can, however, choose tools that make adaptation possible, and then decide deliberately which messages matter enough to adapt first. The note on why accessibility is also an operational question makes the wider case that access problems are operational problems, and the time tax of re-explaining the same thing describes the cost of doing by hand what a tool should carry.
Practical next actions
- List the languages you actually serve. Look at your customer base and your staff and write down the languages in use, in order of how many people they reach. This is your requirement, whatever the software defaults to.
- Add language to your buying checklist. Before purchase, ask whether the interface, templates and help material can be set to each of those languages, and whether the tool stores and prints names and notes correctly.
- Test with a real message. Send a sample reminder or quote to a colleague who reads the other language and ask whether it is clear, polite and correctly formatted. Longer translated text often breaks layouts.
- Translate the few messages that matter most. Start with reminders, payment requests and anything involving safety or cost. Have a fluent speaker write them, instead of relying on raw machine output.
- Record who is doing the translating. If particular staff are quietly covering the gap, make the work visible and share it, and consider whether it belongs in their role and reward. The piece on the skilled professional reduced to copy and paste describes what happens when skilled people become human adapters for a tool.
The business outcome
A business that matches its software to the languages of its customers gets more responses to the same effort. Fewer appointments and payments are missed, fewer hours are lost to retyping, and the staff who speak the extra languages are no longer an unpaid layer of customer service. The business also gains a clearer view of its customers, because differences in response can then be read as differences in need, not in access.
The human dividend
The dividend is predictability and access: a customer who knows what a message says, and a staff member who is not asked to quietly bridge a gap the tool should have closed. The reward is also a form of respect, since being addressed in a language you read comfortably tells you that someone thought about you before sending the message.
The trade-offs
- More languages mean more upkeep. Every translated template must be revised whenever the original changes, or the versions drift apart.
- Machine translation is uneven. It can be useful for a first draft but can produce errors or awkward phrasing in languages with less training material, so it needs a fluent reader.
- Language is not a stereotype. Not every customer of a given background prefers a given language, so offering a choice is better than assuming one.
- Tools with language options may cost more. The extra price should be set against the cost of missed follow-up and hand translation.
Why it matters
Software choices feel technical, but they decide who a business can speak to. When language is part of the selection, follow-up reaches more people and the burden of translation stops landing on a few staff by default. When it is not, the barrier is built in quietly, and the business may never see it, only its effects.
Sources and further reading
Related Mellorca reading
- When Rural Connectivity Decides Who Can Work Remotely
- The Small Business Priced Out of Its Own Tools
- When Digital-Only Leaves Some Customers Behind