The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Dreamforce 2025 was not centered on one new CRM feature. Salesforce used its flagship event to reposition Agentforce as the center of its platform strategy, connecting AI agents with CRM applications, Data 360, Slack and enterprise workflows.
The event took place on October 14–16, 2025, in San Francisco and online through Salesforce+. It is now a completed event, so its importance lies in what the announcements mean for Salesforce customers: more capable AI agents, deeper data and collaboration integration, and a more complicated mix of user-based and consumption-based pricing.
Dreamforce 2025 at a glance
| Item | Details |
|---|---|
| Dates | October 14–16, 2025 |
| Location | San Francisco, with online access through Salesforce+ |
| Main strategic launch | Agentforce 360 |
| Core theme | Salesforce’s “Agentic Enterprise” strategy |
| Most important commercial change | A broader combination of seats, actions, conversations, data usage and edition fees |
Salesforce describes Dreamforce as its major customer, developer, partner and product event. In 2025, the emphasis shifted from individual CRM clouds to a connected platform for deploying and governing AI agents.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What is Agentforce 360?
Salesforce announced Agentforce 360 as the platform connecting its CRM applications, AI agents, Data 360, Slack, automation and enterprise controls.
#1 Best Overall
Salesforce calls the resulting operating model the Agentic Enterprise: people and software agents working together across business processes. That phrase is Salesforce’s strategic framing, not an independently established industry category. The practical meaning is clearer: AI is being embedded into sales, service, marketing, employee support and other Salesforce workflows rather than offered only as a separate chatbot.
Agentforce 360 is therefore better understood as a platform strategy than as a single product. Successful deployments still depend on accurate data, appropriate permissions, reliable actions, testing, monitoring and human escalation.
The biggest product announcements
1. A redesigned Agentforce Builder and Agent Script
Salesforce introduced a more conversational Agentforce Builder for creating agents. Admins and business users can describe the intended behavior in natural language, while the simulator is designed to help test responses and inspect agent behavior.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteSalesforce also highlighted Agent Script and a combination of deterministic logic with AI reasoning. This is important because natural-language instructions alone are not enough for sensitive workflows. An agent may need strict rules for refunds, approvals, eligibility, record updates or escalation.
The benefit is a lower barrier to starting an agent. The trade-off is that conversational setup can make an agent appear production-ready before its data, permissions and business rules have been validated. Administrators still need test cases, version control, auditability and a rollback plan. See Salesforce’s Dreamforce announcements for admins for the product-level context.
2. Agentforce Voice
Agentforce Voice extended Salesforce’s AI-agent ambitions to voice-based customer service and contact-center scenarios. Voice agents can potentially answer questions, perform actions and transfer callers to employees.
However, voice introduces requirements that do not exist in the same form for text agents:
- Call routing and authentication
- Transcription accuracy and latency
- Recording, retention and regional compliance
- Reliable human handoff with conversation context
- Clear handling of interruptions and ambiguous requests
A successful keynote demonstration does not prove that a voice agent is ready for every production contact center. Teams should pilot it against representative call types and measure containment, transfer quality, latency, customer satisfaction and cost.
3. Agentforce Vibes
Agentforce Vibes was presented as an AI-assisted development tool for creating Salesforce applications and components from natural-language descriptions. Salesforce emphasized organizational metadata, its Trust Layer and enterprise governance.
The “vibe coding” label describes the interaction style, not a guarantee of secure or production-quality software. Developers still need code review, automated tests, permission analysis, dependency checks, deployment controls and rollback procedures.
The Salesforce-native advantage is context about metadata and platform conventions. The possible downside is greater dependence on the Salesforce ecosystem. Salesforce also highlighted MCP servers, unified catalog capabilities and semantic data models in its developer material. Product availability may differ by edition, region and release stage, so teams should verify the current documentation before planning deployment. Relevant material is available in Salesforce’s platform recap.
4. Slack as the conversational interface
Slack received a more strategic role in Salesforce’s AI story. Salesforce and Slack presented it as a conversational way for employees to access Salesforce data, applications and agents.
Examples included experiences for Agentforce Sales, IT Service, HR Service and Tableau. The appeal is straightforward: employees already work in conversations, channels and notifications. The risk is that Slack becomes another place where AI-generated information appears without improving the underlying process.
Organizations should ask whether the work is already performed in Slack, whether channel membership matches Salesforce permissions, and whether employees know which system is authoritative. Salesforce and Slack’s announcements are covered in the Slack-native AI overview.
5. Data 360 as the context layer
Agentforce’s usefulness depends on more than a language model. Agents need access to current records, authoritative knowledge, business definitions, policies and external information—and they must access those sources under the correct permissions.
Recommended Free Tools
Salesforce presented Data 360 as the foundation for that contextual information. Poor data quality can undermine an otherwise capable agent through obsolete knowledge, duplicate records, missing customer history or inconsistent definitions between departments.
Data 360 can also affect the business case. Salesforce’s Agentforce pricing page warns that examples may exclude Data 360 credits and other consumption services.
Customer and industry examples
Salesforce’s Dreamforce materials highlighted FedEx, Dell, PepsiCo, Pandora, Goodyear, CaixaBank, Williams-Sonoma, F1 and Nexo. The examples covered customer service, commerce, industry workflows, data unification and AI-assisted operations.
These are useful illustrations of possible applications, but they are customer stories selected and presented by Salesforce—not neutral ROI benchmarks. A responsible evaluation should ask:
- What specific business problem was addressed?
- Which Salesforce products, integrations and services were involved?
- Was the reported result independently verified?
- Did the outcome depend on data cleanup, custom development or consulting support?
- Can the same result be measured in your organization?
Customer success stories should guide use-case discovery, not substitute for a business case.
Dreamforce 2025 pricing: what changed?
Salesforce’s commercial model became more complex because Agentforce can combine user licenses, conversations, Flex Credits, Data 360 usage, CRM editions, integrations and implementation work.
| Pricing item | Public signal on Salesforce’s current pricing page |
|---|---|
| Salesforce Foundations | No-cost entry point with selected capabilities |
| Flex Credits | $500 per 100,000 credits |
| Conversations | $2 per conversation |
| Agentforce User License | $5 per user per month, requiring Flex Credits |
| Agentforce 1 Editions | From $550 per user per month |
Salesforce’s help documentation says a standard Agentforce action consumes 20 Flex Credits. At the listed rate, that works out to $0.10 per action. The same documentation indicates that Agentforce Voice actions consume 30 Flex Credits. These are derived list-price examples, not a universal invoice rate: geography, contract terms, edition, billing basis and other usage can change the result.
Salesforce also announced in 2025 that specified Enterprise and Unlimited list prices would rise by an average of 6% from August 1, 2025. The announcement listed Slack Business+ at $15 per user per month and said Salesforce Channels would be available across Slack plans, including the free plan. Check the pricing announcement and current commercial documentation before budgeting.
Two ways to model the cost
Consumption model: Costs rise with agent actions or conversations. This may be attractive for a small pilot but becomes harder to forecast when usage is unpredictable.
Best Value
License-plus-consumption model: User licenses or a larger edition are combined with Flex Credits, conversations and possible data usage. This can offer a clearer entitlement structure, but it does not necessarily mean unlimited usage.
A free entry point is not the same as a free production deployment. CRM licenses, Data 360, integrations, implementation, governance and support can all affect total cost. Salesforce’s AI usage guidance also explains that billing can depend on the pricing model, environment, interaction type and lifecycle phase, including certain preview or testing activity.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What Salesforce customers should do next
- Choose one measurable use case. Start with a repetitive, high-volume process such as service triage, internal support or knowledge retrieval.
- Set a baseline. Record resolution time, handle time, containment, conversion, cost per interaction and customer or employee satisfaction before deployment.
- Audit the data. Check record completeness, duplicate accounts, knowledge freshness, external synchronization and semantic definitions.
- Design permissions and escalation. Decide what the agent may read, what it may change, when approval is required and how a human takes over.
- Estimate usage. Model conversations, actions, voice interactions, testing and peak demand rather than relying on a single sample price.
- Test realistic scenarios. Include incomplete records, conflicting knowledge, unauthorized requests, unusual language and failed integrations.
- Review the contract. Confirm edition availability, regional terms, consumption rules, Data 360 charges and renewal implications with Salesforce.
Who should adopt—and who should wait?
Agentforce 360 is most promising for organizations already standardized on Salesforce, with mature workflows, clean data, high-volume service or support processes and the ability to measure outcomes.
Free tools Windows power users keep installed
One-click scans. No signup required.
Waiting is sensible when data quality is poor, no team owns AI governance, the process is highly regulated without an approved control framework, or transaction volume is too low to justify consumption costs. Organizations seeking a vendor-neutral architecture should also compare Salesforce-native automation with broader platforms before committing.
Agentforce versus other approaches
| Approach | Best fit | Main trade-off |
|---|---|---|
| Salesforce Agentforce | Salesforce-centric CRM and service workflows | Native context and permissions, but greater platform dependence and pricing complexity |
| General-purpose AI copilots | Cross-application productivity and knowledge work | Broader reach, but potentially more integration and permission engineering |
| Traditional automation | Stable, rules-based processes | Predictable behavior, but less flexible for natural-language requests |
Microsoft Copilot, ServiceNow AI, Google Cloud Vertex AI and enterprise assistants such as Claude may be better fits in organizations centered on Microsoft, ServiceNow, Google Cloud or general knowledge work. They are not direct feature-for-feature or price comparisons; the correct choice depends on existing systems, data ownership, workflow requirements and governance.
Final assessment
Dreamforce 2025 mattered because Salesforce attempted to make Agentforce, CRM, Data 360 and Slack parts of one operating model. The opportunity is substantial, especially for Salesforce customers with clean data and repeatable workflows.
The harder truth is that an agent is not ready merely because it can be created through a conversational builder. Production value depends on data quality, permissions, deterministic controls, testing, escalation, change management and realistic usage modeling. For most organizations, the right response to Dreamforce 2025 is not to buy every new capability, but to select one measurable workflow and prove that the economics and controls work.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
