Skip to main content
An entity is system-of-record identity: a call, a WhatsApp reply, and an email from the same person are one entity with one history - not three records in three systems. Every channel API hands you a different handle for the same human: a phone number on the call, a WhatsApp ID on the message, an address on the email. Without a shared identity layer, your agent treats each as a stranger and your data splits three ways. Entities collapse those handles into one record, so every touch on every channel resolves to the same person before your agent sees it. People and organizations are both first-class. In an enterprise sale the customer is the company - individual contacts roll up to it. In a consumer sale the customer is the person. Your CRM stays where it is; the entity table is the working copy your agents read and write in real time. Upsert a person once with their known identities, and every future interaction on any of those channels resolves to them. This is the shape the unified SDK takes:
Today this lives in People in the Platform and the Space APIs.

​
The primitives

​
On the spine

Entities are where the spine starts: channels deliver every inbound touch to an entity, and every conversation belongs to one. Entities read identity handles from channel payloads, write the resolved person or organization record, and emit entity created, updated, and merged events. The Context Graph hangs facts and history off the entity record.

​
What stays hidden

Matching and dedup implementation. How a raw phone number or email is normalized, scored, and resolved to an existing entity - and how duplicate records get merged - is Unpod’s job. You upsert identities and read one record; the resolution machinery is not a public surface.

​
Status

People and identities: production. Companies (organizations): in build - domain rollup and dedupe are shipping in the open.

​
Go deeper

People

Manage people and their channel identities in the Platform today.

Organizations API

Company records and rollup via the Space APIs.

Conversations

The channel-neutral threads every entity’s touches belong to.

Context Graph

Persistent communication memory attached to each entity.