Who it is for
- AtlasLoop workspaces that need lead review, campaign coordination, encrypted email-account testing, inbound classification, suppression, and send-policy checks.
Betaai_sales_manager
Human-governed sales execution for tenant-scoped leads, campaigns, inbox signals, and follow-ups.
Create and review tenant-scoped leads and campaigns, test encrypted email connections, classify inbound replies, apply suppression, and evaluate controlled send guards. Google Maps discovery remains queued through a separately deployed provider service.
Runtime availability depends on the canonical product status, organization entitlement, workspace permissions, deployment configuration, and any provider-specific authorization required by the workflow. Public product pages do not list prices or offer checkout; commercial availability must be confirmed in writing.
Codebase contract
- Application route: /revenue/sales
- Required permissions: revenue:read
How the current workflow works
- 1Activate the eligible workspace trial, then open AI Sales Manager at /revenue/sales.
- 2Create or review leads and campaigns within the selected workspace.
- 3Configure an encrypted email account and run its safe connection test before any send evaluation.
- 4Use inbound classification and send-policy checks; human approval and suppression rules remain enforced server-side.
Current codebase capabilities
- Tenant-scoped lead deduplication, review states, campaigns, encrypted email-account storage, inbound classification, suppression, and follow-up cancellation.
- Google Maps discovery is queued to a separately deployed provider service and never runs as synchronous scraping in the browser.
Current boundaries
- No production use, provider coverage, pricing, service level, or autonomous follow-up is claimed.
- Controlled send checks do not grant autonomous outbound delivery.
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
revenue:readrevenue:writerevenue:approveRequired permissions
revenue:readWhat to verify after using it
- The workspace catalog and canonical entitlement endpoint must agree before the product can be opened.
- Credential blobs and provider secrets are never returned to the browser.