Salesforce Field Service Review 2026: Pricing, Pros, Cons, Alternatives

What you're buying with Salesforce Field Service, and what the demo skips

Salesforce Field Service earns its money with Field organizations running 50 or more dispatched technicians on commercial service and maintenance contracts, where the customer and asset records already live in Salesforce and there is an admin or implementation partner on payroll to configure the platform. If that's you, it does the job. The sections below are the parts worth checking before you sign. But the fit is narrower than the marketing suggests, and the price isn't the whole cost.

It starts at $175/month. And pricing was verified on 7 August 2026, so you can check every figure below in a browser tab.

The shops Salesforce Field Service fits, and the ones it doesn't

It fits Field organizations running 50 or more dispatched technicians on commercial service and maintenance contracts, where the customer and asset records already live in Salesforce and there is an admin or implementation partner on payroll to configure the platform. That's the half most reviews print. Here's the other half, which is the one worth your time.

Don't buy it if you're An owner-operator or a two-to-eight-truck residential service company with no full-time admin. The entry configuration is a Service Cloud seat plus a Dispatcher seat plus a Technician seat per truck, all on an annual contract with no refunds and no mid-term reductions, and the platform still needs configuring before it dispatches a job. So a five-truck shop is looking at a four-figure monthly licence bill plus an implementation partner, against competitors that publish a working per-company price under $200 a month. Look at Jobber instead.

Don't buy it if you're A company that wants to be running next week. This is a platform build, not a signup. One reviewer was told three months and was still without a dispatchable work order after eighteen. And another says the implementation partner you choose is the deciding factor. So there's no self-serve path from credit card to first dispatched job. Look at Housecall Pro instead.

Don't buy it if you're A seasonal trade that doubles crew size in summer and halves it in winter. MSA section 5.1 forbids decreasing quantities during the subscription term and section 11.2 re-prices the whole renewal at list if volume drops. So the pricing model punishes exactly the headcount pattern that roofing, landscaping and pool work run on. Look at Service Fusion instead.

Don't buy it if you're A contractor whose accounting system is the centre of gravity. Salesforce ships no native accounting sync, and the MSA explicitly disclaims warranty and support for the third-party AppExchange connectors that provide it. So if QuickBooks is where your business lives, you're buying a second vendor relationship to bridge the gap. Look at Knowify instead.

What you'll pay Salesforce Field Service in year one

Salesforce Field Service prints its numbers on its own site. Good. That means you can price your real configuration tonight instead of waiting on a rep.

Every seat is a named per-user license, and the licenses stack rather than substitute. The pricing page footnote states verbatim: "All per user products require an annual contract. Above pricing available on Enterprise Edition. Unlimited Edition versions of Dispatcher and Technician are $330/user/month and Field Service Plus is $380. ** Monthly logins-based Contractor and Contractor+ licenses available. Please contact a sales representative for detailed pricing information. NOTE: Field Service requires at least one (1) Service Cloud user license. Existing Service Cloud customers require at least one (1) Dispatcher license. This requirement can also be met with the Field Service Plus bundle, as it includes the service user functionality. Existing customers can purchase as many Technician (Mobile Employee) user licenses as needed. Field Service Technicians (Mobile Employees) and Contractors require at least one (1) Dispatcher in order to use the scheduling tool." A ten-technician shop therefore buys ten Technician seats, at least one Dispatcher seat, and at least one Service Cloud seat before anything is configured.

There is a discount for paying annually up front: And an annual prepay discount tells you an annual commitment exists, which is worth knowing before anyone mentions a term length out loud.

The Salesforce Field Service costs that show up later

Payment processing. The Technician tier is advertised as being able to "Create quotes and collect payment in the field", but the pricing page publishes no card-processing rate, no per-transaction fee and no named processor. So ask the sales representative which payment product processes the card, what the per-transaction rate and per-transaction fixed fee are, whether that rate is contractually fixed for the term, and whether the processor is a Salesforce product or a third-party AppExchange gateway you have to contract with separately.

Implementation and onboarding. The pricing page publishes no implementation or onboarding figure. It points to Professional Services and to Salesforce Certified Partners without a rate card. So ask for a fixed-scope statement of work with a named go-live date, a written list of what is in scope versus change-order, and the hourly or day rate of the implementation partner. And one Capterra reviewer wrote that they were told the build would take 3 months and were still paying 18 months later for a system that couldn't dispatch a work order, so get the timeline in the contract rather than the pitch deck.

Minimum term. One year minimum. The pricing page footnote states "All per user products require an annual contract." The Main Services Agreement section 11.2 adds that "The term of each subscription shall be as specified in the applicable Order Form", so the actual committed term is whatever the Order Form says and multi-year Order Forms are common at this price point.

Getting out. There is no early exit for convenience. Main Services Agreement section 5.1 states verbatim: "Customer will pay all fees specified in Order Forms. Except as otherwise specified herein or in an Order Form, (i) fees are based on Services subscriptions purchased and not actual usage, (ii) payment obligations are non-cancelable and fees paid are non-refundable, and (iii) quantities purchased cannot be decreased during the relevant subscription term." Section 11.3 allows termination only for cause, "upon 30 days written notice to the other party of a material breach if such breach remains uncured at the expiration of such period", or on the other party's insolvency. Section 11.4 confirms that if Salesforce terminates for your breach, "Customer will pay any unpaid fees covering the remainder of the term of all Order Forms."

Auto-renewal. It auto-renews annually on 30 days' notice, and shrinking triggers a re-price. Main Services Agreement section 11.2 states verbatim: "Except as otherwise specified in an Order Form, subscriptions will automatically renew for additional one year terms, unless either party gives the other written notice (email acceptable) at least 30 days before the end of the relevant subscription term. Except as expressly provided in the applicable Order Form, renewal of promotional or one-time priced subscriptions will be at SFDC's applicable list price in effect at the time of the applicable renewal. Notwithstanding anything to the contrary, any renewal in which subscription volume or subscription length for any Services has decreased from the prior term will result in re-pricing at renewal without regard to the prior term's per-unit pricing."

Modules sold separately. , , , , , , , . But the entry tier is not the price you'll pay. Add the modules your shop needs on day one and compare Salesforce Field Service on that total.

Third-party services you will also pay for. . These are not on Salesforce Field Service's invoice, and they are still part of what this decision costs you every month.

The Salesforce Field Service line items nobody mentions

The subscription is the part everyone quotes. These are the lines that land afterwards, and the ones we could not find are named as unpublished rather than left blank.

Sold separately. , , , , , , , . Price the configuration you'll really run, because an add-on you need on day one is part of the price.

Third-party services you'll also pay for. . None of these are on Salesforce Field Service's invoice, and all of them are part of what this decision costs every month.

The five workflows you pay for

Feature totals are noise. So a shop in this category lives or dies on five things, and those are the five to grade, and each one below carries the evidence it's graded on.

Skills-and-inventory-aware assignment in a dedicated dispatch console, gated behind a $175 Dispatcher seat The Dispatcher licence buys an intelligent dispatch console built into the CRM, with what the vendor calls AI-powered scheduling and route optimization, real-time visibility into field operations, and intelligent job assignment and reallocation. Reviewers who use it well describe the assignment logic favourably. But reviewers also report the console itself loading slowly or crashing. And nothing that isn't a Dispatcher seat can use the scheduling tool at all. A sales engineer, information technology and services, 6-12 months on the platform, writing on 2025-03-05, reports it: "Very intelligent & efficience task distribution system based on availability, skills, inventory, location, etc."A QA & environmental manager, pharmaceuticals, 1-2 years on the platform, writing on 2023-06-24, reports it: "I have had quite a few issues with the loading of the dispatch console. The pop up appears but takes a very long time to load or crashes (connection checked and ok). Customising the system is difficult without in depth training."

Offline-first by design, but the offline promise is undercut by stability complaints The Technician licence covers viewing and updating work orders offline, creating quotes and collecting payment in the field, and building custom mobile experiences with Lightning Web Components. The App Store listing carries a 4.6 rating across roughly 20,000 ratings, so the median experience is good. But the written reviews that exist skew hard toward crash loops, glitchy maps and excessive tap depth, and the same complaint appears independently on Capterra in English and German. On 2025-07-15, a field technician (app user) says: "Besides the horrible design, even the things that work well don't always work. The map feature crashes and glitches. The app freezes and crashes. Probably once a week I have to delete and redownload the app because it gets stuck in a crash loop."On 2025-02-17, a global tech support, machinery, 1-2 years on the platform, says: "Stürzt ständig ab und ist wohl in der Bedienung die mit Abstand schlechteste App, die ich je gesehen habe. Völlig überlagerte und unübersichtliche Menu-Führung"

A genuine per-login subcontractor licence, which almost nothing else in the category offers Contractor at $55 per user per month or $22 per login, and Contractor Plus at $80 per user per month or $32 per login, give external crews secure mobile app access, assigned work orders and job updates, with Contractor Plus adding cross-sell and upsell and performance tracking. And the login-based option is the interesting one for trades that use subs seasonally, because it stops an idle sub from costing a full seat. But the pricing page routes login-based pricing to a sales representative rather than publishing terms.

Van inventory decremented from the field and multi-visit work orders billed as one job Asset management and product tracking is included on every tier per the feature comparison table. And a reviewing CEO describes updating inventory as it's consumed in the field while tracking and billing work orders that span multiple site visits and multi-step solutions. But deeper install-base and service-campaign capability sits in the Asset Service Lifecycle Management add-on at $75 per user per month. But a CEO, hospital & health care, Less than 6 months on the platform, puts it it differently: "Field service allows us to update our inventory as it is used in the field, while also allowing us to track and bill for work orders with multiple site visits, and/or complicated multi-step solutions. Additionally, it allows us to visually track the schedules of more technicians while allowing us to set standards for our management team as it relates to fulfillment and billing."

A hard 30-day export window after termination, then deletion The MSA gives you 30 days from the effective date of termination or expiration to request your data for export or download. And after that window Salesforce has no obligation to maintain or provide it, and will delete or destroy all copies. So that's a shorter runway than it sounds when a migration to a replacement FSM is itself a multi-month project.

How Salesforce Field Service lands by trade

Where your data goes when it leaves Salesforce Field Service

QuickBooks Online and QuickBooks Desktop (via DBSync, third-party AppExchange listing) connects both ways, on every plan. QuickBooks (via Breadwinner, third-party AppExchange listing) connects both ways, on every plan. Your costs map through cost codes, so test yours against your own chart of accounts before you commit. A code your books don't recognise is how a labour charge quietly lands somewhere useless.

Past those, the road ends. Native QuickBooks or Xero sync from Salesforce itself, A countable integration directory, A published payment-processing rate do not connect. So if your books run on an ERP rather than the platforms named above, weigh that before anything else.

Beyond accounting it connects to Service Cloud (Not an integration but a prerequisite. At least one Service Cloud user licence must exist before Field Service can be purchased, and the Field Service Plus bundle exists specifically to satisfy that requirement in one seat.), Sales Cloud (Bundled into the Field Service Plus tier, which combines Dispatcher, Technician, Service Cloud and Sales Cloud into a single $230 per user per month seat.), Slack and Tableau Next (Included only in the Agentforce 1 Field Service tier at $650 per user per month. Tableau Next is listed as "Available for Purchase" on the lower tiers.), Data Cloud (Listed in the feature comparison table and bundled with 2.5M Data Cloud Credits per org per year on the Agentforce 1 Field Service tier.), AppExchange (The marketplace of third-party apps that interoperate with Salesforce, named and defined in the MSA. Salesforce does not warrant or support anything on it unless an Order Form says otherwise.). A public API exists: Salesforce publishes full developer documentation and API references for the platform, and the MSA contemplates customer-built and third-party applications interoperating with the Services. The Field Service pricing page's feature comparison table does not list API access as a separate line item on any tier, so API entitlement follows the underlying Salesforce edition rather than the Field Service licence. Mobile extensibility is explicitly offered through Lightning Web Components, which the product page describes as offline-capable.

Getting help from Salesforce Field Service, and getting it fast

What happens when you want to leave Salesforce Field Service

Nobody reads this section before they buy, and it's the one that costs money afterwards. Four terms decide what leaving looks like.

Minimum term. One year minimum. The pricing page footnote states "All per user products require an annual contract." The Main Services Agreement section 11.2 adds that "The term of each subscription shall be as specified in the applicable Order Form", so the actual committed term is whatever the Order Form says and multi-year Order Forms are common at this price point.

Auto-renewal. It auto-renews annually on 30 days' notice, and shrinking triggers a re-price. Main Services Agreement section 11.2 states verbatim: "Except as otherwise specified in an Order Form, subscriptions will automatically renew for additional one year terms, unless either party gives the other written notice (email acceptable) at least 30 days before the end of the relevant subscription term. Except as expressly provided in the applicable Order Form, renewal of promotional or one-time priced subscriptions will be at SFDC's applicable list price in effect at the time of the applicable renewal. Notwithstanding anything to the contrary, any renewal in which subscription volume or subscription length for any Services has decreased from the prior term will result in re-pricing at renewal without regard to the prior term's per-unit pricing."

Early termination. There is no early exit for convenience. Main Services Agreement section 5.1 states verbatim: "Customer will pay all fees specified in Order Forms. Except as otherwise specified herein or in an Order Form, (i) fees are based on Services subscriptions purchased and not actual usage, (ii) payment obligations are non-cancelable and fees paid are non-refundable, and (iii) quantities purchased cannot be decreased during the relevant subscription term." Section 11.3 allows termination only for cause, "upon 30 days written notice to the other party of a material breach if such breach remains uncured at the expiration of such period", or on the other party's insolvency. Section 11.4 confirms that if Salesforce terminates for your breach, "Customer will pay any unpaid fees covering the remainder of the term of all Order Forms."

Payment processing. The Technician tier is advertised as being able to "Create quotes and collect payment in the field", but the pricing page publishes no card-processing rate, no per-transaction fee and no named processor. So ask the sales representative which payment product processes the card, what the per-transaction rate and per-transaction fixed fee are, whether that rate is contractually fixed for the term, and whether the processor is a Salesforce product or a third-party AppExchange gateway you have to contract with separately.

Salesforce Field Service, from the people who bought it

Salesforce Field Service and the alternatives, side by side

The realistic alternatives, and what each costs to start. Cheaper doesn't win here, and neither does expensive. Fit does.

Microsoft Dynamics 365 Field Service. Publishing a lower per-seat enterprise price with no separate mandatory CRM seat stacked underneath it, and offering a cheaper external-technician seat at $50.00 per user/month. Resource Scheduling Optimization is a defined $30.00 per resource/month add-on rather than a credit-metered agent. But Living inside the Microsoft stack rather than the Salesforce one, which is the wrong answer if your customer and asset records are already in Salesforce. And it carries the same enterprise implementation burden.

ServiceTitan. Being purpose-built for residential and commercial home-services trades rather than generic field work, which directly answers the reviewer complaint that Salesforce Field Service out of the box is "extremely generic" with "little to know industry specific aspects". But Publishing nothing. Its pricing page shows three tiers, Starter, Essentials and The Works, each behind a Request Pricing button, so you can't compare it against a Salesforce quote without going through sales twice.

Service Fusion. Charging per company instead of per seat, with unlimited users. And for a 15-technician crew the arithmetic isn't close: $208 a month total versus 15 Technician seats at $175 each plus a Dispatcher plus a Service Cloud seat. But Depth. It has no asset lifecycle management, no AI scheduling optimization, no offline-first LWC extensibility, and no path into a CRM that the rest of a large enterprise already runs on.

Jobber. Getting a small residential crew running the same week without an implementation partner, at a price a five-truck shop can clear. And every plan price is published with the included user count. But Enterprise scheduling optimization, asset and install-base management, subcontractor login licensing, and anything requiring a real platform layer underneath. It isn't a Salesforce replacement for a 200-technician operation.

Housecall Pro. Self-serve signup with a 14-day free trial and a published upgrade path, which is the exact opposite of a mandatory annual Order Form with non-refundable fees. But Enterprise asset tracking, multi-visit work order complexity, contractor login licensing and integration into a company-wide CRM. And its top published tier costs less than two Salesforce Technician seats.

BuildOps. Focusing specifically on commercial contractors with service and project work in one system, a narrower and better-fitted target than a general-purpose platform. But Transparency. Its pricing page carries no dollar figure of any kind, only a request form.

Who should not buy Salesforce Field Service

Don't buy Salesforce Field Service if you're An owner-operator or a two-to-eight-truck residential service company with no full-time admin. The entry configuration is a Service Cloud seat plus a Dispatcher seat plus a Technician seat per truck, all on an annual contract with no refunds and no mid-term reductions, and the platform still needs configuring before it dispatches a job. So a five-truck shop is looking at a four-figure monthly licence bill plus an implementation partner, against competitors that publish a working per-company price under $200 a month. Look at Jobber instead.

Don't buy Salesforce Field Service if you're A company that wants to be running next week. This is a platform build, not a signup. One reviewer was told three months and was still without a dispatchable work order after eighteen. And another says the implementation partner you choose is the deciding factor. So there's no self-serve path from credit card to first dispatched job. Look at Housecall Pro instead.

Don't buy Salesforce Field Service if you're A seasonal trade that doubles crew size in summer and halves it in winter. MSA section 5.1 forbids decreasing quantities during the subscription term and section 11.2 re-prices the whole renewal at list if volume drops. So the pricing model punishes exactly the headcount pattern that roofing, landscaping and pool work run on. Look at Service Fusion instead.

Don't buy Salesforce Field Service if you're A contractor whose accounting system is the centre of gravity. Salesforce ships no native accounting sync, and the MSA explicitly disclaims warranty and support for the third-party AppExchange connectors that provide it. So if QuickBooks is where your business lives, you're buying a second vendor relationship to bridge the gap. Look at Knowify instead.

The verdict, by shop size

Owner-operator to 8 trucks, residential service

No. The licence stack alone puts this well past a thousand dollars a month before any implementation cost, on an annual contract with non-refundable fees and no mid-term seat reduction, to run work that Jobber or Housecall Pro handle from a published price under $200 a month with a free trial. And there's no version of this arithmetic that favours Salesforce at this size. This band runs 1 to 8 on the crew, doing residential and service work, and that's the profile the recommendation is written for.

9 to 30 technicians, mixed residential and commercial service

No. This is the band where the platform premium is most expensive and least justified. Twenty Technician seats plus a Dispatcher plus Service Cloud is a five-figure annual licence bill before an implementation partner, and reviewers at this scale report the out-of-the-box configuration being too generic for trade-specific work. So a purpose-built FSM covers the workflow for a fraction of the total. But the only exception is a company already running Salesforce as its company-wide CRM, in which case see the conditional band below. This band runs 9 to 30 on the crew, doing residential and commercial and service work, and that's the profile the recommendation is written for.

Any size, already running Salesforce as the company CRM

Only under conditions, and they are worth being honest about. Yes if you already carry Service Cloud seats, have a Salesforce admin on payroll, and the alternative is a second system with a data bridge between it and your customer records. But no if the field team is more than a small fraction of headcount and the deciding factor is technician daily experience, because the mobile complaints are consistent and the technician seat is the most expensive one you buy. So pilot the app on real devices in real buildings before committing. This band runs 15 or more on the crew, doing commercial and service work, and that's the profile the recommendation is written for.

50+ dispatched technicians, commercial contracts, asset-heavy install base

Yes, and this is the shape the product is built for. This is what the product is built for. At this scale you have the admin capacity, the negotiating leverage to get real discount off a $175 list seat, the multi-visit and asset-lifecycle complexity that justifies the platform, and enough subcontractor volume for the per-login Contractor licence to earn its place. So budget the Premier Success Plan at 30% of net licence fees and a partner-led implementation as real line items, not optional extras. This band runs 50 or more on the crew, doing commercial and service work, and that's the profile the recommendation is written for.

Seasonal trades with large summer-to-winter headcount swings

No. The contract mechanics are actively hostile to this pattern. MSA section 5.1 forbids decreasing quantities during the subscription term, so you pay peak headcount for twelve months, and section 11.2 re-prices the entire renewal at list if volume drops. So a seasonal roofing or landscaping company shouldn't sign a per-seat annual contract with those two clauses in it. This band runs undefined or more on the crew, doing residential and commercial work, and that's the profile the recommendation is written for.

What we read on Salesforce Field Service, and what we couldn't get to

Worth saying plainly: this is desk research on Salesforce Field Service, not a season in the field with it. And what stands behind it is documentary: 11 vendor pages read on 7 August 2026, and a review corpus sorted by what went wrong. And every figure above traces to a page we opened on that date, pricing included.

So: 18 quotes on this page, 15 from Capterra and three from Apple App Store.

And help.salesforce.com (every article URL returns a JavaScript shell reading "Salesforce Help Loading ... Sorry to interrupt CSS Error Refresh" with no article body, via both WebFetch and a browser-UA curl; the data-export and account-closure articles could not be read, so the MSA was used as the primary source for both), appexchange.salesforce.com category and search pages (JavaScript-rendered; the Field Service category page returns 142,731 bytes containing only the page title and no listing markup, so no integration count could be obtained), www.capterra.com via direct curl (403 Forbidden; WebFetch succeeded), www.getjobber.com/pricing/ via direct curl (403 Forbidden; WebFetch succeeded), G2 (not fetched, blocks automated access), TrustRadius (not fetched, blocks automated access), Trustpilot (not fetched, blocks automated access) and Reddit (not fetched, blocks automated access) refused automated retrieval for Salesforce Field Service. Forum and social threads are the ones people most want quoted, and they are exactly the ones we cannot verify, so none of them are here.

What that leaves untested: google Play listing for the Field Service app (the package id com.salesforce.fieldservice.app returned a truncated page with no review content; the correct package id was not confirmed, so no Play Store figure is asserted). And everything above is eleven vendor pages and a review corpus, which is documentary rather than hands-on.