How Sentra knows who said what and who owns what
The same person, customer or project shows up under different names in every tool. Sentra resolves them to one entity, keeps new ones as proposals until someone confirms them, and lets anyone correct it in chat.
In short
- People are matched first by their Sentra account, then by email address, so a person in a meeting, an email thread and a Slack channel is the same entity.
- Other entities, such as accounts, projects and deals, are matched by name and known aliases within the organization.
- For entity types an organization has locked, new entities start as proposed and become confirmed only when a person confirms them. Sentra never promotes an entity automatically.
- Corrections are made in chat, shown on a confirmation card and recorded with who made them.
Why this is the bar
A memory that attributes a decision to the wrong person is worse than no memory. Teams that tested other knowledge-graph tools told us the failure they hit was exactly this: the tool got wrong who said what. So getting attribution and ownership right, and making it easy to correct, comes before anything else Sentra does.
How Sentra matches an entity
When Sentra reads a source, it extracts the people, accounts, projects and other entities it mentions, then matches each one to an existing entity in a fixed order before it creates anything new.
- For a person: their Sentra user account, then their email address
- For any entity: an exact match on its name or a known alias within the same organization and type
- Only if nothing matches: a new entity, which starts as proposed if the organization has locked that type
Confirmed and proposed entities
Each entity is confirmed, proposed or rejected. Organizations can lock an entity type, such as customers or projects, so that anything new of that type waits as a proposal. Any member who can see the entity can confirm or reject it, and Sentra does not promote proposals on its own.
Sentra also looks for duplicates, such as two records for the same customer under slightly different names. People are never merged automatically unless the organization opts in.
Correcting Sentra
Anyone can tell Sentra in chat that something is wrong, for example that an account has a new owner. Sentra finds the entity, shows exactly what it will record on a confirmation card, and writes it only when the person confirms. People can also move a fact that landed on the wrong entity.
Ownership matters for corrections too. A change stated by the owner of an item is recorded as a decision. A change stated by someone else is recorded as a proposal pending the owner's confirmation.
Frequently asked questions
How does Sentra know two names are the same person?
People are matched by their Sentra account and then by email address, which are shared across email, calendar, meetings and chat. Other entities are matched by name and known aliases within the organization.
Does Sentra create entities without anyone checking?
For entity types an organization has locked, new entities start as proposed and wait for a person to confirm them. Sentra never confirms a proposed entity on its own.
What happens if Sentra attributes something to the wrong person?
Anyone can correct it in chat or move the fact to the right entity. Sentra shows a confirmation card before it records the correction, and keeps who made it.
Is this a knowledge graph?
Yes. Sentra stores entities, the facts about them and the relationships between them, such as who works on which account or who attended which meeting. Unlike a graph you model by hand, it is built from the company's own email, chat, meetings and systems.