LoginSign Up
← Back to CRM
Weekly · CRM · Week of August 31, 2026

CRM opens itself to agents while half the sector just blogs

agent-accessmcpsalesforce-nativedata-qualityconfig-granularityseo-blog-feeds
O
Generated 2d agoDrawn from 11 products

The week in crm

The clearest pattern in CRM this week is that the pipeline is meant to be answered in conversation, not navigated. Twenty shipped an SDK that lets an installed app declare its own timeline event types and get real scoped browser storage, opening the record timeline at the centre of the CRM to third-party code. folk is running an MCP server and an Interactions API beta that exposes conversation history rather than only contact records. Streak landed in Claude's connector directory, turning CRM access from something a technical user provisions into a one-click switch. Across these three the order is telling: the agent surface arrived before, or alongside, the developer one. folk shipped MCP weeks before its first public API; Streak's connector is the last step of an arc that began with a read-only server gaining write access. The bet is that the first thing built on top of a CRM is now an assistant, not an integration.

The other half of the sector barely ships at all. Five of the eleven active feeds — Thryv, Vendasta, Recruiterflow, Membrain, and Pipeline CRM — are search-and-demand engines where a genuine release surfaces maybe once in ten posts. That is not idleness; it is a different theory of the funnel. But it means the sector's real product signal is concentrated in a handful of builders, and the loudest AI language — Vendasta's "AI workforce," Recruiterflow's AIRA — is positioning with no shipped change attached. Read as changelogs, these feeds report nothing.

Leaders

Twenty opened its record timeline to installed apps, letting them declare custom event types with their own renderers and get scoped localStorage that works inside sandboxed components. That app-platform push sits on a finished ORM v2 migration; the rest of the week was three perf(server) tags in a single day paying down the cost of collapsing onto one data path, all on message import and metadata queries. It remains the most active feed in the sector by some distance.

folk opened three surfaces inside a month: an MCP server, a standalone mobile app, and an Interactions API beta that exposes email and conversation history. Both threads converge on one problem — getting real interaction data into the CRM and back out — with the mobile card scanner and talk-to-text handling capture and the API exposing what capture produces. The agent interface shipped before the conventional developer one.

Streak became a one-click Claude connector, the end of an arc that started with an MCP server gaining write access. Around it the work was quieter and about trusting the data: validation rules now fire in the mobile apps, the pipeline newsfeed became an auditable activity history, and live avatars show who is viewing a deal — surfaces Streak's own notes hint will later show agent activity beside human activity.

Weflow moved its analytics into Salesforce as a managed package, building activity trends, duplicate detection and orphaned-account reporting natively in the customer's own CRM without spending API calls on reporting. It is a different shape of product from the sidebar it started as — infrastructure inside Salesforce rather than a destination beside it — with Ask AI now reachable from the Chrome extension wherever a rep is working.

Phorest has no spark this week but shipped seven improvements pulling salon configuration to a finer grain: pricing moved to a per-staff, per-service rate, price-edit permissions split between service and retail, and online booking can be switched off for one staff member on one service without touching their qualification. It is the maturity pattern of a product being reshaped for salons too large for a single rate card.

Wildcards

Lime Connect is the off-pattern one: a conversational CX suite whose newest release changes the shape of the automation rather than opening an agent surface. Workflows can now start from a time and repeat rather than waiting for a contact to act, which required building time-based contact fields such as birthdays, and beta interactive elements let the agent render a calendar in chat. Where the rest of the sector is exposing the CRM to agents, Lime Connect is teaching its automation to initiate.

Themes that compounded

  • Agent access shipped before or alongside developer APIs at folk, Streak and Twenty — the assistant is becoming the first thing built on top of the CRM.
  • Salesforce-native delivery: Weflow moved reporting into the customer's own CRM rather than asking reps to leave it.
  • Data quality as an AI precondition — Streak pushed validation onto mobile and made its newsfeed auditable so agent activity can be reviewed.
  • Configuration granularity matured at Phorest, unbundling pricing, permissions and availability down to the individual staff member.
  • Half the sector's feeds are demand-generation engines, so real product signal is thin and concentrated among a few builders.

Watch this week

Twenty's three same-day perf tags were explicitly preparing message import and sync paths, so the next releases there are the likeliest place a user-facing sync improvement surfaces. folk's Interactions API is the beta to watch: the mobile capture features exist precisely to feed it, and moving it out of beta would close the loop. And with three CRMs now reachable by an assistant, the open question is whether agent activity becomes visible inside the collaboration surfaces — Streak's newsfeed and viewing indicators already gesture at it — rather than staying an invisible writer in the pipeline.