Explain a change of company name

A company name change may feel like a fresh start internally. To an existing customer, it can look like an unfamiliar organisation has appeared in an inbox or on a bill. The announcement therefore needs to answer questions of continuity before celebrating the new identity.

State the relationship directly

Open with the old name, the new name and the date the change takes effect. Explain whether this is a trading-name change, a wider organisational change or something else, using wording checked against the actual situation. Do not say that nothing changes if contracts, payment details, ownership or service arrangements are also changing.

For example, a hypothetical notice might begin: ‘Harbour Workshop will use the name Harbour Design Studio from 12 November.’ The next sentences should explain the consequences relevant to customers. That example supplies a structure, not a claim that a name change has no other implications. Confirm the facts before choosing the reassuring wording.

Answer the questions people will act on

Customers may need to know which email addresses remain monitored, whether existing bookings continue and where to obtain support. Put those answers ahead of the design story behind the name. If an action is required, separate it clearly from information supplied for awareness. Avoid a vague instruction to ‘update your records’ without saying which records and why.

Changes involving invoices or payment instructions need particular care. Use established communication channels and provide a way to verify the notice through contact information customers already know. Do not make a new link in an unexpected message the only verification route. Coordinate the wording with the people responsible for accounts and customer support.

Plan a period of recognition

A temporary ‘formerly known as’ description can connect the identities on the website and ordinary correspondence. Decide where it helps and when it will be reviewed. Keep the old domain or address working where you control it and where maintaining it is appropriate. Explain any limitations rather than allowing messages to disappear without notice.

Prepare a short answer for colleagues receiving questions. It should give the same facts as the public announcement, not a more dramatic internal account. Update downloadable documents and directory profiles as well as the homepage; an old brochure may remain in circulation long after the launch post has vanished from view.

The creative rationale can appear later for readers who are interested. It should not displace the practical explanation. A successful announcement allows an existing customer to recognise the business, understand the relevant change and continue their task without guessing.

Think through a customer who misses the original announcement. They may return months later through an old bookmark or a saved email. The new site should still provide enough context to establish the connection, particularly near contact and account information. A temporary notice on the old destination can be more useful than expecting everyone to have seen a social post on launch day. Test the routes you control before announcing that they will continue working.

Also distinguish public communication from administrative updates. A polished announcement does not update supplier records, directories or internal templates by itself. Prepare those tasks separately and coordinate their timing. The public wording should describe the state customers will actually encounter, not the state the team hopes to reach once all the background work is complete.