A Contact-Based Inbox for Connected Messages

From channel identity to person#

Communication providers identify people differently. Email uses addresses. Phone-based networks use numbers. Other services may use usernames or provider IDs. Linkrium stores those identifiers on a contact record and uses them to place synchronized messages in the appropriate history.

The provider identity is never discarded. Every message still needs a source label, because the route affects delivery, privacy expectations, formatting, and the actions available for a reply.

Identity matching must be reviewable#

Automatic matching can reduce duplicate histories, but it should not make irreversible assumptions. Two people may share a mailbox, reuse a phone number, or have similar names.

Review the identifiers before combining records. If the evidence is uncertain, separate timelines are safer than an incorrect merge.

What the timeline contains#

A contact timeline can include synchronized inbound and outbound messages, timestamps, provider labels, available attachment references, and the connected identity used for delivery. Coverage depends on the history successfully imported from each account.

It does not guarantee that every item from the native provider is available. Deleted, disappearing, unsupported, inaccessible, or older content may be absent.

A practical verification#

1. Connect an account listed as available.
2. Send a test message from an address attached to a test contact.
3. Confirm the sender, timestamp, direction, and provider label.
4. Add a second verified identifier only when that connection is public.
5. Search for a distinctive phrase and verify the result opens the correct history.

This workflow tests the contact model without relying on broad marketing claims.