{
  "title": "Contacts",
  "internal_name": "RelationOS",
  "slug": "contacts",
  "url": "https://alefos.ai/documentation/contacts",
  "json_url": "https://alefos.ai/documentation/contacts.json",
  "summary": "Open a customer and see the last conversation, promise, blocker and next action.",
  "description": "Open a customer and immediately see the last conversation, what was promised, what is blocking the decision and what should happen next.",
  "category": "Core",
  "last_updated": "2026-07-23",
  "keywords": [
    "contacts",
    "relationship memory",
    "customers",
    "context",
    "follow-ups"
  ],
  "sections": [
    {
      "heading": "The problem",
      "content": "In many companies, customer information is scattered.\n\nA call is in the phone system. A message is in WhatsApp. An appointment is in the calendar. A decision is in a group. A follow-up is in a manager head. An objection disappears after the conversation.\n\nThe result: nobody really knows where a customer stands without asking several people.\n\nAlefOS fixes this at the source."
    },
    {
      "heading": "What a contact becomes in AlefOS",
      "content": "An AlefOS contact brings together the operational context linked to a person or company.\n\nIt can include:\n\n- Recent calls.\n- Important messages.\n- Past and upcoming meetings.\n- Open missions.\n- Planned follow-ups.\n- Missing or requested documents.\n- Products or services discussed.\n- Decisions made.\n- Detected objections.\n- Promises made.\n- Next actions to approve.\n\nA contact becomes a clear view of the relationship. Not a form to fill. A living memory built from activity."
    },
    {
      "heading": "Automatic enrichment",
      "content": "AlefOS does not ask teams to manually enter every detail.\n\nWhen useful information appears in a call, message, meeting or group, AlefOS can connect it to the right contact.\n\nExamples:\n\n- A customer asks to be called back.\n- A prospect mentions a budget.\n- A salesperson promises to send a quote.\n- A manager confirms a decision.\n- Someone mentions a product.\n- An appointment is scheduled.\n- A document is expected.\n\nThese elements become usable context. The contact becomes richer as the company works."
    },
    {
      "heading": "What AI can do with a contact",
      "content": "Once context is connected, ChatGPT can query AlefOS memory.\n\nA user can ask:\n\n- Remind me who this customer is.\n- What did we promise them?\n- Who is waiting for a quote?\n- Which customer should I call back today?\n- Prepare a follow-up message for Marc.\n- Which contacts mentioned the Team offer?\n\nAlefOS does not answer with generic information. It uses real context: history, missions, signals, meetings, products, groups and recent interactions."
    },
    {
      "heading": "Concrete example",
      "content": "Before AlefOS, a manager asks: where are we with Marc Dupont?\n\nSomeone needs to search WhatsApp, call the salesperson, check the calendar, read notes and reconstruct the story manually.\n\nWith AlefOS, the user asks the same question and can get a readable brief:\n\n- Last call yesterday.\n- Interested in the Team offer.\n- Two managers mentioned.\n- Quote requested.\n- Callback planned Friday.\n- Main objection: wants to understand deployment.\n- Next action: send summary and propose a demo.\n\nThe relationship becomes immediately readable."
    },
    {
      "heading": "Partial information and unidentified contacts",
      "content": "Real business data does not always arrive cleanly.\n\nSometimes AlefOS first receives a phone number, an email, a call, a message or a signal before the full identity is known.\n\nAlefOS can keep those elements and progressively connect them to the right contact when more information becomes available.\n\nThe goal is not to create useless records. The goal is to avoid losing important signals just because a contact is not perfectly identified yet."
    },
    {
      "heading": "Why this is different from a classic CRM",
      "content": "A classic CRM often depends on what the team takes the time to enter.\n\nIf the salesperson forgets to write a note, the information disappears. If the note is too short, the context is incomplete. If someone writes \"call back\" without details, the manager understands nothing.\n\nAlefOS starts from the real workflow. It captures authorized signals, connects them to contacts, detects missions and prepares next actions.\n\nThe contact is no longer just a record. It becomes the memory point of the entire relationship."
    },
    {
      "heading": "What this brings to teams",
      "content": "For a salesperson:\n\n- They know who to call back.\n- They recover context before a call.\n- They prepare follow-ups faster.\n- They forget fewer promises.\n\nFor a manager:\n\n- They see where customers stand.\n- They understand blockers.\n- They identify warm prospects.\n- They track actions without asking the same questions again.\n\nFor the company:\n\n- Memory no longer stays only inside people's heads.\n- Decisions are easier to find.\n- New team members understand cases faster.\n- Customers are followed with more continuity."
    },
    {
      "heading": "Primary owner, company queue and collaborators",
      "content": "In Team, a contact can have one primary owner while selected teammates help without taking over the relationship.\n\nThe ownership states are explicit:\n\n- Company queue: an unassigned contact remains visible to the authorized company scope.\n- Primary owner: one member is responsible for the relationship and its next actions.\n- Observer: a collaborator can read only the granted sections.\n- Contributor: a collaborator can help only inside the granted sections.\n\nCollaboration can be limited to exact sections, can include an expiry date and can be revoked. Assignment and collaboration changes are audited. Team collaboration never means impersonation."
    },
    {
      "heading": "Key takeaway",
      "content": "In AlefOS, contacts are not just contact details.\n\nThey are the living memory of the company relationships.\n\nEvery call, message, meeting, mission or decision can enrich the context.\n\nAnd once the context exists, ChatGPT can finally answer the real question: what do we know, where do we stand, and what should we do next?"
    }
  ],
  "typical_questions": [
    "Where are we with this person?",
    "What did we promise them?",
    "Who should I call back today?",
    "Which contacts mentioned the Team offer?"
  ],
  "related_pages": [
    "missions",
    "ibox",
    "calls",
    "calendar",
    "groups",
    "team",
    "team-ownership"
  ],
  "important_notes": [],
  "markdown": "# Contacts\n\nLast updated: 2026-07-23\n\nOpen a customer and immediately see the last conversation, what was promised, what is blocking the decision and what should happen next.\n\n## The problem\n\nIn many companies, customer information is scattered.\n\nA call is in the phone system. A message is in WhatsApp. An appointment is in the calendar. A decision is in a group. A follow-up is in a manager head. An objection disappears after the conversation.\n\nThe result: nobody really knows where a customer stands without asking several people.\n\nAlefOS fixes this at the source.\n\n## What a contact becomes in AlefOS\n\nAn AlefOS contact brings together the operational context linked to a person or company.\n\nIt can include:\n\n- Recent calls.\n- Important messages.\n- Past and upcoming meetings.\n- Open missions.\n- Planned follow-ups.\n- Missing or requested documents.\n- Products or services discussed.\n- Decisions made.\n- Detected objections.\n- Promises made.\n- Next actions to approve.\n\nA contact becomes a clear view of the relationship. Not a form to fill. A living memory built from activity.\n\n## Automatic enrichment\n\nAlefOS does not ask teams to manually enter every detail.\n\nWhen useful information appears in a call, message, meeting or group, AlefOS can connect it to the right contact.\n\nExamples:\n\n- A customer asks to be called back.\n- A prospect mentions a budget.\n- A salesperson promises to send a quote.\n- A manager confirms a decision.\n- Someone mentions a product.\n- An appointment is scheduled.\n- A document is expected.\n\nThese elements become usable context. The contact becomes richer as the company works.\n\n## What AI can do with a contact\n\nOnce context is connected, ChatGPT can query AlefOS memory.\n\nA user can ask:\n\n- Remind me who this customer is.\n- What did we promise them?\n- Who is waiting for a quote?\n- Which customer should I call back today?\n- Prepare a follow-up message for Marc.\n- Which contacts mentioned the Team offer?\n\nAlefOS does not answer with generic information. It uses real context: history, missions, signals, meetings, products, groups and recent interactions.\n\n## Concrete example\n\nBefore AlefOS, a manager asks: where are we with Marc Dupont?\n\nSomeone needs to search WhatsApp, call the salesperson, check the calendar, read notes and reconstruct the story manually.\n\nWith AlefOS, the user asks the same question and can get a readable brief:\n\n- Last call yesterday.\n- Interested in the Team offer.\n- Two managers mentioned.\n- Quote requested.\n- Callback planned Friday.\n- Main objection: wants to understand deployment.\n- Next action: send summary and propose a demo.\n\nThe relationship becomes immediately readable.\n\n## Partial information and unidentified contacts\n\nReal business data does not always arrive cleanly.\n\nSometimes AlefOS first receives a phone number, an email, a call, a message or a signal before the full identity is known.\n\nAlefOS can keep those elements and progressively connect them to the right contact when more information becomes available.\n\nThe goal is not to create useless records. The goal is to avoid losing important signals just because a contact is not perfectly identified yet.\n\n## Why this is different from a classic CRM\n\nA classic CRM often depends on what the team takes the time to enter.\n\nIf the salesperson forgets to write a note, the information disappears. If the note is too short, the context is incomplete. If someone writes \"call back\" without details, the manager understands nothing.\n\nAlefOS starts from the real workflow. It captures authorized signals, connects them to contacts, detects missions and prepares next actions.\n\nThe contact is no longer just a record. It becomes the memory point of the entire relationship.\n\n## What this brings to teams\n\nFor a salesperson:\n\n- They know who to call back.\n- They recover context before a call.\n- They prepare follow-ups faster.\n- They forget fewer promises.\n\nFor a manager:\n\n- They see where customers stand.\n- They understand blockers.\n- They identify warm prospects.\n- They track actions without asking the same questions again.\n\nFor the company:\n\n- Memory no longer stays only inside people's heads.\n- Decisions are easier to find.\n- New team members understand cases faster.\n- Customers are followed with more continuity.\n\n## Primary owner, company queue and collaborators\n\nIn Team, a contact can have one primary owner while selected teammates help without taking over the relationship.\n\nThe ownership states are explicit:\n\n- Company queue: an unassigned contact remains visible to the authorized company scope.\n- Primary owner: one member is responsible for the relationship and its next actions.\n- Observer: a collaborator can read only the granted sections.\n- Contributor: a collaborator can help only inside the granted sections.\n\nCollaboration can be limited to exact sections, can include an expiry date and can be revoked. Assignment and collaboration changes are audited. Team collaboration never means impersonation.\n\n## Key takeaway\n\nIn AlefOS, contacts are not just contact details.\n\nThey are the living memory of the company relationships.\n\nEvery call, message, meeting, mission or decision can enrich the context.\n\nAnd once the context exists, ChatGPT can finally answer the real question: what do we know, where do we stand, and what should we do next?\n\n## Typical questions\n\n- Where are we with this person?\n- What did we promise them?\n- Who should I call back today?\n- Which contacts mentioned the Team offer?"
}