Sales CRM

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.

• 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

• 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.
• A record detail page shows related contacts, deals, contracts and activity only once those links exist. Where nothing is linked yet, each panel says so rather than showing an example, so everything on the screen belongs to the record you opened.
• The import box starts empty and the example row is a placeholder. Nothing is written until you paste your own rows, preview them, and commit. The box used to open with a complete example row already in it, which the preview and commit controls beneath would happily write into your real CRM.
• Sales CRM is a paid module. A workspace on a plan without it sees the upgrade page rather than the CRM screens.

1. 1Open /crm and search the CRM Action Catalog for the task you need.
2. 2Use Dashboard for pipeline posture, or Records for account and deal work.
3. 3Create an account first when a deal needs customer context.
4. 4Create a deal with a name, amount, account, and expected-close datetime.
5. 5Use Import to dry-run CSV-like rows, review conflicts, and commit only after validation passes.
6. 6Use Merge to preview survivor and duplicate behavior before applying governed changes.

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.