IBOX · AlefOS
Send the summary. Keep the full context.
Send a short notification. Keep the complete message in a secure IBOX page, where the recipient can understand it, ask questions and prepare a reply without losing the original context.
One message. Two reading experiences.
The chat stays short. The work stays complete.
WhatsApp notification
Example
Marc sent the deployment analysis.
Budget approved. Two decisions need your response.
Inside IBOX
Deployment analysis
Marc prepared the full deployment context, the approved budget and the two decisions still open.
Ask this message
- What does Marc need from me?
- Which decisions are still open?
- Explain the technical section simply.
- Draft a reply.
Illustrative example.
How IBOX works
Prepare the complete message
The sender develops the analysis, proposal or decision with the context it requires.
Keep it intact in IBOX
The complete message stays together instead of being split across chat messages.
Send only the essentials
The recipient receives a short summary and a link to the complete message.
Understand it before replying
The recipient can identify expectations, decisions and unresolved points before preparing a response.
Why IBOX?
Long messages are easy to produce and hard to receive.
Keep channels readable
The notification contains only what the recipient needs to know before opening the message.
Preserve the original context
The complete message remains intact instead of being shortened, fragmented or copied between tools.
Understand before replying
The recipient can find expectations, decisions, approvals and unanswered questions.
Work across languages
The original message remains available while AI can help explain or translate it.
Not another shared inbox
IBOX does not mirror every conversation or replace WhatsApp and email.
Those channels carry the notification.
IBOX carries the complete message that deserves deeper attention.
Carries the summary and the relationship.
Carries the complete message and its context.
Technical reference
Implementation details for teams, assistants and technical readers.
Message and notification
The notification and the complete message are separate.
The notification carries a short summary and a link.
The complete message stays in IBOX.
The complete message body is not necessarily placed inside the notification channel.
Public access links
A public IBOX link can use the /m/:token route.
The recipient can first view a summary and then request the complete message without signing in.
The link expires no later than five hours after creation.
After the first successful reveal, access expires after 20 minutes or at the five-hour deadline, whichever comes first.
The first successful reveal records the message read time.
The link acts as an access secret and should not be forwarded.
AI and language
The original message remains intact.
The recipient can use a supported AI experience to explain the message, identify expectations or prepare a reply.
The sender and recipient do not need to work in the same language.
Translation or explanation depends on the AI experience used to explore the message.
Operational context
IBOX messages can appear in a sent-message journal.
A message can be connected to a recipient when that context is available.
Some messages can stay connected to contacts, missions or the operational context that caused them.
These relationships depend on the source, permissions and available data.
Notification controls
When WhatsApp notification is enabled, the notification can contain the recipient phone number, a short summary and a temporary IBOX link.
The complete IBOX message body is not placed inside the WhatsApp notification.
Delivery and failure metadata may be processed.
Creating an IBOX message does not guarantee external provider delivery.
A recipient can object to IBOX WhatsApp notifications by replying STOP or UNSUBSCRIBE.
Start with IBOX
Send the full context without overwhelming the recipient.
Use a short notification for attention. Use IBOX for the complete message.