We at SF Ben have covered at length over the last few weeks just how difficult it has become to be a modern Salesforce Admin. Compared to previous years, admins are expected to evolve faster than ever, adapting to constant platform changes, increasing complexity, and growing business expectations. As the ecosystem continues to change, keeping a Salesforce org running smoothly day to day has become significantly harder. But alongside those newer pressures, there are also plenty of frustrating aspects of the role that have existed for years.
Ask a group of Salesforce Admins what frustrates them most, and the answers are usually incredibly relatable. Vague Slack messages saying “Salesforce is broken” with no screenshots attached. Duplicate records constantly reappear, or permission requests pile up. Flows are suddenly failing because someone renamed a field three months ago and never documented it. Much of the frustration actually stems from operational issues surrounding Salesforce rather than the platform itself.
I recently spoke about this topic on LinkedIn, and many Salesforce professionals quickly rallied around the conversation. Many of those who responded highlighted that some of the biggest sticking points for admins have been around for ages, and reinforced our evolving role argument. Many are no longer just system administrators, but support desks, testers, process managers, and troubleshooters, all at once.
In many cases, the tasks admins hate the most are the repetitive, invisible, and emotionally draining ones, not the most technically difficult.
Admins Have Become the Default Owners of Operational Chaos
One of the key aspects of this conversation is that a lot of admins no longer feel like they are simply managing a CRM platform. Instead, they’ve become the people expected to absorb everything around them, too.
One Salesforce professional, Alyssa Lefebrve-Beucsher, spoke to SF Ben and quickly highlighted one universally frustrating example – vague support requests.
“The messages from users saying ‘Salesforce is broken’ without a screenshot or any steps to replicate kill every admin’s soul!”, she said. “Users think we somehow just know what’s going on in the org at all times.”
According to Alyssa, many of these issues are not the fault of Salesforce, but mainly users’ misunderstanding or ignoring the information already in front of them. This includes validation rule messages, permissions prompts, and process instructions that get skipped over entirely. This then leads admins to investigate issues with little to no context.
These frustrations speak to a much broader problem that the role is experiencing at the moment. As mentioned, expectations are growing, and stats from our recent SF Ben Admin Survey reinforce this pressure. Over half of respondents (53.1%) agreed that too much is expected of Salesforce Admins, while 58.6% said Salesforce itself is becoming increasingly complex to work with.
Moreover, part of this issue has been resourcing. The survey found that 42.86% of Salesforce teams are admin-only, meaning nearly half of respondents operate without dedicated support from a developer. Meanwhile, almost one in five respondents (19.47%) identified as solo admins.
This, naturally, then creates an environment where admins often have to inherit responsibilities that would traditionally belong to several different teams.
Alyssa also pointed to another common tension – admins frequently become the face of decisions they didn’t actually make.
“They see us as the people who ‘fix’ Salesforce rather than strategic partners,” she explained. “Very often leaders will demand something that end users end up hating and then blaming us for, even though we didn’t want to do it in the first place.”
The Work Admins Hate Most Is Repetitive, Not Difficult
Interestingly, many of the tasks Salesforce Admins dislike most are not necessarily the hardest to technically do. More often, they are repetitive, reactive, and endlessly disruptive to more strategic work.
For Salesforce Certified Administrator Ryan Kawashima, one of the biggest frustrations was duplicate management.
“At my last place of employment, the task that ruined my day was merging duplicates,” he said. “It wasn’t hard, but it consistently took time out of my day that could’ve been spent on strategic vs. day-to-day work.”
This is a feeling that again likely resonates with many admins. Data cleanup, permission requests, manual updates, and so on, are rarely impossible tasks. The problem is the sheer volume of maintenance work required to keep a Salesforce org running as smoothly as possible.
Our survey data also reflects this, with technical debt ranked as the single most challenging aspect of Salesforce Administration by 56.3% of respondents.
In practice, technical debt can mean years of rushed implementations, inconsistent naming conventions, and old functionality no one really understands anymore. Over time, even small changes become harder to implement safely.
Another Salesforce professional, Zaira Bhatti, highlighted a common example to SF Ben: “Chasing down why a flow suddenly stopped working because someone renamed a field three months ago and nobody documented it.”
Naturally, these issues grow increasingly common as orgs grow more interconnected. Flow Builder massively reflects this shift, with our survey findings highlighting how much harder it has become to build and maintain automations.
According to our survey, the biggest Flow Builder challenges were debugging errors (34.05%), understanding complex logic (32.18%), and ensuring maintainability (30.45%).
Alyssa also told SF Ben that many organizations still struggle to test changes before deployment, particularly in increasingly complex environments.
“Sometimes you can’t fully replicate how something will behave in Production no matter how hard you try,” she explained. “As orgs have more interconnected automations, it’s hard to manually test for every single scenario when you build something new.”
If we return to our survey data, it shows that many admins are dealing with these challenges without enough support or time to properly address them. When asked what would most help reduce tech debt, respondents overwhelmingly selected dedicated time for cleanup and refactoring (62.17%) as the top answer.
Ultimately, the combination of managing fragile systems, meeting rising expectations, and handling monotonous duties represents a significant source of current professional stress.
AI Could Remove Some Admin Work, But Raise Expectations
It’s no secret that artificial intelligence is being considered as a strong option to mitigate, or even automate, many of these repetitive tasks. But for Salesforce Admins, AI may represent both a solution and a warning sign.
Tools like ChatGPT, Claude, and Agentforce are already helping admins automate repetitive tasks, troubleshoot issues faster, and learn more efficiently. Per our survey, 44% of respondents now use AI daily or regularly, with another 41% using it occasionally,
Alec Green, IWU National & Global’s Associate Director of Salesforce Development, has seen those productivity gains firsthand through tools like Claude Code.
“My team has been fortunate to have a Claude team plan, and using Claude Code for Salesforce development has been amazing and fun,” he explained in a recent LinkedIn post. “Watching my team turn thought into reality faster than ever has been genuinely exciting.”
But Alec also highlighted an important question that we must all consider when using AI tools like Claude: “Just because we can, should we?”
While admins can reduce repetitive work and accelerate development, it may also increase expectations around how quickly admins are expected to deliver. This may also be why the majority of admins are avoiding using vibe coding tools at the moment, as the risk may not meet the reward.
In many ways, AI may actually amplify some of the pressures admins already face. As building becomes easier, judgment, governance, and maintainability become more important than ever.
“The skill gap to building something is shrinking in some ways,” Alec said. “The knowledge of whether you should build it, and how to build it right, is becoming more valuable than ever.”
Final Thoughts
This article isn’t necessarily intended to be a place for admins to simply relate to common frustrations. Every role in the ecosystem, of course, has its own challenges and irritations. What’s more interesting is how the expectations placed on Salesforce Admins are quietly continuing to grow in the background, with many now covering areas of the business that may never have originally been part of the job description.
Some of these challenges are long-standing, while others are emerging alongside AI and increasing platform complexity. Either way, they’re important to highlight, especially as the operational burden placed on admins continues to expand.
Many of these themes are based on findings from the SF Ben Salesforce Admin Survey 2026, and we’ll be exploring the data in more detail across a number of upcoming articles. So if you want a clearer picture of what Salesforce Admins are currently thinking, experiencing, and struggling with, keep an eye on SF Ben over the coming weeks.
