How to Use ServiceTitan Forms to Cut Callbacks, Win Rebates, and Standardize Every Job
If you're running an HVAC, plumbing, electrical, or garage door business on ServiceTitan and you're not using Forms yet, you're leaving efficiency — and money — on the table. Forms are one of the most underused features in ServiceTitan, and the businesses that have figured them out are using them to catch missed pressures before a callback, secure utility rebates that require photo proof, and keep two hundred field techs answering the same questions the same way.
We recently sat in on a ServiceTitan Torch Network session dedicated entirely to Forms, where contractors and consultants shared how they're using the feature in production. Watch the full webinar here. Below, we've pulled together the practical takeaways.
What ServiceTitan Forms Actually Do
At a basic level, a form is a structured set of questions your office staff or technicians fill out — tied to a job, a customer, a location, or a technician directly. But the feature goes well beyond a digital checklist. Forms in ServiceTitan can:
Require an answer before a technician can complete a job
Auto-populate fields using Smart Fields (customer name, equipment model, balance, and more)
Apply tags to a job, customer, or location based on how a question was answered
Trigger automatically based on job status (arrived, invoiced, closeout, or "perform work later")
Include photos, signatures, dates, and even embedded HTML
Feed into a dedicated reporting dataset so you can analyze form responses in bulk
The Feature Most Businesses Miss: Conditional Logic
The single biggest lever for making forms actually get used — instead of ignored — is conditional logic. Rather than handing a technician a hundred questions regardless of the job, conditional logic shows only the questions relevant to what they're actually doing.
Channing Morrison, a project manager for Barron Heating, Air Condition, Electrical and Plumbing who oversees ServiceTitan across multiple trades, described building a single sales lead turnover form that expands or collapses based on the scope of work selected. Quote a simple hot water tank, and the tech sees a handful of questions. Quote a heat pump with solar, and the form expands to include every additional field that scope requires. The result: fewer skipped questions, more complete information, and a sales team that actually fills the thing out.
As Channing put it during the session, "too much information is no information at all" — people stop reading past a certain point once a form gets cluttered. Conditional logic — not fewer features, but smarter sequencing — is what keeps a form usable as it grows.
Using Forms to Protect Utility Rebates
Several presenters described using forms specifically to satisfy documentation requirements tied to utility rebate programs — heat pump compliance being a common example. The pattern:
A tag is applied to the job when it qualifies for a rebate program
That tag triggers a required form the moment the technician marks the job "arrived"
The technician is blocked from completing the job until required photos (before/after, gauge readings, model and serial numbers) are uploaded
For a $1,500 rebate, that structure is the difference between money collected and money left on the table because a technician forgot to take a photo mid-job.
Forms as a Callback Prevention Tool
A well-built form doesn't just collect data — it can flag problems before they become callbacks. One example from the session: a form question asking for static pressure after an install, where a high reading automatically applies a tag and fires an internal alert email so the sales or design team can follow up with the homeowner before it turns into a comfort complaint.
Another contractor uses an outdoor temperature field on maintenance forms — if the reading falls below a threshold, a "low ambient conditions" tag is applied automatically. If a callback happens later, the office can immediately see the temperature conditions the original visit was performed under, rather than relying on a technician's memory.
How Do You Know When You Need a New Form?
Zach Kays, Titan Wizards' lead ServiceTitan consultant, put it simply during the session: a form is usually needed the moment you keep hearing "I wish we had more insight on this" from your team. If that phrase is coming up in daily operations, it's a sign there's a gap in what's being captured — and a form is the fix.
This is the same discipline we build into the capacity planning work we do with clients: the platform should be capturing exactly the information the business needs to make decisions, no more and no less.
Don't Start From Scratch
Two shortcuts came up repeatedly:
Titan Exchange: ServiceTitan's built-in library of pre-built forms, available once you subscribe to a network under Settings → Titan Exchange. Contractors described starting with a pre-built form and modifying it rather than building from zero.
AI-assisted form building: Several attendees described exporting an existing form (forms export as JSON), feeding that structure to an AI tool along with a PDF they wanted converted, and asking it to produce a new ServiceTitan-compatible form. The main caution shared: be explicit in the prompt that the output must stay within ServiceTitan's JSON format, since general JSON conventions don't always match what the platform accepts.
A Practical Tip Before You Touch a Complex Form
If you have a form with heavy conditional logic, export a copy before you start editing it. If something breaks mid-edit, you can revert to the last working version instead of rebuilding rules from memory. For very large forms — some businesses are running forms with 300+ conditional logic rules — that backup step matters.
Reporting on Forms
Once you've been running a form for a while, ServiceTitan's Form Submissions reporting dataset lets you analyze responses in bulk rather than opening jobs one at a time. One tip worth keeping in mind: leave the Form ID field checked in your report — it gives you a direct hyperlink back to the original submission, including any photos attached, without having to search for the job manually.
Where This Fits Into Your Broader ServiceTitan Setup
Forms work best when they're part of a deliberate system — tied to your business's actual workflow, not bolted on as an afterthought. That's the kind of structural work we help HVAC, plumbing, electrical, and garage door businesses with every day as part of ourServiceTitan consulting services: making sure the platform reflects how the business actually operates, from lead intake through job completion and retention.
If you want help auditing your current ServiceTitan setup — forms included — reach out to Titan Wizards.
FAQ
-
Native forms are built directly inside ServiceTitan and retain full functionality — conditional logic, tags, triggers, and reporting. PDF forms can look more polished but lose some of that native functionality.
-
Yes. Marking a field as required — including photo, signature, or number fields — blocks job completion until that field is filled in. This is commonly used for rebate documentation and before/after install photos.
-
No. Conditional logic can add tags to jobs, customers, and locations, but it cannot remove them automatically. Job-level tags are generally safe to add freely since they stay tied to a specific job record; tags on customers or locations need to be removed manually, so they're worth using more carefully.
-
Under Settings → Titan Exchange → Library, once you've subscribed to at least one network. Pre-built forms can be imported and customized rather than built from zero.
-
Yes. Since forms export in JSON format, some businesses export an existing form, provide it to an AI tool as a formatting reference, and ask it to build a new form or convert a PDF into ServiceTitan's format. It's important to instruct the AI to preserve ServiceTitan's specific JSON structure rather than applying generic JSON conventions.
