Module guide
Sales CRM
Accounts, contacts, deals, activity, forecasting, imports, and customer timelines.
Overview
Sales CRM is the standalone customer operating surface. It manages accounts, contacts, deals, activities, forecasts, imports, duplicate resolution, timelines, playbooks, and governed write actions. Contract, signing, and PDF links are available only when they add useful context.
Highlights
The capabilities worth knowing before you dive in.
- Account, contact, deal, and activity records with native Atlas ownership
- Searchable CRM Action Catalog for records, pipeline, activity, forecast, playbooks, imports, duplicate governance, and optional handoffs
- Pipeline, probability, weighted forecast, stale-deal rescue, and next-best actions
- Import dry-runs, conflict review, merge, rollback, duplicate suggestions, and saved queues
- Field validation for money, required names, bounded text, object pickers, and expected-close datetime
- Each cataloged CRM action names its user control, validation rule, app API route or standalone module boundary, and MCP target
- Role-aware governance with custom roles, audit logs, approvals, and delegated access
Important to know
Limits, permissions, and sharp edges to keep in mind.
- Amount fields accept numeric currency drafts only and submit integer cents to the API.
- Expected close uses the Atlas datetime picker so users choose an instant rather than typing browser-native date strings.
- CRM does not own PDF Studio, Contract Hub, or Document Sign. Those modules can be opened independently.
- The rep-performance leaderboard names each rep rather than listing their user identifier, because the question the leaderboard is opened to answer is who is ahead. The CSV export carries both the name and the identifier: the name so a person can read it, and the identifier so the file can be joined against other data.
How to use it
The primary workflow, start to finish.
- Open /crm and search the CRM Action Catalog for the task you need.
- Use Dashboard for pipeline posture, or Records for account and deal work.
- Create an account first when a deal needs customer context.
- Create a deal with a name, amount, account, and expected-close datetime.
- Use Import to dry-run CSV-like rows, review conflicts, and commit only after validation passes.
- Use Merge to preview survivor and duplicate behavior before applying governed changes.
FAQ
- Can I type letters into amount fields?
- No. The web control strips unsupported characters, and the API still validates bounded non-negative money in cents.
- Can CRM work without Salesforce or HubSpot?
- Yes. Atlas CRM is first-party. Provider connectors are optional sync and enrichment paths.
- How do I find the right CRM button or API action?
- Use the CRM Action Catalog on /crm. Search by task, field, validation rule, API route, MCP tool, or optional handoff such as PDF Studio.
Automate this module
Everything on this screen is scriptable. Drive it from the REST API, or let an AI agent run it through the MCP server.
Was this page helpful?