Back to all articlesContact identity

Place Historical Notes When the Person Mentioned Is Unclear

Alactic Editorial9 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

Hypothetical opening scenario: An old note records that Sam called about a renewal. Your CRM contains two Sams at the same company, but only one still works there. Attaching the note to the current employee may look tidy. It also turns a present-day assumption into a claim about a past conversation.

To assign old CRM notes to the correct contact, look for evidence identifying the participant at the time of the interaction. An existing filing location is something to investigate, not proof of identity. Sometimes the defensible result is an organisational context; sometimes neither the person nor the organisation can be established.

All illustrative notes, scenarios, names, and numbers in this article are fictional and hypothetical, not Alactic customer results. The filled table below provides a reusable decision record. This guide covers historical identity attribution, not migration mapping, note summarisation, or retention policy.

1. Separate the interaction from its filing location

A historical note contains claims about an interaction. Its location in a CRM makes a separate claim about whose interaction it was. Those claims need not have equal support.

For example, a note recording a request for a revised delivery date may clearly describe the request without identifying the caller. Finding it under a company record does not independently establish that company either: the earlier filing choice could itself have been a guess.

Before changing anything, record:

  • Original wording: preserve it without inserting an inferred surname, employer, or role.
  • Interaction date: distinguish the event date from the date someone entered the note.
  • Existing location: record where the note was found as provenance, not confirmation.
  • Available evidence: identify original messages, signatures, account references, or dated records.
  • Decision history: keep the reviewer, review date, reasoning, and evidence references.

Preserving the original location in a worksheet is different from confirming organisational attribution. If a note must remain physically where it is while reviewed, mark that location as unverified wherever the supported workflow allows. Do not present an unchanged location as a completed identity decision.

2. Choose among three evidence-based outcomes

Person attribution

Attribute a note to a person when historical evidence connects that individual to the interaction and no material contradiction remains. An original message from an individually assigned address, with a full signature and matching request reference, can support that connection. A current contact record alone cannot.

Organisational context, person unresolved

Use this outcome when independent evidence establishes the organisation but not the individual. An original request from an identifiable company purchasing inbox may support the company connection while leaving the sender unknown. Make the unresolved person explicit so readers do not substitute the primary contact or account owner.

Attribution unresolved

Use this outcome when neither identity is established, or material conflicts remain. Record candidate contexts as candidates, not confirmed relationships. Keep the decision in a review worksheet or another supported location that does not imply a verified identity.

These are recommended operating practices, not claims about built-in Alactic controls. Check your workspace and current plan for available note locations and fields. If uncertainty cannot be represented cleanly, use a separate attribution worksheet rather than selecting an arbitrary contact. This guide does not assume identical capabilities across Alactic products or interfaces.

3. Test clues against the historical date

Ask what connects the candidate to this interaction then, rather than who seems most likely now. Start with original correspondence and explicit participant identification. Use dated employment or project information as supporting context, and actively look for contradictions.

  • Direct historical evidence: an original signed message tied to the request or a contemporaneous record explicitly identifying the participant.
  • Supporting context: a role held at the time, a dated directory, or a relevant project assignment.
  • Weak context: today's account owner, a familiar first name, current contact details, or a shared switchboard number.
  • Contradictions: incompatible dates, conflicting account references, or evidence that the candidate had not yet joined.

Several weak clues may share one source. A first name, purchasing role, and company number copied from the same account record are not three independent confirmations. Likewise, a different current employer does not invalidate a well-supported historical relationship.

Write confidence as an explanation, not an invented probability. Saying that original correspondence establishes the organisation but not the individual tells reviewers what remains unknown. A percentage would suggest precision the evidence does not provide.

4. Worked example: a filled attribution table

The following hypothetical table is a reusable worksheet. Copy its five columns and add a note reference, reviewer, review date, and evidence location for each entry. Each row separates the available facts from the decision they support.

Hypothetical historical-note attribution worksheet
Original noteAvailable historical cluesConfidence explanationPlacement decisionReopening condition
A: First-name ambiguity. Sam called about the renewal.Found under Alder Works. Sam Patel and Samantha Reed both worked there then. No original call record, individual number, or independent company link is available.Neither Sam is identified. Their employment makes Alder Works plausible, but does not connect this interaction to it. The filing location is not proof.Attribution unresolved. Record Alder Works only as an unverified candidate context and preserve the original location in the review history.Contemporaneous correspondence or a call reference establishes the organisation or caller.
B: Signed original message. Jordan asked to move the installation.A linked original message comes from an individually assigned address, is signed Jordan Ellis, and matches the note's date and installation reference.The original message connects Jordan Ellis to this request. No conflicting identity evidence is available.Attribute to Jordan Ellis, retaining the original message reference.Evidence shows another sender used the address or the message was linked to the wrong interaction.
C: Shared mailbox. Purchasing confirmed the revised quantities.The original message came from Birch Supply's shared purchasing inbox without a personal signature. The current purchasing manager joined later.The correspondence establishes Birch Supply, not an individual sender. The current manager cannot be inferred to be the historical participant.Retain at Birch Supply's organisational context; person unresolved.A contemporaneous reply or other direct evidence identifies the sender.
D: A current phone-number match does not establish the historical caller. Caller on mobile requested another quote.The recorded number matches Morgan Lee's current details. No dated evidence connects Morgan to the number then; no organisation is named.The current match does not identify the historical caller. It also does not establish any previous holder or change of ownership.Attribution unresolved. Do not attach the note to Morgan Lee.A dated record connects the number and interaction to a person or organisation.
E: Employer changed. Priya approved the sample for Cedar Studio.The original signed message identifies Priya Shah at Cedar Studio on the interaction date. Her current record lists another employer.The historical message supports Priya Shah and Cedar Studio for this interaction. Today's employer does not contradict that evidence.Attribute to Priya Shah while preserving Cedar Studio as the historical organisational context.Evidence shows the message concerned a different Priya Shah or interaction.
F: Conflicting company clues. Alex from Northline called about the account.Found under Northline Services, but an attached reference belongs to Northline Components. Both employed an Alex. No original correspondence is available.The company name is ambiguous, and the attached reference conflicts with the filing location. Neither person is established.Attribution unresolved. List both organisations as candidates without confirming either.Evidence resolves which account the interaction concerned.

Row A illustrates a crucial boundary: a plausible company is not an established company. Row C crosses that boundary because original correspondence independently identifies Birch Supply. Row B goes further because the same historical evidence identifies the individual and the specific request.

5. Make the review repeatable and bounded

Review one note at a time. Several notes filed together may describe different participants; resolving one does not resolve the batch. Use the table to make each decision inspectable:

  1. Capture the unchanged wording, note reference, and existing location.
  2. Establish the interaction date, or explicitly record that only the entry date is known.
  3. List plausible candidates, including an unknown-person option.
  4. Inspect available historical records that the reviewer is permitted to access.
  5. Test the preferred match against conflicting dates, roles, and account references.
  6. Record the supported placement, its reason, and the evidence that would reopen it.

Stop when the defined evidence sources have been checked. Unresolved can be a completed review decision; it need not trigger an indefinite search. For consequential or disputed changes, use a second reviewer before altering attribution.

A reopening condition should name useful evidence, not merely ask for another opinion. For example, an original reply identifying the sender could resolve a shared-mailbox case. A colleague agreeing that one candidate seems more likely would not supply the missing historical link.

6. Prevent uncertain identity from spreading

A tentative match can become harder to challenge after staff repeat it elsewhere. Someone might copy an ambiguous renewal note into Sam Patel's task list, then later treat that task as independent evidence that Sam was the caller. The copied assertion has not strengthened the original evidence.

Keep the attribution explanation beside any operational use of the note. For Row A, a useful hypothetical annotation is: Person and organisation unresolved; Alder Works is an unverified candidate based on original filing location; no direct interaction evidence available.

Do not use unresolved attribution to assert that a particular person made a commitment, expressed a preference, or authorised an action. Where organisational context is independently established, a follow-up may still be appropriate, but the participant should be verified rather than addressed as the confirmed historical speaker.

If a downstream task needs an owner, distinguish the employee responsible for investigating from the person believed to have participated. Assigning review work should not silently assign historical identity.

7. Correct guesses already treated as facts

When a past attribution proves unsupported, record the former placement, revised decision, and evidence prompting the correction. Preserve the original interaction wording rather than silently rewriting it to fit the new interpretation.

Inspect linked tasks, relationship notes, and other records that explicitly relied on the old match. Correct them within the reviewer's authority or route them to their owners. Moving the source note does not necessarily remove copied assertions.

Disproving one candidate does not prove another. If the evidence only rules out the original person, reassess the remaining evidence without automatically choosing the next candidate. Do not merge contacts merely to make ambiguous notes fit.

Where authorised reviewers disagree, document the competing explanations and the missing evidence. A majority preference does not establish who participated in a historical conversation.

8. Measure the review, not apparent completeness

For a hypothetical initial review, select 20 ambiguous notes from one account group. Have a second reviewer check every proposed person attribution and disputed placement. Use the same evidence boundaries throughout so decisions can be compared.

Count decisions by placement outcome, proposed person matches changed after review, and completed decisions missing an evidence explanation. Also check whether candidate organisations have accidentally been recorded as confirmed relationships.

These counts describe the review, not a verified accuracy rate. A higher person-match count is not inherently better. The observable outcome is a set of decisions whose evidence, limitations, and reopening conditions another reviewer can inspect without reconstructing the original guess.

CRM data qualityContact identityHistorical notesData stewardship

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications