Field Service CRM Connected to Jobs and Technicians
The phone rings, caller ID shows a number you don’t recognize, and the person on the other end assumes you remember exactly what your technician did at their house fourteen months ago. That expectation is reasonable on their side, and it’s the entire reason a field service CRM exists. Whether you typed field service CRM, CRM for field service, home service CRM or home services CRM into the search bar to get here, the job on this page is the same: hold the record of who this customer is, what was done at their property, and what’s still open, before the second question leaves their mouth.
A field service CRM is the operational customer record for a business that gets paid for visits rather than closed deals. It organizes around the job at a service address instead of a pipeline stage, and it stays wired to scheduling, the technician’s app and the customer’s own portal rather than sitting off to the side as a standalone contact list.
The data model in one line
Customer
Contact + notes
Property
Service + billing address
Job
Full history
Estimate, invoice, warranty
Attached to the job
Every box on the right belongs to exactly one customer. Nothing here belongs to a deal, a campaign or a pipeline stage.
It is also the part of the stack most often sold by the seat block. Opsler is $25 a seat with no minimum, so an owner and one technician is two seats rather than five — and those two seats are free permanently on the Budding plan, customer records, job history, estimates and invoices included. Most teams have their customer list imported and their first job on the board the same afternoon.
Who is this?
Contact details, service address, billing address and the notes every previous technician left.
What have we done here?
Complete job history at that address, with the service notes and photos recorded on site.
What is still open?
Active warranties with type, status and days remaining, plus outstanding invoices.
One customer, one record: the property, how long they have been with you, and every visit to that address — which is what the next technician needs before they knock.
CRM vs Field Service Management
Search a CRM for field service work specifically, not sales, and the results still split three ways: sales CRMs built around a deal pipeline, marketing platforms built around campaigns, and full field-service suites where “CRM” is one tab bolted onto scheduling and dispatch. Here is the split Opsler actually sits in, plain about what each one does and doesn’t hold.
| Dimension | Sales CRM | Marketing automation | Field service CRM (Opsler) |
|---|---|---|---|
| Organized around | A deal | A contact and a campaign | A job at a service address |
| Core timeline | Pipeline stages | Campaign touches | Service history — what was done, when, by whom |
| Money record | Forecast value | Attribution | Estimate, invoice, payment, job profit |
| Field connection | None | None | Assigned jobs push to the technician app |
| Customer self-service | Rare | Preference center | No-login portal: job, invoices, warranties, chat |
| Campaigns and lead scoring | Some | Yes | Left to your marketing tool, by design |
Zoom out to the wider category and enterprise platforms crowd the results: Dynamics 365 Field Service leads with AI-driven scheduling and IoT-connected assets, and Salesforce’s Agentforce pitches an AI agent running the whole operation. Real capabilities, built for a company with an ops team dedicated to configuring them. Opsler runs the plain four-box model above instead, and the difference shows up on day one rather than in year two: there is nothing to configure before anyone can use it, because there are no opportunities, accounts or contract hierarchies to model first. No AI lead scoring, no IoT sensor feed, no route optimization inside the CRM itself. A two-person shop is running real jobs through it the same week, at the same price per seat as a ten-truck operation.
Working one specific trade rather than shopping the category in general? The HVAC CRM page and the plumbing CRM page build on everything below with trade-specific workflows, pricing examples and terminology.
Customer, Property and Contact Records
The property side of a home service CRM often outlives whoever’s paying the invoice this year — tenants move out, owners sell, the address stays on your books. These are the actual fields Opsler stores against that address today, not an aspirational list.
| Group | Fields |
|---|---|
| Contact | Name (required), phone (required, US-validated), alternate phone, email (optional) |
| Service address | Street, unit or apartment, city, state, ZIP (5-digit or 5+4) — required |
| Billing address | Defaults to the service address, or a full separate billing address |
| Notes | Free-text, 500-character limit, carried across every visit |
That notes field is context, not a database column: customer search matches name and phone only, so anything typed into notes helps whoever opens the record next but won’t surface if you go looking for it later.
Multiple properties, one payer: a customer record holds exactly one service address plus an optional separate billing address — there’s no parent-account object sitting above it. A landlord, property manager or multi-site commercial account gets one Opsler customer per address, with the management office entered as the shared billing address on each. It’s more setup up front, and it means the technician pulling up one building sees only that building’s history, not five others folded into one feed.
Lead and Estimate Pipeline
A home services CRM earns its place the moment a lead needs to become a scheduled visit, not before. Here’s every route a job takes to get onto the calendar.
From a lead
A lead converts into a job through the lead conversion flow, carrying the contact detail across.
From a booking
Customers who self-book through the online booking widget arrive as jobs ready to schedule.
From an estimate
An approved estimate becomes a job automatically, carrying only the approved option's line items.
From the record
Quick actions on the customer page create a job or invoice without re-entering the address.
Illustrative example — same customer, one week
- Monday — A call comes in, gets logged as a lead against a brand-new customer record.
- Tuesday — An estimate goes out; the customer opens the passcode link and signs from their phone.
- Wednesday — The approved line items become a scheduled job automatically; the lead record closes itself out.
Fictional example for illustration — not a live customer record.
Approval leaves real evidence behind, not just a status flip: a one-time passcode goes to the customer’s email, then a typed or hand-drawn signature, with the signature type recorded against the estimate. Rejecting an estimate doesn’t force a reason — the field is optional — but when customers do leave one, it’s the closest thing to a paper trail on why quotes fall through.
If you’re narrowing down exactly what a small service team should keep on a customer, this is the short version: contact and service address, complete job history, current warranty status and what’s outstanding on the account. That’s the full list on this page — anything past it (campaigns, lead scoring, drip email) belongs to a separate marketing tool, not a field-service CRM.
Jobs, Equipment, Notes and Service History
Overview tab
Contact card with ID, name, phone, alternate phone, email and address; a map where coordinates exist; notes; quick actions; and reviews left by this customer.
Jobs tab
The full service history — every visit, its status and what was recorded on site. This is what stops a repeat fault being diagnosed from scratch.
Warranties tab (Pro)
Warranty jobs sorted active, expiring soon, then expired, each with a parts/labor/full badge, days remaining and a shortcut to book the follow-up.
Equipment lives on the job, not its own record. What was fitted, when, and whether it is still covered all travel with the job notes, the job photos and the warranty entry — so a technician arriving three winters later opens one screen and sees the lot. What that is not is a dedicated asset object with its own make, model, serial number and install date living independently of a job. It is text and photos rather than a searchable field, so filtering customers by unit brand or serial number is not something you can do here. For most teams the job history answers the question anyway; if per-unit reporting is the thing you are buying, weigh that first.
Illustrative example — the Jobs tab for one address
- Visit 1 — Diagnostic call, no charge, covered under the labor warranty from the original install.
- Visit 2 — Routine maintenance, notes flag a part nearing the end of its life.
- Visit 3 — Full repair, before/after photos attached, a new warranty entry opened.
Fictional example for illustration — not a live customer record.
Every job assignment, completion and customer edit lands in a timestamped activity log with the name of whoever did it, so “who moved this appointment” has an answer without a phone call. Each one of those entries is a full work order in its own right — see how one moves from open to invoiced on the work order management page.
Customer Portal and Communication History
For a home services CRM, giving the customer a link beats giving them a login — nothing to set up, nothing for your office to reset.
Current job
Status, scheduled window and technician ETA.
History
Every past job at that address with what was recorded on site.
Invoices
Line-item breakdown with per-item tax, PDF download and a Pay Now link.
Warranties (Pro)
Coverage type, status, start and end dates and days remaining.
Two-way chat on the current job. The customer and your office can message back and forth right on the job page — text only, up to 2,000 characters a message, refreshing automatically about every 30 seconds. Once the job is marked complete the thread switches to read-only, so it stays a record of that visit instead of turning into an open-ended inbox.
Access is a no-login token link sent by email. Each link is scoped to that one customer and can be deactivated on your end, so a record shared once doesn’t stay open forever. In practice this is what cuts down the “is my tech on the way yet” calls: the answer lives on a link the customer already has, updated the moment status changes on your side, instead of a phone queue at your office.
Office and Technician Access
“The office” below can be the account admin or a teammate on an Office Staff seat — a combined manager-and-dispatcher role — and both see the same customer-record capabilities. Budding’s free two seats are fixed as one admin and one technician; an Office Staff seat is something you add as the team grows.
The office sees
- The full customer list with server-side search and pagination
- A metrics strip for total customers and total jobs at a glance
- Filter the list by contract status
- An invoice approval queue before anything reaches a customer, where the office turns that on
The technician sees
- Their assigned jobs for the day, in order
- The customer’s prior service notes on arrival
- Job detail, parts and photo capture — status updates and photos keep working without signal and catch up once reconnected
- Status buttons such as View Details and On My Way that update the office board instantly
That approval queue is a permission split, not just a setting: with office approval switched on, a technician can build and send an estimate but an invoice waits in the queue for someone on an admin or Office Staff seat to review, edit and send — the technician’s own account can’t push it straight to the customer. Switch it off and the technician sends directly, which is the faster path for a one- or two-person shop that trusts its own pricing.
Where a Marketing CRM Ends and Opsler Begins
Winning a customer and running their job afterward are different problems, and this page has been describing the second one. That is the half where the money actually lands: Opsler takes over the moment work is booked and keeps the record that makes every future visit to that address cheaper to deliver. Your marketing platform keeps doing what it is good at upstream. The two sit side by side rather than overlapping, which is why most teams pay for both and neither duplicates the other’s work.
Opsler owns
- The operational customer record and job history
- Estimates, approval evidence, invoices and payment status
- Warranty context and the no-login customer portal
- Review requests after completed work
Your marketing tool keeps
- Email campaigns and drip sequences
- Missed-call text-back
- Lead scoring and pipeline forecasting
- Paid-ad attribution and call tracking
On the customer-facing side, updates go out by email and through the job’s own link — one address the customer keeps from the booking through to the invoice and the warranty, rather than a reminder buried in a text thread from six weeks ago.
Fit, Migration and Data-Ownership Checklist
Two minutes here saves a fortnight later. Check the fit, then check you could walk out with your own records — a question worth asking every vendor in this category, and one most of them answer slowly.
Good fit if…
- One or more technicians who get paid for visits, not for closed deals
- A team that wants one record to hold the customer, the job history and the money, instead of three tools cross-referenced by hand
- Recurring or warrantied work where “what did we do here last time” comes up weekly
Built for something else if…
- Your record is the machine rather than the household — a serial-numbered asset register with its own reporting is a different shape of product
- The problem you are solving is winning the customer, not running the job: campaigns, drip sequences, lead scoring and call tracking live upstream of this
- Text messaging is how your customers expect to hear from you — updates here go by email and the job's own link
Import
An Excel template covers name, phone, email, both addresses, alternate phone and notes. One defect to know: the template's postal-code columns don't currently map through on import, so ZIP is left blank on every bulk-imported customer today — add it by hand afterward. Duplicate phone numbers are skipped automatically and reported row by row.
Export
Customer CSV export covering name, phone, email, address, alternate phone and notes — available with no support ticket.
Cost
Free forever for 2 seats on Budding. Pro is $25 per seat per month, no minimum, 14-day trial without a card. Lifetime: $499 for 5 seats, additional seats at $25/seat/month.
Frequently Asked Questions
Is a field service CRM the same as marketing automation software?
No, and they rarely compete for the same budget once you see what each one holds. A marketing platform's job ends when the phone rings. A field service CRM's job starts there — the customer, the property, the job history, the estimate, the invoice, the warranty — and that is the half where the money actually lands. Opsler owns that half completely, which is why the second visit to an address is the profitable one: the technician arrives already knowing what you did last time, what it cost, and what is still under warranty.
Working Out Which Category You Need
“CRM” covers several different products and the labels overlap. If you’re weighing a home service CRM against a sales CRM, a field force tool or an attendance system, the category comparison guide separates them by what the record is actually about, and the field service management definition covers where CRM ends and the rest of FSM begins. For the token-link experience described above, see the customer portal page in full, and for the job side of the same record — scheduling, dispatch and the technician app this CRM feeds — the features hub lists everything else Opsler runs alongside it.
Ready to Run Your Business Without the Chaos?
Scheduling, dispatch, estimates, invoicing, customer portal, and a free branded website — start completely free, upgrade to Pro when you scale.
Free forever on the Budding plan. No credit card required.