{
  "title": "Calendar",
  "internal_name": "CalendarOS",
  "slug": "calendar",
  "url": "https://alefos.ai/documentation/calendar",
  "json_url": "https://alefos.ai/documentation/calendar.json",
  "summary": "Know why the meeting exists before it starts, what to prepare and what should happen after.",
  "description": "AlefOS connects each appointment to the customer context that created it, the preparation needed before it starts and the follow-up that should happen after.",
  "category": "Core",
  "last_updated": "2026-07-23",
  "keywords": [
    "calendar",
    "appointments",
    "meetings",
    "scheduling",
    "follow-up"
  ],
  "sections": [
    {
      "heading": "The problem",
      "content": "In many teams, the calendar tells people when something happens, but not always why.\n\nAn appointment is created. A customer is added to the calendar. A meeting is scheduled. An address is sent in a message. An important detail stays inside a call. A note is forgotten in WhatsApp. A follow-up must happen after the meeting.\n\nOn the day of the appointment, the context must be rebuilt manually:\n\n- Who is this customer?\n- Why are we meeting them?\n- What did they ask for?\n- What did we promise?\n- Which document is missing?\n- What needs to be prepared?\n\nAlefOS connects the calendar to the real work."
    },
    {
      "heading": "What an appointment becomes in AlefOS",
      "content": "A calendar event can become a memory point.\n\nIt can be connected to:\n\n- A contact.\n- A company.\n- A mission.\n- A call.\n- A message.\n- A group.\n- An address.\n- A phone number.\n- A field note.\n- A decision.\n- A follow-up.\n- An action to validate.\n\nThe calendar no longer only answers when. It also helps understand what to prepare and what should happen next."
    },
    {
      "heading": "Before the appointment: preparation",
      "content": "Before an appointment, AlefOS can help prepare a brief.\n\nA user can ask: prepare the context before my appointment.\n\nAlefOS can retrieve recent exchanges, promises made, objections, missing documents, products or services discussed, open missions, people involved, points to check and actions to plan after the meeting.\n\nThe goal is simple: arrive at the appointment with the right context, without searching through calls, messages, notes or groups."
    },
    {
      "heading": "During the appointment: field context",
      "content": "An appointment can also carry practical field information.\n\nExamples:\n\n- Full address.\n- Contact phone number.\n- Access notes.\n- Person to ask for on site.\n- Appointment topic.\n- Documents to bring.\n- Information to verify.\n- Linked mission.\n- Customer history.\n- Manager instruction.\n\nAn appointment becomes an operational file, not just a box in a calendar."
    },
    {
      "heading": "After the appointment: follow-up",
      "content": "The value of an appointment does not end when the meeting ends.\n\nAfter an appointment, there is often a next step:\n\n- Send a message.\n- Create a mission.\n- Confirm a decision.\n- Send a document.\n- Follow up with the customer.\n- Publish a summary in a group.\n- Notify a manager.\n- Plan the next call.\n- Update the contact context.\n\nAlefOS helps transform appointments into follow-up actions. The calendar becomes a source of missions, not only a history of dates."
    },
    {
      "heading": "Connected scheduling sources",
      "content": "When a scheduling source is connected and authorized, AlefOS can use calendar context to enrich operational memory.\n\nThe user existing calendar remains the scheduling tool. AlefOS does not replace it.\n\nAlefOS connects appointments to the rest of the work: contacts, missions, calls, messages, groups, notes, decisions and follow-ups.\n\nDepending on the plan, permissions and available integrations, AlefOS can read calendar context and prepare calendar-related actions."
    },
    {
      "heading": "Creating and updating events",
      "content": "Some calendar actions are engaging.\n\nFor example:\n\n- Creating an appointment.\n- Updating an event.\n- Adding important information.\n- Preparing an invitation.\n- Linking an appointment to a mission.\n- Sending a confirmation.\n\nThese actions must remain controlled.\n\nAlefOS can prepare the action. The user validates before execution.\n\nPrinciple: AlefOS prepares. The user decides."
    },
    {
      "heading": "Calendar, Missions, Contacts and Groups",
      "content": "Calendar is strongly connected to Missions: an appointment can create a mission, and a mission can create an appointment.\n\nA calendar event can also enrich a contact with a past appointment, upcoming appointment, meeting location, topic discussed, people present, promise made, next step planned or important note.\n\nAn appointment or meeting can also feed a Group through a meeting summary, decision, procedure update, shared action or briefing."
    },
    {
      "heading": "Difference from a classic calendar",
      "content": "A classic calendar mainly answers one question: when is the appointment?\n\nAlefOS adds operational questions:\n\n- Why does this appointment exist?\n- Who is involved?\n- What needs to be prepared?\n- What was promised?\n- Which mission is linked?\n- What should happen after?\n\nThis is what turns the calendar into work memory."
    },
    {
      "heading": "Appointment ownership in Team",
      "content": "In Team, a calendar event can have one visible owner.\n\nAn authorized member can assign the appointment, explicitly reassign it or return it to the company queue. The event keeps its customer context, linked mission and audit trail throughout the change.\n\nOwnership answers who is responsible for the appointment. It does not replace calendar-provider permissions or silently act as another user."
    },
    {
      "heading": "Key takeaway",
      "content": "Calendar in AlefOS does not replace the user existing calendar or scheduling tools.\n\nIt adds business context around appointments.\n\nAn event should not only be a date. It should be able to become preparation, memory, a mission, a follow-up, a decision and a next action.\n\nThe simple idea: an appointment should not only be scheduled. It should help the company remember, prepare and act."
    }
  ],
  "typical_questions": [],
  "related_pages": [
    "missions",
    "contacts",
    "meeting-providers",
    "team-ownership"
  ],
  "important_notes": [
    "AlefOS does not replace the user existing calendar or scheduling tools."
  ],
  "markdown": "# Calendar\n\nLast updated: 2026-07-23\n\nAlefOS connects each appointment to the customer context that created it, the preparation needed before it starts and the follow-up that should happen after.\n\n## The problem\n\nIn many teams, the calendar tells people when something happens, but not always why.\n\nAn appointment is created. A customer is added to the calendar. A meeting is scheduled. An address is sent in a message. An important detail stays inside a call. A note is forgotten in WhatsApp. A follow-up must happen after the meeting.\n\nOn the day of the appointment, the context must be rebuilt manually:\n\n- Who is this customer?\n- Why are we meeting them?\n- What did they ask for?\n- What did we promise?\n- Which document is missing?\n- What needs to be prepared?\n\nAlefOS connects the calendar to the real work.\n\n## What an appointment becomes in AlefOS\n\nA calendar event can become a memory point.\n\nIt can be connected to:\n\n- A contact.\n- A company.\n- A mission.\n- A call.\n- A message.\n- A group.\n- An address.\n- A phone number.\n- A field note.\n- A decision.\n- A follow-up.\n- An action to validate.\n\nThe calendar no longer only answers when. It also helps understand what to prepare and what should happen next.\n\n## Before the appointment: preparation\n\nBefore an appointment, AlefOS can help prepare a brief.\n\nA user can ask: prepare the context before my appointment.\n\nAlefOS can retrieve recent exchanges, promises made, objections, missing documents, products or services discussed, open missions, people involved, points to check and actions to plan after the meeting.\n\nThe goal is simple: arrive at the appointment with the right context, without searching through calls, messages, notes or groups.\n\n## During the appointment: field context\n\nAn appointment can also carry practical field information.\n\nExamples:\n\n- Full address.\n- Contact phone number.\n- Access notes.\n- Person to ask for on site.\n- Appointment topic.\n- Documents to bring.\n- Information to verify.\n- Linked mission.\n- Customer history.\n- Manager instruction.\n\nAn appointment becomes an operational file, not just a box in a calendar.\n\n## After the appointment: follow-up\n\nThe value of an appointment does not end when the meeting ends.\n\nAfter an appointment, there is often a next step:\n\n- Send a message.\n- Create a mission.\n- Confirm a decision.\n- Send a document.\n- Follow up with the customer.\n- Publish a summary in a group.\n- Notify a manager.\n- Plan the next call.\n- Update the contact context.\n\nAlefOS helps transform appointments into follow-up actions. The calendar becomes a source of missions, not only a history of dates.\n\n## Connected scheduling sources\n\nWhen a scheduling source is connected and authorized, AlefOS can use calendar context to enrich operational memory.\n\nThe user existing calendar remains the scheduling tool. AlefOS does not replace it.\n\nAlefOS connects appointments to the rest of the work: contacts, missions, calls, messages, groups, notes, decisions and follow-ups.\n\nDepending on the plan, permissions and available integrations, AlefOS can read calendar context and prepare calendar-related actions.\n\n## Creating and updating events\n\nSome calendar actions are engaging.\n\nFor example:\n\n- Creating an appointment.\n- Updating an event.\n- Adding important information.\n- Preparing an invitation.\n- Linking an appointment to a mission.\n- Sending a confirmation.\n\nThese actions must remain controlled.\n\nAlefOS can prepare the action. The user validates before execution.\n\nPrinciple: AlefOS prepares. The user decides.\n\n## Calendar, Missions, Contacts and Groups\n\nCalendar is strongly connected to Missions: an appointment can create a mission, and a mission can create an appointment.\n\nA calendar event can also enrich a contact with a past appointment, upcoming appointment, meeting location, topic discussed, people present, promise made, next step planned or important note.\n\nAn appointment or meeting can also feed a Group through a meeting summary, decision, procedure update, shared action or briefing.\n\n## Difference from a classic calendar\n\nA classic calendar mainly answers one question: when is the appointment?\n\nAlefOS adds operational questions:\n\n- Why does this appointment exist?\n- Who is involved?\n- What needs to be prepared?\n- What was promised?\n- Which mission is linked?\n- What should happen after?\n\nThis is what turns the calendar into work memory.\n\n## Appointment ownership in Team\n\nIn Team, a calendar event can have one visible owner.\n\nAn authorized member can assign the appointment, explicitly reassign it or return it to the company queue. The event keeps its customer context, linked mission and audit trail throughout the change.\n\nOwnership answers who is responsible for the appointment. It does not replace calendar-provider permissions or silently act as another user.\n\n## Key takeaway\n\nCalendar in AlefOS does not replace the user existing calendar or scheduling tools.\n\nIt adds business context around appointments.\n\nAn event should not only be a date. It should be able to become preparation, memory, a mission, a follow-up, a decision and a next action.\n\nThe simple idea: an appointment should not only be scheduled. It should help the company remember, prepare and act.\n\n## Important notes\n\n- AlefOS does not replace the user existing calendar or scheduling tools."
}