Coming soonai_sales_manager

AI-assisted sales coordination is on the roadmap, not an executable workspace yet.

Coordinate lead response, follow-up, pipeline visibility, and sales coaching through AI-assisted sales workflows connected to the shared platform after the capability is shipped.

Runtime availability depends on the canonical product status, organization entitlement, workspace permissions, deployment configuration, and any provider-specific authorization required by the workflow.

Who it is for

  • Teams interested in a future lead-response, follow-up, pipeline-visibility, and sales-coaching workflow built on the shared AtlasLoopOS platform.

Codebase contract

  • Application route: /products/ai-sales-manager
  • Required permissions: ai_sales_manager.access

How the current workflow works

  1. 1Open the Product catalog and confirm that AI Sales Manager is still labelled Coming soon.
  2. 2Review the public product description and planned capability boundary without treating it as an enabled workflow.
  3. 3Request availability if the planned product is relevant to your organization.
  4. 4Do not configure production processes around this product until an executable surface, entitlement path, and updated documentation are shipped.
  5. 5When the status changes in the canonical product manifest, follow the then-current documentation rather than this roadmap description.

Current codebase capabilities

  • The canonical manifest defines the product identity and planned access, lead-response, and API-validation capability names.
  • A public Coming soon description can be presented without implying runtime availability.

Current boundaries

  • There is no executable customer workflow represented by the current product manifest status.
  • No production use, provider coverage, pricing, service level, or autonomous follow-up is claimed.
  • The application route is a roadmap placeholder until implementation is shipped and documented.

Manifest capabilities and permissions

These identifiers are read directly from the canonical frontend product manifest. They describe access boundaries and capability names; they do not by themselves prove provider configuration or runtime availability.

Capabilities

ai_sales_manager.accessai_sales_manager.leads.respondai_sales_manager.api.validate_license

Required permissions

ai_sales_manager.access

What to verify after using it

  • The public catalogue continues to show Coming soon until the canonical manifest is intentionally changed.
  • No user should be told that a roadmap capability is available merely because a route or capability name exists.