There’s been a lot of talk about the Agentforce development lifecycle. As admins, we know that you can’t just jump into building without an implementation plan to guide users to adopt new technology. So how do we get to the development lifecycle and create a partnership between our users, customers, and agents? We build a solid foundation in adoption.
Like any emerging technology, learning about generative artificial intelligence (AI) and implementing Agentforce is an exciting challenge that comes with both “aha!” moments and pain points. On the Admin Relations Team, we want to make sure you’re prepared for a successful implementation—from first exposure to full adoption.
If you’re just beginning your journey with Agentforce, we want to give you a starting point. If you’re already learning and building agents, we want to provide insight into what comes next on your road to successful adoption and building out Agentforce across the enterprise. And wherever you are on your journey, we want to provide helpful resources and actions to take to further your education. Think of the Adoption Framework as your path to becoming confident with this new technology.
Here are the five stages we’ve identified as part of your exciting Agentforce adoption journey.
Before rolling out a new technology initiative, we need to get educated and exposed to the technology. As admins we’re the product owners of Salesforce and will naturally be seen as (and become) the subject matter experts in Agentforce (or any application we’re implementing). Before generating interest internally, we need to gain exposure through Trailhead and different enablement events to get that initial hands-on know-how.
In this phase, you might feel intrigued by Agentforce, hoping to answer some questions and address pain points, such as:
Some actions admins can take to Explore what’s Possible include:
If this sounds like where you are in your Agentforce journey, take a look at these resources.
Once you have foundational skills and an understanding of how Agentforce can work for your organization, it’s time to build interest and gain stakeholder buy-in. This is the stage where you put together a demo for leadership and lead whiteboard sessions to brainstorm ideas for your organization. This is also a great time to talk to your Salesforce Account Executive to get a sense of budgeting.
In this phase, you might feel inquisitive and inspired to bring Agentforce to your own personal use case(s). Pain points might include:
Some actions admins can take to Get Curious include:
If this sounds like where you are in your Agentforce journey, take a look at these resources.
After gaining buy-in with a general Agentforce demo, it’s time to take the use cases you identified and get building using Salesforce Foundations or a Developer Edition. This is the most fun part for us, because it’s where our admin skills intersect with new technology and we get to create optimal experiences for our users and customers.
In this phase, you might feel eager to bring Agentforce to life, and you might encounter a couple pain points that you are well equipped to deal with as an admin, including:
Some actions admins can take to Try it Out include:
If this sounds like where you are in your Agentforce journey, take a look at these resources.
After trying out Agentforce with your own use cases, you’ll take your findings back to your stakeholders to make sure you’re in alignment. After any changes or updates, you’ll be ready to head into activation to turn on Agentforce and deploy your agents to production. At this stage, you should clearly see AI and Agentforce as part of your admin responsibilities, role, and future career plans.
In this phase, you hopefully feel satisfied with your career growth and your ability to actualize Agentforce at your organization. Some new pain points to tackle might include:
Some actions admins can take to Make it Work include:
If this sounds like where you are in your Agentforce journey, take a look at these resources.
The final stage in the adoption journey is true adoption. You’ve brought Agentforce to your organization. Now, you’re transitioning into a regular cadence of using the Agentforce Development lifecycle as you deploy agents across the enterprise, with multiple agents working together.
In this phase, you deserve to feel proud of your accomplishments and might feel excited for the future of Agentforce at your organization. The challenges you experience might be more around user adoption and future proofing and could include:
Some actions admins can take to Use it Often include:
If this sounds like where you are in your Agentforce journey, take a look at these resources.
We want to give you a sneak peek on what we’ve been working on! We’ll continue sharing more content to guide you through each stage of your Agentforce adoption journey. Stay tuned for more content like this!
I want to give a big thanks to the Awesome Admins and MVPs who provided feedback on this framework to share their thoughts, stories, “aha!” moments, and challenges.
If you’re a Salesforce Admin looking for ways to scale support, reduce repetitive work, and make Salesforce easier for your users, employee agents are for you. These built-in artificial intelligence (AI) assistants are now available with Salesforce Foundations (Enterprise Edition or above), and you can get started without extra cost. They’re designed to help your […]
As Salesforce Admins, we’ve dived headfirst into Agentforce. We’re building agents in Trailhead, attending workshops like Agentforce NOW, doing hands-on sessions with our Community Groups and at conferences like TDX, and coming up with ideas of how to put agents to work for our individual business need, even bringing that to fruition through events like […]
If you support a sales team as a Salesforce Admin, you know the balancing act of optimizing workflows, boosting productivity, and scaling operations, often with limited resources. That’s where Agentforce for Sales comes in. This artificial intelligence (AI)-driven solution is designed to unlock a new way to scale revenue growth—not by adding headcount, but by […]
