How do Welsh language standards affect CRM for Welsh businesses?

What to take away

What the Welsh language standards require of a CRM interface

Welsh language standards are the duties set by the Welsh Language (Wales) Measure 2011 and enforced by the Welsh Language Commissioner. They apply to public bodies and to some private companies delivering services on their behalf. If your business handles public contracts in Wales, your CRM software may need to treat Welsh as an equal language, not an afterthought.

The standards cover service delivery, policy making and internal operations. In practice, that means a CRM interface language selector, Welsh-language templates for letters and emails, and the ability to record a customer's language preference. A Welsh speaker who phones a council or health board should be able to continue in Welsh, and the CRM record should show that.

The Welsh Language Commissioner can require organisations to produce Welsh-language user interfaces for software that staff use to deliver services. This is where CRM localisation stops being a nice-to-have. If your staff cannot switch the CRM to Welsh, the organisation may be in breach.

Not every Welsh business is caught. A sole trader in Cardigan selling to English-speaking customers has no legal duty. But a marketing agency in Cardiff working for a Welsh government body will inherit language duties through the contract. Check the contract before you check the software.

For public bodies, the standards also cover complaints, recruitment and staff training. A CRM that logs complaints in English only will create a compliance gap. The same applies to case notes, call recordings and follow-up tasks.

CRM software bought by a Welsh public body should be assessed against the relevant standards before purchase. Ask the supplier for a Welsh language interface, Welsh user documentation and a commitment to keep both updated. If the supplier cannot show that, the procurement may fail.

Key dates: the duties come from the Welsh Language (Wales) Measure 2011 and are set out in regulations. The Welsh Language Standards (No. 1) Regulations 2015 applied standards to Welsh Ministers, county councils and national park authorities.

The Welsh Language Standards (No. 2) Regulations 2016 extended the standards to other public bodies, and later regulations brought in further and higher education and other sectors.

Each body gets a compliance notice that lists the numbered standards it must meet, including the service delivery standards for correspondence, telephone calls and software interfaces.

Bodies publish an annual compliance report, usually by 30 June, and the Commissioner can investigate at any time. Check your own notice for the standard numbers and the reporting date that apply to you.

Bilingual CRM communications and customer records

Bilingual CRM communications means the customer can receive letters, emails and texts in Welsh or English, and the CRM records which language they chose. That choice should travel with the contact record, not sit in a spreadsheet.

Customer records need Welsh-friendly fields. Welsh addresses often include place names with mutations and accents, such as "Llanfairpwllgwyngyll" or "Caernarfon". A CRM that strips accents or limits field length will corrupt your data. Test name and address fields with real Welsh examples before you buy.

Welsh-language Companies House and HMRC pages show how official records handle bilingual naming. The Welsh-language Companies House page uses "Tŷ'r Cwmnïau" alongside the English name, and the Welsh-language HMRC page uses "Cyllid a Thollau EF". Your CRM should store both forms where relevant, so invoices and filings match the official record.

See the Tŷ'r Cwmnïau - GOV.UK page and the Cyllid a Thollau EF - GOV.UK page for the official bilingual formats.

Data protection applies in Welsh too. The Welsh-language Data Protection Act 2018 page is available, and privacy notices should be offered in Welsh where the standards require it. The Data Protection Act 2018 page is the reference point for lawful processing.

A bilingual CRM must keep consent records in both languages without duplicating the customer record.

Email templates are the usual failure point. English templates get translated once, then drift as offers change. Build a Welsh template library and assign an owner. If nobody owns the Welsh copy, it will fall behind within a quarter.

Configuring a CRM so staff can work in Welsh

Configuration starts with the interface language. Most mainstream CRM platforms support multiple interface languages, but Welsh is rarely one of them. You may need a language pack, a custom translation or a Welsh-speaking partner.

Follow these steps:

A bilingual CRM interface does not mean every field is translated. Custom fields you create are your responsibility. Budget time for translation of field labels, picklist values and validation messages.

Start with products that already ship a Welsh interface. Microsoft Dynamics 365 lists Welsh among the interface languages it offers, so standard menus, buttons and validation messages can be switched without custom work. Confirm the current language list with the vendor in writing, because Microsoft adds and drops languages between releases.

Microsoft 365 offers a Welsh display language for documents, help desk scripts and training material. Most CRM products do not ship a Welsh interface, so a custom language pack or a partner translation is usually the only route.

Cymdeithas Cyfieithwyr Cymru, the association of Welsh translators and interpreters, keeps a directory of translators who handle software strings and variables.

Reports and dashboards often stay English-only because they are built with vendor-specific query tools. If your board needs Welsh reports, check whether the report builder accepts translated labels before you commit.

Integration points are the hardest part. Payment providers, email marketing tools and accounting software may have no Welsh option. Map each integration and decide whether the Welsh gap is acceptable. For data protection, design around real purposes and minimum fields so that bilingual records do not become a dumping ground.

Where Welsh SMEs can find Welsh-speaking CRM support

Welsh SMEs have several sources of help when choosing and configuring CRM software. Business Wales provides advice and sometimes funding for digital projects, including software that supports Welsh language duties. The Development Bank of Wales can support larger investments.

Chambers of Commerce across Wales, including Cardiff, Swansea and North Wales, run events where you can compare notes with other firms. The Federation of Small Businesses (FSB) in Wales publishes guidance and lobbies on language and procurement issues. These networks are useful when you need a Welsh-speaking implementation partner.

Local CRM partners matter more in Wales than in larger markets. A partner in Cardiff or Wrexham can attend your office, train staff in Welsh and handle translation queries. Remote-only support often cannot. Ask a prospective partner for a reference from a Welsh public body or a Welsh-speaking client.

Universities and colleges in Wales supply translation and localisation talent. Bangor, Cardiff and Aberystwyth have language and computing departments that run placement schemes. A student placement can translate your CRM templates at low cost, though you still need a review process.

Public sector procurement frameworks in Wales sometimes require Welsh language provision. Check the framework's language requirements before you bid.

Welsh-language public bodies and CRM supplier duties

Supplier duties flow down through contracts, not from the regulations directly. If you supply CRM software or services to a body covered by the standards, you may have to provide a Welsh interface and Welsh support.

Complaints can be investigated by the Welsh Language Commissioner, who may also issue enforcement notices. A supplier that ignores Welsh language duties can damage its public sector pipeline. The safe approach is to treat Welsh as a supported language from the start.

Suppliers should document their Welsh language provision in bids. Show the interface, the templates and the support arrangements. A vague promise to "add Welsh later" will not satisfy an evaluator who knows the standards.

Sub-processors matter too. If your CRM uses a third-party email service that cannot send Welsh, the public body's duty is still unmet. List every sub-processor and its language capability in your data processing agreement.

Training materials and help desk scripts should be available in Welsh. If your support team cannot answer a Welsh query, the public body may have to translate for you. That is a cost and a risk.

A CRM localisation test is the evidence a public body will ask for. Without it, the supplier carries the compliance risk. Build the test into your implementation plan and keep the results.

Testing a CRM in Welsh before rollout

A CRM localisation test checks that the interface, data fields, communications and reports behave correctly in Welsh. Run it before rollout, not after. The test should cover the screens and workflows your staff use most.

Use this checklist:

Here is a worked example. A housing association in Carmarthenshire configures its CRM for Welsh. The tester switches the interface to Welsh and finds that the "Save" button still says "Save". The vendor supplies a language pack, but the custom field for "preferred language" has no Welsh label. The tester adds it.

An email template for rent reminders is translated, but the payment link points to an English-only portal. The association decides that is acceptable for now and notes it as a known gap. The test takes two days and catches four issues before staff training begins.

The test should include a native Welsh speaker, not just a translator. Fluent speakers spot awkward phrasing that a translation tool misses. If you have no Welsh-speaking staff, hire a tester for a day.

Record the test results and the fixes. Public bodies may ask for evidence. Keep the test script and the sign-off.

Costs, effort and the honest limits of a bilingual CRM

Cost and effort of bilingual CRM varies widely. Translation of interface labels and templates is a one-off cost, but maintenance is ongoing. Every new feature, campaign or field needs a Welsh version.

Translation is priced per word rather than per hour, so you can estimate before you start. Ask two suppliers for one rate for interface strings and another for customer letters. Rates move with volume, subject matter and turnaround, and strings with variables or placeholders sit at the upper end.

Worked example, using an illustrative rate because suppliers quote differently. Say your CRM has 400 interface strings and each averages 12 words, so around 4,800 words.

At an illustrative £0.10 per word the first translation is about £480. A review pass at half that adds £240, and annual upkeep for new templates and releases might be an illustrative £150 a year.

Configuration effort falls on your team. Someone must own the Welsh content, review updates and train staff. That is a recurring internal cost, not a project cost.

Training takes longer in bilingual settings. Staff need to know how to switch languages, where templates live and how to record language preference. Budget extra sessions.

Vendor support may be limited. Many CRM vendors have no Welsh-speaking support staff, so you rely on your partner or your own team. Check support hours and language before you sign.

The honest limits: some integrations will never be fully Welsh. Payment gateways, mapping services and some analytics tools are English-only. You can translate the customer-facing layer, but the back end may stay English. Accept that, document it and tell customers what to expect.

A bilingual CRM also adds data complexity. Duplicate records in two languages create confusion. Use one record with a language preference field, not two records. For the wider selection criteria, see PECR, accessibility, migration and exit.

Finally, quality checks matter more when two languages are in play. Before launch, review records, permissions, workflow and recovery so that Welsh and English data stay consistent. A bilingual CRM is achievable for most Welsh SMEs, but it is a commitment, not a checkbox.

Common questions