Understand your work OS

Your team can use what your company already knows.

An AI knowledge base built around the procedures, resolved cases and updates you choose to share. Your team asks a compatible assistant how to handle the work, using authorized company knowledge instead of searching through old group messages.

Explore an example Tools and access conditions

Your public catalogue is not a private working group.

Published offers can be browsed in the customer application. Group knowledge and decisions follow the internal permissions described here. Sharing the app with a prospect does not open your team’s groups.

Everyday work

The answer exists. Why does everyone keep asking?

A procedure gets buried in chat. A colleague explains the same solution again. GroupOS keeps the knowledge your team chooses to publish retrievable, alongside the conversations that continue in your everyday tools.

Your team’s knowledgeIllustrative example

Ask the knowledge your team has shared.

01SupportA case already resolved.

“Have we seen this access problem before?”

Shared case · support group

Check whether the invitation was sent to the address used to sign in. If they differ, ask the account owner to review the invitation.

The answer refers to the case published by the team.

02SalesThe right rule, in the right place.

“What does our diagnostic visit include?”

Published service rule · sales group

The visit includes travel and diagnosis. Repair work needs a separate quote after the diagnosis.

Prepare the reply from the shared offer, not from memory.

03Field teamCarry experience into the next job.

“What should I check before this type of visit?”

Published preparation guide · field group

Confirm the access contact, the permitted arrival time and the documents needed on site.

The shared guide helps preparation; technical decisions remain with the professional.

Fictional example, not a product screenshot. Sources and access require configuration; illustrated answers use the information shown.

Share the useful knowledge. Keep control of its audience.

Procedures, decisions, published offers and lessons from the field can support different groups. Joining a group does not publish a member’s private customer records or catalogue. Each person works with the knowledge their access allows.

Ask your OS from an assistant

On this page

A group should make work retrievable

A meeting decision, support answer, new objection or procedure can disappear inside a chat thread. Managers then repeat the same explanations and new colleagues reconstruct the history.

An AlefOS group organizes memory around a team, topic, process, service, customer segment or professional network. Entries can contain messages, decisions, summaries, procedures, scripts, offers, requests, announcements, rules, field feedback and items awaiting validation.

Internal groups and team knowledge

A sales group can preserve objections and approved answers, a support group its procedures and an operations group its changes. Leadership, training, onboarding and field teams can have their own spaces.

Authorized publication makes information reusable. It does not mean every existing Slack or WhatsApp group is automatically imported, synchronized or searchable.

After the meeting

A report can be added to the right group through the intended workflow. Decisions remain retrievable: who owns the next step, which pricing rule changed, what awaits approval or which commission was agreed.

The calendar supplies the date; the report supplies content when it exists. A meeting without authorized notes or a transcript must not produce an invented history.

Professional networks and opportunities

A group can bring together estate agents, brokers, service providers, consultants, subcontractors, installers or logistics partners. Authorized members publish availability, requests, skills, service areas and opportunities.

Example: an agent shares a two-bedroom apartment near Manchester city centre. Another has a matching customer request. Context can help suggest a match and prepare an introduction. The match still needs verification; it does not authorize sharing the customer’s private file.

Field coordination and sales learning

A team can look for an available professional in an area, a missing skill or the latest service procedure. The group preserves the request, constraints, useful experience and next actions.

A sales group can keep scripts, objection responses, pricing changes, call feedback and reasons for rejection. It provides a working basis for understanding recurring issues. An analysis must not be presented as a measured statistic when the necessary data is missing.

Search, read a digest and prepare an action

An authorized user can ask what changed, find a procedure, search for an opportunity or consult recent decisions. Focused search and digests avoid rereading the entire history.

Depending on enabled workflows, this knowledge can help prepare a mission, message, introduction, summary or alert. Reading publishes nothing. Publishing or editing an entry uses its own tool and permissions.

Membership, roles and control

A group remains a controlled space. Access depends on membership, role, company and authorized context. Invitations and member additions or removals are not equivalent to searching.

The author or administrator may have permission to edit or archive an entry. Knowing a group identifier is not authorization. Shared memory must give the right context to the right people.

Joining, searching and publishing are separate

Joining a group does not publish your customer records, product catalogue or private workspace. A team deliberately selects which decisions, procedures, offers or solved cases should become reusable knowledge.

Members can use different compatible assistants when their connections and permissions support the group. An internal support group and a professional opportunity network serve different audiences; neither makes every member’s private information public.

Help the new colleague find how your team works.

A replacement needs the customer history and the team’s methods. An authorized group member can ask about the approved maintenance terms, the support procedure or a similar solved case from the knowledge deliberately shared by the team.

Joining the relevant groups makes their permitted knowledge available; it does not import private conversations or automatically grant access to customer cases.

Ask about your methods, not just your documents

“How did our team resolve this type of intervention?” The useful answer depends on the resolved cases and procedures shared with that group. It should distinguish the current method from an older example and leave a missing answer open for clarification.

A new colleague uses the same approved knowledge as the rest of the team. You decide what belongs in a support group, a sales group or a shared company reference. Keeping WhatsApp for conversation does not require leaving the working method buried in the message 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.

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.

Tool	Function and effect
`groups.list`	List accessible private groups and recent shared context.
`groups.get`	Read a group and the membership context visible to the current user.
`groups.search`	Search group entries by text, topic, kind and date range.
`groups.digest`	Read a compact digest without publishing anything.
`groups.messages`	Read recent shared work entries in an accessible group.
`groups.draft_send`	Preview or publish a structured entry according to confirmMode.
`groups.message.update`	Edit an existing entry with the required author or administrator rights.
`groups.message.archive`	Archive an entry with the required author or administrator rights.
`groups.members.add`	Add an authorized company member or prepare an external contact invitation.
`groups.members.remove`	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

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 ↗

Decide who can contribute and consult.

Choose how your assistant accesses company knowledge ↗