How to Set Up Jobber for a Plumbing or HVAC Business Without Creating More Office Work

Step 1: Map the workflow before touching settings

Write the normal path from first request to collected payment. Include who answers, what information is required, when an on-site assessment is needed, who builds the quote, how approval is captured, who schedules, what the technician records, when the invoice is sent, and who follows unpaid balances.

Then map exceptions: emergency service, no-access visits, return trips, warranty calls, parts on order, commercial approval, multi-property customers, maintenance agreements, and permit or compliance work. Jobber should reflect those decisions. It should not be the place where the team discovers them.

Step 2: Build a usable services and items list

Use names the office and field understand. Separate customer-facing language from internal detail where needed. Avoid creating a new line item for every tiny variation. The list should support consistent quotes, invoices, reporting, and technician use without becoming impossible to search.

For plumbing, categories might include diagnostic, repair, replacement, drain, water heater, boiler, gas, and compliance work. For HVAC, use diagnostic, maintenance, repair, replacement, equipment, and accessory categories. Confirm taxes, units, costs, markups, descriptions, and accounting mapping with the appropriate financial professional.

• Use a controlled naming convention
• Archive duplicates instead of renaming them repeatedly
• Separate labor, materials, equipment, and fees when reporting requires it
• Create quote templates for common scopes
• Assign one owner for changes

Step 3: Standardize customer intake

Capture only information that affects qualification, dispatch, safety, or follow-up. At minimum, collect caller, service address, billing relationship, problem, urgency, access, service history, source, and preferred contact method. Commercial and property-management calls may need company, authorization, COI, purchase-order, and site-contact details.

Jobber officially supports online requests, manual requests, customer and property records, notes, job history, and communication history. Use those records consistently. Do not bury dispatch-critical information in a long free-text note that technicians cannot scan.[1]

Step 4: Define the quote and estimate flow

Decide which work can be priced during intake, which needs an assessment, who builds the quote, who reviews larger proposals, and how often open quotes are followed up. Jobber's official features include quote templates, optional add-ons, approvals, deposits, and automated quote follow-up. Turn on only what matches the sales process.

Create visible ownership. Every open quote should have a next action and date. Automation can send reminders, but high-value or complicated work may need a personal call. Track reasons for loss in a simple, consistent way so the owner can distinguish price, timing, no decision, competitor, and bad fit.

Step 5: Keep scheduling and statuses simple

The schedule should show who, where, when, and what. Use realistic arrival windows and travel assumptions. Store building access, equipment, parking, and contact details where the field can find them. Assign work based on skill and location, not only the first open space.

Use the fewest statuses that still trigger clear action. Too many statuses create inconsistent choices. For example, the team may need scheduled, en route, on site, needs follow-up, complete, and canceled. Parts-on-order or return-visit conditions may be handled with tasks or a controlled tag if that is clearer.

Step 6: Connect completion to invoice and payment

Decide what evidence is required before a job can be completed: technician notes, photos, time, materials, customer approval, and return-work status. Completion should place the job in a visible invoice queue. The office should not wait for the owner to remember which work is billable.

Jobber officially supports invoice creation, invoice reminders, batch invoicing, automated follow-up, online payments, and a client portal. Configure timing and language to match payment terms. Review exceptions weekly: complete but not invoiced, sent but not viewed, overdue, disputed, or missing accounting data.[1]

Step 7: Use tags, custom fields, and reports with restraint

Create a field only when someone will use it to make a decision, complete work, or report. Good examples may include equipment type, access requirement, lead source, customer type, or service-agreement status. Bad fields collect interesting facts that nobody maintains.

Start reporting with operational queues: new requests, unassigned work, quotes awaiting action, jobs needing follow-up, complete jobs awaiting invoice, and overdue invoices. Add revenue or technician analysis only after the underlying statuses and records are trustworthy.

• One definition per field
• One owner for data quality
• Required only when truly necessary
• No duplicate tag and custom-field concepts
• Monthly cleanup of unused values

Common Jobber setup mistakes

The most common mistake is configuring features before deciding the workflow. Others include importing duplicates, creating too many job types, using notes instead of structured fields, requiring too much technician input, failing to test accounting handoffs, and turning on automation without monitoring the customer experience.

Get help when the setup touches a large migration, pricebook design, multi-location customers, accounting integration, role permissions, or an office process that is already disputed. A one-time implementation can be enough. Ongoing operating support makes sense when nobody internally can own the weekly queues and data.