Decide How to Represent Accented and Non-Latin Names in Email

Separate the address from the name people see

An email address is a routing identifier; a display name is what recipients may see in their mail app. Do not assume that changing the address requires changing the person’s preferred name. Ask each person how their name should appear in everyday communication, including accents, spacing, and order. Record that preference in the appropriate profile or directory process, if available, while following the organization’s access and update rules.

Explain any technical limits plainly. Address rules can vary by mail system and by the systems an organization connects to. Before deciding that a character cannot be used, confirm the actual constraints of your setup rather than relying on a colleague’s guess. Do not promise that every external recipient’s provider will display a name identically.

Choose a default transliteration rule

If the address format cannot represent a person’s original characters, define how the organization converts them. For example, decide whether accented letters are reduced to their base letters, whether spaces and hyphens are removed or replaced, and how to handle characters that have more than one common Latin-letter rendering. Apply the same rule to comparable names across departments, locations, and seniority levels.

Avoid ad hoc choices based on what a manager finds easiest to spell. Ask the person concerned to review the proposed form, especially when a conversion could produce an unwanted word, resemble another employee’s address, or differ from the person’s established transliteration. A consistent default is a starting point, not a reason to dismiss a reasonable individual preference.

Preferred display name: [Márta Nagy]
Default address form: [marta.nagy@example.com]
Person’s confirmed preference: [marta.nagy@example.com]

Check for collisions and practical confusion

Before assigning an address, check whether the proposed form is already in use or could be mistaken for another person’s address. Follow the organization’s approved naming convention for resolving collisions, such as a consistent separator or another permitted distinction. Do not quietly add personal details that the employee did not agree to share.

Also consider how the address will be communicated: on business cards, in a directory, and in messages to customers or partners. A clear display name can help recipients recognize the sender, but it does not eliminate the need to confirm the address itself. Ask the employee to review both fields before the account is treated as ready.

Make exceptions possible without making them arbitrary

An exception may be appropriate when the default transliteration conflicts with a person’s established spelling, creates an embarrassing or misleading result, or makes the address unusually difficult to distinguish. Keep the process simple: the employee explains the requested form and practical reason; an authorized administrator checks whether the mail environment supports it and whether it conflicts with existing addresses; the designated approver records the decision.

An exception is not a promise that every external service will accept or display the chosen characters. If the requested address is unsupported, explain the constraint and discuss the closest workable option with the employee. Keep the preferred display name accurate even if the address must use a different form.

Document the decision so it can be repeated

Store the decision where the people who administer accounts can find it, with access limited to those who need it. Record the employee’s preferred display spelling, the assigned address, the default rule that was considered, the approved exception and its reason, who approved it, and who owns any later changes. Note any technical limitation that shaped the decision. Avoid collecting extra personal information just to justify a spelling choice.

Documentation helps when an account changes hands, a directory is updated, or a new administrator applies the policy. It also makes patterns visible: if many people need the same exception, the default may need revision. Set a sensible review point, such as when the person requests a change or when the organization changes its address rules, rather than repeatedly asking someone to defend their name.

• Confirm the preferred display name directly with the person.
• Apply the published conversion rule, then check for address conflicts.
• For an exception, record the request, reason, approver, assigned form, and change owner.
• Share the final display name and address with the employee for confirmation.

Confirm the result in real use

After the account details are set, have the employee check the profile or directory view available to them and send a message to an internal colleague who can confirm what appears in the recipient view. Verify the sender display name and address separately. If the organization uses other directories or business systems, check those through their normal authorized processes too; a change in one place may not update every connected record.

If something is wrong, correct the relevant field and repeat the check. Do not treat a successful internal display as a guarantee about every outside mail provider. The goal is a usable address, a name presented as the person prefers, and a recorded decision that another authorized administrator can understand and apply.