Commercial trades contractors use Salesforce to run the service side of the business: maintenance agreements, dispatch, technician close-out on a phone, change orders and the reports that show whether service work makes money. It works best when agreements, assets and work orders share one customer record. Accounting keeps ownership of the ledger.
Which parts of a trades business belong in Salesforce?
Put the customer, the building, the equipment, the agreement and the work in Salesforce. Keep general ledger, payroll and final invoicing in your accounting system.
Picture a mechanical contractor with several hundred maintenance customers. Each may have several buildings, dozens of rooftop units and a contact who approves repairs. Every visit adds findings, photos and parts used. That history is what sells the next repair and the renewal.
Salesforce handles that relationship data well. It is weaker as a costing ledger, and forcing it into that role causes most of the pain we see in trades orgs.
| Record | Usually owned by | Why |
|---|---|---|
| Customer, sites and contacts | Salesforce | Sales, service and field staff all read and update it |
| Installed equipment and warranty dates | Salesforce, as assets | Drives maintenance visits, repair quotes and replacement conversations |
| Service agreements and visit schedules | Salesforce | Generates future work and supports renewal pipeline |
| Quotes and change orders | Salesforce | Tied to the opportunity or work order that caused them |
| Parts stock by van and warehouse | Salesforce or ERP, pick one | Two systems counting stock never agree |
| Actual job cost, payroll, invoices | Accounting or ERP | Audited figures belong in the system of financial record |
| Margin by job and customer | Reported in Salesforce, calculated from accounting data | Leaders want it next to pipeline and service history |
Our separate guides cover Field Service setup in depth. This article focuses on the decisions specific to commercial trades.
How do we turn service agreements into predictable recurring revenue?
Model each agreement as a record linked to the customer, the covered sites and the covered equipment. Let the agreement generate visits automatically instead of relying on a dispatcher's calendar.
In Salesforce Field Service, service contracts and maintenance plans can create future work orders on a set frequency. The plan knows which assets it covers and which work type each visit uses. A quarterly coil cleaning becomes four scheduled jobs, not four reminders.
- Agreement tiers: define what each tier includes, such as visit count, labor discounts or response commitments.
- Covered assets: link the actual units, panels or fixtures, so a technician sees what is and is not covered.
- Renewal opportunities: create them automatically ahead of the end date and assign them to the account owner.
- Missed visits: report agreements where a promised visit has no completed work order.
The last item matters most. A customer who paid for four inspections and received three will not renew. Catching that gap early is cheap.
How should quoting and change orders work while crews are on the job?
Quote repeatable work from a guided product catalog, and treat a change order as its own quote linked to the original job. The customer should approve it before the crew starts the extra work.
Trades firms lose margin on small approved-by-phone changes that never reach an invoice. A structured change order fixes that. The technician or foreman describes the added scope, prices it from the same catalog and captures a signature. The approved amount then updates the job budget.
A multi-division painting, drywall, construction and mold-remediation firm we worked with shows why catalogs need care. Each division kept its own products and pricing in Salesforce CPQ. A painting estimator never scrolled through remediation line items, and pricing rules stayed specific to each trade.
Deficiencies found during inspections follow the same path. The finding is recorded against the asset, becomes a repair quote, and turns into a follow-up work order once approved. That loop is often the largest untapped revenue in a service division.
What does dispatch and scheduling need for commercial jobs?
Dispatch needs accurate work types, skills, territories and multi-day appointments. Without them, the schedule board ends up back in Outlook or a whiteboard.
A packaging-automation manufacturer we supported is a useful comparison, even though it is not a contractor. Its dispatchers had managed technician calendars in Outlook because the scheduler was installed but never configured. We set up 37 work types with skill matching and territories aligned to time zones. Service appointments were then created from work orders and assigned a territory by address.
Trades firms have extra wrinkles. Journeyman and apprentice pairings, license requirements by state and after-hours emergency rotation all affect who can take a job. Capture those as skills or crew rules early, because retrofitting them later means reworking the schedule logic.
Long jobs need their own attention. Another partner's build had left an industrial-services firm with unusable scheduling. We added bidirectional sync between work orders and service appointments, ending duplicate entry for dispatchers.
Will technicians actually use the mobile app, including without signal?
They will if screens are short and the app works offline. Mechanical rooms, basements and rooftops often have no coverage, so offline behavior has to be tested, not assumed.
The painting and construction firm started from paper timesheets and no way to log materials or photos from the field. Moving crews to the Field Service mobile app removed the paper and gave managers real-time visibility into job costs. They also received budget alerts when costs ran ahead of the estimate.
- Limit each close-out screen to the fields someone will use later.
- Pre-fill account, site and asset from the work order.
- Require a photo only where it prevents a dispute.
- Test sync with a real technician in a real dead zone before rollout.
How much parts and inventory tracking should we start with?
Start with the parts that are expensive, frequently returned or need tracking by serial number. Tracking every fitting and wire nut rarely pays back.
A scent-marketing manufacturer running field service across more than 40 divisions had techs who could pick stock from any territory. We applied territory-based sharing so each technician saw and consumed only their assigned inventory. A single transfer flow handled moves between territories and returns of defective stock to a quality warehouse.
That company validated the design against its ERP before a piloted rollout. Decide whether Salesforce or the ERP holds the stock count, then make the other system read from it.
Who owns job costing, Salesforce or the accounting system?
Accounting owns actual cost. Salesforce owns the estimate, approved changes and field-captured time and materials, and shows margin by pulling actuals back from accounting.
Field entries in Salesforce are early signals. The accounting system posts the final numbers after payroll burden, overhead and vendor invoices land.
- Estimate and approved change orders: captured in Salesforce.
- Labor hours and materials from the field: captured on the work order, then sent to payroll and accounting.
- Posted actual cost and invoice totals: sent back to Salesforce on a schedule.
- Margin reporting: calculated in Salesforce from those returned figures, never retyped.
Agree on job and cost code numbering first. If the work order and the accounting job use different identifiers, every sync becomes a matching exercise.
How do we handle subcontractors and contract labor?
Decide per group whether they need to log in or only need to be assigned and tracked. That decision drives license cost more than any other.
Salesforce offers license types aimed at contractors and partner users. Confirm current options and pricing with your Salesforce account team. For workers who never open the app, a custom object can be enough.
The industrial-services firm tracked roughly 75 to 100 external laborers and their certifications on a custom Labor Resource object, without a Field Service license each. We also rebuilt its task-creation flows to use variables rather than hard-coded assignments. The old flows had been firing 30 emails at once.
Do commercial customers need a portal?
A portal helps when customers ask the same questions repeatedly: when is my next visit, what did you find, and where is my quote. It is rarely a phase-one requirement.
Salesforce Experience Cloud can give property managers and facility directors access to their sites, open work orders, inspection reports and quotes awaiting approval. Licensing is per member or per login, so check the model with your account team before promising portal access to every customer contact.
Which reports tell us whether service is healthy?
Track first-time fix rate, open backlog by age and gross margin by job type and customer. Add agreement coverage and renewal rate once the service contract data is reliable.
- First-time fix rate: completed jobs that needed no return visit. Define what counts as a return before you build the report.
- Backlog: open work orders by age, territory and work type, including approved quotes not yet scheduled.
- Margin: by job type, customer and technician, from actuals returned by accounting.
- Agreement health: visits promised against visits completed, and renewals due in the next quarter.
- Deficiency conversion: inspection findings quoted, approved and completed.
First-time fix is not a standard field. It depends on how you link return visits to the original job, so design that link before go-live.
Paper inspection forms can feed these reports too. A telecom-infrastructure contractor we worked with ran a proof of concept using Salesforce Document AI with custom schemas. It reliably read the checkboxes and tables that its earlier tooling could not process.
What mistakes do trades contractors make with Salesforce?
Most come from building too much at once or copying accounting into the CRM. A few others show up often enough to plan around.
- Treating Salesforce as the costing ledger and reconciling the two by hand at every close.
- Leaving the scheduler installed but unconfigured, so dispatch drifts back to calendars.
- Licensing every seasonal worker before deciding who actually needs to log in.
- Designing mobile screens in a conference room instead of with a technician.
- Skipping asset records, which leaves agreements, warranties and repair history disconnected.
- Automating notifications without limits, so customers and staff learn to ignore them.
What belongs in phase one for a commercial trades contractor?
Phase one should cover customers, sites, assets, agreements, work orders, dispatch and a simple mobile close-out. Save portals, AI and deep inventory for later.
- Accounts, sites and contacts cleaned and loaded from the current system.
- Assets for equipment under agreement, even if older installs come later.
- Service agreements that generate recurring work orders.
- Work types with realistic durations and required skills.
- Dispatch configured for your longest and shortest common jobs.
- A short mobile close-out with time, materials, photos and signature.
- A one-way feed of completed work to accounting, with actuals returned for margin.
Pick one branch or one trade to go first. Its dispatchers will find the scheduling gaps faster than any test script. Adjust, then extend to the next group.
