Websites & patient experience · Practical guide

Tell visitors which language replies will use

A visitor writes through a translated enquiry page and expects a response in that language. The practice may need to arrange support or may use a different reply process. Someone who sends an enquiry in their preferred language needs to know what to expect in return. State the practice's actual reply arrangements and any support that can be discussed.

Read the guide Make your action list
Healthcare website and appointment calendar displayed on devices at an empty clinic reception.
Make the website useful for the people who use your practice.

What to change

Describe the actual response arrangement before the enquiry is sent. Confirm what the receiving team can provide, and avoid promising language support based solely on translated website content.

A worked example

Illustrative example

A translated contact page explains how to request a reply in a preferred language and that the team will confirm the available arrangement. It does not automatically assign a language-capable staff member.

Healthcare website design showing connected desktop and mobile service and enquiry layouts.
Make the service and next step clear on every screen.
Healthcare website accessibility illustrated by a focus outline, keyboard key, contrast samples and form.
Review keyboard access, contrast and understandable form fields.

Put it into practice

Do not let the language of the form imply that every member of staff can respond in it. Ask reception to check the acknowledgement too; it should not make a broader language promise than the team can fulfil.

Include the same language-support explanation in the acknowledgement where useful. It should prepare people for the next contact, especially if the form and the team's reply use different languages.

What to agree before publishing

Ask the receiving team to describe its actual language support before publishing the promise. Distinguish the language of the interface from the language used for replies and any appointment arrangements. If support requires discussion, give that route clearly. Review the acknowledgement as well, since it may be the message visitors keep while waiting. The website should make contact easier without leaving somebody to discover after submission that the expected conversation cannot happen in the language they assumed.

How to check the result

The visitor understands how their language preference will be handled after submitting the enquiry.

A mistake to avoid

Do not imply that an automatically translated page creates a guaranteed staffed response service in the same language.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore websites & patient experience services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.