Handle a prospect whose company record shows a name change

Check the dated company-name evidence and the entity identifier before changing an active account, then preserve the original conversation under its historical name. A new name is not proof of a new company, a new email domain or permission to restart an old sales sequence.

Preserve the conflicting names and the point of discovery

Start a change record when a current company source conflicts with the name on an active account. Save the previous account value, its stable record key and the source that revealed the new name. Note when you discovered the conflict separately from when the change took effect. A website announcement, a revised email signature and a register entry may describe different events. Do not turn the date you saw a new logo into the official change date.

Identify the practical consequence. An open proposal may use the old name, an account display may confuse a colleague or a reply may arrive under a different label. These are separate affected items. List them before editing the account so that the team can check each one afterwards. A cosmetic display correction does not automatically update an issued proposal, and editing a historical message would erase the context you need to explain why the old name appeared.

Freeze any automatic name replacement within the affected workflow until the identity is checked. The task is not to rename every matching string across the database. Two companies may have similar names, and the old label may appear in an attachment unrelated to this entity. Use stable account and document references rather than a global search-and-replace. Preserve the evidence of the mismatch so that the responsible reviewer can distinguish a simple dated change from a transfer to another organisation.

Establish the event rather than assuming a rebrand is a legal change

GOV.UK states that a company name does not officially change until Companies House registers it. Its public company-information service includes previous company names. Use the relevant official record to check the entity and the dated event. The scope of this guide is an operational account correction after the evidence is established; it does not instruct a company how to make a legal change or decide the consequences for a particular contract.

Compare the identifier in the old account evidence with the identifier in the current record. If they disagree, do not describe the event as a confirmed name change merely because the branding looks continuous. It may require a separate entity investigation. Keep the mismatch explicit and hold the proposed rename. If the available record shows the same entity with a previous name, record the actual dates and the supporting document reference. Do not substitute an undated third-party directory for the dated evidence.

Distinguish a registered-name change from a trading label used alongside it. A current website may introduce a new brand without changing the registered company name. In that situation, a verified alias note may be appropriate instead of replacing the legal-name field. The evidence determines which task you have. Keep both labels where they serve different purposes, and do not use a name-change workflow to bypass the more difficult question of whether another company now operates the business.

Fill a fictional dated-change decision

The following account case is entirely fictional and uses no real company identity. An active record contains Old Name O and an established entity identifier. A current fictional official extract identifies New Name N, lists Old Name O as a previous name and records a dated change for that same identifier. The reviewer records the old value, new value, effective date, discovery date and source reference. The proposed correction applies to the current registered-name field on the existing account.

The fictional case also contains an earlier conversation and a draft proposal. The conversation keeps its original wording and timestamp. The draft proposal is flagged for its owner to review before issue; it is not silently rewritten by the data correction. The current display can show New Name N with a dated former-name note, while the existing opportunity remains on its original stable record. The decision makes no claim about contract continuity or any customer obligation.

In the contrasting fictional case, a website says “our new name” but the available company identifiers differ and no dated continuity evidence resolves them. The current registered-name update remains on hold. The team records the announcement as a source observation without calling it a verified legal change. These are constructed examples of accepted and unresolved decisions, not real account outcomes. A live correction requires the actual identity evidence and review of the documents affected in that particular account.

Preserve the original conversation and inspect active documents

Do not rewrite the body, sender details or attachments of an earlier message to make the history appear current. Instead, add a dated explanatory note through your approved recordkeeping process. A later reader should understand both the name used at the time and the established current name. Preserve objections and closed statuses as well. A company-name correction does not erase a request not to be contacted or convert an earlier refusal into a new opportunity.

Inspect active outputs individually. A draft quotation, supplier questionnaire or meeting brief may require its owner to decide which name belongs in the document. An issued contractual document may need authorised commercial or legal review; this guide supplies no automatic amendment rule. Record the item, its owner and its actual review status. Avoid marking every downstream item complete after changing a single account field. A truthful exception list is more useful than an unsupported claim that all references have been updated.

Check for duplicate accounts created when the new label first appeared. Their existence is an exception to investigate, not permission to combine histories immediately. The confirmed name change helps identify the relationship, but each affected record still needs a preview of opportunities, restrictions and attachments before any separate merge decision. Keep this correction bounded to the current name and its dated evidence. Wider consolidation belongs to a distinct reviewed operation with its own scope and recovery method.

Review the current route without inventing a new address

A registered-name change does not establish a change of domain, employee role or email address. Check the communication route needed for the active task independently. A reply in the existing thread may provide context, while a current official company contact statement may establish a published business route. Do not generate a replacement personal address from a new brand name. A plausible naming pattern is not evidence that the address belongs to the same person or is appropriate for the conversation.

If a message asks you to move sensitive information or change commercial instructions, follow your organisation’s independent verification process rather than relying on the name-change story. The account correction itself does not validate that request. Keep document sharing limited to the established recipient and purpose until the relevant check is complete. This is an operational precaution, not a claim that every name change is suspicious. The point is to avoid treating one verified fact as verification of an unrelated request.

Where the contact route remains unknown, keep the current-name evidence but hold the route-dependent activity. The record can be correct while a follow-up remains unapproved or undeliverable. Document who will resolve that separate point and what evidence is missing. This guide does not provide a legal permission to send marketing or a product feature that automatically tracks company changes. The actual outreach and document controls continue to apply, regardless of how confidently the company’s new name has been established.

Check the update and leave a usable undo record

Preview the smallest authorised edit and verify the actual post-change state. Reopen or export the affected account fields and confirm the same stable key, the new current name, the dated former-name reference and unchanged history links. Compare the result with the saved pre-change snapshot. If an operation also changes ownership or creates a second entity, stop and investigate that behaviour. Do not describe a broad operation as a harmless rename when its observed effects exceed the approved correction.

The final handover contains the source conflict, identity evidence, dates, affected items, observed correction check and an undo instruction for the fields changed. A later correction can then be made without pretending the previous decision never happened. This differs from routine list normalisation because the dated event, historical conversation and active contact route each require their own decision. It also differs from alias linking: here the task is to establish what name became current and when, rather than merely associating simultaneous labels.

Sources, checked 18 October 2026: GOV.UK, Company name, https://www.gov.uk/make-changes-to-your-limited-company/company-name ; Get information about a company, https://www.gov.uk/get-information-about-a-company . Sources support registration of a name change and availability of previous names. The correction workflow and cases are editorial recommendations or explicitly fictional; no individual contract, contact permission or real company transition is assessed.

You can test this in practice with open email infrastructure statistics for domains on check.live-direct-marketing.online.

FAQ