Change Log

Saleshandy introduced Prospect Enrollment for Sequences, letting users cap how many new prospects enter the first step of a sequence per day, week or month. The release also includes rebuilt API documentation and expanded API access.

Pacing entry into a sequence is a direct deliverability control: it prevents the volume spikes that trigger filtering and it protects a warming domain from a large list import. Putting the cap at the sequence level rather than the mailbox level means the limit follows the campaign rather than the sender.

Lusha released API version 2.13.0, introducing a dedicated Conversations tag for conversational intelligence. The update adds stricter validation, where a pageSize above 100 or an invalid date format now returns a 400 error, and it unifies the response for missing or still processing transcripts under a single 404.

Teams integrating Lusha's conversational intelligence need to update pagination and error handling, since requests that previously succeeded will now fail validation. The unified 404 also removes the ability to distinguish a transcript that does not exist from one that is still processing, so retry logic has to assume both.

Close released a new Event Log that records organisational data changes including the user, the action and the source of each modification. The release includes an Event Log API and webhooks, allowing teams to stream those events to external reporting or audit systems.

Sales operations and security teams get a full audit trail of CRM activity and a way to trace unexpected data changes back to their source, including changes made by integrations rather than people. Streaming the log out by webhook also makes the record independent of the vendor, which matters for buyers who need retention beyond the platform's own.

Lusha released API version 2.12.0, adding a maxContactsPerCompany parameter to the Prospecting Contacts endpoint and a required maxResultsPerSignal parameter to the Signals API. The Contact Lookalikes endpoint moved to a v3 path with fully replaced request and response schemas that are not backwards compatible.

This is a breaking change. Any integration calling Contact Lookalikes has to be rewritten against the v3 schema, and calls to the Signals API now fail without the new required parameter. The per company cap is the useful addition, giving operations teams direct control over credit consumption during prospecting.

Pipedrive published a Model Context Protocol connector on Claude's official marketplace. The connector lets users query, create and update CRM data including deals, activities and contacts from the assistant using natural language.

Teams can work their CRM from inside an AI assistant without building against the API or paying for middleware. A connector that can create and update records also means the assistant holds write access to the system of record, so permission scoping and audit review belong in the rollout plan.

Revenue.io released its August 2026 product updates, introducing configuration options for Meeting Assistant recording announcements. Administrators can now control how often the recording disclosure replays during a meeting. The release also expands targeting for Moments, Scorecards and Conversation Agents so teams can scope those tools more precisely.

Making the recording disclosure replay configurable puts a consent control in the administrator's hands, and it can be tuned in either direction. For two party consent jurisdictions and for meetings where participants join late, a repeated announcement is the safer setting, and the fact that it is now a setting rather than a fixed behaviour is what buyers need to know.

Revenue.io launched the Guided Selling Summer 2026 Release, version 13, expanding automation with automatic SMS and working day aware sequence timing. The release also includes a redesigned Participant Overview, email engagement tracking and new tools for organising sequence libraries.

Working day aware timing stops sequences firing into weekends and holidays, which protects both response rates and the sender's reputation. Automatic SMS raises a separate question, since text messaging carries consent obligations that email does not, and the release note does not describe how consent is captured or enforced.

Outreach updated its Android and iOS applications to include MCP connector management and Knowledge Search for Omni. The release also introduces a read only Opportunity Detail Page and support for SMS tasks on mobile.

Field reps can manage integrations, read opportunity detail and work SMS tasks from a phone rather than a desktop. Moving connector management onto mobile also moves an administrative control onto a device class that is usually outside a team's endpoint policy, which is worth a look for regulated buyers.

Instantly introduced Company Sources in SuperSearch, allowing users to find contacts at named target companies. Users can upload a CSV, use saved company lists or draw on live integrations to build contact lists from tech stack data, ecommerce stores or lookalike audiences.

Teams can run account based prospecting inside Instantly rather than assembling lists in a separate enrichment tool first. The data behind the tech stack and lookalike sources is not described, so buyers with a provenance requirement will need to ask where those signals come from.

QuickProsp released version 1.19.0, introducing AI driven campaigns that research prospects and draft personalised emails against a campaign specific offer. The update adds support for bringing your own OpenAI, Anthropic or Gemini API keys, custom Message IDs for SMTP sending, an option to skip List Unsubscribe headers, and a bulk mailbox deletion API endpoint.

Bringing your own model key removes the markup on AI credits and puts the model choice in the buyer's hands. The List Unsubscribe toggle cuts the other way: one click unsubscribe headers are a bulk sender requirement at the major mailbox providers, so shipping an option to omit them is a control a compliance minded team will want switched on rather than off.

Clari2026-08-11

Impact

High

Verification

Verified

Clari's August 2026 release introduces Model Context Protocol servers for ChatGPT and Claude, letting users query Copilot data from outside the platform. The release also adds AI Themes for bulk call analysis across up to 1,000 calls, multi call Ask Copilot querying, inline AI email revisions and automated Salesforce account linking.

Revenue leaders gain a route to query pipeline and call data from inside a general purpose AI assistant rather than only through Clari's own interface, and analysts can look for themes across a full quarter of calls instead of one at a time. Teams running both Clari and Salesloft should read this alongside the Salesloft release note, which carries a required Salesforce connectivity migration.

Meet Drake2026-08-11

Impact

Medium

Verification

Verified

Meet Drake introduced native CRM and Messenger capabilities to its LinkedIn automation platform. The CRM allows users to filter contacts, update records and perform bulk actions, while the Messenger centralises LinkedIn conversations, enabling users to manage InMails and apply message templates.

Consolidating LinkedIn messaging and contact management into a single interface reduces the switching between the automation tool and LinkedIn itself. It also moves more of the conversation record off the platform and into the vendor, which is worth checking against the vendor's stated position on platform terms.

Reply.io2026-08-11

Impact

High

Verification

Partially Verified

Reply.io moved its AI SDR API surface into public beta, taking 39 endpoints from documented to callable. The set covers the full AI SDR sequence lifecycle including autopilot enable, disable and force start, pending approvals with bulk send, Live Data searches, sequence preview and personalisation, offer generation, the Strategist and Inbox AI drafts. Documentation was restructured into API Reference, MCP, Skills and CLI sections alongside a new command line client at v0.3.0.

Sales operations and developer teams can now drive Reply's AI SDR from their own systems rather than the dashboard, which matters most to agencies running many client workspaces and to teams embedding outbound inside an agent stack. Approval mode and pending approvals are exposed as API objects, so the human in the loop step is scriptable and can also be scripted away.

Salesloft2026-08-11

Impact

Medium

Verification

Verified

Salesloft rolled out its August 2026 release, introducing automated CRM account linking and a change to its MCP Server for Claude. The platform now links accounts to matching Salesforce, HubSpot or Dynamics records on domain and website matching and detects when accounts are merged. The MCP Server for Claude no longer returns raw transcripts, though AI generated call summaries and key moments remain available.

Automated account linking and merge detection reduce manual data entry and duplicate records. The removal of raw transcript retrieval from the MCP server is the change to act on: any external workflow that reads full transcripts through that server will stop working and has to move to summaries or another route.

SalesCaptain2026-08-10

Impact

High

Verification

Partially Verified

SalesCaptain introduced Actions and Marketing Flow, new capabilities that allow its AI agents to automate tasks across connected systems. The Actions feature enables AI agents to autonomously schedule appointments, update records, trigger APIs, fetch live data from custom knowledge bases, and send payment requests in real time.

Revenue and operations teams can use these features to move beyond conversational AI, letting agents execute workflows, update CRM records and trigger external APIs directly from customer interactions. Nothing is published about approval steps or human review before an agent writes to a connected system, so buyers should confirm what an agent is permitted to do unattended.