Contact Data
Part of CRM data quality
Standardising company names and account ownership
Set a company naming rule, preserve useful alternate names and resolve account ownership without obscuring customer work.
Decide what a CRM account represents before standardising its name. Then keep a consistent display name and any useful alternate names. Set account ownership by an explicit responsibility rule. Neither a familiar name nor an ABN automatically reveals which sales account or person owns the relationship.
Separate names that serve different jobs
A customer may have a registered entity name, a registered business name and a name staff use in conversation. Keep those meanings separate where they matter. Choose a display name that helps colleagues find the account, and retain an alternate name or source note when it explains a known variation. Do not silently replace a customer's preferred name with a legal label.
Australian register checks can resolve a specific uncertainty. ASIC's business names register identifies registered business names and their holders. ABN Lookup provides public ABN details and historical trading names where available. They do not decide whether your CRM should represent a group, legal entity, branch or buying unit as one account.
A naming rule can set the display format, how abbreviations are treated, where alternate names go and who approves a rename. Keep an old-to-new name mapping for changed accounts so staff can recognise and find them.
Define what the owner is accountable for
Write down the account owner's responsibility. For example: "The account owner coordinates the continuing customer relationship and resolves handovers." A deal owner or service contact can have a different job. Agree how an active owner is retained, when a transfer is approved and who reviews an unowned or disputed account.
| Case | Decision to record |
|---|---|
| Two names appear to describe one account | Is the account boundary the same, and which name should staff see? |
| One legal entity has several buying units | Should the units remain separate CRM accounts? |
| An account has no active owner | Who accepts responsibility, and from when? |
| An import proposes a different owner | Is this an authorised transfer or a source-file mismatch? |
Change records without losing work
Before a bulk rename or owner change, identify affected accounts and their open deals, tasks and customer commitments. Record the intended new value and approver. Apply the change to a small representative set through the organisation's approved route and inspect the account and related work before expanding it.
Afterwards, confirm a colleague can find the account under its old and current names and identify who handles an open request. Keep exceptions assigned until those questions have reliable answers.
