Category: Uncategorized

What happens when the person who knows Salesforce is away?

Posted on October 15, 2026 by - Uncategorized

What you’ll find in this blog

  • Why Salesforce configuration doesn’t always explain the business decisions behind it
  • Which processes and dependencies are worth documenting first
  • How to prepare useful cover before your Salesforce expert takes leave
  • A practical way to test whether someone else could pick up the work

A validation rule is blocking an opportunity from progressing. The salesperson wants it switched off, and the colleague covering Salesforce can see how to do it.

What they can’t see is why it was introduced.

Was it there to prevent an invoicing problem? Does delivery rely on that information? Is it still needed, or does it protect a process the business stopped using last year?

The person who knows is on holiday.

Now a relatively small request needs a decision nobody feels comfortable making. The salesperson waits, someone starts investigating, and there’s a temptation to send a quick message to the person who’s supposed to be taking a break.

This is where Salesforce knowledge transfer becomes practical. Someone needs enough context to handle an ordinary question without guessing.

Access gives you the configuration, but only part of the story

A colleague can open a Flow and follow its logic. That may tell them when a record changes and what happens next. It won’t necessarily explain why the business chose that approach, which exceptions matter or who should be consulted before changing it.

Those answers often sit with the person who has maintained Salesforce for years. They remember the original request, the awkward conversation between teams and the alternative that was tried and abandoned.

That experience is valuable. Problems arise when everyday work depends on being able to reach them.

Even a well-supported org can run into this. Several people may have the technical skills to investigate an issue, while only one knows enough about the business process to judge the consequences.

Start where missing knowledge would hold up the business

“Document Salesforce” is a sizeable task to put on someone’s already busy list. It’s also difficult to know when it’s finished.

A more useful starting point is to identify the processes where uncertainty would cause a real delay or lead to a risky decision.

That might be the automation that creates delivery work after a sale, the integration sending information to Finance, or the report leadership relies on at month-end.

For each one, ask what another person would need to know if a question arrived tomorrow.

Usually, that includes:

  • What the process is meant to achieve
  • Which teams rely on it
  • The important dependencies or known exceptions
  • Who can approve a change to the business rule

You can add links to the relevant Salesforce components, existing instructions or support records. The aim is to make the explanation easy to find and useful at the point someone needs it.

Write down the reason while you still have it

The easiest time to capture a decision is when you’re making it.

Suppose a team agrees that a renewal opportunity should be created 90 days before a contract ends. The Flow can show that timing. A short accompanying note can explain that Account Management needs those 90 days to review usage and agree the next contract.

It can also identify the person responsible for confirming whether that timing should change.

Without that context, a future request to reduce the period to 30 days might look like a simple configuration update. With it, the Admin knows there’s a business conversation to have first.

The same applies when a request is declined. Recording why an apparently simpler approach wasn’t suitable can save someone repeating the investigation six months later.

Keep the explanation alongside the work where possible, and make sure colleagues know where the fuller record lives. Notes are less useful if finding them requires asking their author.

Agree what cover actually involves

A handover needs to explain what requires attention while someone is away.

Who receives Flow error notifications? Is there an import that needs checking on a particular day? Which requests can wait until the usual Admin returns?

It’s worth being specific about the limits of cover too. Someone may be comfortable investigating a failed process but need approval before changing it. Another colleague may be able to manage users and answer routine questions without having the experience to amend complex automation.

Agree an escalation route that reflects those differences. Include a business contact who can explain the impact of an issue and make decisions about how work continues.

If an external support partner is providing cover, they need that context as well. They can investigate the configuration and explain the technical options. Someone within the business still needs to confirm the intended outcome.

Test the handover with a real question

You don’t have to wait for annual leave to find out whether the notes work.

Choose a question the Salesforce team dealt with recently and ask a colleague to work through it using the information available.

Could they find the relevant process? Could they explain its purpose and identify who to contact? Would they know when to stop investigating and escalate?

Where they get stuck tells you what to add. Perhaps the note needs a link, the business owner has changed or an important dependency was assumed rather than explained.

This is a manageable way to improve documentation over time. It also avoids spending hours writing material that doesn’t answer the questions people actually have.

Give knowledge transfer time in the working week

If sharing knowledge is always something to do after the support queue is cleared, it may never happen.

Build a little time into changes, handovers and routine reviews. When an issue takes significant investigation, capture the finding before closing it. When a process changes, update the explanation and its owner at the same time.

The person who knows Salesforce best shouldn’t have to spend every holiday wondering whether a message will arrive. Their colleagues shouldn’t have to choose between waiting and making an uninformed change.

Start with one important process. Give the next person enough information to understand it, recognise a problem and find the right decision-maker.

If your team needs help maintaining Salesforce alongside this work, explore Xenogenix Salesforce Managed Services.

The Salesforce work everyone assumes someone else owns

Posted on September 29, 2026 by - Uncategorized

What you’ll find in this blog:

Why important Salesforce work can lose its owner

The difference between using a process and owning its outcome

Four moments where ownership becomes unclear

A simple way to settle the next decision

The Salesforce work everyone assumes someone else owns

A report is used in Monday’s sales meeting. The figures start to look odd, so the sales manager asks the Admin to check it. The Admin finds that the report is working exactly as built. The underlying data changed three weeks ago when a team altered the way it records renewals. Who was supposed to tell the report owner? And who decides what the report should now show?

Nobody has necessarily made a mistake. Each person may have done their own job. The problem is that the work crosses the boundary between those jobs, and the boundary has no owner.

That is a familiar Salesforce problem. It appears in reporting, integrations, automation, permissions and the small process changes that never quite become a project. It rarely announces itself as a major incident. More often, people compensate: they export a report, keep a second spreadsheet or ask the one person who seems to know how it works.

A named Admin does not settle every question

An Admin can maintain a Flow, investigate an error and explain what a field does. They cannot decide alone whether a sales handover is still the right business process, whether a report answers the question leadership now asks, or which team should resolve a disputed record.

For a process that crosses teams, it helps to separate three responsibilities. Someone owns the business outcome: what should happen, and what counts as success? Someone owns the platform component: how does Salesforce support that outcome, and how is it maintained? Someone notices and escalates when the reality no longer matches the intention.

One person might cover more than one role in a small organisation. That is fine. The point is to make the decision explicit, so it does not depend on who happens to be available.

Where ownership tends to disappear

When a deal moves from Sales to delivery. Sales has completed its part, but delivery needs the scope, dates and expectations in a form it can actually use. If those details change, who checks that both teams are working from the same understanding?

When an integration quietly fails. IT may own the connection and the Admin may own the fields it updates. The business team experiences the missing data. Unless someone is responsible for noticing and deciding what happens next, each group may assume another is watching.

When a dashboard outlives the decision it was built for. People continue to open it because it is there. Its filters, definitions or targets no longer match the business question. Technical ownership of the dashboard is not the same as ownership of the decision it informs.

When a workaround becomes normal. A spreadsheet may start as a sensible temporary fix. Six months later, it is the only place a team can see the full picture. Who decides whether to change Salesforce, change the process or keep the workaround deliberately?

Start with one awkward handover

You do not need an ownership chart for every field in the org. Choose one piece of work that keeps coming back as a question or a surprise. Write down the point where it passes from one person or team to another. Then agree four things: who owns the intended outcome, who maintains the Salesforce element, what signal would tell you it is going wrong, and who makes the call when it needs to change.

That conversation often reveals a more useful next step than adding another field or building another dashboard. Sometimes the system needs changing. Sometimes a team needs a clearer handover. Sometimes the issue is simply that nobody was expected to look.

Salesforce works best when responsibility travels with the work. If a process matters enough to automate or report on, it matters enough to decide who will notice when it no longer serves its purpose.

Dreamforce 2026: What Was Announced and What Actually Matters?

Posted on September 21, 2026 by - Uncategorized

Dreamforce 2026 brought a flood of announcements, from AIforce and Koa to new Agentforce capabilities, Slackforce and deeper partnerships with Anthropic, AWS and Google Cloud. But not every announcement needs to change your Salesforce roadmap.

In this blog, we cut through the noise and look at the developments we think existing Salesforce customers should understand, what they could mean in practice, and where it’s probably too early to take action.

What you’ll find in this blog

  • The biggest announcements from Dreamforce 2026
  • What AIforce could change about how people interact with Salesforce
  • Why Koa and the latest Agentforce developments matter
  • What existing Salesforce customers should prioritise now

Dreamforce 2026: What Was Announced and What Actually Matters?

Dreamforce is very good at making everything sound like it’s about to change immediately.

New products.

New AI.

New partnerships.

New names for things you’d only just learned the last name of.

Dreamforce 2026 was no exception.

Salesforce unveiled AIforce, introduced its first CRM-specific reasoning model, expanded Agentforce, pushed Slack further towards becoming an AI workspace and announced deeper integrations with some of the biggest names in technology.

There is genuinely important stuff in there.

But if you’re running an existing Salesforce environment, the more useful question probably isn’t:

“What did Salesforce announce?”

It’s:

“Which bits actually matter to us?”

So, let’s go through the biggest developments.

1. AIforce is probably the biggest strategic shift

The headline announcement was AIforce.

Salesforce describes it as a new live interface layer designed to make the data, workflows, business logic, permissions and governance inside Salesforce available from other AI interfaces and places where people already work.

That’s a fairly big change in thinking.

Historically, Salesforce has largely been somewhere users go to do work.

You log in.

You open a record.

You update an opportunity.

You run a report.

AIforce points towards a future where Salesforce increasingly sits underneath the experience instead.

You might interact with Salesforce through Slack, Claude, another AI assistant or a custom interface, while the Salesforce platform continues to provide the trusted data, rules, permissions and processes behind the scenes.

Why does this actually matter?

Because it could eventually change one of the oldest Salesforce challenges of all:

adoption.

Instead of constantly trying to get users to work in Salesforce, Salesforce may increasingly come to the places where they already work.

That could be hugely useful.

But there’s a catch.

Those interfaces still rely on what sits underneath them.

Bad data doesn’t become good data because an AI agent accesses it.

An overly complicated process doesn’t suddenly become sensible because you access it through a different interface.

And weak governance becomes more important, not less, when AI can take action on a user’s behalf.

Our take

You probably don’t need an “AIforce project” tomorrow.

You do need to make sure your Salesforce environment is something you would actually be comfortable allowing an AI agent to use.

That means trusted data, clear processes, appropriate permissions and well-managed automation.

2. Koa: Salesforce is building AI specifically for CRM

Another major announcement was Koa, Salesforce’s first CRM reasoning model, developed with NVIDIA and built on NVIDIA Nemotron. Salesforce says it has been designed specifically to reason through complex CRM tasks and multi-step business processes.

This is interesting because much of the AI conversation so far has centred around large general-purpose models.

Koa represents a slightly different direction.

Rather than asking a general AI model to understand how selling, servicing customers and managing CRM workflows works, Salesforce is building a model specifically around those kinds of tasks.

Why does this matter?

Because enterprise AI increasingly seems to be moving towards specialisation.

A model that understands the context of CRM, business processes and Salesforce-specific workflows could potentially make agents more reliable when they’re dealing with complex operational work.

That matters much more than whether an AI can simply write a nice email.

The long-term opportunity is AI that understands enough context to help make decisions and carry out multi-stage work.

Our take

This is one to watch rather than something most customers need to act on immediately.

Salesforce is making some strong claims about Koa’s CRM reasoning performance, but those claims are currently based on Salesforce’s own benchmarking, so real-world customer results will matter more over time.

The broader direction, though, is important.

AI inside Salesforce is becoming less about generating content and more about reasoning through actual business processes.

3. Agentforce is moving from experiments to real work

Agentforce itself wasn’t the new shiny announcement this year.

And that’s arguably significant.

Salesforce’s Dreamforce 2026 announcements increasingly position Agentforce as an established layer of the platform rather than something experimental. Its official Dreamforce coverage included new long-horizon agents, expanded AgentExchange capabilities and more examples of customers deploying Agentforce across sales and service.

The conversation is changing from:

“What could an AI agent do?”

to:

“What work should we actually let one do?”

That’s a much healthier question.

Why does this matter?

Because the value of AI agents isn’t in having one.

It’s in finding processes where automation genuinely improves speed, consistency, customer experience or employee productivity.

That might be:

  • qualifying or responding to inbound enquiries
  • resolving straightforward service requests
  • preparing information before a human interaction
  • carrying out repetitive administrative work
  • supporting users through a multi-stage process

The use case matters far more than the technology label.

Our take

Start with the process, not Agentforce.

If a workflow is inconsistent, poorly documented or relies on questionable data, automating it probably isn’t your first move.

Find something repetitive, reasonably structured and measurable.

Then ask whether agentic automation could make it better.

4. Slackforce shows where Salesforce thinks work is heading

Yes, Slackforce is now a thing too.

Salesforce is increasingly positioning Slack as more than a collaboration or messaging tool. Its Dreamforce coverage describes Slackforce as part of its move towards a workspace where employees and AI agents can work together.

This connects directly to AIforce.

If Salesforce becomes less dependent on a traditional CRM interface, Slack becomes one obvious place for employees to interact with Salesforce data and agents.

Why does this matter?

Because for a lot of organisations, the biggest obstacle to Salesforce adoption isn’t functionality.

It’s friction.

If somebody can ask a question, approve something or trigger a process from the place they already spend their day, that could make Salesforce much easier to use.

Our take

Don’t start planning around the word “Slackforce”.

Look at how your employees actually work.

If your organisation already lives in Slack, these developments could become very relevant.

If it doesn’t, there’s little value in forcing another interface into the mix simply because Salesforce has given it a new name.

5. Claudeforce and the partnerships might be more important than they first appear

One of the interesting themes around Dreamforce wasn’t Salesforce trying to build absolutely everything itself.

Salesforce announced Claudeforce with Anthropic before Dreamforce, alongside deeper integrations and partnerships with AWS and Google Cloud. Its official Dreamforce announcements also highlighted expanded infrastructure and agent integrations with both cloud providers.

This links back to AIforce.

Salesforce increasingly seems comfortable with the idea that customers may use another company’s AI model or interface, while Salesforce provides the underlying trusted business context.

Why does this matter?

For customers, potentially quite a lot.

It points towards greater choice rather than a future where every company has to use one Salesforce AI model in one Salesforce interface.

That could allow organisations to choose different AI tools for different use cases while keeping Salesforce as the system providing trusted customer and operational data.

Our take

This is a direction worth watching carefully.

The future enterprise stack may be much less about buying one giant AI platform and much more about connecting the right models and interfaces to trusted business systems.

Which makes your underlying architecture, integrations and governance increasingly important.

6. The “headless” Salesforce idea is getting much more real

Before Dreamforce, Salesforce had already been talking about Headless 360, allowing Salesforce functionality and data to be exposed to external agents and interfaces.

AIforce takes that idea much further.

Salesforce is essentially saying:

the Salesforce interface doesn’t have to be the only front door to Salesforce anymore.

Its own Dreamforce resources link the Headless 360 expansion directly with the broader move towards agentic experiences outside the traditional Salesforce UI.

Why does this matter?

Because over time it could change how Salesforce projects are designed.

Instead of asking:

“What Salesforce screen should the user see?”

we may increasingly ask:

“Where does this user already work, and how should Salesforce support them there?”

That’s potentially a much better starting point.

So, what should existing Salesforce customers actually do?

Probably less than the Dreamforce keynote makes you feel you should.

You don’t need to implement every new product.

You don’t need to rewrite your roadmap around every announcement.

And you certainly don’t need to adopt something simply because the word AI has appeared in front of it.

But there are a few sensible things worth doing now.

Check your data

AI agents need reliable information.

If duplicate, incomplete or inconsistent data already causes problems for your human users, it will also create problems for AI.

Review your processes

Ask whether your Salesforce automation and workflows still reflect how your organisation works today.

There’s little point automating an outdated process more efficiently.

Review permissions and governance

The more agents can access and act on business data, the more important governance becomes.

Make sure people and systems have access to what they genuinely need.

Identify worthwhile AI use cases

Start looking for repetitive, structured work where faster execution could create measurable value.

Avoid starting with:

“Where can we put Agentforce?”

Start with:

“Where are our teams wasting time?”

Get your Salesforce foundations ready

This may be the least exciting Dreamforce recommendation.

It may also be the most valuable.

The organisations that will get the most from Salesforce’s newer AI capabilities are unlikely to be those that simply adopt them first.

They’ll be the organisations whose data, processes and architecture allow them to use those capabilities well.

Our biggest takeaway from Dreamforce 2026

Dreamforce 2026 wasn’t really about one new product.

It was about Salesforce becoming less dependent on the traditional idea of Salesforce as a piece of software you log into.

Data 360 provides trusted data.

Salesforce provides the underlying processes, permissions and business logic.

Agentforce provides agents capable of carrying out work.

AIforce allows that capability to appear in more places.

And models such as Koa are being developed to reason about the business processes sitting underneath all of it.

That direction is genuinely interesting.

But the practical advice for most Salesforce customers remains surprisingly familiar:

Get the fundamentals right first.

Because whatever interface, agent or AI model you eventually use, it will still depend on the Salesforce environment underneath it.

And that’s the bit you can start improving today.

Not sure whether your Salesforce org is ready for what comes next? Get in touch with us today and we will be happy to run through your orgin more detail.

Salesforce Changed the Name Again: Your Guide to What Everything Is Called Now

Posted on September 17, 2026 by - Uncategorized

If you work with Salesforce, you may have noticed that keeping up with the technology is sometimes easier than keeping up with what everything is called.

Data Cloud became Data 360.

Sales Cloud became Agentforce Sales… and now Sales Cloud is making a comeback.

Revenue Cloud became Agentforce Revenue Management.

Marketing Cloud Next became Agentforce Marketing.

Headless 360 arrived and Salesforce Platform promptly re-entered the conversation.

And now, following Dreamforce 2026, we have another name to learn: AIforce.

Confused?

You’re definitely not the only one.

So rather than simply listing the latest Salesforce terminology, we’ve pulled together a guide to what has actually changed, what’s genuinely new, and which familiar names you can safely continue using.

What you’ll find in this blog

  • The biggest Salesforce product name changes
  • Which changes are simply rebrands and which represent new technology
  • What’s changed again following Dreamforce 2026
  • What the new terminology actually means for Salesforce customers

First, why does Salesforce keep changing the names?

There is actually some logic behind much of it.

Salesforce has spent the last couple of years moving away from positioning its products as separate “clouds” and towards a much more connected platform built around data, AI agents and shared services.

That shift accelerated with Agentforce.

During 2025 and 2026, the Agentforce name began appearing across Salesforce’s portfolio as the company increasingly positioned AI agents as part of the core platform rather than an optional extra.

But ahead of Dreamforce 2026, something interesting happened.

Some of those familiar product names started coming back.

So let’s translate.

Sales Cloud → Agentforce Sales → Sales Cloud

This might be the best example of why Salesforce customers can be forgiven for losing track.

Sales Cloud became Agentforce Sales, reflecting Salesforce’s push to embed AI agents directly into the sales process.

Then, shortly before Dreamforce 2026, Salesforce started using Sales Cloud prominently again.

The underlying direction hasn’t reversed. Agentforce capabilities remain part of Salesforce’s sales proposition. What’s changed is the label being put on the box.

So if somebody says Sales Cloud, you haven’t missed another new product.

They’re talking about the sales platform you already know.

Service Cloud → Agentforce Service

Service Cloud has also been increasingly presented as Agentforce Service.

Again, this reflects more than Salesforce simply deciding it fancied a new name.

Agentforce is being built into service workflows so AI agents can work alongside human service teams, resolve routine requests and support employees across channels.

You’ll still see both Service Cloud and Agentforce Service terminology across Salesforce materials, so don’t be surprised if the names are used interchangeably for a while.

Data Cloud → Data 360

This one is much simpler.

Data Cloud is now Data 360.

Same product. New name.

Data 360 remains Salesforce’s real-time data platform, bringing information from different sources together and making that trusted data available across Salesforce.

The new name reflects its increasingly important role beyond traditional customer data use cases, particularly as the data foundation underneath AI and Agentforce.

If someone says Data Cloud, they’re talking about what Salesforce now officially calls Data 360.

Revenue Cloud → Agentforce Revenue Management

This one needs a little more explanation.

Salesforce now refers to Revenue Cloud as Agentforce Revenue Management.

But this shouldn’t be interpreted as Salesforce simply changing the logo at the top of the screen.

Agentforce Revenue Management represents Salesforce’s broader approach to managing the revenue lifecycle, bringing areas including product configuration, pricing, quoting, contracts, orders and billing closer together.

It’s particularly important for businesses still using Salesforce CPQ.

And what about Salesforce CPQ?

Salesforce CPQ hasn’t simply been renamed Agentforce Revenue Management.

They’re not the same thing.

CPQ is the established configure, price and quote product many Salesforce customers still use today.

Agentforce Revenue Management represents Salesforce’s newer revenue architecture and broader direction of travel.

For organisations using CPQ, the important question therefore isn’t:

“What’s CPQ called now?”

It’s:

“What does Salesforce’s revenue roadmap mean for our existing CPQ implementation?”

That’s a much more useful conversation.

Pardot → Marketing Cloud Account Engagement

This is one of the older name changes, but it’s still probably the one we hear ignored most often.

Pardot officially became Marketing Cloud Account Engagement, usually shortened to MCAE.

The product didn’t disappear overnight and plenty of people in the Salesforce ecosystem still call it Pardot.

So if somebody says Pardot in a meeting, nobody needs to correct them.

We all know what they mean.

Marketing Cloud → Marketing Cloud Engagement

The established Salesforce marketing platform became Marketing Cloud Engagement, or MCE.

This distinction became increasingly important when Salesforce started building its next-generation marketing platform.

Which brings us to…

Marketing Cloud Next → Agentforce Marketing

Salesforce introduced Marketing Cloud Next as its next-generation marketing platform, built natively on the Salesforce Platform and closely connected with Data 360 and Agentforce.

That platform is now being positioned as Agentforce Marketing.

This isn’t simply Marketing Cloud Engagement with another new name.

It’s part of Salesforce’s newer marketing architecture, designed around unified data, automation and AI agents capable of doing more of the campaign work themselves.

At Dreamforce 2026, Salesforce expanded that vision further with Campaign Agent, which can help create content, assemble audiences and campaigns, select channels and optimise activity against a marketer-defined goal.

So this is one of the name changes where the technology underneath really does matter.

Einstein → Agentforce… sort of

This is another area where it’s tempting to create a neat before-and-after arrow.

Unfortunately, reality isn’t quite that tidy.

Salesforce used the Einstein brand for AI capabilities for years, with names including Einstein AI, Einstein GPT and Einstein Copilot.

Agentforce has increasingly become the umbrella for Salesforce’s agentic AI capabilities.

But Einstein hasn’t simply been renamed Agentforce everywhere.

You’ll still encounter Einstein terminology within Salesforce products and features.

It’s better to think of this as an evolution of Salesforce’s AI strategy rather than a straightforward product rename.

Headless 360 → Salesforce Platform

Here’s one of the newest additions to the list.

Earlier in 2026, Salesforce introduced Headless 360, an architecture designed to expose Salesforce data, workflows, business logic and actions through APIs, MCP tools and other developer interfaces.

Ahead of Dreamforce, Salesforce began putting the Salesforce Platform name front and centre again.

The technology and “headless” strategy haven’t disappeared.

In fact, they’re central to one of the biggest announcements from Dreamforce 2026.

And now meet AIforce

If you only learn one genuinely new Salesforce term from Dreamforce 2026, make it this one.

AIforce is Salesforce’s new live interface layer.

The idea is that people and AI agents shouldn’t necessarily have to open Salesforce to use everything stored and configured inside it.

Instead, Salesforce can bring its data, workflows, permissions, business logic and actions into the interface where someone is already working.

That could be Slack.

It could be Claude.

It could be another AI interface.

Or it could still be Salesforce itself.

Underneath AIforce sits the technology Salesforce has been developing through its headless architecture.

So Headless 360 hasn’t exactly vanished. Its underlying approach has become part of a much bigger story.

Salesforce is increasingly separating where the work happens from where the business logic and data live.

That’s a significant shift.

Claudeforce is another name you’ll start hearing

Yes. There’s another one.

Claudeforce comes from Salesforce’s expanded partnership with Anthropic.

It brings Salesforce context and actions into Claude so users can work with Salesforce data, workflows and business logic directly through Anthropic’s AI interface.

Unlike Data Cloud → Data 360, this isn’t a product rename.

It’s an integration and partnership proposition.

Still, expect to hear the name a lot.

And apparently we’re calling it Slackforce now too

Dreamforce 2026 also introduced the Slackforce language.

Again, this doesn’t mean Slack has disappeared and been replaced by a completely different product.

It’s part of Salesforce’s broader vision of Slack becoming an interface where people and AI agents work together, rather than simply somewhere teams send messages to each other.

The important thing here isn’t really the name.

It’s the direction.

So what should Salesforce customers actually call everything?

The simplest rule is: don’t worry too much about using yesterday’s name.

If you say Pardot instead of MCAE, people will understand you.

If you say Data Cloud instead of Data 360, you’re not talking about an obsolete platform.

And if you’ve only just trained everybody to say Agentforce Sales and Salesforce starts calling it Sales Cloud again, you’re allowed a small sigh.

What’s much more important is understanding whether a name change represents:

A rename
The product is essentially the same, but Salesforce has changed its name.

An evolution
The familiar product is developing into a broader or differently architected offering.

A genuinely new capability
There’s new technology underneath the new terminology.

Those distinctions matter far more than memorising Salesforce’s latest vocabulary.

The bigger Dreamforce 2026 story isn’t actually the names

Look past all the branding changes and Salesforce’s direction becomes much clearer.

Data 360 provides the trusted data.

The Salesforce Platform provides the workflows, permissions and business logic.

Agentforce provides AI agents capable of reasoning and taking action.

AIforce increasingly allows all of that to appear wherever people actually work.

And integrations with platforms such as Claude, Slack, Google and AWS mean Salesforce is becoming less dependent on users spending their day inside a traditional Salesforce interface.

That’s the bit businesses should be paying attention to.

Because the question isn’t really whether your team can remember what Salesforce has renamed something.

It’s whether your existing Salesforce environment, data and processes are ready to take advantage of what those new capabilities can actually do.

And that starts with getting the foundations right.

If you’re trying to understand what Salesforce’s latest changes mean for your existing setup, roadmap or investment, talk to the Xenogenix team. We’ll help you separate the genuinely useful developments from the new terminology and work out what actually matters for your organisation.

Salesforce Winter ’27: What Should You Actually Be Paying Attention To?

Posted on September 1, 2026 by - Uncategorized

Salesforce Winter ’27 is on its way.

If you’re responsible for Salesforce, that usually means one thing: a very large set of release notes and the slightly daunting job of working out which bits actually matter to your organisation.

The good news is that you don’t need to care about everything.

Salesforce releases new functionality three times a year, and Winter ’27 includes updates across Sales, Service, automation, analytics, security, Agentforce, Data 360, Revenue Management and more.

But the most useful way to approach a Salesforce release isn’t to ask:

“What’s new?”

It’s to ask:

“What does this mean for our Salesforce org?”

What you’ll find in this blog:

  • What Salesforce customers should be checking ahead of Winter ’27.
  • Why existing processes and integrations should come before shiny new features.
  • How to identify updates that could simplify the way you currently use Salesforce.
  • A practical way to decide what deserves action now, later or not at all.

Start with what could affect what you already have

It’s tempting to head straight for the new features.

Before you do, look at the things that could affect your existing Salesforce environment.

Salesforce’s Release Updates can include changes to performance, security, business logic and usability, and some can affect existing customisations. Salesforce specifically recommends reviewing these as part of release preparation.

Winter ’27 also gives us a good example of why this matters.

Salesforce is ending support for API traffic using incorrect instanced URLs. Shortly after an org receives Winter ’27, affected API traffic will no longer be supported, with enforcement taking place on a rolling basis.

It’s not the most exciting item in the release notes.

But if it affects one of your integrations, it’s considerably more important than a shiny feature you’ll never use.

That’s why we’d always recommend starting with impact before opportunity.

Use your sandbox for what it’s actually there for

The Winter ’27 sandbox preview began on 28 August, giving Salesforce teams an opportunity to test the release against their own configuration before production upgrades.

And that’s the important bit.

A pre-release environment can show you how a new Salesforce feature works.

Your sandbox can help you understand how that change works with your Salesforce configuration.

That means testing the things your organisation actually depends on:

  • important business processes;
  • automations and Flows;
  • integrations;
  • custom development;
  • third-party applications;
  • permissions and security;
  • critical reports and dashboards.

Salesforce recommends using the preview period to validate core business processes, custom code and third-party integrations.

The more complex your Salesforce environment is, the more important that becomes.

Then look for opportunities to simplify

Once you’ve established that nothing is likely to cause a nasty surprise, then I’d start looking at what’s new.

But with a slightly different question.

Instead of:

“What can we add?”

Try:

“Could anything new replace something we’re already doing the hard way?”

Perhaps you’ve built a custom solution because Salesforce couldn’t previously do something you needed.

Maybe your users rely on a workaround.

Perhaps you’ve got an automation that has gradually become more complicated as requirements have changed.

A new standard capability won’t always be the answer. But each Salesforce release is a useful opportunity to challenge whether the way you’re doing something today is still the best way to do it.

Sometimes the best use of a new Salesforce feature isn’t adding more to your org.

It’s allowing you to take something away.

What will your users actually notice?

Release readiness isn’t purely a technical exercise.

Some Winter ’27 changes will happen automatically when the release reaches your org, while others require an administrator to enable or configure them. Salesforce specifically recommends considering whether changes need to be communicated to users in advance.

So alongside technical testing, ask:

Will anything change the way our users work?

If the answer is yes, think about communication and adoption before the change reaches them.

A useful feature can still create frustration if nobody understands why something suddenly looks or behaves differently.

And yes, there’s plenty of AI

Unsurprisingly, Agentforce and generative AI feature heavily in Winter ’27.

Salesforce describes the release as helping businesses move AI from experimentation towards measurable business impact, with developments across Agentforce and the wider Salesforce platform.

There are some interesting capabilities in there.

But our advice remains the same:

Don’t adopt AI simply because Salesforce has made it available.

Start with the business problem.

Is there a process where AI could genuinely remove effort, improve customer experience or help people make better decisions?

Is your underlying data good enough?

Are your permissions and governance ready?

And can you actually define what success would look like?

If not, the newest feature can wait.

Adopt. Investigate. Ignore.

One of the simplest ways to make a Salesforce release manageable is to put relevant changes into three categories.

Adopt

There’s a clear use case, benefit or requirement, and you’re confident about the impact.

Investigate

It looks potentially useful, but you need to understand the implications, test it or build a stronger business case.

Ignore

It isn’t relevant to your organisation right now.

And ignore is a perfectly valid category.

The goal of release readiness isn’t to use as many new Salesforce features as possible.

It’s to make sure your organisation understands what is changing, protects the things it already relies on and takes advantage of the improvements that genuinely make Salesforce work better.

Need a second pair of eyes on Winter ’27?

If you’re unsure which Winter ’27 changes could affect your Salesforce environment, or which new functionality is actually worth investigating, Xenogenix can help you review your org and prioritise what matters.

The Salesforce Problems That Aren’t Quite Big Enough to Become a Project

Posted on August 19, 2026 by - Uncategorized

What you’ll find in this blog

  • Why small Salesforce frustrations can have a bigger impact than you think.
  • How everyday workarounds and inefficiencies gradually add complexity to your org.
  • Why these problems often stay stuck on the Salesforce to-do list.
  • How a fresh pair of expert eyes can help, without turning every issue into a major project.

There’s an interesting middle ground in Salesforce.

At one end, you have the big projects. A new implementation, a major integration, a significant piece of development or a wider transformation programme. They have budgets, timelines and people assigned to them.

At the other end are the everyday tasks your Salesforce team deals with as part of keeping the platform running.

But somewhere in between sit all those other problems.

They’re not business-critical. Salesforce still works. Nobody is raising a major incident. But something isn’t quite right.

Perhaps a report has never given you exactly what you need. A process takes six steps when it feels like it should take three. There’s a Flow nobody particularly wants to touch because the person who built it left two years ago.

Individually, these things don’t feel important enough to become a project.

So they stay on the list.

When “not broken” becomes the problem

It’s very easy to prioritise Salesforce work according to what’s broken.

If users can’t do their jobs or a critical process stops working, it naturally moves straight to the top of the list.

The harder decisions are around the things that technically work, but could work considerably better.

Over time, small inefficiencies become normal. Users develop workarounds. Someone exports data into Excel every Friday because that’s simply how the report gets produced. Extra clicks become part of a process because nobody has had time to investigate why they’re needed.

Eventually, people stop questioning them.

That’s when “not broken” can become quite an expensive standard to work to.

Small Salesforce frustrations rarely stay small

One unnecessary step in a process doesn’t sound particularly concerning.

But if 20 people complete that process several times a day, it starts to look rather different.

The same applies to poor data quality, unreliable reporting, duplicate records, underused automation and manual workarounds. The individual problem can seem insignificant while the cumulative effect is anything but.

There’s another consequence too.

A Salesforce environment gradually becomes harder to manage when these little compromises accumulate. New automation gets built around old processes. New fields get added rather than existing ones reviewed. Another workaround is introduced because fixing the underlying issue feels too difficult.

Five years later, everyone knows Salesforce is more complicated than it needs to be, but nobody can point to the single decision that made it that way.

Usually, there wasn’t one.

Why these jobs keep getting pushed down the Salesforce to-do list

The problem isn’t necessarily a lack of willingness to fix them.

Often, it’s capacity.

Salesforce Admins and CRM Managers have plenty competing for their attention. There will always be a more urgent user request, another report needed for a meeting, a new business requirement or a larger project demanding time.

Sometimes it’s also expertise. An internal team may know what isn’t working but be less certain about the best way to solve it.

And occasionally, the biggest barrier is simply confidence.

When you’re looking at an automation or configuration that’s been in place for years and you’re not entirely sure what else depends on it, “leave it alone for now” can feel like the safest option.

That’s understandable.

But it does mean the same problems can sit on a Salesforce to-do list month after month.

Sometimes you just need a fresh pair of eyes

Not every Salesforce problem needs a consultancy project.

Sometimes what you really need is someone who hasn’t been staring at the same org for years to look at the problem and ask a few different questions.

Why does the process work this way?

Does it still need to?

Is Salesforce already capable of doing this differently?

Is there a simpler approach?

What would we do if we were building it today?

Even if the answer is something your internal team can implement themselves, getting an outside perspective can help you get past the point where a problem has simply become part of the furniture.

And that’s the thinking behind something we’re trying this summer.

Introducing the Salesforce Summer Surgery

For the remainder of the summer, we’re opening a limited number of free 30-minute Salesforce Summer Surgery sessions.

The idea is deliberately simple.

Bring us one Salesforce problem.

It could be a reporting frustration, an awkward process, troublesome automation, an integration question, a growing Admin backlog, a data issue or something else entirely.

We’ll give you 30 minutes with one of our Salesforce experts to talk it through and give you our perspective on what we’d do next.

There won’t be a presentation or a generic Salesforce demo, and you don’t need to turn it into a project afterwards.

One problem. One expert. 30 minutes.

No sales pitch. Just practical advice.

What’s been sitting on your Salesforce list?

If there’s something in your org that isn’t technically broken but you know could work better, this might be a good opportunity to finally take another look at it.

Bring it to the Salesforce Summer Surgery.

Book your call here.

5 Salesforce Jobs Worth Tackling During a Quieter August

Posted on August 11, 2026 by - Uncategorized

What you’ll find in this blog

  • Practical Salesforce tasks that are ideal for quieter periods.
  • Why reports, access and automation benefit from regular review.
  • How small data and usability improvements can make Salesforce easier to use.
  • Why reviewing your existing to-do list can be just as valuable as completing it.

August can be an unusual month for Salesforce teams.

For some organisations, things carry on exactly as normal. For others, annual leave, fewer meetings and slightly quieter customer activity create something that’s fairly rare during the rest of the year: a little breathing room.

It can be tempting to use that time to finally tackle some of the bigger items on the Salesforce roadmap, but there’s another opportunity that’s easily overlooked.

Look at the small things.

Most Salesforce environments accumulate them over time. They’re not broken enough to become urgent and they’re rarely exciting enough to become a project, so they simply sit there while more pressing work takes priority.

August can be a good opportunity to give some of them attention.

1. Take a Fresh Look at Your Reports and Dashboards

Reports have a habit of multiplying.

Someone needs a particular view for a meeting, another team creates their own version, somebody leaves the organisation and eventually you’re left with a reporting library that nobody entirely understands.

Rather than immediately building another report, use the opportunity to look at what already exists.

Which reports are genuinely being used? Are there several versions showing essentially the same information? Are your most important dashboards still answering the questions the business is asking today?

You don’t necessarily need to delete everything. Simply understanding what is useful and what has become noise can make Salesforce much easier to navigate.

2. Review Who Has Access to What

User access is another area that’s easy to overlook while everything is working.

People change roles, responsibilities move between teams and temporary permissions have a habit of becoming permanent.

A quieter period is a useful time to review users, profiles, permission sets and access levels and ask whether they still reflect the way your organisation operates today.

It’s not glamorous Salesforce work, but it’s important.

3. Revisit Your Automation

Automation is usually created for a good reason. The problem is that the business process behind it doesn’t necessarily stay the same.

Over time, organisations can accumulate Flows, alerts and automated processes that overlap, no longer add much value or make a relatively simple process far more complicated than it needs to be.

You don’t need to rebuild everything. Start by understanding what’s there and whether it’s still doing something useful.

You may uncover opportunities to simplify processes before the business gets busy again.

4. Look at Your Data Through a User’s Eyes

It’s easy to talk about data quality as though it’s purely a technical issue.

Often, it’s actually a usability issue.

Duplicate records, inconsistent naming, unnecessary fields and missing information all make Salesforce harder for people to trust and use.

Spend some time looking at the CRM as your users experience it. Are they being asked to enter information nobody uses? Is important information difficult to find? Are there obvious inconsistencies that have gradually crept in?

Small improvements here can make a surprisingly big difference.

5. Revisit the List You’ve Been Ignoring

Every Salesforce team has one.

The list of things everyone agrees would be useful but which never seem quite important enough to do today.

A quieter period is a good opportunity to revisit it, but don’t simply start at the top and work down.

Ask whether each item still matters.

Business priorities change, and something requested six months ago may no longer be relevant. Equally, something that once seemed minor may now solve a genuine problem.

You may find that the most valuable outcome isn’t completing the list at all. It’s making the list shorter by deciding what you no longer need to do.

Don’t Wait for Something to Break

Salesforce optimisation doesn’t always need to involve a major project.

Often, the greatest improvements come from regularly stepping back, reviewing what’s accumulated and making small changes that keep the platform aligned with the business.

If August gives you a little more breathing room, it’s worth using some of it to look at the things that don’t normally get your attention.

Because once September arrives, that to-do list probably isn’t going to get any shorter.

Why Your Salesforce To-Do List Never Gets Any Shorter

Posted on July 27, 2026 by - Uncategorized

What you’ll find in this blog

  • Why Salesforce to-do lists naturally continue to grow as organisations become more reliant on their CRM.
  • The difference between being busy and making meaningful progress with Salesforce optimisation.
  • Why prioritisation is one of the most valuable skills for Salesforce CRM Managers.
  • When additional Salesforce support or Managed Services can help maintain momentum and accelerate improvement.

If you’ve been responsible for Salesforce for any length of time, you’ll probably recognise the feeling of crossing three jobs off your to-do list only to find another five have appeared before the day is over. It can sometimes feel as though no matter how productive you are, the list never really gets any shorter.

The obvious assumption is that there is simply too much work to do, but that’s rarely the real issue. More often than not, it’s a sign that Salesforce has become an increasingly important part of the organisation. As more departments rely on the platform, more people naturally begin to see opportunities to improve it. Sales want better visibility, marketing would like additional information, finance need more accurate reporting and customer service are looking for ways to remove repetitive manual tasks. Each request is perfectly reasonable when viewed in isolation, but together they create a constant stream of competing priorities.

Ironically, this is often a symptom of success. Nobody asks for improvements to a system they don’t use. When people actively suggest new reports, automations or dashboards, it’s usually because they can already see the value Salesforce brings and believe it could do even more. The challenge isn’t stopping those ideas from coming in. It’s deciding which improvements will create the greatest value for the business.

Why Every Salesforce CRM Manager Has a Growing To-Do List

Salesforce is never really “finished”. Businesses evolve, priorities change and the platform itself introduces new functionality three times a year. What worked twelve months ago may no longer be the most efficient way of working today, which is why most organisations treat Salesforce as something that should be continually refined rather than left untouched after implementation.

That’s exactly what Salesforce optimisation is all about. It’s the ongoing process of reviewing how the platform supports the business, identifying opportunities to work more efficiently and making incremental improvements over time. The better Salesforce becomes, the more people rely on it, and the more ideas they have for making it even better. While that’s a positive position to be in, it also means your to-do list is unlikely to stop growing any time soon.

Why Being Busy Doesn’t Always Mean You’re Making Progress

One of the biggest challenges for Salesforce CRM Managers is that every request arrives with a sense of urgency. A reporting issue raised in this morning’s meeting suddenly feels like the highest priority. A new dashboard requested by Sales seems essential. Marketing would like another automation before their next campaign launches. Meanwhile, the larger improvement project that could benefit the entire organisation quietly slips further down the list.

Before long, the day becomes a series of reactive tasks. You’re constantly solving problems and supporting users, but it’s difficult to point to the work that’s genuinely moved the organisation forward.

Being busy isn’t the same as making progress. In fact, some of the busiest Salesforce teams struggle to make meaningful improvements because their time is consumed by whatever happens to land in their inbox next. Without clear priorities, it’s easy to spend weeks making small changes while larger opportunities to improve adoption, streamline processes or increase efficiency continue to wait.

Prioritisation Is More Important Than Productivity

The organisations that get the most from Salesforce aren’t necessarily the ones with the shortest to-do lists. More often, they’re the ones that have a consistent way of deciding what deserves attention first.

Instead of asking, Can we do this?, they ask a slightly different question:

Should we do this now?

That simple change in mindset shifts the conversation away from individual requests and towards business value. It becomes easier to explain why one improvement is being prioritised over another, and it helps ensure time is invested where it will make the biggest difference.

Of course, saying “not yet” isn’t always easy. Most CRM Managers enjoy helping colleagues and improving the platform, so there’s a natural temptation to say yes whenever someone has a good idea. The reality, however, is that every new request comes with an opportunity cost. Every hour spent creating another report or adding another field is an hour that can’t be invested in a project with greater strategic value.

Prioritisation isn’t about saying no. It’s about making sure the right work gets done at the right time.

When Capacity Becomes the Real Challenge

Even with a clear process for prioritising work, there often comes a point where the challenge is no longer deciding what should happen next but finding the capacity to deliver it.

Many organisations already know what they want to achieve. They’ve identified the projects that will improve user adoption, simplify business processes or enhance reporting. They simply don’t have enough internal resource to keep everything moving.

This is often where additional Salesforce support becomes valuable. Whether it’s specialist expertise for a complex project, ongoing Salesforce Managed Services or simply extra capacity during busy periods, the right support allows internal teams to continue focusing on strategic priorities while ensuring improvement work doesn’t stall.

The most successful organisations don’t wait until Salesforce becomes a problem before seeking help. They recognise that maintaining momentum is just as important as delivering the next major project, and that having access to experienced Salesforce consultants can help keep that momentum going.

Your Salesforce To-Do List Shouldn’t Be Empty

The reality is that your Salesforce to-do list will probably never disappear completely, and that’s not necessarily a bad thing.

As your organisation evolves, your CRM should evolve alongside it. New ideas will emerge, business priorities will shift and Salesforce will continue introducing new capabilities that create fresh opportunities to improve the way your teams work.

Success isn’t measured by reaching the bottom of the list. It’s measured by consistently working on the improvements that will deliver the greatest value to your organisation. The businesses that get the most from Salesforce aren’t the ones that say yes to every request. They’re the ones that know what deserves attention first.

Ready to make more progress with Salesforce?

If your improvement list is growing faster than your team can deliver it, our Salesforce Managed Services Overview explains how flexible support can help you prioritise, deliver and continuously improve your Salesforce environment, without adding pressure to your internal team.

Are You Measuring the Right Salesforce KPIs?

Posted on July 21, 2026 by - Uncategorized

What you’ll find in this blog

  • Why activity metrics don’t always demonstrate Salesforce success.
  • How to align Salesforce KPIs with wider business objectives.
  • Why reviewing reports and dashboards should be part of your ongoing Salesforce optimisation strategy.
  • How a Salesforce Health Check can help ensure you’re measuring what really matters.

Ask someone whether their Salesforce implementation has been successful and you’ll often hear the same responses.

“User adoption has improved.”

“We’ve automated several processes.”

“The sales team has access to more reports than ever before.”

They’re all positive developments, but are they really measures of success?

It’s an important question because Salesforce has evolved far beyond being a system for storing customer information. For many organisations, it now sits at the centre of sales, marketing, customer service and operations. If it’s supporting such a significant part of the business, measuring its success should involve more than counting users or dashboards.

The most successful organisations don’t just ask whether Salesforce is being used. They ask whether it’s helping the business perform better.

Activity Doesn’t Always Equal Value

One of the easiest traps to fall into is measuring activity instead of outcomes.

It’s understandable. Activity is easy to see.

You can report on the number of users logging in, how many dashboards have been created, how many records have been updated or how many automations have been built. Salesforce makes all of this information readily available.

The problem is that none of these metrics tell you whether they’re making a meaningful difference.

An automation that nobody trusts isn’t adding value.

A dashboard that’s never opened isn’t helping anyone make better decisions.

Even high user adoption can be misleading if people are using inefficient processes or entering inconsistent data simply because they have to.

Activity tells you what’s happening.

It doesn’t necessarily tell you whether it’s working.

Start With the Business, Not the Platform

The best Salesforce KPIs rarely begin with Salesforce itself.

Instead, they begin with a business objective.

Perhaps the organisation wants to reduce sales cycle times.

Maybe customer response times need to improve.

Perhaps leadership wants greater confidence in forecasting or better visibility across projects.

Salesforce should be supporting those outcomes, not becoming the outcome itself.

When you start with the business objective, it becomes much easier to decide what success looks like. Rather than celebrating the creation of a new dashboard, you can measure whether managers are making faster decisions. Instead of reporting on how many Flows have been built, you can look at whether manual effort has actually reduced.

The conversation shifts from features to outcomes, and that’s where Salesforce delivers its greatest value.

Are Your KPIs Still Relevant?

Another challenge many organisations face is that the metrics they introduced when Salesforce was implemented remain unchanged years later.

The business has grown.

Teams have changed.

New products have been launched.

Salesforce itself has evolved significantly.

Yet the same reports continue landing in inboxes every Monday morning because they’ve always been there.

It’s worth asking a simple question every so often:

“If we stopped producing this report tomorrow, would anyone notice?”

If the answer is no, it’s probably time to review what you’re measuring.

Regular optimisation isn’t just about introducing new functionality. It’s also about making sure the information you’re collecting and reporting on still reflects the needs of the business today.

Measuring the Things That Matter

Every organisation will have different priorities, but the strongest Salesforce KPIs usually have one thing in common.

They help people make better decisions.

That could mean improving forecast accuracy, increasing sales productivity, reducing administrative effort or giving leadership greater confidence in the data they’re using.

These are the measures that demonstrate business value, rather than simply showing how active the platform has been.

When Salesforce becomes a strategic business tool rather than just another application, the questions you ask naturally begin to change.

Instead of asking, “How many people logged in this week?”, you begin asking, “What difference did Salesforce make this week?”

Reviewing Success Should Be Part of Your Salesforce Roadmap

Just as businesses evolve, the way you measure success should evolve too.

Reviewing your Salesforce KPIs shouldn’t be something that’s only discussed during a major implementation or transformation project. It should form part of your ongoing Salesforce optimisation strategy.

Taking the time to regularly review your reports, dashboards, automations and business objectives helps ensure your platform continues to support the organisation as it grows. It also creates opportunities to remove unnecessary complexity, improve adoption and focus investment where it will have the greatest impact.

For many organisations, this type of review becomes much easier with an external perspective. A Salesforce Health Check can highlight where your current reporting, processes and KPIs are supporting the business well, as well as identifying opportunities to improve them.

Success Is About Business Outcomes

Salesforce doesn’t become successful because it contains more reports, more dashboards or more automation than it did last year.

It becomes successful when it helps people make better decisions, work more efficiently and achieve better business outcomes.

Those are the measures worth tracking.

Everything else is simply supporting evidence.

Ready to review your Salesforce KPIs?

If you’re not sure whether your reports, dashboards and automations are still supporting your business objectives, our Salesforce Health Check provides an independent review of your Salesforce environment, highlighting opportunities to improve performance, adoption and long-term value.

Why Salesforce Health Checks Shouldn’t Be an Annual Exercise

Posted on July 21, 2026 by - Uncategorized

What you’ll find in this blog:

  • Why waiting for an annual Salesforce health check can allow small issues to grow into bigger business challenges.
  • The key areas CRM Managers should review regularly to keep Salesforce secure, reliable and performing effectively.
  • How regular health checks create a stronger foundation for future projects, including AI, automation and integrations.
  • Practical advice on building a simple monthly review routine to keep your Salesforce environment aligned with your business needs.

For many organisations, Salesforce health checks are something that only happen when there’s a problem.

Perhaps user adoption has fallen, reports are no longer trusted, a new project is about to begin, or someone has raised concerns about data quality.

At that point, reviewing the health of the platform makes perfect sense.

But by then, the warning signs have often been there for months.

Like any business-critical system, Salesforce is constantly evolving. New users join, processes change, automation is introduced, reports are updated and new functionality is added with every release. None of these changes are inherently risky, but without regular review, small issues can gradually accumulate and begin to affect the way the platform performs.

That’s why we believe Salesforce health checks should become part of your regular CRM management routine, rather than something reserved for major projects.

Small issues rarely stay small

It’s easy to overlook something that doesn’t seem urgent.

An inactive user still holding unnecessary permissions.

A report that nobody has questioned for years.

A Flow generating occasional errors that haven’t yet impacted users.

Duplicate records that are increasing a little each month.

Individually, none of these are likely to bring your organisation to a halt.

Collectively, they can reduce confidence in Salesforce, create unnecessary risk and make future improvements far more difficult than they need to be.

Regular health checks help identify these issues while they’re still straightforward to resolve.

A healthier Salesforce is easier to improve

One of the biggest advantages of carrying out regular health checks is that they make future projects much simpler.

Whether you’re introducing AI, rolling out new automation, integrating another system or supporting business growth, it’s always easier to build on a platform that’s already well maintained.

Organisations often focus on adding new functionality, but maintaining the foundations is just as important. Clean data, well-managed users, reliable reporting and streamlined automation all contribute to a Salesforce environment that’s ready to support whatever comes next.

It doesn’t have to take hours

A health check doesn’t need to become a major exercise.

Many of the most valuable checks can be completed in less than thirty minutes each month.

Reviewing user access, monitoring automation, checking data quality and confirming reports are still relevant can quickly highlight opportunities for improvement before they become larger pieces of work.

The key is consistency.

Small, regular reviews are almost always more effective than waiting for an annual audit or a major project to uncover problems.

Building good habits

The most successful CRM Managers we work with all have one thing in common.

They don’t wait for Salesforce to tell them something is wrong.

They make regular reviews part of the way they manage the platform.

That proactive approach helps maintain user confidence, supports better decision-making and ensures Salesforce continues to evolve alongside the business rather than falling behind it.

Start with a simple monthly checklist

If you’re looking for an easy way to build this habit, we’ve created a free resource to help.

Download our guide: 10 Things Every Salesforce CRM Manager Should Check This Month

It’s a practical monthly checklist covering user access, data quality, automation, reporting, integrations and release readiness, helping you identify potential issues before they become bigger problems.