Relationship context
Keep Relationship Context Beside Every Conversation
Relationship context is useful when it helps you recognize the person, understand recent exchanges and choose the next action without hiding uncertainty.
- Publication date
- Published
- Reading time
- 1 min read
- Author
- Linkrium Editorial Team
On this page5 sections
What relationship context includes#
Linkrium can place the person's stored identifiers, synchronized conversation history and relevant follow-up information around the same contact record. WhatsApp numbers, Telegram identities and email addresses remain distinct identifiers even when they belong to one person.
Review identity matches#
Automatic matching is limited by the data a provider exposes and the accuracy of the contact record. Similar names, recycled phone numbers, shared mailboxes and incomplete profiles can create ambiguity. Review uncertain associations before merging histories, and separate an identity when the evidence does not support the match.
A practical verification flow#
- Create a test contact whose identities you control on the available providers.
- Synchronize one message from each connected channel.
- Confirm every message retains the correct source label and timestamp.
- Open relationship context and verify that it points to the intended person.
- Create a follow-up task and return to the correct source conversation.
Data handling boundaries#
Store only the identifiers and relationship notes you need. Do not use inferred sensitive attributes as relationship context, and do not treat AI-generated summaries as verified facts. Provider permissions, Linkrium access controls and applicable privacy obligations continue to govern the underlying data.
Troubleshooting#
If a message appears under the wrong person, stop adding more identifiers, record the provider and message reference, and separate the incorrect match. Recheck the stored address, handle or phone number before reconnecting it.