Everyday work
Field teams: continue an intervention with its context
Connect the request, preparation, on-site findings and next steps so the next professional does not start from scratch.
Prepare the visit without losing the original request.
Customers describe their needs through the journey you share. Internal work can then bring together exchanges, access instructions, findings and follow-up work. This field-service scope is configured separately from the base catalogue and enquiries.
Workflow example
A concrete workflow, from the signal to the next step
Review the appointment, address and access instructions.
The visit reveals a part or external specialist is needed.
Preserve the finding and dependency in the appropriate work context.
Prepare the second visit with the next responsible person.
Fictional illustration. Available capabilities, sources and access depend on your environment; conditions are explained below.
On this page
Context gets lost between the office and the field
Installers, maintenance technicians, providers and coordinators work across the initial call, address, access instructions, appointment, report and additional request.
The schedule shows where and when to go. It does not always explain what was promised, what a colleague has already found or what is still blocking progress.
Arrive with the right information
Before the visit, retrieve the contact, available address, access constraints, purpose, previous interventions and expected documents or preparations. Context must come from authorized sources.
An old instruction should be checked if the situation has changed. The OS does not replace the trade’s technical and safety rules.
Preserve what changes on site
A part is missing, the scope differs, access is impossible or another skill becomes necessary. An authorized note or signal can connect the finding to the customer, appointment and next action.
The professional’s observation remains distinct from AI analysis. A photo or message is not technical certification.
From findings to the next intervention
After a visit, a mission can carry a part request, quote preparation, customer approval or second appointment. The reason stays attached to the work.
Example: the technician identifies a specific part as necessary. The office retrieves the context, prepares the customer request and waits for the applicable approval before continuing scheduling. Part or technician availability must be confirmed in the appropriate tools.
Coordination and shared knowledge
Groups can preserve procedures, field feedback, published availability and requests for help. A team finds useful experience or the colleague to consult without exposing an entire customer file.
Repetition can reveal a preparation problem to examine. It does not automatically constitute a fault diagnosis or official performance measurement.
What each role gains
The professional understands the request before leaving. The coordinator sees dependencies and next actions. The manager retrieves blocked situations within their scope. The next colleague takes over with accessible decisions and commitments.
Assignments, roles and permissions remain explicit. Customer notifications and other consequential actions follow their intended workflows; technical decisions, warranties and professional approvals remain with the professional.
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.
Calendar and booking context
An invitation, a booking link and a confirmed event are not the same state. Draft tools support review; authorized internal calendar operations can also run directly, according to the deployed tool policy.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
calendar. | List appointments, optionally filtered by date range. |
calendar. | Read an event’s available owner, contact, mission and provider context. |
calendar. | Prepare an event creation preview with an action_id. |
calendar. | Prepare an update or move preview for an existing event. |
calendar. | Assign or reassign an event with the required company role and audit trail. |
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. |
GroupOS knowledge and publishing
Search and digest are read operations. Publishing uses its confirmation mode. Updating or archiving a post and changing membership require the relevant author or administrator rights.
Scroll the table to read every column. With a keyboard, use the left and right arrow keys.
| Tool | Function and effect |
|---|---|
groups. | List accessible private groups and recent shared context. |
groups. | Read a group and the membership context visible to the current user. |
groups. | Search group entries by text, topic, kind and date range. |
groups. | Read a compact digest without publishing anything. |
groups. | Read recent shared work entries in an accessible group. |
groups. | Preview or publish a structured entry according to confirmMode. |
groups. | Edit an existing entry with the required author or administrator rights. |
groups. | Archive an entry with the required author or administrator rights. |
groups. | Add an authorized company member or prepare an external contact invitation. |
groups. | Remove membership within the role’s scope; the group creator cannot be removed. |
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 ↗