ARIA Sales documentation
ARIA Sales is the prospecting and sales-operations specialist inside the ARIA ecosystem. The current foundation has both a Random Target AI internal Sales workspace and an entitlement-aware customer Sales path that use organization-scoped prospect data.
Customer access
ARIA Sales remains visible in the customer console even when locked. Operational customer access requires an accessible aria_sales entitlement — currently Active or Trial — plus an allowed user role.
The customer route is /console/sales.php. A locked customer sees a product explanation and upgrade path rather than the operational prospect workspace.
Random Target AI internal versus customer Sales
Random Target AI's own operations remain at /console/internal/sales.php. The customer page does not redirect into that internal route.
The two pages can reuse the same presentation include while still operating in different authenticated organization contexts.
Prospects
A prospect record can include company, website, contact name/email/phone, industry, location, contact channel, contact status, stage, lead score, owner, approval state, source, notes and discovery/run metadata.
Creating and updating a prospect uses a deduplication key derived from available identifiers such as normalized website, email, phone or company/location. A duplicate is handled as a conflict rather than silently inserting another copy.
Stages and approval state
Prospect stage and outreach approval are separate fields. The foundation intentionally exposes separate endpoints so changing a workflow stage does not accidentally approve outreach.
Approval actions should remain auditable and scoped to the same organization as the prospect.
Review queue
The Sales workspace can filter prospects that are ready for human review and surface approval state, lead score, owner and recent outreach context. The purpose is to support controlled prospecting rather than automatically contacting every discovered business.
Prospecting runs
A prospecting run records criteria, connector state, status, result count and any error. Runs are stored by organization and can be listed or summarized without mixing one customer's run history with another's.
Export
Authorized Sales users can export the organization's filtered prospect rows to CSV through the Sales export endpoint. Export respects organization scoping and the same prospect filters used by the workspace.
Organization isolation
Every customer-facing Sales repository operation must preserve the authenticated user's organization_id. The current ProspectRepository, ProspectActivityRepository and ProspectingRunRepository use organization conditions for find, list, update, counts, activities and run history.
Discovery connector
The current prospecting-run endpoint behaves honestly when no discovery connector is configured. It records the run as failed with an explanation instead of pretending that an internet search occurred.
A future discovery/search connector should be configured separately and should honor industry, location, channel, deduplication, daily outreach and approval rules.
Customer roles
The current customer Sales operational path aligns with the existing Sales API guard for Admin and Manager. Member-level Sales permissions need a more detailed RBAC design before broad write access is granted.
Current limitations
- An external discovery connector may not be configured for a given deployment.
- Automatic outreach delivery/reply tracking depends on the connected channel integration.
- Billing does not yet automatically switch Sales entitlements.
- Member-level granular Sales permissions are not complete.
See Product access and Security & privacy.