Understand your work OS
WhatsApp Business: keep the conversation moving. Keep the context.
A message, a document, a voice note — then perhaps a call. Keep the useful exchanges with the customer relationship so the next colleague can continue the work. Messaging and calling have distinct connection paths.
A business connection to include in the project.
A WhatsApp connection adds a business channel to the agreed scope. Accessible data, the provider account and permissions must be verified. It does not open every personal conversation and is not automatically included in the customer application.
Everyday work
The latest detail is somewhere in the chat.
A changed address, a voice message, an answer to yesterday’s question. Those details matter beyond the conversation. The supported connection brings available messages into the work context without making every message a task.
A change that the next colleague can find.
01Message receivedA detail changes.
Camille updates the access instructions.
“Please use the courtyard entrance. The main entrance will be closed.”
The message must reach the connected, authorized account.
02Work contextKeep the change with the customer.
“What should the technician know before arriving?”
Camille asked the team to use the courtyard entrance. Check the appointment details alongside this message.
The source remains a message, not proof that the visit happened.
03Team handoverRead before asking again.
An authorized colleague reviews the exchange in IBOX.
Use the courtyard instruction when preparing the visit. Clarify any missing details before promising an arrival time.
Visibility follows the assigned member and supervision rights.
Fictional example, not a product screenshot. Sources and access require configuration; illustrated answers use the information shown.
The channel can change. The relationship continues.
Start with the received messages, documents and voice notes. A calling deployment is a separate next step, with its own readiness checks. IBOX and Contacts keep the available exchanges useful to the people taking over.
Explore the calling pathsOn this page
- Customers keep their familiar channel
- Information that can support work
- Messages and calls: two connection paths
- WhatsApp Business Calling — a path to prepare
- The next colleague should not start again
- From conversation to draft
- Configure and verify the connection
- Distinguish conversations from IBOX notifications
- Voice notes, media and available history
- Delivery and provider charges
- Tools and prerequisites
Customers keep their familiar channel
WhatsApp Business remains the place for the conversation. AlefOS uses only the context supplied by the configured connection that the user is allowed to consult.
This workflow does not promise to import every personal conversation or automatically synchronize every WhatsApp group.
Information that can support work
A request, promise, objection, submitted document or follow-up date can be attached to the customer and next action. Useful context depends on the message actually received and the processing supported.
A different language can be handled by a compatible AI experience. The original message and inferred information must remain distinguishable.
Messages and calls: two connection paths
A voice note is a message; a WhatsApp call is a live conversation. Connecting business messaging does not activate calling. A calling project must cover the professional account, calling permissions, the audio connection and the interface used by the team.
WhatsApp Business Calling — a path to prepare
The aim is to continue an exchange by phone and keep its authorized content with the same customer relationship. This path is in preparation: WhatsApp calling is not yet available as an active feature. Availability must be confirmed for the proposed deployment.
The proposed calling path inside the AlefOS interface includes a WebRTC module. The media and provider connection are also part of its preparation. An enabled messaging account or a calling settings screen is not evidence that calls are operational.
The next colleague should not start again
A customer sends an access instruction, shares a document and asks to be called. Received messages provide the starting context. If a calling path is subsequently delivered, the authorized content it captures can extend that relationship. The colleague retrieves the available sources and what remains to confirm before replying.
From conversation to draft
A workflow can prepare a response, mission, appointment proposal or document follow-up. The recipient, context and channel must be checked before the intended send operation.
Successful preparation does not guarantee WhatsApp delivery. Provider results, permissions and channel rules still apply.
Configure and verify the connection
The company’s WhatsApp Business account, its permissions, received events and environment mapping must be checked. Consent rules and the data actually supported are part of the scope.
A connection must not be described as active just because a configuration page exists. A useful test checks an authorized event, its correct mapping and behaviour when data is missing or the connection is lost.
Distinguish conversations from IBOX notifications
An IBOX notification sent through WhatsApp uses a short summary and a temporary link to the complete message. This path is separate from working with WhatsApp conversation history.
Recipients can opt out of IBOX notifications through the documented process. Access to an IBOX message and access to WhatsApp exchanges must not be confused.
Voice notes, media and available history
A voice message, its transcription and an attached image are different resources. Transcription requires an available audio-processing flow and authorized content. An attachment indicator does not prove that its contents were read. Keep the original and the interpreted information distinct.
Connection does not guarantee a complete historical import, personal WhatsApp access or group synchronization. Check the scope of received messages and contact-level analysis controls during setup. Pausing analysis, opting out of IBOX notifications and disconnecting WhatsApp are different requests.
Delivery and provider charges
Creating a draft, accepting a send request and delivering a message are separate results. Business permissions, message rules and provider responses govern the external delivery. Any provider charges and audio-processing capacity should be specified in the offer, rather than inferred from an old subscription plan.
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.
Contacts and relationship context
Search identity fields, read linked context and inspect confirmed products. Adding or enriching a contact is a write operation; the preview mode depends on the tool policy.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
contacts. | Search contacts by identity fields, with cursor pagination and source filtering. |
contacts. | Read one contact profile and its available relationship context. |
contacts. | Find confirmed products in the contact’s product memory. |
contacts. | Add or enrich a contact; preview behavior follows the selected mode. |
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. |
Missions and responsibility
Read the source and execution state before acting. Confirming executes a pending mission; rejecting and archiving have different effects. Assignment follows company roles.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
missions. | List the current user’s missions, optionally grouped by contact. |
missions. | Read a mission’s source, related objects and execution state. |
missions. | Confirm and execute a pending mission. |
missions. | Reject a pending mission without executing it. |
missions. | Archive a mission without executing or deleting its action. |
missions. | Assign from the company queue or reassign with the required role; changes are audited. |
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Source | What must be verified |
|---|---|
| CallOS | Select the calling mode, numbers, media path and recording conditions. An embedded WebRTC interface is one option, not a requirement for every calling setup. Reference → |
| Phone services and providers | Define the account, available interfaces, call content and enabled operations. Existing and custom connections have an explicit scope. Reference → |
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 ↗