# ClickSoftware implementation cost: Field Service licences, add-ons and services ClickSoftware's scheduling technology lives on in Salesforce Field Service, sold per user from US$175 a month. The licence choices, the work an implementation involves, and the costs quotes miss. **Published:** 2025-12-15 **Canonical:** https://synconai.com/clicksoftware-salesforce-implementation-cost **Author:** SynconAI Architecture Team ## In short ClickSoftware's technology lives on in Salesforce Field Service, now marketed as Field Service and Operations. As at October 2026 Dispatcher and Technician list at US$175 per user per month (AU$245), Field Service Plus at US$230, and Contractor Plus at US$80 per user per month or US$32 per login, on Enterprise Edition, billed annually. Implementation is quoted separately. ## Sources - **The ultimate guide to Salesforce product rebrands** (retrieved 2026-10-10) https://gearset.com/blog/salesforce-product-rebrands/ > Field Service Lightning, acquired from ClickSoftware in 2019, became Salesforce Field Service with the Winter ‘21 release. - **Field Service** (retrieved 2026-10-10) https://help.salesforce.com/s/articleView?id=service.fs_overview.htm&type=5 > 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. - **Field Service and Operations Pricing** (retrieved 2026-10-11) https://www.salesforce.com/service/field-service-management/pricing/ > Field Service and Operations requires at least one (1) Service Cloud user license. ## What to take away - Field Service is priced per user: Dispatcher and Technician US$175, Field Service Plus US$230, Agentforce 1 Field Service US$650 per user per month on Enterprise Edition, billed annually, as at October 2026. - It needs at least one Service Cloud user licence, and Unlimited Edition prices are higher: US$330 for Dispatcher and Technician and US$380 for Field Service Plus. - The services quote is set by territories, work types and skills, scheduling policies and optimisation, the offline mobile app, inventory, and ERP and asset integrations. - Quotes often miss add-ons such as Appointment Assistant, devices and mobile device management, address cleanup, technician training time and scheduling tuning after go-live. ## The guide ClickSoftware built its name on scheduling: putting the right engineer, with the right skills and parts, at the right door at the right time. Salesforce bought the company in 2019 and folded that capability into its own field service product, which was called Field Service Lightning before it was renamed Field Service with the Winter '21 release. The name has moved again since. Salesforce's own help now says: "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." Whatever the label on the invoice, a ClickSoftware implementation in 2026 means a Salesforce Field Service implementation, and the cost has two parts: per-user licences that Salesforce publishes, and a services project shaped by how your field operation actually works. ## What Field Service costs, as at October 2026 Salesforce publishes Field Service prices on its [Field Service and Operations pricing page](https://www.salesforce.com/service/field-service-management/pricing/). The figures below were read on 11 October 2026. A footnote on the page says that all per user products require an annual contract and that the prices shown are for Enterprise Edition. | Licence | US list price | Australian list price | Who it is for | | --- | --- | --- | --- | | Dispatcher | US$175 per user per month | AU$245 per user per month | Schedulers working in the dispatch console | | Technician | US$175 per user per month | AU$245 per user per month | Mobile employees using the Field Service mobile app | | Contractor Plus | US$80 per user per month or US$32 per login | AU$112 per user per month or AU$47 per login | External contractors through a portal and mobile access | | Field Service Plus | US$230 per user per month | AU$322 per user per month | Dispatcher and Technician combined with Service Cloud and Sales Cloud | | Agentforce 1 Field Service | US$650 per user per month | AU$910 per user per month | The full suite, with Salesforce's AI features included | The page also lists add-ons, in US dollars: Agentforce for Field Service and Operations at US$125 per user per month, Asset Service Lifecycle Management at US$75, Visual Remote Assistant at US$50 and Appointment Assistant at US$25, all per user per month, and Connected Assets at US$15,000 per org per month. Two footnotes matter for budgeting. The first is the edition: Unlimited Edition versions of Dispatcher and Technician are US$330 per user per month, and Field Service Plus is US$380. If your org runs Unlimited Edition, the Enterprise prices in the table do not apply. The second is the prerequisite. The page states: "Field Service and Operations requires at least one (1) Service Cloud user license." It adds that existing Service Cloud customers need at least one Dispatcher licence, a requirement that Field Service Plus also meets because it includes service user functionality. A rough frame helps. An operation with five dispatchers and sixty technicians on Enterprise Edition is sixty-five users at US$175, or US$11,375 a month at list. That is US$136,500 a year before add-ons, the Service Cloud licence and any negotiation. The same headcount on Unlimited Edition is more than US$257,000 a year at list. The edition you already run matters as much as the headcount. ## Choosing the licence mix The licence mix is where many field service budgets are won or lost, and it is worth working through role by role before any services quote arrives. Dispatchers and schedulers need Dispatcher. Employed technicians who use the mobile app need Technician. Supervisors who both schedule and occasionally go into the field may be better on Field Service Plus, which also brings Service Cloud and Sales Cloud functionality, useful if the same people log cases or raise quotes. Contractors are the interesting case: Contractor Plus can be bought per user per month or per login, and the right choice depends on how often each contractor works for you. A subcontractor who does three jobs a year is a very different cost from one who works for you every day. The page notes that monthly login-based Contractor and Contractor Plus licences are available through a sales representative. Agentforce 1 Field Service at US$650 per user per month is a different proposition. It bundles Salesforce's AI features into the licence, and the comparison table lists 1M Flex Credits and 2.5M Data Cloud (now Data 360) credits per org every year. Whether it is worth it depends on whether you have specific uses ready, such as summarising job history for technicians or drafting service reports, and the data quality to support them. Price it as an option, not a default. ## If you still run ClickSoftware outside Salesforce Some organisations still run ClickSoftware's standalone scheduling products rather than Salesforce Field Service. For them, the project is not an upgrade. It is a migration of scheduling logic from one engine to another, and it should be scoped and priced that way. Confirm the support position of your current product in your own contract rather than relying on dates you read elsewhere. The concepts map, but not one to one. Click resources become Service Resources. Skills, calendars and working hours become Skills, Operating Hours and Resource Absences. Regions become Service Territories. Job types become Work Types with durations and required skills. Scheduling objectives and rules become Scheduling Policies, with work rules and service objectives weighted against each other. Each mapping is a design decision, and the weightings in particular need testing against real days of work before anyone trusts the new schedule. ## What drives the implementation cost **Territories and resources.** The number of service territories, how they overlap, and how many resources sit in each. A national operation with shared technicians across regions is far more complex than a single metro team. **Work types, skills and durations.** Every work type needs a duration, required skills and often required parts. Organisations with hundreds of job codes spend real time rationalising them before they can be configured. **Scheduling policies and optimisation.** This is the heart of a Field Service project and the closest thing to ClickSoftware's original value. Choosing between rules and objectives, setting priorities, deciding when to optimise the whole day and when to fix individual appointments, and tuning the enhanced scheduling and optimisation engine all take iteration. Expect several rounds of tuning with real data and experienced dispatchers in the room. **The mobile app.** Technicians work offline in basements, plant rooms and rural sites. The app must have the right records on the device before the technician loses signal, which means designing what is downloaded, how much, and how conflicts are resolved when the device reconnects. Custom flows on the mobile app, service reports and signature capture add to the build. **Inventory and parts.** Product Items, Product Requests and Product Transfers for van stock, plus the link to the warehouse or ERP that owns parts. If technicians carry stock, this can be a project of its own. **Assets and maintenance.** Preventive maintenance plans, asset hierarchies and service contracts. Asset Service Lifecycle Management is an add-on and widens the scope. **Integrations.** ERP for parts, pricing and invoicing, a geographic information system or mapping service for addresses, telematics for vehicle location, and sometimes an HR or payroll system for timesheets. Each is its own work package. **Customer communication.** Appointment booking, arrival notifications and real-time tracking for customers. Appointment Assistant is the Salesforce add-on for this, priced separately. ## Phasing the rollout to control cost Field Service projects that try to do everything at once tend to overrun, because scheduling, mobile, inventory, assets and customer communication each carry their own risks, and a problem in one delays all the others. A phased plan spreads both the services cost and the licence ramp, and it gives the operation time to absorb each change. A common first phase puts work orders, dispatch and the mobile app in place for one region, with simple scheduling rules and no inventory. Dispatchers learn the console, technicians learn the app, and the business sees whether jobs are being completed and closed properly. Only Dispatcher and Technician licences for that region are needed at this stage, which keeps the early licence bill in proportion to the value being delivered. A second phase turns on optimisation in earnest, with policies tuned against the first region's real data, and rolls out to further regions. A third adds van stock and parts, preventive maintenance and asset hierarchies. Customer-facing features such as appointment booking and arrival tracking often come last, once the schedule itself is reliable enough to promise customers a time. Phasing has a cost of its own. Each phase needs testing, training and cutover, and some integration work is done twice if the first phase uses a temporary interface. Ask bidders to price both a single rollout and a phased one, and to explain the difference. The phased option is often slightly dearer in total services, and noticeably cheaper in risk. It also helps with licence timing. Salesforce contracts are annual, so buying every technician licence on day one of a twelve-month rollout means paying for months of unused seats. Agree a licence ramp with your account executive that follows the regions as they go live. ## The work packages in a comparable quote Discovery should include ride-alongs with technicians and time in the dispatch room, not just workshops. A field service design built only from interviews with managers misses how work really happens. Design covers the data model, territories, work types, scheduling policies, mobile app experience, inventory model and integration architecture. Build covers configuration, scheduling policies, mobile flows, service report templates, inventory and integrations. Data migration covers customers, locations with clean addresses and geocodes, assets, service contracts, open work orders and future appointments. Address quality matters more here than in almost any other Salesforce product, because scheduling depends on travel time. Testing must include optimisation runs on real historical days, compared with what actually happened, and mobile testing in poor-signal conditions on the devices technicians will carry. Training splits by role. Dispatchers need deep training on the console and policies. Technicians need short, practical training on the app, ideally in small groups so the operation keeps running. Cutover is usually by region or territory, with hypercare that includes someone who understands scheduling, not just someone who can fix a page layout. ## Hidden costs and the questions to ask **The Service Cloud prerequisite.** If you do not already have Service Cloud, you need at least one licence. **Edition.** Check whether your org is Enterprise or Unlimited Edition before using any list price. **Add-ons.** Appointment Assistant, Visual Remote Assistant, Asset Service Lifecycle Management, Connected Assets and the Agentforce add-on are all priced separately. **Devices and mobile device management.** Phones or tablets, rugged cases, data plans and a mobile device management tool rarely appear in a Salesforce quote. **Address and location cleanup.** Geocoding and correcting customer addresses is often a significant piece of work before scheduling can be trusted. **A Full Copy sandbox.** Testing optimisation against real volumes needs realistic data. **Technician time off the road.** Training sixty technicians is sixty people not doing paid jobs for a day. Budget it. **Scheduling tuning after go-live.** Policies always need adjusting once real days run through them. Ask whether the quote includes a tuning period. **Support.** Premier Success is priced as a share of net licence fees. When you request proposals, send every bidder the same facts: users by role, territories, work types, average jobs per day, contractor model, inventory scope, integrations, devices, and your current scheduling rules. Ask each to state how many optimisation tuning cycles are included, how mobile offline will be tested, which add-ons they assume, and whether address cleanup is theirs or yours. ## Where to go next Licence and renewal questions are on [the ClickSoftware licence cost page](/clicksoftware-salesforce-licence-cost). The acquisition story is on [what happened to ClickSoftware](/what-happened-to-clicksoftware), and the product today is described on [the Field Service page](/clicksoftware-field-service). For choosing a firm, read [who to hire for ClickSoftware](/hire-clicksoftware-salesforce-partner). For ERP, mapping and telematics links, see [integrating ClickSoftware with Salesforce](/integrating-clicksoftware-with-salesforce), and if you are weighing a move off a standalone Click product, [should I migrate from ClickSoftware](/should-i-migrate-from-clicksoftware) covers the decision. Our [Field Service](/salesforce-field-service) page explains how we run these projects. ## Questions ### How much does Salesforce Field Service cost per user as at October 2026? On Enterprise Edition, billed annually, Dispatcher and Technician are US$175 per user per month (AU$245), Field Service Plus is US$230, Agentforce 1 Field Service is US$650, and Contractor Plus is US$80 per user per month or US$32 per login. ### Do we need Service Cloud to buy Field Service? Yes. The pricing page says Field Service and Operations requires at least one Service Cloud user licence, and that existing Service Cloud customers need at least one Dispatcher licence. Field Service Plus meets the requirement because it includes service user functionality. ### Are Unlimited Edition prices different? Yes. The pricing page footnote lists Unlimited Edition versions of Dispatcher and Technician at US$330 per user per month and Field Service Plus at US$380. Check which edition your org runs before building a budget from list prices. ### How is moving from a standalone ClickSoftware product different? It is a migration of scheduling logic, not an upgrade. Click resources, skills, calendars, regions and scheduling objectives must be redesigned as Service Resources, Skills, Operating Hours, Service Territories, Work Types and Scheduling Policies, then tuned against real days of work. ### What do Field Service proposals usually leave out? Add-ons such as Appointment Assistant and Visual Remote Assistant, devices and mobile device management, address cleanup and geocoding, a Full Copy sandbox, technician time off the road for training, scheduling tuning after go-live, and Premier Success. --- SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Field Service (https://synconai.com/salesforce-field-service).