{
  "title": "IBOX",
  "internal_name": "IBOX",
  "slug": "ibox",
  "url": "https://alefos.ai/documentation/ibox",
  "json_url": "https://alefos.ai/documentation/ibox.json",
  "summary": "Send a short notification while the complete message stays available in IBOX.",
  "description": "Send a short notification and keep the complete message in a secure IBOX page that the recipient can understand before replying.",
  "category": "Core",
  "last_updated": "2026-07-23",
  "keywords": [
    "IBOX",
    "complete message",
    "notification",
    "recipient AI",
    "WhatsApp notification",
    "secure message links"
  ],
  "sections": [
    {
      "heading": "Message and notification",
      "content": "The notification and the complete message are separate.\n\nThe notification carries a short summary and a link.\n\nThe complete message stays in IBOX.\n\nThe complete message body is not necessarily placed inside the notification channel."
    },
    {
      "heading": "Public access links",
      "content": "A public IBOX link can use the /m/:token route.\n\nThe recipient can first view a summary and then request the complete message without signing in.\n\nThe link expires no later than five hours after creation.\n\nAfter the first successful reveal, access expires after 20 minutes or at the five-hour deadline, whichever comes first.\n\nThe first successful reveal records the message read time.\n\nThe link acts as an access secret and should not be forwarded."
    },
    {
      "heading": "AI and language",
      "content": "The original message remains intact.\n\nThe recipient can use a supported AI experience to explain the message, identify expectations or prepare a reply.\n\nThe sender and recipient do not need to work in the same language.\n\nTranslation or explanation depends on the AI experience used to explore the message."
    },
    {
      "heading": "Operational context",
      "content": "IBOX messages can appear in a sent-message journal.\n\nA message can be connected to a recipient when that context is available.\n\nSome messages can stay connected to contacts, missions or the operational context that caused them.\n\nThese relationships depend on the source, permissions and available data."
    },
    {
      "heading": "Notification controls",
      "content": "When WhatsApp is used as the notification channel, the service notification can contain the recipient phone number, a short message summary and the temporary IBOX link.\n\nThe complete IBOX message body is not placed inside the WhatsApp notification.\n\nDelivery and failure metadata may be processed.\n\nCreating an IBOX message does not guarantee external provider delivery.\n\nThe recipient can object to IBOX WhatsApp notifications by replying STOP or UNSUBSCRIBE."
    }
  ],
  "typical_questions": [
    "What does the sender expect from me?",
    "Which decisions are still open?",
    "Explain the technical section simply.",
    "Draft a reply."
  ],
  "related_pages": [
    "mcp-cockpit",
    "contacts",
    "missions",
    "whatsapp",
    "team"
  ],
  "important_notes": [
    "The notification and complete message are separate.",
    "Temporary public links act as access secrets and must not be forwarded.",
    "WhatsApp notifications are best-effort external notifications when enabled."
  ],
  "markdown": "# IBOX\n\nLast updated: 2026-07-23\n\nSend a short notification and keep the complete message in a secure IBOX page that the recipient can understand before replying.\n\n## Message and notification\n\nThe notification and the complete message are separate.\n\nThe notification carries a short summary and a link.\n\nThe complete message stays in IBOX.\n\nThe complete message body is not necessarily placed inside the notification channel.\n\n## Public access links\n\nA public IBOX link can use the /m/:token route.\n\nThe recipient can first view a summary and then request the complete message without signing in.\n\nThe link expires no later than five hours after creation.\n\nAfter the first successful reveal, access expires after 20 minutes or at the five-hour deadline, whichever comes first.\n\nThe first successful reveal records the message read time.\n\nThe link acts as an access secret and should not be forwarded.\n\n## AI and language\n\nThe original message remains intact.\n\nThe recipient can use a supported AI experience to explain the message, identify expectations or prepare a reply.\n\nThe sender and recipient do not need to work in the same language.\n\nTranslation or explanation depends on the AI experience used to explore the message.\n\n## Operational context\n\nIBOX messages can appear in a sent-message journal.\n\nA message can be connected to a recipient when that context is available.\n\nSome messages can stay connected to contacts, missions or the operational context that caused them.\n\nThese relationships depend on the source, permissions and available data.\n\n## Notification controls\n\nWhen WhatsApp is used as the notification channel, the service notification can contain the recipient phone number, a short message summary and the temporary IBOX link.\n\nThe complete IBOX message body is not placed inside the WhatsApp notification.\n\nDelivery and failure metadata may be processed.\n\nCreating an IBOX message does not guarantee external provider delivery.\n\nThe recipient can object to IBOX WhatsApp notifications by replying STOP or UNSUBSCRIBE.\n\n## Typical questions\n\n- What does the sender expect from me?\n- Which decisions are still open?\n- Explain the technical section simply.\n- Draft a reply.\n\n## Important notes\n\n- The notification and complete message are separate.\n- Temporary public links act as access secrets and must not be forwarded.\n- WhatsApp notifications are best-effort external notifications when enabled."
}