Salesloft

Breadth across classes, and the CRM-agnostic position is the distinctive part. Salesloft runs natively against both Salesforce and HubSpot rather than assuming a single system of record, which is the practical reason teams running different CRMs across business units pick it.

Around that sit the Salesloft Connect extension inside Gmail and Outlook, dialer and calendar connectivity, conferencing for call capture, and a stated partner ecosystem feeding the enterprise data model.

Programmatic reach runs through the v2 REST API covering people, accounts, cadences, memberships, actions, tasks, notes, calls and emails, with SCIM 2.0 for identity, and outward through the MCP server into AI clients.

Sourcesalesloft.com/platform/enterprise-data-platform and api.salesloft.com/v2read 2026-09-04

Signals in, a ranked queue out, executed across modules. Rhythm consolidates buyer signals from across the funnel and the Prioritizer AI Agent turns them into a prioritized per-seller workflow carrying the reason each action surfaced, so the output is an ordered decision rather than a task list.

Beneath it Cadence runs multi-step multichannel sequences with branching logic, Conversations supplies call intelligence, and Deals and Forecast carry the closing motion, with chat agents feeding website intent into the same queue rather than a separate inbox. The chain is addressable from outside through the v2 REST API's cadence and cadence-membership resources and through the MCP server.

Sourcesalesloft.com/platform/rhythm and salesloft.com/platform/enterprise-data-platformread 2026-09-04

Grounded on interaction history and CRM state, not on a corpus the customer supplies. Chat agents tailor responses using web activity, CRM data and past conversations, and the enterprise data model assembles real-time context across signals so an agent knows what has already happened with an account before it speaks.

That is behavioral and record context rather than a documented retrieval layer over customer content. No document ingestion, knowledge base connection, content library or citation surface is documented, so nothing lets a team ground an agent in their own product documentation, pricing rules or approved messaging.

Sourcesalesloft.com/platform/chat-agents and salesloft.com/platform/enterprise-data-platformread 2026-09-04

A stated position and admin constraints, no gate on an action. The platform says the AI knows when to act autonomously and when to bring in a human, the home page labels plays Agent+Human and shows a review of human against AI forecast projections, role permissions set what users and integrations may do, and MCP access is enabled per user by an admin; no approval queue, review step or threshold that holds an agent action is documented.

Sourcesalesloft.com and salesloft.com/platform/enterprise-data-platformread 2026-10-01

Compliance and access are both documented. Salesloft holds SOC 2 Type 2, examined annually across the Salesloft and Drift services, along with ISO 27001 and ISO 27701, and the trust center at trust.salesloft.com lists CSA, GDPR, CCPA and the Data Privacy Frameworks beside documents and a dated subprocessor list. On access, the platform offers administration privileges and role permission configuration, SAML single sign-on and SCIM 2.0 provisioning, with SCIM on the Enterprise tier.

Sourcetrust.salesloft.com and salesloft.com/security-complianceread 2026-10-01

Managers see the pipeline and the rep; nobody sees the agent. Forecast, Deals and Conversations give visibility across pipeline movement, deal state and rep activity, call intelligence surfaces what was said, and Rhythm attaches to each surfaced action the reason it was ranked, which is decision transparency at the prioritization layer and better than a bare queue. Nothing traces agent behavior.

There is no log of what the Prioritizer weighed before ranking an action, no record of what a chat agent said to a visitor and on what basis, no configuration change trail, and no retention control over such a record. The chat agents make the gap material rather than theoretical, since they converse with buyers unattended and the transcript is the only artifact. Role permissions and administration privileges govern what a user or integration may do; that is access control, not a record of what was then done.

Sourcesalesloft.com and salesloft.com/platform/rhythmread 2026-09-04

An interaction store, not memory. The enterprise data model retains signals from customer interactions, chat agents draw on past conversations and CRM data, and cadence membership and activity state persist; those are business records the agents read, and no memory the agents keep as their own state, with a scope, lifetime or delete path, is documented.

Sourcesalesloft.com/platform/enterprise-data-platformread 2026-10-01

Multi-tenant cloud with no location or topology control offered. No region selection, EU or other in-region option, private cloud, VPC, single-tenant tier or on-premises route appears on the platform pages, the security and compliance page or the trust center.

The trust center is otherwise detailed, publishing eight compliance badges, twelve documents and a maintained subprocessor list, yet it names no hosting region or residency option. What the trust center does carry on cross-border movement is legal cover: certification under the EU-US and UK-US Data Privacy Frameworks alongside GDPR and CCPA. Legal cover is not residency.

Sourcetrust.salesloft.com and salesloft.com/security-complianceread 2026-09-04

Named agents that ship built, and no catalog to browse. The agents are real: a Prioritizer AI Agent inside Rhythm that turns buyer signals into a ranked per-seller queue with the reason attached, and the Drift-derived chat agents that engage on the website and route captured intent into that same queue. No agent marketplace, play library or template gallery is documented.

Sourcesalesloft.com/platform/rhythm and salesloft.com/platform/chat-agentsread 2026-09-04

Buyer behavior sets the work in motion without anyone starting it. Chat agents engage a visitor on arrival and pipe captured intent into the seller's Rhythm queue in real time, and Rhythm consolidates buyer signals into ranked actions without waiting to be opened; channels out are email, phone, LinkedIn and direct mail through Cadence, website chat and the Connect extension. No scheduled run or webhook listener is documented by name.

Sourcesalesloft.com/platform/chat-agents and salesloft.com/platform/rhythmread 2026-10-01

The customer does not choose the model and no provider is named. No model list, routing policy, per-workspace selection or bring-your-own-key option appears on the platform pages, the security and compliance page or the trust center.

The AI is presented as built on Salesloft's own enterprise data model, which is a claim about the data the models reason over rather than about which models they are.

The MCP server lets a customer's own assistant, with Claude named among the clients, query Salesloft data; that is the customer picking the interface that reads the vendor, not a choice of what powers the product.

Sourcesalesloft.com/platform/enterprise-data-platformread 2026-09-04

Two external routes, one long-established and one recent. The versioned v2 REST API at api.salesloft.com has been the integration surface for years, covering people, accounts, cadences, cadence memberships, actions, tasks, notes, calls and emails, authenticated by personal access token or OAuth 2.0, with SCIM 2.0 exposed separately at the same host for identity provisioning.

Alongside it a Salesloft MCP Server shipped in the April 2026 release, letting AI tools pull live pipeline, call and account data directly, with setup documented in the vendor's own help center, availability gated to the Salesloft Agentic add-on and enablement controlled per user by a workspace admin.

Sourcesalesloft.com and api.salesloft.com/v2read 2026-09-04

An optimization loop over outcomes, aimed at the business result rather than at the agent. The vendor states that agents analyze millions of interactions and outcomes to tune what to do and when, so the ranking model calibrates against what actually converted, and cadence analytics let a team read step-level performance and adjust sequences accordingly.

Nothing tests the agents under control. There is no evaluation harness, scored test set, benchmark, regression check when a cadence or the prioritization model changes, and no sandbox or dry run before an agent acts, which matters most for the chat agents since their output reaches a buyer directly with no reviewer in between.

Sourcesalesloft.com/platform/rhythmread 2026-09-04

Everything the platform touches arrives through an authenticated interface. The Salesloft Connect browser extension surfaces the platform inside Gmail, Outlook and the CRM so a rep works without switching tabs, but it renders Salesloft into those pages under user control rather than driving software the vendor does not control.

Chat agents run on the customer's own website, which is a property the customer owns and instruments deliberately, not a third-party interface being operated without one. Everything else moves through native Salesforce and HubSpot connectivity, the dialer, the v2 REST API and the MCP server. No portal autofill, headless session, screen or click automation appears anywhere.

Sourcesalesloft.com and salesloft.com/platform/chat-agentsread 2026-09-04