---
title: "Scheduling"
url: "https://fieldcamp.ai/hvac-software/scheduling/"
date: "2026-07-27T09:48:42+00:00"
modified: "2026-08-07T12:03:55+00:00"
type: "Article"
resource: "https://fieldcamp.ai/hvac-software/scheduling/"
timestamp: "2026-08-07T12:03:55+00:00"
author:
  name: "Jeel Patel"
categories:
  - "Uncategorized"
word_count: 3165
reading_time: "16 min read"
summary: "Home › HVAC Software › Scheduling"
description: "HVAC scheduling software that builds the day around skills, location and agreement coverage, and schedules recurring maintenance visits automatically."
keywords: "Uncategorized"
language: "en"
schema_type: "Article"
related_posts:
  - title: "Best Aircon Servicing Software in Singapore 2026"
    url: "https://fieldcamp.ai/sg/aircon-software/best-software/"
  - title: "Best Pest Control Software in Singapore 2026"
    url: "https://fieldcamp.ai/sg/pest-control-software/best-software/"
  - title: "How Much to Charge for Gutter Cleaning in 2026"
    url: "https://fieldcamp.ai/blog/how-much-to-charge-for-gutter-cleaning/"
---

# Scheduling

_Published: July 27, 2026_  
_Author: Jeel Patel_  

[Home](/) › [HVAC Software](/hvac-software/) › <mark class="has-inline-color" style="background-color:rgba(0,0,0,0);color:#0f0e0b">**Scheduling**</mark>

HVAC · Scheduling

# HVAC scheduling software that finds the best slot — *and lets you confirm it in one click.*

 One calendar that books the job, checks who can actually serve it, holds the recurring seasonal maintenance, and reminds the customer. Tick “Let AI find the best time” and FieldCamp scans every technician, filters out anyone who can’t take the work, and returns the best slot with its reasoning. It’s the scheduling layer of FieldCamp’s [HVAC software](/hvac-software/) — same board, same data model as dispatch, CRM, and invoicing.

[Book a 15-minute call](https://calendly.com/jeel-fieldcamp/30min)Watch the AI assign a live HVAC board on the call.

AI slot

suggested with reasoning + alternatives

Recurring

jobs or visits created by workflow

One board

booking → dispatch → accounting

Dispatch · Wed, May 293 trucks · 9 visitsAI assigningScheduledTimelineResourceMapTechnicians8 AM10 AM12 PM2 PM4 PMRKRiya K.

Truck B · EPA 608 Univ.

88% full<svg aria-hidden="true" fill="none" height="10" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.2" viewbox="0 0 24 24" width="10"><path d="M5 13l1.6-4.6A2 2 0 0 1 8.5 7h7a2 2 0 0 1 1.9 1.4L19 13M5 13h14v4h-2v-1H7v1H5v-4z"></path><circle cx="8" cy="15.5" r="0.6"></circle><circle cx="16" cy="15.5" r="0.6"></circle></svg> 11m<svg aria-hidden="true" fill="none" height="10" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.2" viewbox="0 0 24 24" width="10"><path d="M5 13l1.6-4.6A2 2 0 0 1 8.5 7h7a2 2 0 0 1 1.9 1.4L19 13M5 13h14v4h-2v-1H7v1H5v-4z"></path><circle cx="8" cy="15.5" r="0.6"></circle><circle cx="16" cy="15.5" r="0.6"></circle></svg> 16m#1041AlvarezUrgent
No-cool · 8:00–9:45

#1043Boyd
AC tune-up · 10:15–12:00

#1046Tran
Heat-pump swap · 12:45–3:30

DADaniel A.

Truck A · EPA Type II

63% full<svg aria-hidden="true" fill="none" height="10" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.2" viewbox="0 0 24 24" width="10"><path d="M5 13l1.6-4.6A2 2 0 0 1 8.5 7h7a2 2 0 0 1 1.9 1.4L19 13M5 13h14v4h-2v-1H7v1H5v-4z"></path><circle cx="8" cy="15.5" r="0.6"></circle><circle cx="16" cy="15.5" r="0.6"></circle></svg> 9m<svg aria-hidden="true" fill="none" height="10" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.2" viewbox="0 0 24 24" width="10"><path d="M5 13l1.6-4.6A2 2 0 0 1 8.5 7h7a2 2 0 0 1 1.9 1.4L19 13M5 13h14v4h-2v-1H7v1H5v-4z"></path><circle cx="8" cy="15.5" r="0.6"></circle><circle cx="16" cy="15.5" r="0.6"></circle></svg> 14m#1042Ortiz
HP diag. · 9–10

#1044Shah
IAQ install · 10:30–1:00

#1047Kim
Plan visit · 2–3 PM

MRMarco R.

Truck C · EPA Type I

80% full<svg aria-hidden="true" fill="none" height="10" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.2" viewbox="0 0 24 24" width="10"><path d="M5 13l1.6-4.6A2 2 0 0 1 8.5 7h7a2 2 0 0 1 1.9 1.4L19 13M5 13h14v4h-2v-1H7v1H5v-4z"></path><circle cx="8" cy="15.5" r="0.6"></circle><circle cx="16" cy="15.5" r="0.6"></circle></svg> 21m<svg aria-hidden="true" fill="none" height="10" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.2" viewbox="0 0 24 24" width="10"><path d="M5 13l1.6-4.6A2 2 0 0 1 8.5 7h7a2 2 0 0 1 1.9 1.4L19 13M5 13h14v4h-2v-1H7v1H5v-4z"></path><circle cx="8" cy="15.5" r="0.6"></circle><circle cx="16" cy="15.5" r="0.6"></circle></svg> 12m#1040Weiss
Tune-up · 8:00–9:15

#1045Fox
No-heat · 10:00–11:30

#1048Diaz
Furnace install · 12:15–3:45

<svg aria-hidden="true" fill="currentColor" height="11" viewbox="0 0 24 24" width="11"><path d="M12 2l1.8 5.4L19 9l-5.2 1.6L12 16l-1.8-5.4L5 9l5.2-1.6L12 2z"></path></svg>Why Riya got the no-cool: EPA 608 Universal · already in Zone 2 · 11 min to her next stop · truck still has headroom.<svg aria-hidden="true" fill="currentColor" height="11" viewbox="0 0 24 24" width="11"><path d="M12 2l1.8 5.4L19 9l-5.2 1.6L12 16l-1.8-5.4L5 9l5.2-1.6L12 2z"></path></svg> AI assigned the day · 1m 38s0 conflictsOne calendar for booking, recurring maintenance, capacity, and the handoff to dispatch.

<mark class="has-inline-color" style="background-color:rgba(0,0,0,0);color:#e8935a">•</mark> Residential

<mark class="has-inline-color" style="background-color:rgba(0,0,0,0);color:#e8935a">•</mark> Commercial

<mark class="has-inline-color" style="background-color:rgba(0,0,0,0);color:#e8935a">•</mark> Seasonal peaks

<mark class="has-inline-color" style="background-color:rgba(0,0,0,0);color:#e8935a">•</mark> Multi-branch

01 The lifecycle

## One calendar, from the first call to the *recurring tune-up.*

Scheduling connects jobs and visits to time and availability. FieldCamp keeps the scheduling record connected to [dispatch](/hvac-software/dispatch/), while [configured recurring workflows create seasonal maintenance requirements](https://docs.fieldcamp.ai/job-management/recurring-jobs).

1

Book

### From a call, the web, or a plan

A job enters the calendar from a phone call — answered by a person or the [AI receptionist](/hvac-software/ai-receptionist/) — from a configured online-booking path, or from recurring work tied to a maintenance agreement. Booking hours, slot rules, and approvals are implementation decisions.

✓ Triaged

1

Slot

### A slot that can actually be served

Set the duration and any travel limit, and the engine scans every technician for that window. It removes anyone without an exact skill match, already booked, over their daily job capacity, or on time-off — then ranks whoever is left. You get the best slot plus alternatives to compare.

✓ Slotted

1

Remind

### Confirm, remind, cut no-shows

Configured confirmation and reminder workflows can use enabled communication channels. Exact sending, reply handling, and measured outcomes should be verified for your implementation.

✓ Confirmed

1

Sync

### Straight to the back office

The job moves to the board for assignment, is tracked to completion on the tech’s mobile app, then flows into [invoicing](/hvac-software/invoicing/) and the customer record — no double entry, no re-keying.

✓ Synced

02 What it is

## What is HVAC scheduling software?

HVAC scheduling software automates booking, technician assignment, real-time tracking, and customer reminders on one shared calendar — including the recurring seasonal maintenance an HVAC business runs on — and syncs completed jobs to accounting and CRM.

How the AI actually picks a slot. On the job form you tick “Let AI find the best time” and set the parameters — how long the job takes, when it needs to be done by, and how much travel you’ll accept. From there the engine works in two passes.

→

<mark class="has-inline-color" style="background-color:rgba(0,0,0,0);color:#0f0e0b">**First it filters — hard rules, no exceptions**</mark>. Anyone without an exact skill match for the job is out. So is anyone already booked in that window, anyone over their daily job capacity, and anyone on time-off or outside business hours. Those aren’t preferences the AI weighs; they remove a technician from consideration entirely.

→

<mark class="has-inline-color" style="background-color:rgba(0,0,0,0);color:#0f0e0b">**Then it ranks whoever survives.**</mark> Travel distance from that technician’s previous job to this site. Current workload balance — it prefers the underloaded tech over the one already stacked. The customer’s stated preference if they asked for a morning or afternoon. And performance history on similar job types.

→

<mark class="has-inline-color" style="background-color:rgba(0,0,0,0);color:#0f0e0b">**You confirm — it doesn’t book behind your back**</mark>. The best option appears with its reasoning written out, along with alternatives if you want to compare. Click Accept and the visit is created with that time and technician. Nothing is scheduled until you do.

→

<mark class="has-inline-color" style="background-color:rgba(0,0,0,0);color:#0f0e0b">**Or ask for it in plain language.**</mark> From the Command Centre: “find the best time for a heat-pump repair at 789 Pine Street, keep travel under 30 minutes”, or “schedule Sarah Johnson’s annual maintenance — assign the closest available tech”.

→

<mark class="has-inline-color" style="background-color:rgba(0,0,0,0);color:#0f0e0b">**Scheduling AI vs AI Dispatcher — when to use which.**</mark> The built-in AI scheduling covers day-to-day job creation and is included. [AI Dispatcher](/hvac-software/dispatch/) is a separate credit-based add-on for teams handling high volumes of incoming work who want a dedicated dispatch operations centre. Most shops start with the former.

→

<mark class="has-inline-color" style="background-color:rgba(0,0,0,0);color:#0f0e0b">**Scheduling vs dispatching.**</mark> Scheduling sets *when*; dispatching sets *who* goes and in what route order. FieldCamp does both on one board — a scheduled job is already assignable, because the calendar and the dispatcher share one data model.

→

<mark class="has-inline-color" style="background-color:rgba(0,0,0,0);color:#0f0e0b">**What it isn’t.**</mark> The calendar doesn’t fill or rebalance itself on a timer. Recurring maintenance is created by a workflow you configure, and automatic demand forecasting, seasonal capacity protection, and calendar rebalancing are not part of it.

Riya K. · this afternoonRe-optimizing1:00 PM#1046Heat-pump swap · Tran4218 Maple Ave · unchangedIn progress2:15 PM#1049No-cool · AlvarezUrgent96°F day · nearest qualified techInserted3:30 PM#1043AC tune-up · BoydRoutine · new ETA texted<svg aria-hidden="true" fill="none" height="9" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.6" viewbox="0 0 24 24" width="9"><path d="M12 5v14M6 13l6 6 6-6"></path></svg> was 2:154:45 PM#1047Plan visit · KimAgreement visit · new ETA texted<svg aria-hidden="true" fill="none" height="9" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.6" viewbox="0 0 24 24" width="9"><path d="M12 5v14M6 13l6 6 6-6"></path></svg> was 3:30<svg aria-hidden="true" fill="currentColor" height="11" viewbox="0 0 24 24" width="11"><path d="M12 2l1.8 5.4L19 9l-5.2 1.6L12 16l-1.8-5.4L5 9l5.2-1.6L12 2z"></path></svg>Two visits re-sequenced · new ETAs texted · +0 min drive added.<svg aria-hidden="true" class="flex-shrink-0" fill="currentColor" height="11" viewbox="0 0 24 24" width="11"><path d="M12 2l1.8 5.4L19 9l-5.2 1.6L12 16l-1.8-5.4L5 9l5.2-1.6L12 2z"></path></svg> Emergency jumped the queue · re-optimized in 4s

### Who HVAC scheduling software is for

Growing residential shops

Evaluate the configured booking path, reminders, job and visit records, technician skills, and daily capacity ceilings.

Commercial & multi-site

Evaluate recurring-work configuration, multi-site records, scheduling review, and separately verified accounting mappings.

High-volume / seasonal

Use schedule and availability context to review urgent demand. Automatic surge absorption or capacity protection is not implied.

Multi-branch / enterprise

Model locations, teams, service lines, jobs, visits, and availability without implying autonomous branch planning.

### From a whiteboard to AI-assisted scheduling

Four ways HVAC shops schedule today — and where each one gives out.

Swipe the table sideways to see all columns →

 | Approach | How it works | Suitable for | The limitation |
|---|---|---|---|
| Paper calendar / whiteboard | Jobs written on a wall calendar or whiteboard; the office calls to confirm. | Low-volume operations with simple scheduling requirements. | No self-booking, no reminders, no recurring automation — and it collapses under a seasonal surge. |
| General calendar tool | Appointments in a shared calendar. | Very small teams that just need shared visibility. | No technician-skill logic, no capacity awareness, no recurring maintenance, no reminders tied to jobs. |
| FSM scheduling board | A purpose-built drag-and-drop board with text reminders and online self-booking. | Most growing shops — the current mainstream. | Ask whether the board shows availability or actually recommends a slot, and whether that recommendation explains itself. |
| <svg fill="currentColor" height="11" viewbox="0 0 24 24" width="11"><path d="M12 2l1.8 5.4L19 9l-5.2 1.6L12 16l-1.8-5.4L5 9l5.2-1.6L12 2z"></path></svg>AI-assisted scheduling (FieldCamp) | The engine filters on skills, conflicts, capacity, and availability, then ranks on travel, workload, customer preference, and performance history — and returns a slot with reasoning plus alternatives. | Any shop that wants the slot decided for them and still wants the final click. | Skills, capacity ceilings, and availability need an initial setup. The calendar does not rebalance itself on a timer. |

  03 Core features

## Key features to look for — *each one handled natively.*

A shared calendar is the starting point. These are the capabilities that decide whether the operation has clear scheduling ownership — the checklist to evaluate any tool against.

### Shared calendar & board

Every job, tech, and truck on one view — read the day by calendar, by tech, or by capacity, and drag to override any slot. Booked, assigned, and tracked from intake to close, updating in real time.

### AI slot finding

“Let AI find the best time” on the job form. Set duration, completion deadline, and a travel limit; get back the best technician-and-time pairing with written reasoning and alternatives to compare. Accept, or pick one yourself.

### Configured online booking

A supported website or link flow can create the configured request or job record. Booking hours, availability rules, service-area logic, and approvals should be verified for the implementation.

### Recurring & seasonal maintenance

Spring and fall tune-ups and service-agreement visits schedule through configured recurring jobs or visits — not an implied self-running calendar. It’s the HVAC-specific need a generic scheduler misses, and it runs on the same records as your [maintenance agreements](/hvac-software/maintenance-agreements/).

### Skills as a hard requirement

Skills are set per technician and matched exactly — a tech without the required skill for a job type is filtered out before ranking even starts, not ranked lower. EPA cert level, refrigerant handling, light-commercial comfort: your matrix, your rules.

### Capacity ceilings & conflict detection

A max-jobs-per-day default you can override per technician, plus time-off and business-hours awareness. Anyone already booked in the window is removed automatically — [conflicts are caught before they book](https://docs.fieldcamp.ai/ai-dispatcher/handling-conflicts-and-overlaps).

### Seasonal capacity planning

Use schedule views, job context, and explicit operating rules to plan around busy and slow seasons. Automatic demand forecasting, capacity protection, and calendar rebalancing are not implied.

### Configured customer reminders

Configured confirmations and reminders can support attendance. The exact channels, two-way behavior, triggers, and measured outcome should be verified for the implementation.

### Mobile field app

Techs see the day, open the work order with customer history and parts, capture notes and photos, and take payment from the app — office and field on one live picture.

### Connected operating and accounting context

Work orders use FieldCamp operational records. A separate configured [QuickBooks Online connection](/hvac-software/quickbooks/) supports defined customer, estimate, and invoice workflows.

### Reporting dashboards

Revenue by tech, trade, and job, margins, and tech scorecards — clean data back to ownership, so scheduling decisions are measured, not guessed.

### Travel awareness, and full routing next door

Scheduling weighs travel distance from the technician’s previous job and respects a travel limit you set. Re-sequencing a whole day’s stops to cut driving lives on the [dispatch side](/hvac-software/dispatch/) of the same board.

04 The FieldCamp difference

## One system, from enquiry to *scheduled visit.*

The complaint under every feature list is the same one: work scattered across a calendar, a phone, a spreadsheet, and an accounting package. FieldCamp’s answer is that the enquiry, the request, the job, and the visits are the same chain of records — nothing is re-keyed between them.

Online booking

website enquiry

Service request

captured & triaged

Job

converted

Visits

on the calendar

05 Any size

## Configure scheduling around the *operating model.*

FieldCamp supports multi-site and multi-branch scheduling context because it’s built on a [customizable data model](/customizable-data-model/) rather than a fixed template — start on the out-of-box HVAC layout, then reshape objects, fields, statuses, and workflows to how your operation actually runs.

06 Integrations

## Syncs with the stack *you already run.*

A calendar shouldn’t live in a silo. FieldCamp keeps scheduling in step with your accounting and calendars through separately configured integrations — confirm direction and field ownership during implementation.

Live map · 3 trucksTrackingBTruck B · Riya K.

En route · I-10 E

ETA 3:24ATruck A · Daniel A.

On site · 44 Oak Ct

On siteCTruck C · Marco R.

Stopped · supply house · 12 min

Stopped?“Where is Mike?”

Last known · 5th & Main, 2:41 PM

Found<svg aria-hidden="true" fill="currentColor" height="11" viewbox="0 0 24 24" width="11"><path d="M12 2l1.8 5.4L19 9l-5.2 1.6L12 16l-1.8-5.4L5 9l5.2-1.6L12 2z"></path></svg> ETA texted from the truck’s real position07 Compare

## How to compare *scheduling products.*

Use the same criteria on every product you evaluate — including ours. Verify each competing claim against that vendor’s own current documentation rather than a comparison page.

 | Criterion | FieldCamp | What to ask the other vendor |
|---|---|---|
| Filling the calendar | AI filters on skills, conflicts, capacity, and availability, then ranks and recommends a slot | Does it show availability, or actually recommend the best slot? |
| Explainability | Written reasoning on the suggestion, plus alternatives to compare | Can the CSR see *why* that slot before confirming? |
| Skill enforcement | Exact match required — unqualified techs are filtered out, not ranked lower | Is a skill a hard rule or a soft preference? |
| Recurring seasonal maintenance | Configured recurring jobs or visits tied to service-agreement records | Is it a real recurrence engine or a duplicated job? |
| Online booking | Configured request or job path with service-area logic | What record does a booking create, and who approves it? |
| Data model | Scheduling, dispatch, CRM and invoicing on one customizable model | One record, or modules that sync? |
| Commercial model | AI scheduling is included; AI Dispatcher is a credit-based add-on | What is per-seat, metered, or a paid add-on? |

 08 How to choose

## How to choose HVAC scheduling software — *seven questions.*

Whichever tool you evaluate — including ours — put these to it. If the demo can’t show an answer, the calendar will still be filled by a person.

01

### Does it recommend a slot, or just show gaps?

FieldCamp filters unqualified and unavailable techs out, then ranks the rest and recommends one with its reasoning. Ask whether the other tool decides, or leaves it to you.

02

### Does it handle recurring and seasonal maintenance?

Configured recurring jobs or visits represent seasonal maintenance. FieldCamp does not imply a self-running or self-rebalancing calendar.

03

### Are capacity and skills real constraints?

In FieldCamp a missing skill, a booking conflict, an exceeded daily capacity, or time-off removes a technician from consideration. Confirm any zone, shift, or seasonal-planning rules during implementation.

04

### Does it offer self-booking?

Online booking is a separate intake capability. Supported hours, slot rules, approvals, and the record a booking creates should be configured and verified.

05

### Does it reduce no-shows?

Configured confirmations and reminders can support attendance, but the exact channels, two-way behavior, and measured no-show outcome should be verified.

06

### Does it sync to the field, accounting, and CRM?

FieldCamp connects scheduling to its customer and work records. QuickBooks Online support covers verified customer, estimate, and invoice mappings; confirm direction and field ownership.

07

### Scheduling or design software?

Make sure you’re buying job scheduling, not HVAC design and load-calculation software — they share a search term, not a purpose.

09 The foundation

## Runs on your data model, *not a template.*

FieldCamp’s scheduling runs on the same customizable data model as [dispatch](/hvac-software/dispatch/), [CRM](/hvac-software/crm/), and [invoicing](/hvac-software/invoicing/). [Your job types, zones, availability rules](https://docs.fieldcamp.ai/ai-dispatcher/service-areas-and-zones), and recurring-maintenance plans are configured to how your shop actually runs — residential or commercial, without a developer.

Add a refrigerant-certification field to your technicians and skill matching now enforces *your* matrix, not a preset list. Same system, no re-platform.

<svg fill="none" height="17" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0 0 24 24" width="17"><path d="M3 21h18M6 21V9l6-4 6 4v12M10 21v-4h4v4"></path></svg>Locationthe property · residential or multi-site commercial<svg aria-hidden="true" fill="none" height="14" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.4" viewbox="0 0 24 24" width="14"><path d="M5 12h14M13 6l6 6-6 6"></path></svg><svg fill="none" height="17" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0 0 24 24" width="17"><path d="M12 2 2 7l10 5 10-5-10-5zM2 17l10 5 10-5M2 12l10 5 10-5"></path></svg>Unit → Equipmentmain floor · rooftop · furnace, AC, heat pump<svg aria-hidden="true" fill="none" height="14" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.4" viewbox="0 0 24 24" width="14"><path d="M5 12h14M13 6l6 6-6 6"></path></svg><svg fill="none" height="17" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0 0 24 24" width="17"><path d="M20 21v-2a4 4 0 0 0-4-4H8a4 4 0 0 0-4 4v2M12 11a4 4 0 1 0 0-8 4 4 0 0 0 0 8z"></path></svg>Client & historyevery visit rolls up to the record<svg aria-hidden="true" fill="none" height="14" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.4" viewbox="0 0 24 24" width="14"><path d="M5 12h14M13 6l6 6-6 6"></path></svg><svg fill="none" height="17" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewbox="0 0 24 24" width="17"><path d="M4 7l8-4 8 4-8 4zM4 7v10l8 4 8-4V7"></path></svg>AI dispatcherassigns on your real records10 Glossary

## The scheduling terms that matter.

Scheduling vs dispatching

Scheduling sets when a job happens; dispatching sets who goes and in what route order.

Hard filter vs ranking factor

A hard filter removes a technician from consideration — missing skill, booking conflict, capacity exceeded, time-off. A ranking factor only changes their order among those who remain.

Self-booking

A customer booking their own slot online without an office call.

Recurring maintenance

Repeat jobs or visits created by a configured workflow using service-agreement context.

Capacity planning

Rules limiting how many jobs of a type can be booked per day, zone, or shift — and planning around busy and slow seasons.

Travel limit

A cap you set on acceptable travel for a job, used when the engine ranks candidate technicians.

Service area

The zones a shop covers, used to keep bookings inside serviceable territory.

HVAC design software

A separate category for sizing systems and drawing ductwork (Manual J, duct CAD) — not scheduling.

11 FAQ

## HVAC scheduling software, *answered.*

**What is HVAC scheduling software?**

HVAC scheduling software automates booking, technician assignment, real-time tracking, and customer reminders on one shared calendar — including the recurring seasonal maintenance an HVAC business runs on — and syncs completed jobs to accounting and CRM.

**How does the AI pick a time and technician?**

You enable “Let AI find the best time” on the job form and set the duration, the deadline, and any travel limit. The engine scans every technician’s schedule for that window and eliminates anyone who lacks the required skill, is already booked, exceeds their daily job capacity, or is on time-off or outside business hours. It then ranks the qualified, available technicians by travel distance from their previous job, current workload balance, the customer’s time-window preference, and performance history on similar job types. The best option appears with its reasoning and alternatives; you click Accept and the visit is created.

**Does the calendar fill itself?**

No. The AI recommends a slot and technician, and you confirm it. Recurring maintenance is created by a workflow you configure. The calendar does not rebalance itself on a timer, and automatic demand forecasting or seasonal capacity protection is not implied.

**What’s the difference between scheduling and dispatching?**

Scheduling sets when a job happens; dispatching sets who goes and in what route order. FieldCamp does both on one board — the calendar shares its data model with the AI Dispatcher, so a booked job is already assignable.

**Do I need AI Dispatcher as well?**

Not for day-to-day job creation — the built-in AI scheduling covers that and is included. AI Dispatcher is a separate credit-based add-on aimed at teams handling high volumes of incoming work who want a dedicated dispatch operations centre, with bulk dispatch and route optimization on the same records.

**Does it handle recurring maintenance?**

FieldCamp service agreements store maintenance context. Configured recurring workflows create the required jobs or visits on the cadence you set; the calendar does not fill or rebalance itself by default.

**Can customers book themselves?**

FieldCamp supports a configured online-booking path. Confirm supported hours, service-area logic, slot rules, approvals, and whether the flow creates a request or a job during implementation.

**Can HVAC scheduling software support multi-branch operations?**

Yes. Evaluate branch, service area, job, visit, time, availability, and dispatch handoff. FieldCamp’s customizable model supports operating complexity without crew-size positioning.

**Does it reduce no-shows?**

Configured confirmations and reminders can support attendance, but the exact channels, two-way behavior, and measured no-show outcome should be verified for the implementation.

**Does it sync with accounting?**

FieldCamp has a separate verified QuickBooks Online connection for supported customer, estimate, and invoice workflows. Confirm direction and field mapping during implementation.

**Is this the same as HVAC design or load-calculation software?**

No — HVAC design software (Manual J load calculators, duct-design CAD) is a separate category for engineering a system. HVAC scheduling software books, assigns, and tracks the service work.

**How much does HVAC scheduling software cost?**

Pricing depends on operating requirements and implementation scope. A demo should verify jobs, visits, availability, skill and capacity rules, recurring-work configuration, booking boundaries, and the dispatch handoff.

12 Related

## The rest of the HVAC platform.

[HVAC Software](/hvac-software/)

The whole platform this board belongs to — data model, scheduling, CRM, invoicing, payments.

[HVAC Dispatch](/hvac-software/dispatch/)

The who and the route order — assignment recommendations and route optimization on the same board.

[Online Booking for HVAC](/online-booking/hvac)

The customer-facing intake flow that checks availability and creates the record the scheduler reviews.

[Maintenance ](/hvac-software/maintenance-agreements/)[Agreements](/hvac-software/maintenance-agreements/)

The buyer’s comparison — what to evaluate, and how the category actually differs.

[HVAC CRM](/hvac-software/crm/)

The customer, property, and equipment records every scheduled visit hangs off.

[AI Receptionist](/hvac-software/ai-receptionist/)

Answers the call, triages the urgency, and books into a real slot — nights and heat waves included.

[HVAC Estimating](/hvac-software/estimating/)

Good-better-best quotes that become dispatchable jobs the moment they’re approved.

[HVAC Invoicing](/hvac-software/invoicing/)

The dispatched visit closes into a branded invoice, synced to QuickBooks Online.

[HVAC Dispatching Tips](/hvac-software/dispatching-tips/)

Practical guidance for running the board day to day, whoever is driving it.

Get started

## See scheduling and dispatch share *one operating record.*

Fifteen minutes. Watch AI pick a slot on a live HVAC calendar — skills, capacity, travel, and the reasoning behind the pick — then hand it to the board.

Book a 15-minute call


---

_View the original post at: [https://fieldcamp.ai/hvac-software/scheduling/](https://fieldcamp.ai/hvac-software/scheduling/)_  
_Served as markdown by [Third Audience](https://github.com/third-audience) v3.6.1_  
_Generated: 2026-08-07 12:03:56 UTC_  
