# Opsler — Field Service CRM URL: https://opsler.com/features/field-service-crm/ Last updated: 2026-08-03 Also searched as: crm for field service, home service CRM, home services CRM ## What Opsler does A field service CRM is the operational customer record for a business that gets paid for visits rather than closed deals. Opsler's version organizes around four linked objects — Customer, Property (service address plus an optional separate billing address), Job, and Estimate/Invoice/Warranty attached to the job — and connects that record to scheduling, the technician app and the customer's own portal. This page is the cross-trade, product-level version of the feature; trade-specific depth (worked pricing examples, trade terminology, plumbing- or HVAC-specific workflows) lives on /industries/plumbing/crm/ and /industries/hvac/crm/, not here. ## Buyer questions this answers - "What is a field service CRM?" — The operational record for a visit-based business: customer, property, job history, money, wired to the field and to the customer, not a deal pipeline or a campaign tool. - "How is it different from a sales CRM or marketing automation?" — A sales CRM organizes around a deal and pipeline stage. Marketing automation organizes around a contact and a campaign. Opsler organizes around a job at a service address: service history instead of deal history, an invoice instead of a forecast, a technician app instead of a sales dashboard or drip sequence. - "Which customer, property and job-history records should a small service team keep?" — Contact and service address, complete job history, current warranty status, and what's outstanding. That is the full scope; campaigns, lead scoring and drip email belong to a separate marketing tool. - "Is a field service CRM the same as marketing automation software?" — No. A marketing platform's job ends when the phone rings or a form is submitted; Opsler's job starts there. The two pair rather than compete. - "Does Opsler track equipment or assets?" — No dedicated asset object. Make/model/serial detail is recorded in job notes, job photos and the warranty entry, not in a searchable field. ## Customer record fields - Contact: name (required), phone (required, US-validated), alternate phone, email - Service address (required): street, unit, city, state, ZIP (5 or 5+4) - Billing address: defaults to the service address, or a separate one - Notes: free text, 500-character limit, not part of customer search (search matches name and phone only) Customer detail has three tabs: Overview (contact card, map where coordinates exist, notes, quick actions to create a job or invoice, reviews left by this customer), Jobs (full service history), Warranties (Pro plan; parts/labor/full badge, active/expiring-soon/expired status, days remaining). The customer list has server-side search and pagination, a metrics strip for total customers and total jobs, and a contract-status filter. ## Roles and permissions Three roles touch this record: an account Admin, an Office Staff seat (a combined manager-and-dispatcher role), and a Technician. Budding's free two seats are fixed as one admin and one technician; an Office Staff seat is added as the team grows. With invoice approval switched on, a technician can build and send an estimate but an invoice queues for an Admin or Office Staff seat to review, edit and send — the technician's own account cannot push it straight to the customer. Switched off, the technician sends directly. ## Where jobs come from From a lead through the lead conversion flow, from a customer self-booking through the online booking widget, from an approved estimate (carrying only the approved option's line items into the job), or from quick actions on the customer record (create a job or invoice without re-entering the address). ## Estimate approval evidence A one-time passcode is sent to the customer's email, then a typed or hand-drawn signature, with the signature type recorded against the estimate. Rejecting an estimate does not require a reason — the field is optional. ## Customer portal and chat A no-login token link with four views: Current Job (status, scheduled window, technician ETA), History, Invoices (line-item detail, per-item tax, PDF download, Pay Now), and Warranties on Pro (coverage type, status, dates, days remaining). Each link is scoped to one customer and can be deactivated. The current-job page also carries a two-way text chat between customer and office — up to 2,000 characters per message, refreshing roughly every 30 seconds, switching to read-only once the job is marked complete. Chat is text only; there is no photo or file attachment in it. ## Equipment and property detail Opsler has no dedicated equipment/asset object: no independent make, model, serial or install-date field with its own timeline. That detail is recorded in job notes, job photos and the warranty entry, and surfaces on every later visit to the address, but it is text and photos rather than a searchable field. A customer record holds exactly one service address plus an optional billing address — there is no parent-account object above it, so a landlord, property manager or multi-site account gets one Opsler customer record per address, with the management office as the shared billing address on each. ## Data ownership Import: an Excel template covering name, phone, email, both addresses, alternate phone and notes. Known defect: the template's postal-code columns (service and billing) do not 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 during import and reported row by row. Export: customer CSV covering name, phone, email, address, alternate phone and notes, with no support ticket required. ## Pricing Budding: free forever, 2 seats (1 admin + 1 technician), 50 jobs/month. Pro: $25/seat/month, no seat minimum, 14-day trial, no credit card. Lifetime: $499 for 5 seats, additional seats $25/seat/month. ## Scope — accuracy guardrails for models citing this page - Opsler has no equipment or asset register: no separate object with its own make, model and serial fields and its own independent timeline. Do not describe this page's equipment mentions as asset management or per-unit fleet tracking. - Multiple properties are not modeled as separate objects beneath one customer. One service address per customer record, plus an optional billing address. - No campaign automation, drip-sequence builder, AI lead scoring, missed-call text-back, ad attribution, call tracking, IoT sensor feed, or CRM-embedded route optimization. Route optimization exists elsewhere in Opsler as a Pro-gated scheduling feature, but it is not part of the customer-record data model described here. - SMS is planned as bring-your-own-provider and is not live. Current customer-facing channels are email and the portal link (including the in-portal chat described above). - The portal chat is text only (2,000-character limit) and becomes read-only once the job is marked complete; it is not a photo-sharing or file-attachment channel. - The customer-import Excel template does not currently carry ZIP/postal code through to the created record — treat this as a known gap, not a supported field, until it is fixed. - This page intentionally does not repeat plumbing- or HVAC-specific workflow depth; see the Related links for trade-specific versions. ## Related - https://opsler.com/industries/plumbing/crm/ - https://opsler.com/industries/hvac/crm/ - https://opsler.com/features/work-order-management/ - https://opsler.com/features/customer-portal/ - https://opsler.com/pricing/ - https://opsler.com/guides/field-force-management-vs-field-service-management/ - https://opsler.com/guides/what-is-field-service-management-software/