Understand your work OS
WhatsApp and Gmail. Keep every customer conversation in view.
A shared inbox for the exchanges received through your configured connections. Your manager or the colleague taking over can find what the customer asked and what was answered, within their permissions, without asking the team to reconstruct each conversation.
Contact journeys and the complete inbox remain distinct.
The customer base scope sends an enquiry to the company. Full IBOX functions and the channel connections described here are separately scoped extensions. A recorded message, sent notification and received response remain different events.
Everyday work
“Can someone tell me what we said to this customer?”
The answer should not depend on finding the colleague who remembers it. IBOX makes the messages received by your OS consultable, so you can return to the exchange before preparing the next step.
The exchange, before the status report.
01Customer → teamThe request arrives.
Camille needs a visit, with an access constraint.
“Could you come on Thursday? The building is only accessible after 2 pm.”
The incoming message stays available with its sender and time.
02Team → customerFind the actual reply.
Léa has replied through the connected channel.
“I’ll check Thursday with the technician. Please send the access details.”
A reply was sent. A visit was not yet confirmed.
03Authorized supervisorSee what is still waiting.
“What did Léa tell Camille, and what do we need next?”
Léa said she would check Thursday. Access details are still needed. The technician must confirm availability.
Review the accessible messages without replying as your colleague.
Fictional example, not a product screenshot. Sources and access require configuration; illustrated answers use the information shown.
One place to consult. Clear access for each person.
Team members consult their own IBOX. Authorized managers can review the member inboxes assigned to their supervision. Gmail ingestion and WhatsApp connections must be configured; this is not automatic access to every mailbox.
Understand collaboration and permissionsOn this page
- Consult connected exchanges
- Review the team’s exchanges within your scope
- Messages and notifications are different objects
- Access through a temporary link
- Explore a message with AI
- Sending history and operational context
- WhatsApp notifications and opting out
- What does the sender need from me?
- A shared inbox that helps the next person answer
- A request from ChatGPT still needs a follow-up
- Tools and prerequisites
Consult connected exchanges
IBOX stores messages from supported WhatsApp and Gmail ingestion paths, alongside AlefOS messages. WhatsApp incoming and outgoing messages can carry the sender, recipient, time and conversation reference. Gmail reception contributes the email content supplied by the configured connection.
The available message list and contact filters let an assistant consult relevant entries. Source labels can be normalized by the interface; neither a connector nor a received message proves a complete mailbox import or a successful outgoing email.
Review the team’s exchanges within your scope
Each member has their own IBOX. Owner and administrator supervision covers non-administrator member inboxes in read-only mode. Managers need an explicit supervision grant for the member concerned. Other owner and administrator inboxes remain outside this supervision.
The unassigned queue has its own dispatch permissions. Reviewing a colleague’s messages does not authorize replying in their name or marking their messages as read. These rules apply to the configured workspace and the available messages.
Messages and notifications are different objects
The notification contains a summary and a link. The complete body remains in IBOX; it is not necessarily inserted into the channel used for notification.
A report, response or detailed update can therefore retain its full content without forcing it all into a WhatsApp notification. Creating a message does not prove that the provider delivered the notification.
Access through a temporary link
A public IBOX link uses the /m/:token path. The recipient can see the summary, then request the complete message without signing in. This link is an access secret: it must not be shared as an ordinary public page.
The link expires no later than five hours after creation. After the first successful opening of the full message, access expires after twenty minutes or at the five-hour deadline, whichever comes first. This first opening records that the message has been read.
Explore a message with AI
The original message remains intact. A compatible AI experience can help explain the content, identify what is expected or prepare a response.
Sender and recipient can work in different languages. Translation and explanation depend on the AI experience used; they do not automatically change the original or replace verification of important information.
Sending history and operational context
Messages can appear in a sending log. A message can be associated with a recipient, contact, mission or the context that produced it, when those links and permissions are available.
Internal IBOX consultation is separate from opening a temporary link. A message being available to one account does not mean the whole team has the same access.
WhatsApp notifications and opting out
When WhatsApp is the notification channel, the service notification can use the recipient’s number, a short summary and the temporary IBOX link. The complete IBOX message body is not placed in that notification.
Delivery or failure metadata may be processed. The recipient can opt out of IBOX notifications on WhatsApp by replying STOP or UNSUBSCRIBE. Recording a message, sending a notification and reading it are three different events.
What does the sender need from me?
Example: a notification says the deployment proposal is ready and two decisions remain open. The full IBOX message keeps the analysis, budget assumptions and questions together. The recipient can ask a compatible assistant which decisions are pending, request an explanation or prepare a reply.
The sender and recipient can work in different languages while retaining the original message. AI assistance depends on the experience used: a temporary message link alone does not guarantee an embedded chat. IBOX is not a mirror of every email or WhatsApp conversation.
A shared inbox that helps the next person answer
Illustration: a customer asks about a quote on WhatsApp, then sends a document through the configured Gmail connection. The authorized manager finds the received messages and the open question in the customer context. The next colleague can prepare a relevant reply instead of asking everyone to forward their exchanges.
A short notification points to the work; it is not the whole IBOX experience. Consultation, reply preparation and sending have their own access and provider conditions. Personal accounts are not opened merely because someone is a manager.
A request from ChatGPT still needs a follow-up
Your customer asks for help from your business plugin. The configured journey brings the request into your follow-up space with the question and the details needed to act. Your team can understand the request without asking the customer to start again.
You define where it is received, who handles it and how the customer receives the next update. The assistant must distinguish a draft from a successfully submitted request; submitting it does not mean the issue has been resolved.
Fictional example
Also share a complete message, without crowding the notification.
The notification
Your intervention quote is ready. Read the details in your IBOX message.
The complete message
The quote covers the visit and diagnosis. Repair work will be quoted after the diagnosis. Please confirm the intervention address and any access constraints.
Understand, then prepare a reply
- What is included?
- What should I confirm?
- Can you explain it in my language?
Thank you. I confirm the address provided. Access is possible after 2 pm. Could you clarify the expected duration of the visit?
These questions and this draft illustrate help from a compatible assistant, depending on available access and experience. They do not guarantee an assistant embedded in every link or an automatic send. The original remains separate from its translation.
Operational reference
Modules, tools and access conditions
This reference describes MCP operations and their effects. The list exposed to your assistant depends on the deployed server, enabled modules and permissions. Reading, preparing and executing are distinct operations.
IBOX messages
A stored message, an external notification and a read receipt are different states. A temporary /m/:token link grants access to its message; keep that link private.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
ibox. | List IBOX messages visible to the current user. |
ibox. | Read one accessible IBOX message. |
ibox. | Record a message as read. This does not send a reply. |
messages. | Prepare an outbound message preview with an action_id for confirmation. |
actions. | Execute previously prepared work identified by action_id after confirmation. |
The scenarios on this page illustrate workflows, not real customer data or guaranteed outcomes. Connections and capabilities must be enabled and verified for your environment. Official business systems retain their responsibilities.
Continue exploring
A capability of your company’s environment. Your team can use this capability from a compatible assistant through its configured MCP access. The deployment defines the enabled tools and permissions. Understand your AI connection ↗