Salesforce Field Service Just Got Renamed Again — What “Field Service and Operations” Actually Means for Your Org

You’re three calls into evaluating Salesforce Field Service for your operation, and every source seems to call it something different. Salesforce’s own product page now says “Field Service and Operations.” A review site you were reading an hour earlier lists it as “Agentforce Field Service (formerly Salesforce Field Service).” Your AE mentioned it as just “Field Service” the whole call. Salesforce Field Service just got renamed again, and if you’re trying to figure out whether that means a new product, a new price, or a new decision to make, this post walks through exactly what changed and what didn’t.

1. Yes, This Is a Real Rename — Not a New Product

The confusion is legitimate, because this is genuinely the third name this product has carried. It launched as Field Service Lightning, dropped “Lightning” to become simply Field Service, and has now picked up “and Operations” in Salesforce’s own materials while review platforms independently settled on “Agentforce Field Service.” Specifically, none of these renames changed what you’re buying: the same Work Order, Service Appointment, and Service Resource data model underneath, the same scheduling engine, the same mobile app. This is confusing, but it’s a marketing decision, not a product migration.

2. A Short History: From Field Service Lightning to Agentforce Field Service

Tracking the naming history matters because it tells you how to read older documentation, case studies, and job postings that still use the earlier names. A five-year-old implementation guide referencing “Field Service Lightning” is describing the same underlying product you’d be evaluating today under a newer name, not a deprecated predecessor.

3. What Actually Changed Under the Hood

The rename does coincide with real product movement, which is likely why Salesforce chose this moment to fold it into the Agentforce brand. The platform has expanded its predictive intelligence, including automated scheduling suggestions that weigh technician skills, travel time, and parts availability, along with predictive maintenance alerts flagging equipment likely to fail before a customer calls. Consequently, the branding shift tracks a real shift in emphasis from reactive dispatch toward proactive, AI-assisted service. However, this expanded intelligence sits on top of the existing scheduling engine rather than replacing it, so an org already live on Field Service isn’t starting over to take advantage of it.

4. What Didn’t Change: Licensing and Pricing

This is the part that actually matters for a budget conversation, and it’s the part most likely to get lost in the naming confusion. Field Service is still an add-on product, purchased separately from standard Service Cloud licenses, not bundled in automatically under any of its names. Pricing still varies by the features and access level different user types need, the same structure it’s always had. Notably, none of the public naming changes reference a new SKU, a new pricing tier, or a licensing migration path, which means a rename alone is not a reason to expect your renewal quote to change.

5. What This Means If You’re Evaluating Field Service Right Now

If you’re mid-evaluation, treat the naming as noise and focus your due diligence on the same questions that mattered before the rebrand: your technician count, your scheduling complexity, and whether the built-in mobile app’s offline reliability holds up in your actual coverage areas. This is exactly the kind of vendor-terminology confusion that eats time in an evaluation if nobody untangles it early, and it’s a five-minute conversation in an org review rather than something worth stalling a decision over. Whichever name your AE, your renewal paperwork, or a review site uses, confirm you’re scoping the same underlying product before comparing quotes or timelines across vendors.

Frequently Asked Questions

Do I need to re-license or repurchase anything because of this rename?

No. The rename doesn’t introduce a new SKU or require a licensing migration. If you’re already licensed for Field Service under any of its earlier names, your existing licenses continue to work the same way under the new branding.

Is Agentforce required to use Field Service now?

No. Field Service is positioned as part of the broader Agentforce brand ecosystem, but Agentforce itself is not a required dependency to use the core Field Service product. The predictive scheduling and maintenance features layer on top of the existing product rather than gating access to it.

Why does G2 call it something different than Salesforce’s own site?

Review platforms and vendors don’t always update product listings on the same timeline. Salesforce’s own FAQ currently uses “Field Service and Operations,” while G2’s listing uses “Agentforce Field Service (formerly Salesforce Field Service).” Both refer to the same product; the discrepancy is a branding lag between sources, not two different offerings.

How do I find out which version or name applies to my org?

Check Setup and search for “Field Service” to see the feature and licensing labels your org currently uses, since Salesforce doesn’t always rename every internal Setup reference the moment a marketing page changes. If you’re unsure whether what you’re licensed for matches what a vendor conversation is describing, a quick org review can confirm exactly what you have versus what’s being pitched.

Should this rename change my evaluation timeline?

No, it shouldn’t. Since the rename didn’t change pricing, licensing, or the core data model, there’s no reason to pause or restart an evaluation already in progress. Treat the new name as a label update and keep evaluating based on your actual scheduling complexity, technician count, and mobile requirements.