Dreamforce 2024: Agentforce and the Future of CRMA Dashboards
Dreamforce just wrapped, and we're still processing what we heard and saw over the last three days in San Francisco. Like a lot of years, there's a gap between the keynote energy and what actually matters to practitioners who spend their days building datasets, lenses, and dashboards in CRM Analytics. This year that gap feels smaller than usual — not because the announcements were incremental, but because the direction they're pointing has real structural implications for how we think about CRMA as a platform.
The headline is Agentforce. Let's talk about what it actually is, what we think it means, and where we're genuinely uncertain.
What Agentforce Actually Is
Strip away the stage lighting and the demos, and here's what was announced: Agentforce is Salesforce's AI agent platform. It's not a single product or a new cloud — it's a framework for building autonomous agents that can reason, take actions, and operate with varying degrees of human oversight.
The three components that matter most for our purposes are:
The Atlas reasoning engine. This is the underlying capability that allows agents to move beyond single-shot prompt-and-response interactions. Atlas is described as the reasoning layer that lets agents plan across multiple steps, evaluate intermediate results, and adjust their approach. From an analytics standpoint, this is interesting because it suggests agents aren't just retrieving answers — they're doing something closer to structured analysis.
Agent actions. This is how agents actually do things. Actions are the connective tissue between reasoning and outcomes. They can invoke flows, call APIs, query data, and interact with Salesforce records. The action framework is what makes Agentforce more than a chatbot with a fancy name.
The agent platform itself. The deployment, monitoring, and configuration layer. This matters operationally because it implies some level of governance infrastructure around what agents can do and when.
What wasn't fully clear from the announcements — and we've been in enough of these to know that clarity often comes three to six months later — is exactly how CRMA surfaces and datasets plug into this architecture as first-class citizens versus as data sources that agents can query incidentally.
Why This Changes the Dashboard Conversation
Here's the uncomfortable truth we've been sitting with since the keynote: the traditional CRMA dashboard is a passive artifact. Someone builds it, someone opens it, someone reads it. The intelligence lives in the human who interprets the numbers and decides what to do next. That has always been the ceiling of the medium, and it's a ceiling most of our clients have accepted without thinking much about it.
Agentforce, if it develops the way the architecture suggests it will, starts to dissolve that ceiling.
Consider what a typical CRMA dashboard does well: it aggregates data, applies filters, surfaces trends, and presents comparisons. A sales performance dashboard might show pipeline coverage by region, conversion rates by stage, and rep-level attainment. A good analyst can look at that and say, "Pipeline in the Northeast is thin for Q4, and the stage 2 to stage 3 conversion rate dropped eight points last quarter — someone should look at qualification criteria." Then they write that up and send an email, or they tag someone in Slack, or it comes up in a meeting.
That entire chain — observe, interpret, recommend, act — is what Agentforce is designed to compress or partially automate. An agent with access to the same CRMA datasets, equipped with the Atlas reasoning engine, could theoretically traverse that chain continuously without waiting for a human to open a browser tab.
We're not saying dashboards are dead. We've been in this industry long enough to remember when people said dashboards were dead because of natural language querying, and before that because of mobile BI, and before that because of self-service analytics. Dashboards are resilient. But their role is shifting, and Dreamforce 2024 is probably the moment we'll look back on as when that shift became unavoidable to plan around.
What We're Rethinking in Our CRMA Practice
After three days of sessions, hallway conversations, and admittedly too much coffee, here's what we're bringing back to our team.
Datasets as Agent Inputs, Not Just Dashboard Sources
We've always talked about dataset design in terms of what a dashboard needs — grain, cardinality, join strategy, incremental refresh windows. We're now starting to think about dataset design in terms of what an agent needs, which is somewhat different.
Agents need data that is labeled clearly and consistently, because they're interpreting field names and values in ways that a human designer might never have intended. A field called Opportunity_Score__c with values 1, 2, and 3 is legible to a human who has context. It may not be legible to an agent without additional metadata or documentation baked into the dataset schema.
We also need to think about freshness differently. A human analyst checks a dashboard when they decide to. An agent might be reasoning against a dataset at any time, potentially flagging outdated information as a meaningful signal when it's actually just a refresh lag. Dataset documentation and metadata management — which most orgs treat as optional — starts to look like a reliability requirement when agents are in the loop.
The Complexity of Agent Actions Against CRMA
This is where we want to be honest about uncertainty. The action framework in Agentforce is powerful, but the specifics of how agents query and interact with CRMA data — versus how they interact with standard Salesforce objects — weren't fully spelled out in the announcements. There's a meaningful difference between an agent that can read a CRMA dataset and an agent that can construct a meaningful analytical query against it, interpret the results in context, and take action downstream.
We've seen plenty of AI integrations that are technically capable of querying a data source but fail in practice because the query logic doesn't map to how the data was actually structured. That problem doesn't go away with a better reasoning engine. If anything, a more autonomous agent that fails quietly is worse than a chatbot that returns a bad answer and makes the failure visible.
We're planning to be conservative here in near-term engagements — treating CRMA datasets as carefully documented inputs to agents rather than assuming agents can navigate them reliably without significant prompt engineering and testing.
Rethinking What "Done" Means for a Dashboard
This one is cultural as much as technical. A lot of our implementation work ends with a dashboard handoff. The client has what they need to see; our job is done. That model is going to change.
If an Agentforce agent is going to act on CRMA insights, the dashboard is no longer the end product — it's an intermediate layer in a decision loop that includes agent reasoning and agent actions. That means our scope for a CRMA engagement potentially extends into how the agent is configured, what actions are available to it, what guardrails are in place, and how human oversight is maintained.
This is actually good for practices like ours, but it's a significant change in how we scope and price work. We're starting to think about it now rather than waiting for clients to ask.
The Governance Questions Nobody Is Talking About Yet
Every Dreamforce has an announcement layer and a consequences layer. The announcement layer is loud. The consequences layer takes longer to surface.
For Agentforce, the consequences layer that we're most focused on involves governance. When a human reads a CRMA dashboard and makes a decision, there's a clear accountability chain. When an agent reads CRMA data and takes an action — updates a record, triggers a flow, sends a communication — the accountability chain is murkier.
Who is responsible when an agent acts on stale data? What happens when an agent's reasoning leads to an action that contradicts a business rule that was implicit in how a human would have interpreted the same numbers? These aren't hypothetical edge cases for enterprise organizations with complex data environments — they're predictable failure modes.
We've done enough implementations to know that data quality issues which are tolerable in a dashboard context — where a human reviewer can recognize an anomaly and discount it — can become serious operational problems when an agent acts on them autonomously. The Atlas reasoning engine may improve an agent's ability to catch some of these, but it doesn't eliminate the underlying data quality requirement.
Our current thinking is that any CRMA-to-agent integration should start with read-only agent actions and significant logging, with human confirmation required before agents can take write actions. This is probably more conservative than what Salesforce will demonstrate in their reference architectures, but it reflects what we think is appropriate for most enterprise environments in the early stages of adoption.
What We're Actually Excited About
We've spent a lot of words on uncertainty and caution, which is probably appropriate given that Agentforce was announced two days ago. But we want to be clear that we're genuinely excited about where this is going.
The analytics problems we've never been fully able to solve with dashboards are precisely the ones that an agent-driven approach handles better. Proactive alerting that goes beyond static thresholds. Analysis that adapts to context rather than waiting for a user to change a filter. Recommendations that are grounded in data but expressed in operational terms that a businessperson can act on immediately.
CRMA has always had strong capabilities around data integration and complex aggregation. Those capabilities are more valuable, not less, in an Agentforce world — but they need to be packaged differently. The work we've done on clean dataset architecture and consistent data models is exactly the foundation that makes agent integration tractable.
We're also watching the action framework carefully because it's where CRMA's position in the Salesforce ecosystem becomes an advantage. Data that lives in CRM Analytics can stay close to the processes and records it describes. Agents that reason in that same environment have a shorter path from insight to action than any cross-platform integration we've tried to build.
Our Near-Term Posture
For clients who are asking what they should do right now, our answer is pretty simple: don't rebuild your CRMA architecture for Agentforce yet, but start auditing it as if you might.
Specifically:
- Document your dataset schemas with agent-legible labels and descriptions, not just human-legible ones
- Review your data quality processes with an eye toward what happens if an agent acts on a bad value
- Have a conversation about governance and oversight before you get an executive who wants to deploy an agent against your pipeline data in Q1
The Agentforce platform is real and the direction is clear. But we've seen enough enterprise AI rollouts to know that the organizations that benefit most are the ones that get their data foundations right first. Dreamforce set the direction. Now the actual work starts.
Our practice has completed over 300 CRM Analytics implementations across enterprise clients. Observations and opinions in this article reflect our team's experience and our interpretation of Dreamforce 2024 announcements as of September 19, 2024. Platform capabilities and availability may evolve as Agentforce reaches general availability.