Category

Heather Rinke

A broken CRM seller experience acts like a tax on your pipeline, dragging down deal velocity and rendering new AI investments practically useless. Identifying the friction is easy, but executing the cure is where most teams get stuck. So, how do you transition from diagnostic firefighting to actual, scalable optimization? The answer isn’t a full rebuild, it’s a Seller Experience Audit. It pinpoints exactly where your system is broken, and then applies a practical CRM optimization framework that targets high-friction areas first, proves fast ROI, and builds momentum.

To help you map this out, we’ve broken down the core architecture from our full 2026 CRM Optimization Playbook. Here is the exact 6-step roadmap to transform your CRM from a roadblock into a high-velocity revenue engine.

Download the 2026 CRM Optimization playbook.

Groundwork: Uncovering Where the Friction Lives

Before you change a single validation rule or field setting, you have to gather your boots-on-the-ground intelligence. A successful CRM optimization framework relies on two distinct discovery exercises:

  • Walk your funnel like a customer: Take a handful of recent closed-won accounts and map every single technical and human touchpoint. Did the buyer experience a massive lag between marketing handoff and sales outreach? Did they have to repeat their pain points? Funnel walkthroughs surface your biggest gaps faster than any dashboard.
  • Shadow your sellers: Sit down with your sellers and watch them navigate a typical day. Ask the direct questions: Where are you clicking too much? What fields feel completely pointless? What context are you keeping in a shadow spreadsheet because the CRM is too slow? When you design the process for the front line, you have to hear it from the front line.

The 6-Step CRM Optimization Framework

Once you know where the drag lives, work through these six execution steps in order. 

1. Define Stages and Strict Ownership

Alignment is the bedrock of any CRM optimization framework. Get your Sales, Marketing, and Customer Success leaders in one room to establish absolute clarity around buyer journey milestones.

Define exactly what qualifies a lead at each stage, and more importantly, who owns the record at every handoff. Clear operational boundaries stop lead leakage before it starts.

Another key team to align with is IT. For alignment to actually be actioned, data must be able to flow seamlessly from one department to the next to provide the right context. That data can sometimes be owned in systems where IT needs to collaborate for access. Therefore, ensuring that all teams are aligned ahead of time will help to make the execution easier.

“Bringing IT into the conversation and creating a collaborative relationship across departments when defining stages and strict ownership is critical. Friction when unlocking your data can often be due to department silos rather than just technology silos.” 

– Austin Frink, Director, Data Technologies, Sercante l Trilliad

2. Cleanse and Trim the Fields

Audit your current fields and page layouts with one brutal question: Does this field help a rep move a deal forward right now? If a seller is in early discovery, they shouldn’t be forced to look at 40 blank legal or billing fields. Use conditional visibility to show the right fields at the right deal stage. The answer to “can we track that?” is always yes, but the smarter question is “should we?”

3. Automate the Administrative Burden

Identify the repetitive, manual tasks that drain your team’s energy. Logging basic activity, routing leads, progressing stages, and triggering standard follow-ups. Let your system handle these based on real-time buyer engagement. This is what the technology was built to do. Don’t pay premium seller salaries for manual data entry.

4. Close the Handoff Gap

Map out the exact second a lead passes from marketing to sales. Ensure all marketing context, intent signals, and engagement history travel with the record. Fixing this single point of friction rebuilds cross-functional trust between Marketing and Sales faster than almost anything else.

5. Layer in AI and Advanced Automation

Now that the foundation holds, your data is clean, and your workflows are automated, AI becomes an incredible asset rather than a liability. This is where you can confidently execute an Agentforce or agentic roadmap. Start with a single high-friction use case, like auto-captured activity, next-best-action prompts, or signal-based prioritization—prove the time savings, and expand. For additional insight on the strategic approach to creating an effective AI roadmap, check out Jenna Packard’s blog, The AI Roadmap for Enterprise: A Framework for Identifying Value-Driven AI Use Cases.

6. Build Continuous Feedback Loops

CRM optimization is a continuous rhythm, not a one-time project. Establish a monthly cadence where your RevOps, Sales Ops, or Marketing Ops teams shadow an account executive to look for new layout errors, system speed bumps, or shadow spreadsheets.

Framework StepCore FocusOutcome
Define OwnershipSLA & Handoff AlignmentEliminates lead leakage
Cleanse & TrimUI/UX MinimalizationHigh CRM adoption & clean data
Automate AdminWorkflow AutomationReclaims hours of selling time
Close the GapData Context SyncingBridges the Marketing Visibility Gap
Layer AIAgentic & Generative ToolsMassive operational leverage
Feedback LoopsContinuous ShadowingLong-term technical scalability

 Getting Started with Your CRM Optimization

Every technical change in this framework directly drives a business outcome. That is how you justify the work to leadership, and it’s how you ensure the changes actually stick. The ultimate goal is simple: transition your tech stack from a static tracking system to an active revenue producer.

But if the friction has been there so long that it has just become background noise, it can be hard to know which of these steps to prioritize first.

That is exactly why the Sercante l Trilliad team guides revenue teams through a structured Seller Experience Audit. We assess your systems, data quality, and cross-functional handoffs to turn guesswork into a prioritized, impact-driven roadmap tailored to this exact CRM optimization framework. Reach out to the Sercante l Trilliad team to schedule your Seller Experience Audit.

Contact the Sercante | Trilliad team to get your CRM Seller Experience Audit.

The painful reality of a clunky CRM configuration is low adoption, messy data, and an estimated 14% drop in closed deals. When your CRM is built for management oversight instead of seller enablement, everyone suffers, especially your buyers. But knowing you have a problem is only half the battle. The real questions for Marketers, RevOps, and Sales Operations leaders are: What does an ideal CRM seller experience actually look like in 2026, and how do we get there? Why does this matter now more than ever?

As we outline in our 2026 CRM Optimization Playbook, three major industry forces are shifting CRM optimization from a “nice-to-have project” to an absolute revenue priority. If you want your tech stack to act as a force multiplier for sellers rather than a budget drain, you need to understand the modern blueprint for a frictionless CRM.

Download the 2026 CRM Optimization Playbook

Why Are the Stakes Higher in 2026?

We aren’t operating in the same B2B landscape we were a few years ago. If you are still running a CRM configured for 2018 reporting needs, you are actively fighting three major headwinds:

  • ROI is Under a Microscope: CFOs are holding the tech budget to a much higher standard. It’s no longer about whether a platform is successfully deployed. It’s about whether it’s actually being adopted by the front lines. 
  • Buyers Are Further Ahead: Prospects are over halfway through their buying journey before they ever talk to sales. Sellers need instant, unified context the second a lead routes to them to add value in the few moments they have left.
  • AI Raises the Stakes on Clean Data: Everyone is eager to layer in AI assistants or platforms like Agentforce. But here is a sobering reality: at least 50% of generative AI projects were abandoned after proof of concept because of factors including poor data quality, inadequate risk controls, escalating costs, or unclear business value (Gartner).

The Modern Blueprint: An Ideal CRM Seller Experience

When you optimize the seller experience, the wins ripple across the entire lead-to-revenue lifecycle. It stops being a “Sales Ops project” and becomes a multi-department win.

Here is what happens when you design a CRM for your front lines:

Focus AreaThe Frictionless WorkflowThe  Impact 
Smarter ProspectingIntent and signal-based outreach take the guesswork out of who to call and what to say.~47% higher conversion rate over traditional scoring models (Landbase).
Frictionless Activity ManagementThe system automatically captures email, meeting, and call data, giving sellers next-best-action coaching without manual data entry.~4.8 hours per week are saved by AI (Gartner).
Strategic Account GrowthData-driven whitespace identification points account for teams exactly where cross-sell and upsell potential is highest.~Sales teams using AI are 30% more likely to report year-over-year revenue growth (Salesforce). 
Seamless Sales ProcessesHeadless CRM systems, like Salesforce, allow data and actions to be used inside additional tools sellers are already using, such as Slack, Microsoft Teams, email inboxes, or AI agents. Allowing them to access clean data in their flow of work, across all channels.~49% increase in seller productivity and 28% shorter sales cycles from process automation (Rox).

How AI Acts as the Ultimate Friction-Reducer (If You Let It)

Once you lay a solid data foundation, AI can step in to eliminate the heavy administrative burden that has plagued sellers for decades. Instead of forcing sellers to be data-entry clerks, optimized platforms allow AI to do what it does best:

  1. Capture the Busywork: Auto-logging meeting notes, participants, and next steps directly from calls without the salesperson typing a single line.
  2. Read the Room at Scale: Surfacing real-time deal health alerts and coaching prompts to catch stalling deals before it’s too late.
  3. Draft the Follow-Up: Triggering timely, personalized outreach based on real-time buyer engagement signals so hot leads never go cold.

By removing the digital drag, you free up your sellers’ brainpower to focus on what they actually do best: building relationships with buyers.

The 2026 Mandate: Trade the Junk Drawer for a Seamless Seller Experience

At this stage in the B2B landscape, a CRM configured merely for management oversight is an active drain on your pipeline, your budget, and your team’s performance. The modern blueprint for growth requires shifting away from the digital drag of manual data entry and embracing a frictionless, optimized CRM seller experience. By laying a clean data foundation and allowing AI to automate the busywork, capture real-time deal health, and surface actionable intent signals, you transform your system from a static reporting tool into a high-powered revenue engine. 

Tackling this all on your own can be overwhelming, and you may not have the bandwidth or the resources to evaluate your CRM and the friction it’s causing on your sellers and your pipeline. Tap into the expertise of the Sercante l Trilliad team with our Seller Experience Audit to fast-track your path to an optimized CRM and get a customized blueprint for quick wins and major revenue impact.

Contact us to get your Seller Experience Audit

Think about your last pipeline review. How many times did you hear “oh yeah, I just haven’t updated that”? Meanwhile, marketers, RevOps, and sales leaders are left with limited pipeline visibility, wondering which campaigns are actually moving the needle, and how far off the team will be from the original forecast. This CRM data quality issue is the symptom of a much bigger problem. And it’s quietly costing you revenue. With how much the CRM can impact sales performance and the buyer’s experience, it’s critical that marketing, sales, and operations leadership understand the case for CRM optimization.

For most revenue teams, the CRM has become the thing sellers tolerate rather than the thing that helps them win. That’s not a people problem. It’s a design problem. Sellers are wrestling with clunky interfaces and manual processes, while hunting down intel in fragmented systems, and buyers feel the friction when they’re waiting to be followed up with, or have to repeat themselves on a call.

In Sercante l Trilliad’s playbook, The CRM Paradox: Why Your System is Killing Pipeline (And How to Fix It), it dives into the statistics and impacts on sellers, buyers, and the overall business when the CRM is not set up to be aligned with how sellers actually sell, and includes a proven framework for identifying the friction and how to start solving it. Get the highlights on the case for CRM optimization below and download the playbook to get all the details.

Download the CRM Optimization Playbook

The case for CRM optimization: Your real cost of a “broken” CRM

CRMs weren’t originally built for sellers. They were built for reporting, tracking, and management oversight. So when we drop a seller into a system designed for someone else’s job, friction is the natural result.

The numbers tell the story:

  • 48% of sales leaders say their CRM is more of a burden than a help (Forbes).
  • 76% of salespeople say their CRM is too complex, time-consuming, and outdated (Medium).
  • Companies with low CRM adoption have reported closing  14% fewer deals (ARP Ideas).

Here’s the cycle every revenue leader knows but rarely names: friction leads to low CRM adoption. Low adoption leads to bad data. Bad data leads to obscured buyer views, bad forecasts—and lost revenue.

You’ve most likely felt the downstream cost of seller friction firsthand.

For marketers: 

  • The leaky funnel: Marketing hands off a lead and loses sight of it. Without tracking, delayed follow-ups let hot leads go cold.
  • Painful ROI reporting: Low CRM data quality hides campaign impact, making it impossible to prove what actually drove the deal.
  • Limited personalization: Poor data tracking means limited customer insight, stopping teams from building the tailored experiences today’s buyers expect.

For sales leaders:

  • Blind forecasting: Low CRM adoption leads to inaccurate deal data, forcing leaders to guess on pipeline numbers, making forecasting challenging.  
  • Limited coaching: Without the right deal context in the system of record, managers can’t spot where sellers are stuck or guide them effectively.

For RevOps:

  • Funnel visibility gaps: Siloed intelligence makes it impossible to accurately track funnel velocity and shifting conversion rates.  
  • Legacy drag: Outdated setups force teams to build manual workarounds rather than scalable, automated workflows, making the data issue worse as well as efficiency.

For customer success: 

  • Reactive support: A lack of proactive data insights means CSMs can’t identify or save at-risk accounts before they decide to churn.
  • Eroded kickoff trust: Passing accounts with limited sales context creates a clunky onboarding experience that kills lifetime value.

Where the CRM friction actually lives

Before you can fix it, you have to find it. In most organizations, the drag clusters in five predictable places.

  1. Administrative burden. Sellers spend 60%+ of their time on manual data entry instead of selling (Salesforce). Every redundant field and extra click is selling time you’re paying for and not getting.
  2. The seller’s CRM perception. If sellers don’t see the CRM as being useful and only have frustrating experiences when using it, their view of the CRM will only continue to lead to low CRM adoption.
  3. Siloed intelligence. Critical deal context lives in Slack, email, and “shadow” spreadsheets—everywhere except the system of record. When the insight isn’t where the seller is working, it may as well not exist.
  4. Legacy configuration. Many orgs are running a CRM built for 2018 reporting needs, not 2026 workflows. The business changed. The setup didn’t.
  5. The marketing visibility gap. This is the one that quietly breaks cross-functional trust. Marketing hands off a lead and loses sight of it. Sales picks it up with no context. And no one can prove what actually drove the deal.

Ask yourself: Which of these five is costing my team the most right now? You probably already know the answer.

Your buyer feels every bit of it

Here’s the part that’s easy to miss from inside a pipeline dashboard: internal friction never stays internal. If your sellers are fighting their tools, they aren’t fighting for your buyers.

In Part III of Sercante l Trilliad’s series, Built to Buy, industry experts explore what a broken seller experience looks like from the buyer’s side of the table:

  • The delayed hand-off. A hot marketing lead goes cold because the assignment logic is broken or buried in a rep’s queue. The buyer raised their hand—and heard nothing back.
  • The interrogation session. A prospect repeats their pain points, budget, and scope on a call because the marketing context never synced to the record. To them, it feels like your left hand doesn’t know what your right hand is doing.
  • The missing follow-up. A customized proposal arrives days late because the seller is drowning in admin instead of engaging. By then, attention has moved on.
Watch Part III of Built to Buy Series: A Better CRM For Sellers = A Better Experience for Buyers

Your customer doesn’t think, “Am I in a marketing, sales, or success experience?” They just know they’re having an experience—and they want it to be easy. When your departments feel out of sync, buyers quietly move to a competitor who feels organized. A CRM that feels clunky to your seller feels clunky to your buyer.

Getting started on your CRM optimization

The key to getting started is acknowledging the impact that the state of the CRM has on your business for sellers, your buyers, and every department. Then it’s about spotting where the friction actually lives and mapping out the next steps for solving it. 

If you’d like to fast-track getting started with your CRM optimization, reach out to the Sercante l Trilliad team for a Seller Experience Audit. Then, receive a clear blueprint for quick wins with a big impact and a roadmap for your ideal CRM seller experience.

Contact us for your CRM Seller Experience audit

The recent unveiling of Salesforce Headless 360 marks a significant paradigm shift in the CRM industry, signaling a move away from rigid, UI-bound ecosystems toward a decoupled, “AI-first” infrastructure. For growth leaders, marketing executives, and revenue operations professionals, this means the CRM is no longer a destination users must manually log into, but rather a background engine. This engine can be accessed conveniently via natural language and “agentic” interfaces like Slack, Teams, or custom coding tools, fundamentally changing how teams interact with critical customer data and functionality.

1. Agentic Orchestration and the Model Context Protocol (MCP)

The core of this transformation is the decoupling of the CRM interface from its data layer, opening up the platform with comprehensive external API access. This shift converts Salesforce data, workflows, and business logic into over 60 composable Model Context Protocol (MCP) tools. These tools act as building blocks that allow AI agents to seamlessly interact with Salesforce without a traditional UI.

This agentic approach promises to automate complex workflows. Operational tasks, such as updating a Salesforce record or opportunity, can now be executed through agentic interfaces like Slack, completely bypassing the need to log into the traditional CRM UI. This functionality also supports extending beyond Salesforce-owned products to a wide variety of other interfaces such as Microsoft Teams, custom web and mobile apps,  or even communication channels like Voice, WhatApp or SMS, as long as they adhere to the MCP protocol. The ultimate positive evolution is toward improved operational efficiency, giving users a consistent experience wherever they are already working, allowing teams to execute tasks like managing pipeline, building dashboards, and campaign journeys easier and without as many technical barriers.

2. Evolving Skillsets: Prompt Engineering and Data Hygiene

As systems transition to an agentic execution model, this democratizes the platform by transforming how non-developers, such as business users and admins, interact with and build upon the system.  This highlights a growing need for a critical emerging competency: prompt engineering. For end users, especially marketers and sales representatives, the ability to write precise instructions are paramount to getting the desired results from AI. This shift necessitates that teams quickly adopt an “AI-first” approach for building solutions. 

However, foundational pieces also remain crucial; even Headless 360, requirements like good data quality and metadata hygiene practices are still essential for success. AI does not natively “know” your business; it relies on your data (the facts) and your metadata (the context, rules, and structure) to make real-time decisions. Keeping data clean, deduplicated and up to date, and ensuring fields have descriptions, picklists are organized and accurate, gives AI the correct information, and the business logic and context to understand what it means. 

3. Strategic Skepticism and Navigating Release Reality

While the potential for improved operational efficiency is high, leaders should approach the Headless 360 announcement with strategic skepticism. As with many major platform evolutions, the full scope of Headless 360 will likely unfold in phases rather than arriving as an immediate, all-in-one solution. While the announcements focus on a complete platform of tools, all are not generally available at this time, with some features in pilot now or planned for release in the summer and beyond, so customers should prepare for implementation over a phased roadmap. Ultimately, the move to Headless360 is a necessary and welcome alignment with modern market standards, ensuring Salesforce remains competitive as organizations increasingly adopt headless architectures.

Executives should view this development as a positive step forward, particularly for organizations that prioritize prompt engineering training and robust data governance. The headless model offers a more seamless and convenient way to integrate  Salesforce functionality where users typically work day-to-day, which is an effective strategy for boosting user adoption. The foundation for this is already emerging, with capabilities such as the Agentic Enterprise Search (also known as Ask Agentforce) feature currently in beta, which uses natural language queries to synthesize summaries from connected systems.

Conclusion 

The Headless 360 announcement marks the beginning of a future where growth is driven by a decentralized, AI-first engine. As technical complexity is abstracted away by agentic interfaces, success will hinge on empowering teams to adopt prompt engineering as a new competency and maintaining unwavering data hygiene. Organizations that can adapt their skillsets and navigate the gap between marketing promise and practical application will be best positioned to leverage this evolution for superior operational efficiency and accelerated growth.

With the upcoming June 2026 updates Salesforce has just announced, Salesforce is once again raising the bar for platform security. While these updates are designed to keep your data safer than ever, they do require some proactive heavy lifting from admins to ensure integrations don’t break and user access remains seamless.

In line with the messaging we’ve seen from Salesforce recently—focusing on the intersection of AI, Data, and Trust—these enhancements are mandatory. We want to make sure you’re ahead of the curve. Let’s dive into the core security requirements and what you need to do to prepare.

Email Domain Verification 

  • What is changing: Salesforce now strictly requires all outbound email-sending domains to be verified. To verify a domain, you must establish ownership using either DKIM key (recommended) or a verified entry in the authorized email domains list. As part of this change, Salesforce will no longer deliver emails from unverified domains, even if the specific sender’s individual email address was previously verified.
  • Why it matters: Email deliverability is becoming stricter globally, with major mail providers increasingly filtering or rejecting unauthenticated domains. If your organization attempts to send an email from an unverified domain, the delivery will fail and the email will be silently dropped. It won’t generate a bounce notification or an error message for your automations.
  • Who is impacted: Any emails sent directly from the Salesforce platform, which includes emails sent via the Email Composer, Apex email, Flow-triggered emails and even system-generated emails like notifications of a new Lead or Opportunity assignment.
  • Timeline: Enforcement began rolling out to sandboxes in March 2026, and production orgs in April 2026. 
  • How to prepare: 
    • You can check the verification status in your org by going to Deliverability settings in Setup and enter your domain in the Check Domain Verification section.
    • Ensure your email sending domains are verified using one of the following methods:
    • Enable a Safety Net: To minimize immediate business disruption while waiting for domain verification, enable “Use a substitute email address for unverified domains” on the Deliverability Setup page. 
Domain verification section

MFA Mandatory for All Users

  • What is changing:  While Multi-Factor Authentication (MFA) has been a contractual “requirement” for some time, Salesforce is moving toward technical enforcement for all UI logins (i.e. the login.salesforce.com page). This means any user logging into the Salesforce UI must use Multi-Factor Authentication. The ability to toggle this off for specific profiles or bypass it via legacy settings is being deprecated.
  • Why it matters: Data breaches are commonly linked to compromised credentials. Making MFA a technical requirement for every single user, ensures that even if a password is compromised via social engineering, your org remains protected.
  • Who is impacted: All users logging into Salesforce (direct UI or SSO logins) in production or sandbox orgs and do not have one of these permissions: System Administrator profile, Modify All Data, View All Data, Customize Application, or Author Apex. (Users with these permissions are considered “privileged” and have their own MFA requirements, see the next section)
  • Timeline: Enforcement is rolling out in waves, starting in Sandboxes on June 22, 2026, and production orgs starting July 20th.
    • Ahead of enforcement, orgs that have the setting “Require multi-factor authentication (MFA) for all direct UI logins to your Salesforce org”  disabled may start seeing this pop-up message as a heads-up on the upcoming enforcement.
    • Orgs with that have been updated will see the “Require multi-factor authentication (MFA) for all direct UI logins to your Salesforce org” setting (under Setup > Session Settings)  enabled and greyed out.
MFA Reminder pop-up message
  • How to prepare:
    • Audit users still not using MFA to assess who will be impacted. Use the “Identity Verification Methods Report” to view the methods being used by your organization.
    • Identify users relying on the “Waive Multi-Factor Authentication for Exempt Users” permission. To restore this exemption for valid use cases (e.g., automated testing tools), you can contact Salesforce Support for approval.
    • Identify the MFA methods available for your users and determine how they choose a method during initial registration.
    • If you are using Single Sign-On (SSO) through another identity provider (e.g. Okta, Entra), make sure that provider is using MFA and sending valid signals to validate MFA was used (for more information, see Salesforce’s breakdown of signal requirements).
    • Ensure users are prepared for the change and how to register their MFA method.  
  • More information: Prepare for MFA Enforcement for All Employee Users

Phishing-Resistant MFA for Admins or Privileged Users

  • What is changing: Salesforce is introducing a requirement for phishing-resistant MFA for users with “privileged” access. This means moving away from verification codes and toward FIDO2/WebAuthn-based passkeys, hardware security keys (e.g. YubiKeys) or built-in authenticators (e.g. Windows Hello or FaceID) that use FIDO2/WebAuthn standards.
  • Why it matters: Admins hold the keys to the kingdom. Phishing-resistant methods ensure a stronger protection against identity-based threats, and ensures access is tied to authorized users. 
  • Who is impacted: 
  • This change affects all users logging into Salesforce (direct UI or SSO logins) in production or sandbox orgs who meet any of the following conditions:
    • Users assigned with the System Administrator profile
    • Users assigned with any one of these privileged permissions: Modify All Data, View All Data, Customize Application, or Author Apex
  • Once in effect, users will be prompted to register their phishing-resistant MFA method on their next login. 
What it will look like to register the phishing-resistant MFA method on the next login.
  • Timeline: This change will be introduced in sandboxes starting June 22, 2026, and in production orgs starting July 1, 2026
  • How to prepare:

Containment for “High Risk” Connections

  • What is changing: Salesforce will automatically detect and contain traffic that:
    • Are from “High-Risk” connections through Connected App or API usage.
      • Examples of “high risk” connections include anonymizing VPNs (e.g. NordVPN, ExpressVPN, Surfshark, or ProtonVPN), Proxies (e.g. HideMyAss or KProxy) or high-risk IP addresses (e.g. public wifi, blocklisted IPs)
      • Connected App or API usage may include integrations, plugins (e.g. Salesforce Inspector Reloaded) or use of CLI tools.
    • Are significant, novel deviations from typical user login activity based on network, client, authentication events, and geolocation. (detected through an AI-driven monitoring system)
    • If a high risk connection is identified, the following actions will be taken:
      • The affected user account will be frozen.
      • All OAuth refresh tokens granted to the user will be revoked.
      • An email will be delivered to org admins from Salesforce Security (See Administrator Notifications below).
      • The affected user will need to contact their org admin to restore access to their account.
  • Why it matters: This enhancement is aimed at protecting against suspicious activity via anonymizing VPNs, proxies, or high-risk IP addresses; credential harvesting; and token theft. 
  • Timeline: This change started April 24, 2026
  • How to prepare:
    • Ensure users running integrations, plugins or connects are not doing so from high-risk sources
    • If automated containment affects a user, review their session and restore access by unfreezing their user
    • Users will need to avoid connecting from high-risk connections to prevent re-containment. They will also need reauthorize any connected apps
    • If your only admin account is locked out, contact Salesforce Support by phone to have your account reactivated  
  • More information: Preventing Connections from Anonymizing VPNs, Proxies and High-Risk IP Addresses

Step-Up Authentication for Reports

  • What is changing: Salesforce is introducing “Step-Up Authentication.” Even if a user is already logged in, they will be prompted to re-verify their identity (via MFA) when they attempt to run or view reports if a configurable amount of time has passed since their last step-up challenge.
What it looks like when a user is prompted to re-verify their identity (via MFA)
  • Why it matters: This change is intended to prevent malicious data breaches or unauthorized transfer of data to external locations. Given that report views and exports can be susceptible to scraping or unauthorized external use, the step-up authentication ensures these actions require a stronger authentication challenge.
  • Who is affected: This change impacts all users (direct login or SSO) who run or export reports.
  • Timeline: Sandboxes will see this available starting May 27, 026 and enforced starting June 3, 2026. Production orgs will see this available starting May 27, 026 and enforced starting June 10, 2026. 
  • How to prepare:
    • Ensure all users (especially SSO users) have a registered Salesforce MFA method, a valid email, or an SMS phone number, as they will need this to pass the challenge.
    • Review and Configure the Policy: In Setup, go to Identity Verification settings and adjust the cool-down period threshold if your business requires a timeframe different from the 120-minute default.

The Bottom Line

June 2026 is right around the corner. By leaning into preparing for these enhancements now, you’re not just racing to a deadline—you’re hardening your business against the next generation of digital threats.

As you prepare for the rollout, keep these three steps top of mind:

  • Audit: Identify which users will be impacted by the permission changes.
  • Test: Run your critical processes in a Sandbox environment.
  • Educate: Ensure your stakeholders understand the ‘why’ behind the new security protocols.

With a clear plan in place, the transition to a more secure Salesforce platform will be a seamless one.Need a hand getting your security posture ready for 2026? The Sercante team is ready to help you audit and prepare your org for these upcoming changes and your overall security posture. Reach out today!

If you’re exploring Agentforce or Data Cloud, but feel unsure where to start—or how to ensure real outcomes—you’re not alone. In our recent webinar, “A No-Nonsense Guide to Launching Agentforce & Data Cloud,” we heard from marketing, RevOps pros, admins, and IT professionals across industries who are in the same boat.

The good news? You don’t need to launch a massive initiative to get started. But you do need a strategy. To help guide yours, I’ve shared the key concepts from the webinar where I spoke alongside Sercante’s VP of Growth & Alliances, Lauren Noonan, and Data Cloud Practice Director, Austin Frink, for our proven approach to creating a strategy for Agentforce & Data Cloud that sets you up for success.

A No-Nonsense Guide to Launching Agentforce and Data Cloud
Watch On Demand

Why having a strategy for Agentforce and Data Cloud is imperative

Implementing Agentforce or Data Cloud without a clearly defined strategy is like building a house without blueprints. According to RAND, over 80% of AI initiatives fail—not because the technology doesn’t work, but because teams skip over the foundational work of aligning their tools to real problems, realistic goals, and existing infrastructure.

What we’ve often experienced is that implementing these tools without a clear strategy often exposes existing challenges:

  • Data silos become more obvious.
  • Misaligned processes are harder to ignore.
  • Adoption falters because people don’t see the value.

When we’ve asked organizations about their vision or what they want to accomplish, we’ve heard many who say, “I want an agent” or “I want a unified profile.” While those are great aspirations, they are just starting points. A successful implementation requires more than a desire for automation or consolidated data. It requires a full vision of the why, the what, and the who.

Setting an impactful vision

Instead of focusing on the tool, focus on the challenge, the opportunity, and the people involved.

Ask yourself:

  • Why do we want an agent or a unified profile?
  • What business challenge are we solving?
  • What do we want the agent to actually do? / What will the data be used for?
  • How will the data or AI support better decisions?
  • Who will benefit, and how?

When considering these questions, be specific. If your starting point is, we want to have better segmentation or to deliver more personalized experiences, dig deeper. What would you like to segment by? Are there specific segments you’re focusing on for a business need? What part of the customer experience would you like to personalize more? Uncovering the more specific needs that lie within will help shape a more actionable vision.

Other questions you can consider for getting started to identify your use cases are:

  • Where are the friction points in your customer journey?
  • What repetitive tasks are your teams spending time on?
  • What segmentation or personalization capabilities are limited by your current data?

Use this framework to build your vision statement. Your vision should capture:

  • WHAT: The capabilities you’re adding
  • WHY: The impact those capabilities will have
  • WHO: The people in your organization who will benefit

This vision becomes your team’s north star. As you outline the use cases for Agentforce and Data Cloud, you will also need to define how they will impact the business.

Anchoring your Agentforce & Data Cloud use cases to business value

Lauren Noonan emphasized during the webinar, that this step is often missed, but it’s key to alignment. The use cases that drive meaningful business value are the ones that sustain momentum and stakeholder support.

To help frame your use cases in terms of the level of impact, consider impact levels such as the following:

  • High: Critical to strategic goals or revenue
  • Medium: Important contributor to organizational priorities
  • Low: Helpful improvements, but not game-changing

For example, one Agentforce use case that would be considered higher impact would be streamlining lead qualification and routing.

Use Case: AI-Powered Lead Qualification & Routing Agent
Scenario: Deploy an Agentforce assistant that engages with inbound demo requests, asks qualifying questions (budget, timeline, decision-maker status), and routes hot leads to the correct rep in real-time based on region, product, or account type.
Why It’s High Value:

  • Directly impacts pipeline acceleration and conversion rates
  • Reduces lead response time, which is closely tied to revenue performance
  • Supports strategic goals around improving sales velocity and rep productivity
  • Teams Impacted: Marketing Ops, Sales Development, Revenue Leadership, Prospects, Customers

Notice how the above framing points to impacts such as increased pipeline velocity and speed to lead which leads to higher conversion rates, all tied to revenue.

Medium to low-impact Agentforce use cases might include ones that result in internal efficiency gains, such as streamlining campaign brief creation or surfacing answers to FAQs faster using articles from your knowledge base. However, these lower-impact use cases are often a low-risk and lower level of effort to deploy, so they can be a great starting point as small efficiency gains do add up and free up your team’s time to focus on higher-impact initiatives. Continue to weigh this as you frame your roadmap of priorities.

The other detail to call out from the lead qualification and routing Agentforce example is that it outlined the people who would be impacted. Which is often overlooked, but absolutely necessary when creating your strategy.

Considering the level of impact on your people

Agentforce and Data Cloud aren’t just technical implementations—they’re changes to how people work. According to CIO Dive, 42% of businesses have scrapped most of their AI initiatives in the last year, where studies have shown that the teams that see success are ones that are customizing their use cases and prioritizing them according to their needs and impact. As Lauren shared in her previous article on how to create your AI roadmap, “your unique AI path is the only one that matters.”

You have a unique set of people at your organization with different skill levels, needs, and talents. Not considering a change management plan for how your Agentforce and Data Cloud rollout will be applied will often lead to low adoption rates, causing a low level of success and your initiative to fizzle out.

That’s why it’s so important to assess:

  • How will workflows shift?
  • What training or enablement will be needed?
  • How disruptive will this be to current roles?

Then classify the level of impact on your people:

  • High: Many roles and processes change significantly
  • Medium: Moderate impact with some changes to roles or responsibilities
  • Low: Minimal disruption to current workflows

Evaluating the level of business value alongside the level of impact on your people will help determine which use cases you might want to prioritize first based on the level of effort to deploy.

During the webinar, we showed the chart below as a visualization of the ideal intersection point, which is medium-to-high business impact and low-to-medium people impact, with a lower level of effort to deploy.

A chart that shows the business impact on the x-axis and the people impact on the y-axis with the level of of effort ranging from low to high above. On the chart, Customer Self-Help is plotted on the low to medium business impact level and medium people impact with a lower level of effort. Sales coaching/productivity is mapped at higher level of effort, business impact and people impact.

Take your considerations of the people impact a step further with this on-demand MarDreamin’ Session: Empowering Your People: Nailing Change Enablement for AI Rollouts by Director of Change Enablement at Sercante, Debra Engles. 

The other aspect of your strategy that needs to be considered is the dependencies involved with deploying your use case for Agentforce and Data Cloud.

Understanding your dependencies

As Austin Frink and I emphasized in the webinar: implementation depends on more than just ideas. You need to understand the full picture of what it’ll take to make your use case a reality. That full picture includes the infrastructure that you have, including:

  • Technology: What do you already have? Where are the gaps?
  • Data: Do you have the right data sources? Are they integrated? Is the quality strong enough?
  • People & process: Who owns what? Where will the lift be felt most?

Dependencies aren’t necessarily roadblocks, but more factors that will help you to decide where you might want to start when it comes to implementing technology like Agentforce and Data Cloud.

The last piece to consider when defining your strategy is the metrics you’ll use to measure the impact of your Agentforce and Data Cloud initiative.

Defining your metrics for measurement

Your metrics will be used to help prove the business values that you defined earlier. For every use case, identify one or two key success metrics. Before you start your Agentforce and Data Cloud project, measure where you are right now to get a baseline, so that you can benchmark later on and compare your level of improvement.

Some ideas:

  • Customer satisfaction
  • Campaign performance
  • Churn rate

Ideas of metrics that could be associated with our Agentforce use case example of lead qualification and routing, would be speed to lead, conversion rate, and sales cycle time. If your use case will focus more on efficiency gains, consider the amount of time it takes your team to perform the task without the agent implemented, and then measure the hours of time that are saved as a result.

Pro tip: When bringing your strategy to stakeholders, share what your team will accomplish with the time gained back. This goes beyond just thinking through the metrics, and it will be key when articulating the full picture of the impact that implementing Agentforce and Data Cloud can have on your business.

Identifying a success metric is one part of it, you also want to make sure you have defined how that metric will be tracked and validated. For example, will it come from Salesforce, Data Cloud or an external system? Consider, are you capturing the fields that are needed for that metric today?

Also, don’t forget to capture a pre-project snapshot of your metric. Without a clean, documented baseline gathered before any implementation, you lose the ability to accurately show ROI.

Common misconception: you don’t need to start with a massive rollout

One of the most common misconceptions when teams are thinking about implementing Agentforce and Data Cloud is that it requires a massive rollout and overhaul. However, this is not the case.

You don’t have to ingest all your data to use Data Cloud. You don’t need to first implement Agentforce into every aspect of your business.

Start with:

  • 1–2 use cases
  • Lower people impact
  • Medium-to-high business value

Clearly defining your use cases will inform you of the data that you’ll need, which will then point to the data sources required. The use case will then point to the agent that you’ll need and the teams or subsect of a department that will be impacted. 

As the CMO of Mogli, Christina Scarmeas, shared during her conversation with us about how her team approached implementing Agentforce, “It’s okay to take a crawl, walk, run approach.”

Using AI and Agentforce to Make it Easier to Text on Salesforce
Watch On Demand

Which is why Sercante service offerings such as an Agentforce Quickstart or Data Cloud In-A-Box are so helpful for teams. They enable you to start small, accelerate time-to-value, and showcase the impact, to then scale the initiative to other areas of the business.

Let’s get started with your approach to Agentforce and Data Cloud

To recap, a successful approach to Agentforce and Data Cloud includes:

  • A clear, problem-driven vision
  • Use cases tied to real business value
  • Understanding the people impact
  • Mapping your technology and data dependencies
  • Identifying the metrics that will be used to measure impact

Having this all defined will help to serve as your team’s north star to guide a successful approach to Agentforce and Data Cloud.

Now I know how it can be overwhelming to think through all of this, especially with multiple department goals and initiatives, so if you’d like support with creating your Agentforce and Data Cloud strategy, reach out to the Sercante team. We’ll listen to understand your goals, challenges, and help bridge the gap between your vision and reality, for an impactful Agentforce and Data Cloud rollout.

Create Your Roadmap with the Experts
Contact Us

No more posts to show