Entities

Entities represent people, companies, vendors, accounts, etc. that DelegateZero should recognize - specifically if the entity has its own set of facts, preferences, and special handling attached that might be utilized.

Some examples:

• ABC Company is a long-term client on an annual contract. They prefer clear, formal communication. They typically review reports monthly.
• Sam Reynolds is our engineering manager. He handles approvals related to infrastructure changes.
• Stripe is our payment processor. Any issues or changes involving billing should be escalated.

Here are some examples with better reasoning and more specificity:

Client with scoped behavior:

ABC Company
-Strategic client.
-Use a professional, direct tone
-Avoid mentioning internal tools or processes
-Do not speculate about future features or timelines
-Escalate requests involving scope or pricing changes

This is good because it specifies tone, content boundaries, and escalation rules, preventing common communication mistakes.

Internal decision-maker with context:

Jamie Lee is our Director of Operations.
-She approves vendor contracts and renewals
-She prefers concise summaries over long explanations
-Escalate anything time-sensitive or involving compliance to Jamie

This entity entry clarifies responsibility, includes preferences, not just role, and helps to route decisions correctly.

Vendor with risk considerations:

Acme Hosting
-Our infrastructure provider.
-Historically slow to respond to support requests
-Any outages or billing discrepancies should be escalated immediately to them
-Avoid committing to timelines with tasks including Acme without confirmation

This entry is aware of risk history, guides escalation behavior, and applies across many situations.

Relationship history

Entity entries are not static profiles. Every time a decision involves a known entity, DelegateZero evaluates whether that decision revealed anything not already captured - a new preference, a shift in relationship dynamic, a changed contact, a decision outcome that modifies how this entity should be understood.

When net-new signal is found, the entity entry is automatically updated and condensed. The previous content is not appended to - it is rewritten as a tighter, more current narrative that incorporates both existing knowledge and the new signal. This keeps entity entries lean and current without manual maintenance.

The result is that entity context reflects the full arc of your relationship, not just an initial profile. When a new decision comes in involving that entity, DelegateZero is matching against relationship history, not a snapshot.

You can always edit or override entity content directly in the dashboard. Automatic updates only add signal - they never remove something you wrote intentionally.