The Lead Nobody Has to Retype: Website Forms That Arrive in ServiceTitan Whole

Four forms, four levels of hurry, one destination

Most contractor sites carry four forms whether anyone planned them or not. Each is written for a different moment in a customer's week, and each deserves its own treatment on the way into ServiceTitan. Treating them alike is how a burst pipe ends up in the same queue as a polite question about gutter guards. The wider picture is on the ServiceTitan integration hub.

Booking, lead form or lead: choosing the door into ServiceTitan

ServiceTitan gives a website more than one way in, and picking the right one is half the integration. Bookings are, in ServiceTitan's words, "incoming inquiries that are funneled to the Calls screen in ServiceTitan," where a customer service rep books each one into a job or dismisses it. The CRM API also has a lead form endpoint, described as "Submits a lead form," and a plain leads endpoint. Each one has its place on a contractor site.

For anything that ends with a truck at a house, we usually send a booking, because it lands where the CSRs already work and a person looks at it before a job exists. For marketing forms, such as a tune-up reminder signup, a lead form fits better. Since December 2025 the API can also convert a booking or a lead into a job by passing its ID when the job is created, which keeps the trail from form to invoice unbroken.

The choice shapes ad reporting, too. In ServiceTitan's Google Ads integration, lead forms and bookings received from the API count as leads, and those sent with a Google click ID are reported to Google Ads as "ServiceTitan Integrated Lead Forms" and "ServiceTitan Integrated Bookings." A form that only emails the office counts as nothing at all. The marketing attribution page shows what that silence does to a monthly report.

The field map, signed before the first line of code

Every form integration we build starts with a field map: a table both sides approve, showing where each answer on the form goes in ServiceTitan. It sounds bureaucratic. It is the cheapest hour in the project, because a mapping argument settled on paper costs nothing and the same argument settled in production costs leads. This is the map we start from for a booking.

The web session travels separately. A second call attaches the landing page, the referrer, any click IDs (Google's gclid, gbraid and wbraid, Meta's fbclid, Microsoft's msclkid), the UTM tags and the Google Analytics client ID to the booking or lead form. That is the difference between a lead whose source is website and one whose source is a specific campaign, keyword and page. One caution: every job in ServiceTitan needs a customer and a location, and the API cannot merge duplicate customers, which is another reason a person should see a booking before it becomes a job.

Spam, typos and the bot that fills in forms at 3 a.m.

A form connected to ServiceTitan takes on a new duty: whatever it sends lands on a real person's screen. An inbox can absorb spam. A Calls screen full of fake bookings costs CSR time every morning and teaches the office to distrust every web lead, including the real ones. So the filtering happens on the server, before anything leaves.

• Validate on the server. Browser checks are a courtesy; the server checks again, because bots skip the browser. A phone number has ten digits, an address has a street, and the summary is not a link to a pharmacy.
• Use a honeypot and a clock. A hidden field that only bots fill in, and a minimum time between page load and submit, stop most automated junk without asking a homeowner to identify buses.
• Limit the repeats. One address sending twenty forms in a minute is not a customer in a hurry.
• Hold the doubtful ones. A submission that fails a soft check goes to a review queue on the site, not to ServiceTitan and not to the trash.
• Say what went wrong. A form that rejects a typo should name the field in plain words and keep everything else the customer typed.

We have written about why forms attract spam and how to stop it without punishing real customers, and our form repair service handles sites whose forms have stopped sending entirely.

When ServiceTitan does not answer, the lead waits in line

Connections fail, and a form integration is judged by what happens next. Access tokens expire after 15 minutes and ServiceTitan issues no refresh tokens, so the server must fetch a new one on time. The rate limit is 600 calls per 10 seconds per application per tenant. A settings change on the ServiceTitan side can break a working connection, and a scope change creates a new app version whose new permissions wait until an admin accepts it. None of that should cost a lead.

1. 1

   The customer presses send

   The browser posts the form to your own site, not to ServiceTitan. The customer sees a thank-you page at once, with the phone number for anything urgent.

2. 2

   The server checks it

   Required fields, formats and spam checks run on the server. Junk stops here and never reaches the Calls screen.

3. 3

   The submission is saved first

   Before anything goes out, the submission is written to the site's own queue under its ID, so no lead exists only in transit.

4. 4

   The send and the receipt

   The server sends the booking and the web session to ServiceTitan, records that both were accepted, and emails the office a short receipt.

5. 5

   Retry, then alert

   If ServiceTitan refuses or times out, the queue retries with growing gaps. Because it records which submission IDs already landed, a retry never doubles a booking. After repeated failures, a person gets an alert that says what broke.

After launch, Argus, the site-watch agent in Athena CMS, watches for failing forms alongside broken links and slow pages. The point is to learn a form broke from an alert on a Tuesday morning, not from a suspiciously quiet phone in March.

Zapier, WordPress plugins and the other shortcuts

There are lighter ways to connect a form, and sometimes they are the right call. ServiceTitan's Zapier integration can book a job or create a task, a job note or an attachment. ServiceTitan says it "is currently in open beta" and is provided "as is," it needs a client ID and secret, and whether your package includes it is a question for ServiceTitan. On WordPress, a WordPress.org search on October 26, 2026 found four plugins mentioning ServiceTitan, none published under ServiceTitan's name; one form plugin, Advanced Form Integration, lists ServiceTitan among its destinations.

The trade-offs of plugin installs get a full page in WordPress vs custom, and the server-side alternative is on the Next.js integration page. If you need data flowing the other way too, the ServiceTitan API page covers custom syncs, and WordPress to Next.js covers the move if the site itself is the obstacle.

What it costs, how long it takes, and which form to fix first

Connecting the forms on an existing site is quoted after a free review. The price depends on how many forms there are, how they route, and whether the site can run server code at all. A connection between two systems typically takes one to three weeks, per our API integrations page. If the forms are part of a new site, custom builds are a fixed price starting at $1,750, and $3,500 for a site with a portal or web app, as the web design pricing page shows, with 0% financing at 25% down.

Fix the form with the most money behind it first. For most contractors that is the estimate request on paid landing pages, because it carries the click IDs that conversion tracking setup depends on. Phone leads deserve the same care on the call tracking page, and booking on the online booking page. Electrical contractors can see trade examples on our electrical industry page, plumbers on plumbing websites.

To start, send us the forms on your site for a free site audit, or ask for the free mockup of a new home page. Or call (210) 346-0848 and tell us what the last web lead looked like when it reached ServiceTitan.