Everyday work
Sales teams: resume each opportunity with its story
From the first need to the next exchange, keep the customer, offer, objections and commitments in the same work context.
Connect the prospect’s interest to the next conversation.
You can first share the customer application to present offers and receive an enquiry. The sales workflow described here concerns the team: context, objections, responsibilities and next steps. These internal functions are defined under a separate scope.
Workflow example
A concrete workflow, from the signal to the next step
Recover the previous promise before the next call.
A WhatsApp exchange changes the requirement.
Review the ProductOS offer and the manager approval still needed.
Prepare a relevant follow-up and verify the sending result.
Fictional illustration. Available capabilities, sources and access depend on your environment; conditions are explained below.
On this page
Who this workflow is for
Salespeople, account managers, sales leaders and follow-up teams often work across calls, WhatsApp, appointments, notes and documents. The problem is not just missing information: the fragments exist, but the person who needs to act cannot always recover their connection.
The OS follows an authorized sales story: expressed need, discussed budget, proposed offer, objection, decision and next action. It does not automatically replace existing CRM fields or official records.
Before the next call
Retrieve what the prospect was looking for, what they rejected and what they still expect. Check whether the information is recent and the situation has changed. Contact context, available calls and open missions help prepare the exchange.
“Which customer is waiting for the revised quote?” and “Who needed a solution before the end of the quarter?” are work questions. Their answers must be traceable to accessible information.
Turn a conversation into a visible next step
A customer requests a narrower proposal after a call. The need and objection are preserved; a mission specifies the expected quote, responsible salesperson and deadline. A draft response can use the validated offer in ProductOS.
The salesperson checks recipient and content before sending through the intended workflow. The next conversation resumes from the same context. Rejecting one offer must not erase the reason another offer could become relevant later.
What the manager sees
Within their scope, a manager can retrieve waiting customers, unmet commitments, recurring objections and files blocked by a decision. Sales groups keep scripts and validated answers without exposing every private conversation.
The aim is to explain situations requiring intervention. A call disposition or checked task does not by itself describe the opportunity’s state.
Roles and handover
The salesperson owns follow-up, the manager handles decisions within their remit and the colleague taking over receives authorized context. Responsibility must remain explicit in contacts and missions.
A handover does not reset the relationship or authorize impersonation of the previous salesperson. Role, assignment and source limits continue to apply.
Conditions of use
Calls and messages must come from configured connections; meetings require available, authorized content. Sales preparation is neither a conversion guarantee nor an automatic pricing decision.
Deployment configures useful team modules and approval flows. Phone services, billing tools and official sales records retain their role.
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. |
ProductOS catalog
A detected suggestion, a confirmed internal product and a published /p/:productId page are distinct. Check the record and publication scope before sharing an offer.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
products. | List managed products and services within current catalog limits. |
products. | Read a managed catalog product or service. |
products. | Prepare a product or service creation preview. |
products. | Update an internal product; preview mode returns an action_id. |
products. | Archive an internal product; preview mode is available. |
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. |
Call context
An indexed call does not imply a transcript is available. Read the actual provider content; resolve an unknown contact explicitly before using its relationship context.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
calls. | List the calls visible in the current scope. |
calls. | Read an identified call’s available details. |
calls. | Read the available transcript for an explicit call_id. |
calls. | Prepare an explicit link between an unresolved call and an existing contact. |
calls. | Assign a call within the authorized company workflow. |
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
This workflow uses capabilities configured in your company’s environment, under your brand. Your team can use a compatible assistant to consult authorized context through its configured MCP connection. Understand your AI connection ↗