{
  "title": "Team",
  "internal_name": null,
  "slug": "team",
  "url": "https://alefos.ai/documentation/team",
  "json_url": "https://alefos.ai/documentation/team.json",
  "summary": "See which customers are waiting and why without chasing every salesperson.",
  "description": "AlefOS turns authorized calls, messages, meetings and follow-ups into shared company memory, so managers can see blockers, commitments and actions that need attention.",
  "category": "Business",
  "last_updated": "2026-07-23",
  "keywords": [
    "Team",
    "company memory",
    "managers",
    "permissions",
    "deployment"
  ],
  "sections": [
    {
      "heading": "Who Team is for",
      "content": "Team is built for organizations that work with several people.\n\nExamples:\n\n- Sales teams.\n- Phone sales teams.\n- Field teams.\n- Agencies.\n- Professional firms.\n- Partner networks.\n- Support teams.\n- Sales managers.\n- Small and medium businesses.\n- Companies that sell by phone, messaging and appointments.\n\nThese teams often share the same problem: each person knows part of the story, but nobody sees the full picture clearly."
    },
    {
      "heading": "The problem",
      "content": "In a team, important information is often scattered.\n\nA salesperson speaks with a customer. A manager gives an instruction. An appointment is scheduled. An important message is sent. An objection comes back often. A follow-up is forgotten. A decision is posted in a group. A warm customer stays inside one person memory.\n\nThe result:\n\n- Managers need to ask where each case stands.\n- Salespeople repeat the same mistakes.\n- Follow-ups are not always tracked.\n- New team members learn slowly.\n- Decisions disappear.\n- The company depends too much on individual memory.\n\nTeam exists to move that memory out of people's heads and structure it inside AlefOS."
    },
    {
      "heading": "Shared operational memory",
      "content": "Team gives the company a shared operational memory.\n\nThis memory can bring together:\n\n- Contacts.\n- Calls.\n- Messages.\n- Appointments.\n- Missions.\n- Groups.\n- Products or services.\n- Decisions.\n- Scripts.\n- Objections.\n- Field feedback.\n- Customer follow-ups.\n- Sales signals.\n- Actions to validate.\n\nThe goal is not to create another CRM to fill manually. The goal is to connect real work and make it searchable, understandable and actionable."
    },
    {
      "heading": "Tenant / Owner",
      "content": "In Team, the Tenant / Owner represents the company main workspace.\n\nIt is the central memory.\n\nThe Owner is the first level of control and management inside the tenant.\n\nThe Owner can manage the company memory, users, managers, permissions, groups, access, integrations and general configuration.\n\nThe Tenant / Owner is the starting point of every Team plan."
    },
    {
      "heading": "Field users",
      "content": "Field users are the people who produce signals from real work.\n\nThey can be salespeople, phone agents, field agents, support agents, operators, team members, employees or contractors.\n\nThey feed the memory through calls, messages, contacts, missions, appointments, notes, exchanges and actions.\n\nA field user does not necessarily need to manage the entire company. Their role is mainly to use AlefOS in daily work and contribute to the operational memory."
    },
    {
      "heading": "Managers",
      "content": "Managers have a different role.\n\nA manager is not just one more user. A manager has a cockpit.\n\nA manager can see, analyze and follow authorized signals according to their scope.\n\nA manager can be responsible for a team, group, region, department, pipeline, network or set of users.\n\nA manager can ask AlefOS:\n\n- What missions are open?\n- Which customers are waiting for a reply?\n- Which salespeople have late follow-ups?\n- What objections came back this week?\n- Which calls created missions?\n- Which prospects are warm?\n\nThe manager no longer depends only on manual reports. They manage from AlefOS memory."
    },
    {
      "heading": "Permissions and visibility",
      "content": "Team is based on permissions.\n\nNot everyone sees everything.\n\nThe company can organize visibility according to roles, managers, teams, groups, contacts, missions, signals and authorized scope.\n\nThe goal is to give each person the memory they need without exposing the entire company unnecessarily.\n\nA manager sees the authorized signals of their team. A field user sees what is relevant to their work. The Owner keeps the global view of the tenant."
    },
    {
      "heading": "Team Groups",
      "content": "In Team, Groups become very powerful.\n\nA company can create shared memory spaces for sales, support, management, procedures, training, meetings, objections, products, operations and partners.\n\nEach Group can become searchable memory.\n\nA manager can ask what was decided in the sales Group, what the latest procedure is, which objection comes back most often and what changed this week.\n\nGroups help teams stop repeating the same explanations and keep decisions accessible."
    },
    {
      "heading": "Team Missions",
      "content": "Team allows the company to track actions across a team.\n\nMissions can come from a call, message, appointment, Group, decision, manager or detected signal.\n\nThey can represent a follow-up, callback, document to send, message to validate, meeting to confirm, internal action, customer follow-up or blocked action.\n\nFor managers, this creates a clear view of execution. They can see what is prepared, pending, validated, blocked or forgotten."
    },
    {
      "heading": "Deployment",
      "content": "Team is not only a subscription. It is a deployment.\n\nDeployment helps structure the company correctly inside AlefOS:\n\n- Tenant creation.\n- Owner configuration.\n- Manager configuration.\n- User setup.\n- Permissions.\n- Groups.\n- Integrations.\n- Initial configuration.\n- Manager training.\n- Onboarding support.\n\nThe purpose of deployment is not only to create an account. The purpose is to make sure the team actually uses AlefOS correctly."
    },
    {
      "heading": "Onboarding support",
      "content": "The initial Team deployment includes onboarding support.\n\nThe goal is to help the company understand AlefOS, configure the right scopes, train managers, activate users, structure Groups, follow the first Missions, correct early usage and build the right habits.\n\nThe first months matter because this is when the company memory begins to grow. Once the memory is installed, AlefOS becomes much harder to replace."
    },
    {
      "heading": "Pricing model",
      "content": "Team pricing is structured around the company setup.\n\nThe model is based on:\n\n- Tenant / Owner: the company central memory and first management layer.\n- Field users: users who feed the memory through daily work.\n- Additional managers: manager cockpits with authorized visibility over teams, scopes or departments.\n- Deployment: configuration, permissions, onboarding and manager setup.\n\nDetailed pricing depends on the team structure, number of users, number of managers and deployment needs.\n\nFor a Team plan adapted to the company structure, the user should contact AlefOS Sales.\n\nDo not display the full internal pricing formula on this public documentation page."
    },
    {
      "heading": "Team deployment model",
      "content": "The Team deployment model depends mainly on the number of managers and the complexity of the structure.\n\nAdding a field user is usually simple.\n\nAdding a manager requires more configuration:\n\n- Visibility.\n- Permissions.\n- Team scope.\n- Groups.\n- Cockpit setup.\n- Onboarding.\n- Training.\n\nThis is why manager deployment is treated differently from simple user activation."
    },
    {
      "heading": "Difference between Solo and Team",
      "content": "Solo is built for one person. Team is built for an organization.\n\nSolo helps one user retrieve and act on personal work memory.\n\nTeam helps a company structure shared memory, give managers visibility and follow collective execution.\n\nSimple distinction: Solo organizes personal memory. Team organizes company memory."
    },
    {
      "heading": "What Team gives the company",
      "content": "For managers, Team helps follow real activity, view open missions, detect forgotten follow-ups, understand objections, identify warm customers, track team signals, prepare meetings, train faster, reduce manual reporting and manage without asking the same questions again.\n\nFor field users, Team helps recover customer context, prepare follow-ups, avoid forgotten actions, access useful Groups, track Missions, prepare calls and work with less mental load.\n\nFor the company, Team helps build memory that remains. When a team member leaves, part of the context remains in AlefOS. When a new team member joins, they can learn faster. When a manager asks where a customer stands, they can ask AlefOS."
    },
    {
      "heading": "Clear ownership without closed silos",
      "content": "Team keeps responsibility explicit without preventing authorized collaboration.\n\n- New or released work can remain in the company queue.\n- One primary owner stays responsible for the customer, mission or appointment.\n- Observers can read only the sections they are allowed to see.\n- Contributors can help only inside the sections they are allowed to change.\n- Access can expire or be revoked.\n- Assignment and collaboration changes are audited.\n\nA collaborator does not become the owner and cannot silently impersonate the responsible member."
    },
    {
      "heading": "Key takeaway",
      "content": "Team is the AlefOS plan for companies that want to move from scattered work to shared memory.\n\nIt is not a manual CRM. It is not only a collaboration tool. It is not a simple per-user subscription.\n\nIt is operational memory with field users who feed it, managers who drive it and an Owner who controls the tenant.\n\nThe simple idea: your team already works. AlefOS makes sure it remembers, aligns and acts faster."
    }
  ],
  "typical_questions": [
    "What needs manager attention today?",
    "Which customers are still waiting for a reply?",
    "Which follow-ups are overdue?",
    "What needs manager approval?",
    "Which prospects are warm but blocked?"
  ],
  "related_pages": [
    "deployment",
    "contact",
    "call-provider",
    "meeting-providers",
    "groups",
    "missions",
    "ibox",
    "contacts",
    "team-ownership"
  ],
  "important_notes": [
    "Do not expose the full internal pricing formula publicly.",
    "Detailed pricing belongs in sales conversations."
  ],
  "markdown": "# Team\n\nLast updated: 2026-07-23\n\nAlefOS turns authorized calls, messages, meetings and follow-ups into shared company memory, so managers can see blockers, commitments and actions that need attention.\n\n## Who Team is for\n\nTeam is built for organizations that work with several people.\n\nExamples:\n\n- Sales teams.\n- Phone sales teams.\n- Field teams.\n- Agencies.\n- Professional firms.\n- Partner networks.\n- Support teams.\n- Sales managers.\n- Small and medium businesses.\n- Companies that sell by phone, messaging and appointments.\n\nThese teams often share the same problem: each person knows part of the story, but nobody sees the full picture clearly.\n\n## The problem\n\nIn a team, important information is often scattered.\n\nA salesperson speaks with a customer. A manager gives an instruction. An appointment is scheduled. An important message is sent. An objection comes back often. A follow-up is forgotten. A decision is posted in a group. A warm customer stays inside one person memory.\n\nThe result:\n\n- Managers need to ask where each case stands.\n- Salespeople repeat the same mistakes.\n- Follow-ups are not always tracked.\n- New team members learn slowly.\n- Decisions disappear.\n- The company depends too much on individual memory.\n\nTeam exists to move that memory out of people's heads and structure it inside AlefOS.\n\n## Shared operational memory\n\nTeam gives the company a shared operational memory.\n\nThis memory can bring together:\n\n- Contacts.\n- Calls.\n- Messages.\n- Appointments.\n- Missions.\n- Groups.\n- Products or services.\n- Decisions.\n- Scripts.\n- Objections.\n- Field feedback.\n- Customer follow-ups.\n- Sales signals.\n- Actions to validate.\n\nThe goal is not to create another CRM to fill manually. The goal is to connect real work and make it searchable, understandable and actionable.\n\n## Tenant / Owner\n\nIn Team, the Tenant / Owner represents the company main workspace.\n\nIt is the central memory.\n\nThe Owner is the first level of control and management inside the tenant.\n\nThe Owner can manage the company memory, users, managers, permissions, groups, access, integrations and general configuration.\n\nThe Tenant / Owner is the starting point of every Team plan.\n\n## Field users\n\nField users are the people who produce signals from real work.\n\nThey can be salespeople, phone agents, field agents, support agents, operators, team members, employees or contractors.\n\nThey feed the memory through calls, messages, contacts, missions, appointments, notes, exchanges and actions.\n\nA field user does not necessarily need to manage the entire company. Their role is mainly to use AlefOS in daily work and contribute to the operational memory.\n\n## Managers\n\nManagers have a different role.\n\nA manager is not just one more user. A manager has a cockpit.\n\nA manager can see, analyze and follow authorized signals according to their scope.\n\nA manager can be responsible for a team, group, region, department, pipeline, network or set of users.\n\nA manager can ask AlefOS:\n\n- What missions are open?\n- Which customers are waiting for a reply?\n- Which salespeople have late follow-ups?\n- What objections came back this week?\n- Which calls created missions?\n- Which prospects are warm?\n\nThe manager no longer depends only on manual reports. They manage from AlefOS memory.\n\n## Permissions and visibility\n\nTeam is based on permissions.\n\nNot everyone sees everything.\n\nThe company can organize visibility according to roles, managers, teams, groups, contacts, missions, signals and authorized scope.\n\nThe goal is to give each person the memory they need without exposing the entire company unnecessarily.\n\nA manager sees the authorized signals of their team. A field user sees what is relevant to their work. The Owner keeps the global view of the tenant.\n\n## Team Groups\n\nIn Team, Groups become very powerful.\n\nA company can create shared memory spaces for sales, support, management, procedures, training, meetings, objections, products, operations and partners.\n\nEach Group can become searchable memory.\n\nA manager can ask what was decided in the sales Group, what the latest procedure is, which objection comes back most often and what changed this week.\n\nGroups help teams stop repeating the same explanations and keep decisions accessible.\n\n## Team Missions\n\nTeam allows the company to track actions across a team.\n\nMissions can come from a call, message, appointment, Group, decision, manager or detected signal.\n\nThey can represent a follow-up, callback, document to send, message to validate, meeting to confirm, internal action, customer follow-up or blocked action.\n\nFor managers, this creates a clear view of execution. They can see what is prepared, pending, validated, blocked or forgotten.\n\n## Deployment\n\nTeam is not only a subscription. It is a deployment.\n\nDeployment helps structure the company correctly inside AlefOS:\n\n- Tenant creation.\n- Owner configuration.\n- Manager configuration.\n- User setup.\n- Permissions.\n- Groups.\n- Integrations.\n- Initial configuration.\n- Manager training.\n- Onboarding support.\n\nThe purpose of deployment is not only to create an account. The purpose is to make sure the team actually uses AlefOS correctly.\n\n## Onboarding support\n\nThe initial Team deployment includes onboarding support.\n\nThe goal is to help the company understand AlefOS, configure the right scopes, train managers, activate users, structure Groups, follow the first Missions, correct early usage and build the right habits.\n\nThe first months matter because this is when the company memory begins to grow. Once the memory is installed, AlefOS becomes much harder to replace.\n\n## Pricing model\n\nTeam pricing is structured around the company setup.\n\nThe model is based on:\n\n- Tenant / Owner: the company central memory and first management layer.\n- Field users: users who feed the memory through daily work.\n- Additional managers: manager cockpits with authorized visibility over teams, scopes or departments.\n- Deployment: configuration, permissions, onboarding and manager setup.\n\nDetailed pricing depends on the team structure, number of users, number of managers and deployment needs.\n\nFor a Team plan adapted to the company structure, the user should contact AlefOS Sales.\n\nDo not display the full internal pricing formula on this public documentation page.\n\n## Team deployment model\n\nThe Team deployment model depends mainly on the number of managers and the complexity of the structure.\n\nAdding a field user is usually simple.\n\nAdding a manager requires more configuration:\n\n- Visibility.\n- Permissions.\n- Team scope.\n- Groups.\n- Cockpit setup.\n- Onboarding.\n- Training.\n\nThis is why manager deployment is treated differently from simple user activation.\n\n## Difference between Solo and Team\n\nSolo is built for one person. Team is built for an organization.\n\nSolo helps one user retrieve and act on personal work memory.\n\nTeam helps a company structure shared memory, give managers visibility and follow collective execution.\n\nSimple distinction: Solo organizes personal memory. Team organizes company memory.\n\n## What Team gives the company\n\nFor managers, Team helps follow real activity, view open missions, detect forgotten follow-ups, understand objections, identify warm customers, track team signals, prepare meetings, train faster, reduce manual reporting and manage without asking the same questions again.\n\nFor field users, Team helps recover customer context, prepare follow-ups, avoid forgotten actions, access useful Groups, track Missions, prepare calls and work with less mental load.\n\nFor the company, Team helps build memory that remains. When a team member leaves, part of the context remains in AlefOS. When a new team member joins, they can learn faster. When a manager asks where a customer stands, they can ask AlefOS.\n\n## Clear ownership without closed silos\n\nTeam keeps responsibility explicit without preventing authorized collaboration.\n\n- New or released work can remain in the company queue.\n- One primary owner stays responsible for the customer, mission or appointment.\n- Observers can read only the sections they are allowed to see.\n- Contributors can help only inside the sections they are allowed to change.\n- Access can expire or be revoked.\n- Assignment and collaboration changes are audited.\n\nA collaborator does not become the owner and cannot silently impersonate the responsible member.\n\n## Key takeaway\n\nTeam is the AlefOS plan for companies that want to move from scattered work to shared memory.\n\nIt is not a manual CRM. It is not only a collaboration tool. It is not a simple per-user subscription.\n\nIt is operational memory with field users who feed it, managers who drive it and an Owner who controls the tenant.\n\nThe simple idea: your team already works. AlefOS makes sure it remembers, aligns and acts faster.\n\n## Typical questions\n\n- What needs manager attention today?\n- Which customers are still waiting for a reply?\n- Which follow-ups are overdue?\n- What needs manager approval?\n- Which prospects are warm but blocked?\n\n## Important notes\n\n- Do not expose the full internal pricing formula publicly.\n- Detailed pricing belongs in sales conversations."
}