ClickSoftware licence cost after the acquisition

Field service is one of the few Salesforce products priced almost entirely by who is in the van. The scheduling engine that ClickSoftware built is now part of Salesforce Field Service, and the rebrand record notes how the names moved: "Field Service Lightning, acquired from ClickSoftware in 2019, became Salesforce Field Service with the Winter ‘21 release." The product help adds the current name and a reassurance about the old one: "Field Service is now Agentforce Field Service and Operations. In some cases, we still use Field Service to refer to this product area in Salesforce applications and documentation." For licensing, the live name is Agentforce Field Service and Operations, and its price list is public.

#The listed licences

Salesforce publishes the pricing on its Field Service and Operations pricing page, which we read on 13 October 2026. The figures are per user per month, billed annually, and apply to Enterprise Edition. The page states the commitment: "All per user products require an annual contract."

The page adds a line that matters for budgets: Unlimited Edition versions of Dispatcher and Technician are US$330 per user per month and Field Service and Operations Plus is US$380. Which Salesforce edition your org sits on can change the seat cost by a large margin, so check it before you read any of the figures above.

#The rules that shape the count

Two requirements on the page decide how many of each licence you need, and they trip up first-time buyers.

The first is the Service Cloud requirement. The page is direct: "Field Service and Operations requires at least one (1) Service Cloud user license." For existing Service Cloud customers the requirement becomes at least one Dispatcher licence, and the Plus bundle can satisfy it because it includes the service user functionality. If you are starting from Sales Cloud alone, you need to price a Service Cloud seat as well.

The second is the Dispatcher dependency. Technicians, called Mobile Employees on the page, and Contractors require at least one Dispatcher in order to use the scheduling tool. A crew of forty technicians therefore needs, at a minimum, one Dispatcher, and in practice as many as your dispatch desk requires. The count that matters is how many people schedule work, not how many do it.

#Add-ons and what they cost

The page lists add-ons that most real deployments end up discussing.

Notice that Connected Assets is priced per org and is a very different order of cost from the per-user lines. A business with fifty technicians would pay a modest amount for Appointment Assistant and a very large one for Connected Assets, so the add-on that sounds minor is not always the one that moves the budget. Notice also that the top edition bundles Appointment Assistant and Visual Remote Assistant, so check what you are paying for twice.

#The contractor question

Contractor Plus is the only line with two prices, and the choice between them is a modelling exercise worth ten minutes. At US$80 per user per month or US$32 per login, the break-even sits at two and a half logins a month. If a contractor logs in twice, the login rate is cheaper at US$64. If they log in three times it is US$96, which is dearer than the monthly rate. The page does not define the period over which logins are counted, so ask whether a login is counted per month, per day or per session, because that definition decides whether the rate is a bargain or a trap.

The practical rule is that occasional overflow contractors, who appear a few times a year, suit the per-login rate, and regular subcontractors who work most weeks suit the monthly one. A blended crew may need both, and the contract should allow you to move a person between them.

#Sizing a crew

Right-sizing starts with a roster, not a headcount. List the people who schedule work, the people who do it on mobile, the contractors and the people who only need visibility. Each group maps to a different licence, or to none.

Count dispatchers against desk hours. Dispatcher and Technician list at the same price, so an unnecessary dispatcher costs as much as an unnecessary technician. A desk that runs nine to five does not need a licence per person if schedules are set by two people on shifts.

Check whether technicians need the full Technician licence or whether a lighter arrangement serves seasonal staff. The page offers Contractor Plus for non-employee users, which may be cheaper than a Technician seat for people who are not on payroll, but check the access it gives against the work they do.

Then test the bundle. Field Service Plus at US$230 combines Dispatcher, Technician, Service Cloud and Sales Cloud. If your dispatchers also need a Service Cloud seat, Plus is cheaper than buying the two separately at US$175 plus a Service Cloud licence, but only if you need all of the pieces. Compare the sum of the separate licences against the bundle for your real mix.

#A worked crew

An illustration helps, because the licence mix is easier to see with numbers. Take a crew of three dispatchers, thirty technicians and six regular contractors on Enterprise Edition. At list, the dispatchers cost 3 times US$175, or US$525 a month. The technicians cost 30 times US$175, or US$5,250. Six contractors on the monthly rate cost 6 times US$80, or US$480. The monthly total is US$6,255, which is US$75,060 a year, before the Service Cloud licence the page requires and before any add-on or support plan.

Now change one assumption. If the same three dispatchers took Field Service Plus at US$230 so that they also hold Service Cloud and Sales Cloud, the dispatcher line rises to US$690 a month, a difference of US$165. That is cheaper than buying Service Cloud seats separately, but only if the dispatchers need both clouds. And if the org is on Unlimited Edition, the dispatcher and technician lines alone become 33 times US$330, or US$10,890 a month, which is US$130,680 a year. The edition under the licence is the biggest single variable in the model.

#The top edition against building it up

Agentforce 1 Field Service at US$650 is described as everything in Plus and the full suite of AI, with unlimited Agentforce usage for employees, Appointment Assistant, Visual Remote Assistant, Slack and Tableau Next, and 1M Flex Credits and 2.5M Data Cloud credits per org each year. You can test it against a build-up from the listed prices. Plus at US$230, the Agentforce add-on at US$125, Appointment Assistant at US$25 and Visual Remote Assistant at US$50 total US$430 per user per month. The top edition therefore costs US$220 more per user than those four pieces, and what that buys is the credit allowances, the unlimited usage and the Slack and Tableau entitlements. If you will use the credits, the bundle is sound value. If you will not, the build-up is cheaper. Ask what you can do with the credits before you pay for them.

#Reading an older order form

Orders placed before the rename may still use the previous product names, and the rebrand record notes that Field Service Lightning became Salesforce Field Service with the Winter '21 release. The names are labels. The entitlement is whatever the order lists: which licence types, how many of each, on which edition, for what term. At renewal, ask for a mapping from each line on your old order to a line on the current price list, and check that none has been dropped or split in a way that raises the total.

#Contract and true-up mechanics

The page says every per-user product needs an annual contract, which sets the baseline. Ask the questions below before you sign.

How are additional users added mid-term, at what price and from what date? A pilot that grows quickly can end up with a staircase of co-termed add-ons, so ask for a fixed rate for the term.

What is the renewal uplift cap, and does it apply to each licence type?

Does the Flex Credits allowance in the top edition roll over, and what is the price of extra credits? The page quotes 1M Flex Credits and 2.5M Data Cloud credits per org each year, and the Data Cloud product has since been renamed Data 360.

How are support plans priced? The pages show Standard as included, Premier as a stated share of net licence fees and Signature through your account executive. Premier scales with licence value, so a seat change moves it.

#Seasonal crews and mixed workforces

Field businesses rarely run a flat headcount. A utility doubles its crews after a storm, an installer hires through the summer, and a facilities contractor brings in specialists for a single job. The licence structure rewards you for knowing which of those people are permanent and which are not.

For permanent employees, the monthly Technician licence is the baseline, and the annual contract means you pay for the seat whether or not the person works every day. For people who work for you part of the year, ask whether seats can be added on a short co-term and removed at anniversary, and whether a seat that is removed can be added back at the same price. For genuinely external workers, Contractor Plus exists so that you do not buy a full employee seat for someone who is not on your payroll.

The risk to watch is quiet creep. A contractor who was added for a project and never removed keeps being billed, and a technician who moved to the office keeps a mobile seat. Put a quarterly licence review in the calendar, because the annual contract means an error found in month eleven has already cost you eleven months.

#Comparing offers

An offer from a reseller and one from Salesforce can look alike and differ in the underlying edition. Write down the Salesforce edition, the licence mix, the seat counts, the add-ons, the term, the uplift and the support plan. Convert both to annual cost for your crew and compare.

Be careful with one comparison in particular. If you are weighing Field Service against a second scheduling product, remember that a rename does not require you to buy anything. The field product Salesforce acquired from ClickSoftware is already what runs as Field Service, and the product help confirms that the older name is still used in places for the same product area. A different scheduler is a separate purchase with its own licence, integration and training costs, and has nothing to do with the acquisition.

#Where the other questions sit

The licence is what you pay Salesforce. The cost of configuring service territories, skills, scheduling policies and mobile flows is covered in the ClickSoftware implementation cost guide. The acquisition is in what happened to ClickSoftware. How schedules connect to other records is in integrating ClickSoftware with Salesforce, whether to move is in should I migrate from ClickSoftware, and the delivery view is on the ClickSoftware implementation page.