For service contractors running dispatch from a whiteboard and maintenance agreements from a spreadsheet, we build Salesforce around the service call, the agreement and the technician's phone.
An implementation for a commercial trades contractor usually starts with three records that everything else hangs on: the customer site, the equipment installed there, and the service agreement that says what you owe that site each quarter or season. With those modeled, the first release puts work orders, scheduling and a mobile app in front of dispatchers and technicians. Estimating, repair quoting and project work for installs follow in later releases. Each phase goes live on its own, so the office stops double-keying before the whole program is finished.
Service contractors carry obligations that most sales-first builds never model. A preventive maintenance contract promises visits, filter changes, inspections or treatments on a calendar, and missing one can void a warranty or fail a code inspection for the building owner. Customers are often property managers or facilities teams responsible for many buildings, each with its own access rules and contacts. Technicians hold licenses and certifications that decide who may take which job. Revenue arrives through agreement renewals, service calls, repair quotes and install projects at once, and each follows a different path. A trades implementation has to respect all four before it adds dashboards.
We model accounts, service locations and the assets at each location, such as rooftop units, boilers, fire panels, backflow devices or elevator controllers. Service agreements link to those assets and carry the visit schedule, coverage terms and renewal date. Maintenance plans then generate work orders automatically ahead of each due date. Dispatch sees upcoming obligations by territory rather than discovering a missed inspection when the building owner calls.
Field Service scheduling is configured around your territories, crews and skills, including licenses that restrict who can work on gas lines, fire systems or high-voltage gear. Multi-day installs and single-visit service calls live on the same console. In one manufacturer rollout we replaced calendar-based scheduling with a configured dispatch console and skills-based matching, and that pattern carries directly into trade contractors with mixed crews.
Technicians get a short mobile workflow for arriving, logging time and parts, capturing photos, collecting a signature and flagging follow-up repairs. Offline support matters in basements, mechanical rooms and rooftops with poor signal. A painting and construction contractor we worked with moved its crews from paper timesheets to Field Service mobile with annotated photos, which is the model we use for a first release.
Deficiencies found on a maintenance visit should become a quote the same week. We set up quoting in Revenue Cloud or CPQ with catalogs per division and pricing rules for labor and materials, so a technician's finding flows to an estimator and then to the customer for approval. Separate catalogs keep a plumbing division from quoting with electrical labor rates by mistake.
We begin with ride-alongs and dispatch-desk sessions, because the real process is visible there and rarely in written procedures. Service managers, dispatchers, a lead technician, an estimator and accounting join design sessions. The data model is built and tested in a sandbox with real sites and agreements before any configuration of screens. The first release covers agreements, work orders and mobile for one division or branch; others follow once that group trusts it. Cutover happens outside your busiest season, with the old schedule kept readable until dispatch confirms nothing was dropped.
Completed work orders, time and parts flow to invoicing and job costing, while payment status and customer credit holds come back so dispatch knows before sending a truck.
Larger install and retrofit bids may stay in a dedicated estimating tool; totals, versions and scope notes attach to the opportunity so the project team inherits what was sold.
Vehicle location can inform scheduling for urgent calls, with dispatch deciding how much location detail technicians and customers ever see.
Equipment records drive maintenance schedules, warranty tracking and repair history. If assets are skipped in the first design, agreements end up as text fields and nobody can report on what is installed where. Decide the level of detail per trade, since a fire sprinkler system and a single exhaust fan need different treatment.
Store technician licenses, expiry dates and trade certifications as data the scheduler can use. Local rules on who may perform fire, gas or electrical work vary, so confirm the requirements with your compliance lead rather than relying on a configuration default. Expiring credentials should alert a manager ahead of time.
An HVAC contractor should not cut over during the first heat wave, and a landscaping or snow services firm has its own crunch. Schedule go-live and training for the quieter stretch, and keep a fallback so dispatch can still work if a sync issue appears on day one.
Client names are anonymized.
Usually both, in a narrow slice. Agreements without dispatch create work orders nobody schedules, and dispatch without agreements leaves recurring visits tracked outside the system. We pick one branch or trade, load its active agreements and equipment, and switch its scheduling to Salesforce together. Expanding to other branches is then a data load and a training session rather than a redesign.
Often, yes. Contract laborers can be modeled as a custom resource record carrying their qualifications, so dispatch can plan around them without licensing every name. Whether that fits depends on what those workers must do in the app. Anyone who needs to update work orders from a phone needs a license; people who are only scheduled and tracked may not.
The technician flags the deficiency on the work order with photos and notes. That creates a quote request routed to the right estimator or service sales rep, who prices it with the catalog for that trade and sends it for approval. Approved quotes become new work orders. The customer site keeps the full history, so the next technician sees what was recommended and what was declined.
It depends on how calls arrive. If customers phone, email or submit requests through a portal, Service Cloud gives the call center cases, entitlements and routing before a job is dispatched. Contractors whose work comes almost entirely from scheduled maintenance and project installs can sometimes start with Field Service and Sales Cloud alone and add case management later.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.