Your Website Should Feed ServiceTitan, Not a Shared Inbox

The contact form that emails a shared inbox is not an integration

Here is what passes for a ServiceTitan website integration on a great many contractor sites. A contact form sends an email to a shared inbox. Someone reads it between calls and types it into ServiceTitan by hand. The subject line says New Submission. The name is in all caps. The phone number is missing a digit about as often as you would fear, and nobody finds out until the callback fails.

The typing is the smallest cost. The larger ones never show up on an invoice. The lead sits in the inbox while the first business to answer gets the job. The Google click ID that arrived with the visitor never leaves the browser. And when the record finally reaches ServiceTitan, its source says "website," which is true in the way "North America" is a true mailing address.

ServiceTitan can only credit the marketing it was told about.

None of this is ServiceTitan's fault, and none of it takes exotic engineering to fix. ServiceTitan is a public company whose latest annual report counts "approximately 10,800 Active Customers" (customers with over $10,000 of annualized billings, as of January 31, 2026), and it publishes an API for exactly this job. Its developer documentation even names the case: a custom widget on your website can use the bookings endpoint. The work is using it properly.

Seven handoffs a contractor website can make

An integration is not one connection. It is a set of small handoffs, each with its own place in ServiceTitan and its own way of going wrong. These are the seven that matter on a contractor site, roughly in the order owners ask about them. Each has its own page in this section.

• Online booking. A customer picks a service and a window, and the request lands on the Dispatch Board or the Calls screen instead of in an email. Scheduling Pro does this, and so can a custom flow built on the API; the trade between them is on the online booking page.
• Forms. Estimate requests, callbacks, contact and emergency forms arrive as bookings or lead forms, checked and with their source attached. The field map and the failure handling are on the web forms page.
• Calls. Tracked numbers tie a phone call to the page and the ad that produced it, and then to the job that followed. Call tracking covers ServiceTitan's own numbers and CallRail's certified app.
• Ad attribution. The site catches the click ID from Google, Meta or Microsoft on arrival and sends it with the lead, so revenue can flow back to the ad account. See Google Ads conversion tracking, Meta ads and Local Services Ads.
• Reviews. A finished job triggers the request, and the good reviews end up on the service and town pages where buyers read them. The reviews page lists which tools do the triggering.
• Memberships. The maintenance plan sells on the website and arrives in ServiceTitan as a membership sale, not a sticky note on a monitor. See memberships.
• The customer portal. Customers check invoices and history through ServiceTitan's portal or a branded one on your own site, as the customer portal page explains.

What ServiceTitan covers on its own, and where the website build starts

Give the software its due first. ServiceTitan ships a good deal of this itself, mostly as Pro products the contractor licenses from ServiceTitan, which publishes no prices for them. A website build does not replace those tools. It decides whether they work on your actual pages, with your actual tracking, or only in the sales demo.

Read the right-hand column as the gap between owning a tool and having it plugged in. Scheduling Pro behind a button that reloads the page still books jobs, but ServiceTitan's own install guide warns that the link-style install "can disrupt lead source tracking." Most integration work on a contractor site is that sort of detail, found and fixed a dozen times over.

One-way traffic: how the connection works today

The mechanics decide what a website can promise, so here they are. ServiceTitan's API accepts only the OAuth 2.0 client credentials grant. Access tokens expire after 15 minutes, no refresh tokens are issued, and ServiceTitan recommends caching them. Every call carries the token plus an app key. The published rate limit is 600 calls per 10 seconds per application per tenant, outside the reporting APIs. All of that belongs on a server, which is one reason the keys should never sit in a browser.

The other fact is about direction. The main API has no webhooks today. ServiceTitan's FAQ says "V2 webhooks are currently being developed" and gives no date, and all 25 API families in the portal's catalog were listed without webhooks as of October 26, 2026. So a website pushes into ServiceTitan, and where it needs something back, such as open capacity or a job's status, it asks on a schedule within the rate limit. Scheduling Pro has two webhooks of its own, in Private Preview.

Access is the contractor's to give. Whether your ServiceTitan package allows API use is between you and ServiceTitan, and its own pages disagree about which packages qualify, so ask your ServiceTitan contact rather than a blog. The connection is approved by your admin, in your account, under Settings > Integrations > API Application Access, where ServiceTitan shows the requested scopes and offers Allow or Decline. The whole program is laid out on our ServiceTitan API page.

Fifteen pages, one per problem: find the one that sounds like your office

This section is built so you can skip most of it. Find the line below that sounds like last Tuesday in your office and start there. Every page links back here and across to the others, so the rest is one click away when the first answer raises a second question.

How we build it, and two builds that already talk to ServiceTitan

DataCram is a web studio in San Antonio, Texas. We build custom sites on Next.js with our own content system, Athena CMS, and we run SEO, ads and local marketing for businesses across the US. We are not a ServiceTitan partner and we are not listed in its Marketplace. We build the website side and connect it through ServiceTitan's published API with your approval, the way our API integrations service connects any two systems.

Both are in our work. The method behind them is the same on every project, and it is deliberately unglamorous:

1. 1

   A free review and a written field map

   We look at what the site sends today and agree, on paper, which form field goes to which ServiceTitan field before anyone writes code.

2. 2

   Tests against a copy of your data

   Your admin can request ServiceTitan's integration environment, which holds a copy of your production data, so testing never touches a live customer.

3. 3

   A connection that lives on the server

   Leads are validated on the server before anything is sent. Keys stay there too. Writes are idempotent, so a retry never makes a second booking.

4. 4

   Queues, retries and logs in plain words

   A failed send is queued and retried, never lost, and the log says what happened in sentences a person can read.

5. 5

   Your approval, then production

   Your admin approves the app and its scopes in ServiceTitan. We switch to production credentials and watch the first real bookings arrive.

After launch, Argus, the site-watch agent in Athena CMS, flags failing forms, broken links and slow pages. That is how a quietly broken booking button gets noticed on a Tuesday instead of at the quarterly review, in front of the dashboard nobody opens.

Rebuild the website, or connect the one you already have

You do not need a new website to connect ServiceTitan. Scheduling Pro installs on custom sites, WordPress, Wix, Squarespace, GoDaddy and Duda, and ServiceTitan documents each one. What an existing site may lack is a safe place to run server code, which is where booking flows, form queues and click-ID handling live. Some sites have that already. Many builder sites do not, and no amount of plugins will give it to them.

When the site is old, slow or held together by plugins, a rebuild often costs less than wiring around it. Our Next.js approach keeps the connection on the server. If you are weighing a move, WordPress to Next.js explains the migration and should I leave WordPress makes the case for staying, too. The trade pages show what we build for HVAC, plumbing, electrical and roofing companies, and home services covers the rest.

Prices, financing and a free first step

Custom builds and rebuilds are a fixed price starting at $1,750. Sites with a store, portal or web app start at $3,500, and a site with online booking or an estimate flow is about $9,000 on our web design pricing page. Integration work on an existing site is quoted after a free review, and a connection between two systems is typically one to three weeks. Ongoing care runs on our hosting and maintenance plans, with no long contract.

Financing is 0% with 25% down, for up to 12 months, through website financing. On a $9,000 site that is $2,250 down and $562.50 a month for twelve months. Tracking work has its own pages: conversion tracking setup, PPC advertising and local marketing, which starts at $500 a month. Your ServiceTitan subscription and any Pro products stay between you and ServiceTitan.

The cheapest way to start is to look. Ask for the free mockup of your home page, run a free site audit on the site you have, or call (210) 346-0848 and describe how a lead travels from your website to your dispatch board today. Most owners have never traced it end to end, and the trace alone is worth the call.