Understand your work OS
WhatsApp CRM: keep the reason for the next exchange
Your customer already explained the request on WhatsApp Business. In your company’s environment, the authorized colleague taking over can find the received exchange and the promised reply.
Your WhatsApp channel and customer application serve different roles.
The customer application lets people browse offers and submit an enquiry. The WhatsApp connection described here adds received, authorised business exchanges to the work context. It is a separate scope with its own provider and access conditions.
Workflow example
The colleague changes. The customer does not start again.
A customer sends a photo through the connected WhatsApp Business channel.
The exchange received by the OS remains available within the permitted scope.
A colleague finds the photo and the promised reply in IBOX before calling.
The WhatsApp reference explains connection prerequisites; IBOX explains consultation and team access.
Fictional illustration. Available capabilities, sources and access depend on your environment; conditions are explained below.
On this page
WhatsApp already carries part of the work
Customers ask questions, send documents, confirm a budget, move an appointment and request a follow-up. The conversation remains useful; the risk is losing the reason for the next action inside the thread.
Preserve useful context
When a WhatsApp Business conversation is connected, available and authorized, requests, promises, objections, documents and follow-up dates can be linked to the right customer’s work.
Depending on the supported workflow, this context can contribute to a contact, an IBOX message, a mission or a prepared action. Every message does not automatically create a record or mission.
WhatsApp remains the channel
AlefOS does not replace WhatsApp Business or read every conversation. It does not promise a universal shared inbox. Only exchanges supplied by an authorized connection can support work continuity.
An existing WhatsApp group is not automatically a GroupOS group. Publishing knowledge in GroupOS follows its own workflow and permissions.
Prepare a reply before sending it
The OS can help prepare a response or follow-up from available context. Preparing is not sending: enabled capabilities, the provider, permissions and the approval flow still apply.
An IBOX notification through WhatsApp is a separate use: it contains a short summary and a link to the complete message. It does not turn every WhatsApp exchange into an IBOX message.
Team continuity respects access rights
People responsible for a file retrieve the context available to them. A manager role does not mean all employees’ raw conversations become visible.
Visibility depends on role, assignment, workspace and source permissions. A disconnected source or missing information must remain visible as a limitation, without inventing the missing history.
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. |
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 ↗