Hemory TeamOn this page
You search for Harbor’s minimum order exception and find nothing. The customer used to be called North Pier, and the discussion happened before the change. The transcript is there; the name you remember using today is absent from it.
To find an old transcript after a name change, search both names, confirm that they refer to the same customer or project, and preserve the connection somewhere your search can reach. You can repair this specific gap without relabeling every conversation.
Establish what changed before treating the names as equivalent
A customer rename, a project codename, and a transfer to a different legal entity are different events. Similar names do not establish that two records concern the same account, scope, or agreement.
Look for an available source that explains the relationship: an account update, project announcement, or captured discussion. Note whether the change concerns a display name, a project phase, or the organization itself. If the relationship remains uncertain, search both terms but keep the results separate until you can clarify it.
The same care applies to people. Two references to “Marco” may concern different participants. A person mentioned in a transcript may not have attended the discussion.
Search the old and new names separately
Try the former name with the subject you need, then try the current name. If you remember only a project codename, combine it with a distinctive topic or approximate period. Separate searches work even when the tool has no special alias feature.
For a fictional example, suppose an account update confirms that North Pier began trading as Harbor on 1 October, with the account unchanged. You need the reason for a minimum order exception discussed near the September regional launch.
| Search clue | What it may help locate |
|---|---|
| North Pier + minimum order | The original exception discussion |
| Harbor + minimum order | Later references using the new trading name |
| Regional launch + order | A discussion that describes the topic without naming the customer |
| September, used as an approximate clue | Likely conversations around the launch |
The rename date helps explain the wording; it does not prove that every earlier record uses the old name. Participants may adopt a new name early or continue using an old one afterward.
If you can open the likely transcript but cannot find a distinctive phrase from it, investigate the search route first. The conversation search troubleshooting guide covers content access and indexing problems that aliases will not solve.
Add the missing connection without rewriting old statements
Where your system supports searchable notes or headers, add the naming relationship and its source. Keep the transcript’s original wording intact. This example is a retrieval note, not a Hemory interface or required metadata format:
Current customer name: Harbor
Former trading name: North Pier
Relationship: Same account; trading-name change from 1 October
Basis: Account update dated 1 October
Relevant discussion: Minimum order exception for the regional launch
Historical wording: The September transcript uses North PierOnly add facts you can establish. If the source says that a business unit moved to a new organization, record that narrower relationship rather than calling the two organizations interchangeable.
Put the note where it will be useful: beside the relevant transcript, in an accessible account record, or in a small index that links to the source. Check that your chosen search route can read the added text. A note in an unrelated folder may not help the next lookup.
For project codenames, retain both the codename and the later project name. If a codename was reused, add the period or scope that distinguishes this project. Avoid replacing historical names everywhere; doing so can erase the wording that helps you recognize the original discussion.
Give Hemory the naming context when you ask for help
For new discussions, Hemory creates transcripts and organized Memory with people, topics, and time-related context. That gives you more ways to return to an exchange than a filename alone, while you focus on the conversation.
For a known Hemory conversation, ask a follow-up question about the relevant point. When the answer draws on several discussions, a compatible AI agent connected to Hemory can retrieve available context. Supply the naming relationship instead of expecting it to infer that every alias refers to the same entity.
For the fictional Harbor example, you could ask the connected agent:
Find the reason and conditions for the minimum order exception in the
available Hemory discussions about Harbor or North Pier.
The account update I provide says North Pier began trading as Harbor
on 1 October and the account stayed the same. The original discussion
may have been near the September regional launch.
Search for both names. Identify the relevant sources and separate an
accepted exception from a proposal. Flag records that may concern a
different account or project.Provide historical transcript exports separately if the agent needs them and can read that format. This workflow does not assume Hemory imports or indexes your external archive. If your main problem is getting existing files into a searchable location, see making meeting records searchable.
Check the agreement before reusing it under the new name
Finding the old discussion establishes what was said then. It does not establish that an exception still applies, that a new entity inherited it, or that a later project phase uses the same terms.
In the Harbor example, the account update connects the names. The pricing discussion supplies the exception’s scope and reason. A current agreement or appropriate confirmation is still needed if your response depends on whether those terms remain in force.
Once you have the answer, include the useful naming reference in the current account or project note. For future discussions, Hemory helps preserve the surrounding conversation so a later name change does not leave you relying on a vague recollection.
FAQ
Should I tag every transcript with every former name?
Start with the records and aliases that affect real searches. A searchable account note or index may make the connection without editing every file. Test whether your search can actually reach that note.
Can AI automatically work out that two names mean the same thing?
It may suggest a relationship, but use a source to establish it when the distinction matters. Give the agent known aliases and ask it to keep uncertain matches separate.
What if only the product name changed?
Check whether the new name refers to the same product, a new version, or a different offering. Preserve the version or period when it affects the meaning of the old conversation.
