ServiceTitan app for contractors: 5 AI workflows to run this week

A ServiceTitan-using contractor crew is not a one-trade operation — it is the 1-truck ST owner-operator running Pricebook + Job Costing + Membership Auto-Renewal on a tablet in the truck, the 5–15-truck ST dispatcher who runs the morning dispatch board against the skill matrix and ships the day across Schedule Optimization, the multi-region ST enterprise controller auditing Job Costing across regions on Workmanship multiples — and ServiceTitan already runs the request → schedule → dispatch → job → Job Costing → invoice → Membership Auto-Renewal loop; the question is which moments inside that loop deserve a prompt pre-loaded, and which moments deserve the ST operator paying full attention. Below are five AI workflows any ServiceTitan-using contractor crew can put into service this week, with copy-paste prompts you can run in any assistant that takes natural-language input. None of them require leaving ServiceTitan — each one drops into the ST Dispatch Board, Pricebook, Job Costing, Membership, or Customer Communication field you already use — and the broader ServiceTitan playbook (ecosystem overview, daily ST Dispatch Board cadence, 30/60/90 rollout for both a 1-truck operator and a 5–15-truck dispatcher, and the ST failure-mode prompts) lives at /for/service-titan (see /for/service-titan).

1. After-hours emergency dispatch on the ST Dispatch Board

The first 60 seconds of an after-hours call decide whether the homeowner trusts the on-call tech or starts googling the next company on the list — and the ST Dispatch Board is where the call either lands as a clean visit with the right Pricebook line items pre-loaded, or gets re-typed mid-crisis as a generic labour-only line. Use this prompt any time an ST dispatch line picks up the phone outside business hours:

> You are an after-hours emergency-dispatch assistant for a ServiceTitan (ST) using field-service business. A customer has just called with [BRIEF DESCRIPTION OF ISSUE]. In 90 seconds produce: (1) one empathy line that names the disruption without over-apologizing; (2) three triage questions I MUST ask before I create an ST job — focused on safety, accessibility, and whether anyone is on site; (3) one piece of practical advice I can give right now to limit damage before the tech rolls; (4) a warm handoff line that introduces the on-call tech, with the ETA pulled from the ST arrival window. Plain paragraph for the customer-facing portion. Bullets only for the internal triage list.

Run it on every after-hours call for a week and the assistant will start producing the exact opening line your best on-call tech already uses. The four outputs map straight onto ST's job fields — paste the empathy-and-advice paragraph into the ST Customer Communication thread, and the three triage questions into the internal-only ST job note before the tech accepts the dispatch. The Pricebook line items that should ride along (one Wrench bundle, one Wrench + Material bundle if parts are likely) get attached to the ST job at dispatch, not re-keyed by the dispatcher minutes before the truck rolls.

What to do with the output: the empathy-and-advice paragraph goes on the customer's ST Customer Communication thread verbatim. The three triage questions land in the ST job's internal note field before the tech accepts. The handoff line becomes the standing arrival-window message template for any after-hours ST appointment. The Pricebook line items are loaded from the morning-board template — not a fresh dispatch re-key.

2. Job-site quote intake before the ST quote goes out

An underbid repipe, a mis-scoped rewire, a retrofit that surprises on the install day — every ST crew has lost margin on an estimate the dispatcher did not pre-qualify. Use this prompt the moment the customer sits down at the kitchen table or walks the property with a tech:

> I'm at the job site with a [CUSTOMER TYPE] asking for an ST estimate on [QUOTE SCOPE]. They have not yet given me full access. Give me FIVE discovery questions I have not yet asked that, if answered yes, would change the price by more than 15%. For each question: what is the question, why it changes the price, and the price-direction it points. Then list the top three permit / code-compliance flags that trigger a permit pull in [CITY/COUNTY] for this kind of work, with the supporting ST Pricebook item I add to the estimate template so the permit cost lands on the estimate, not as a surprise on the invoice. Then give me the close-without-overcommitting language — one paragraph I can say next that secures the bid walkthrough without committing to a price I have not earned.

Run the prompt on five real ST estimates in a row. The discovery questions will converge on the same five your best senior estimator already asks, and the ST Pricebook item additions will start to repeat. The ST Customer Fields on the estimate (job source, property type, technician of record, service type, recurring flag) are where the discovery answers get captured so the next tech who opens the job sees what was already known.

What to do with the output: the five-question list lands in the ST estimate template as a pre-estimate checklist. The Customer Field captures are added to the ST estimate as required fields. The permit flags become required ST Pricebook items on every estimate that hits a permitted scope. The close-without-overcommitting paragraph is the script the salesperson keeps on their tablet.

3. Tech-on-truck diagnostic walkthrough with the secondary failure-mode check

A tech on a "no cool" / "no flow" / "breaker keeps tripping" / "zone won't hold" suspicion has 60 minutes before the customer starts writing the next check to a competitor — and the diagnostic is the moment a second failure mode hides behind the first. Use this prompt when the diagnosis starts to feel like guessing:

> I'm diagnosing [SYMPTOM] in a [PROPERTY TYPE: SINGLE FAMILY / MULTI FAMILY / COMMERCIAL] with [SYSTEM / INSTALL TYPE]. The homeowner or property contact is on site. Walk me through: (1) the three most likely root causes ranked by probability with the cheap test that distinguishes them; (2) the order I should run those tests to keep the ST invoice honest; (3) what I should tell the contact RIGHT NOW to set expectations on cost and timeline, written into the ST work-order note so it survives the handoff to the next tech; (4) the single worst question I can ask the contact, so I avoid it; (5) the one secondary failure mode that, if I miss it, costs a return visit next week. Plain English — no code section numbers unless I ask.

The ST work-order note field is exactly where the test-order list belongs — paste it in as a numbered list, and the next tech who opens the ST job sees what was tried and in what order. The customer-visible ST job note is where the homeowner-facing cost-and-timeline line goes, so it does not get lost when the tech rolls to the next call. Job Costing reads from this same note when the tech marks the job Complete on the mobile app, so a clean diagnostic note is the difference between a clean job-cost write-down at EOD and a 3-day-late margin question.

What to do with the output: the testing-order list goes on the ST work-order note as a numbered list, not a paragraph. The homeowner-facing cost + timeline line goes on the ST customer-visible job note. The secondary failure-mode check is the one that turns a return-visit into a same-day fix.

4. Maintenance-plan renewal cadence at 60 / 90 / day-of

Recurring revenue is what keeps an ST-using contractor alive in the slow season — and the renewal text that never lands is the renewal that quietly churns. Use this prompt 60 days before an ST Membership Auto-Renewal is set to run:

> A customer on a $[TIER] ST Membership auto-renewal is 60 days out from the renewal date. They have $[ANNUAL VALUE] in completed ST work on file with us over the last 12 months. Their last two tune-ups were [TUNE-UP OUTCOMES]. They have not opened our last two emails. Write me: (1) the day-60 nudge — short SMS (under 160 chars), warm, no discount, that references the last two tune-ups by what we actually did; (2) the day-90 upgrade offer — an email, two paragraphs, an extension price 8–12% above the standard plan, that names the two specific outcomes from the last year; (3) the day-of loyalty upgrade path — a phone-script line, one paragraph, asking if they would like the next-tier membership with the next service date already reserved in their ST calendar. Pair the SMS with a Twilio send (ST's SMS integration), pair the email with a Mailchimp send (ST's Mailchimp integration), and time the Google Reviews request for 14 days after the renewal lands. Plain sentences. Do not sound like a chatbot.

The ST Membership Auto-Renewal trigger holds the renewal itself; the Twilio send holds the day-60 nudge; the Mailchimp send holds the day-90 upgrade email; the Google Reviews request holds the 14-day-after ask. Each one is wired separately, but the cadence is the same shape — and the ST job history is what lets the prompt reference the last two tune-ups by what was actually done, not by a generic recap.

What to do with the output: the day-60 SMS goes in the ST Twilio template slot, the day-90 email lands in Mailchimp via the ST integration, the loyalty-upgrade line goes in the ST renewal-call guide, and the Google Reviews request is set in the ST automation queue 14 days post-renewal.

5. Parts ordering with the lead-time honesty note + ST → QBO / Xero sync line

Lead time is the silent killer of an ST-using service business. A tech staring at a 4-day wait on a part is one short customer text away from a cancellation — and an ST invoice that does not reconcile cleanly into QuickBooks Online or Xero at month-end is the same kind of silent failure. Use this prompt when the tech is staring at the parts catalog, or the day an ST → QBO / Xero sync drops a partial Pricebook line item:

> I'm about to order [PART NAME] for a [JOB TYPE] job on a [PROPERTY TYPE] install. The OEM version is [OEM PRICE + LEAD TIME]; the aftermarket version is [AFTERMARKET PRICE + LEAD TIME]. Help me decide: (1) which version is the right call given [INSTALL ENVIRONMENT / CUSTOMER TIER / WARRANTY POSTURE]; (2) the lead-time question I must ask the parts house RIGHT NOW to guard the customer from a 4-day wait, written as a single sentence I can paste into an email; (3) the price-honesty note I need to add to the ST estimate — a two-sentence written note that explains the price difference AND the lead-time difference to the customer; (4) AFTER the install — if the ST → QuickBooks Online / Xero sync only writes the labour line and stalls on the materials line, write me the exact reconcile script: the QBO-side journal entry that posts the materials line to the same Customer:Job with the same job number, and the one-line ST Customer Communication message I send the customer about the missing line item, and the one-line email I send ST support so the sync retires at the source. Plain prose. No bullet points in the customer-facing portion.

The ST estimate template is where the OEM-vs-aftermarket decision goes as a required field. The parts-desk standing order-notes checklist is where the lead-time question lives. The price-honesty note goes on every ST estimate that includes a premium part. The QBO-side reconcile script runs the first Monday after close when a partial sync surfaces on the ST integration status screen. The ServiceTitan Payments / Stripe payout-split reconcile lives next to it — the merchant fee lands on the ServiceTitan Payments / Stripe side but the QBO deposit line carries the gross, and the bookkeeper needs both halves in the same view.

What to do with the output: the OEM-vs-aftermarket decision goes on the ST estimate template as a required field. The lead-time question goes in the parts-desk standing order-notes checklist. The price-honesty note goes on every ST estimate with a premium part. The QBO / Xero reconcile script lands in the bookkeeper's standing-orders checklist alongside the ServiceTitan Payments / Stripe payout-split reconciliation prompt.

The 30/60/90 rollout

You do not need to roll out all five workflows at once. Run them in this order:

• Days 1–30: after-hours dispatch + parts ordering. Both run on every job without changing how the tech works on site. The wins are clean and the dispatchers see the time savings within the same week. The ST Customer Communication templates gain two saved inserts the team reaches for without prompting. The ServiceTitan Payments / Stripe payout-split reconciliation starts earning its keep the first week.
• Days 31–60: job-site estimate intake. Add the discovery-questions prompt and the price-honesty note to the ST estimate-prep checklist. The first five estimates of the second month will tell you whether the prompt is earning its keep — measure against close rate, not against estimate volume. The Customer Fields on the estimate capture the discovery answers so the next tech sees what was already known.
• Days 61–90: maintenance-plan renewal cadence + the ST → QBO / Xero sync line. Run the renewal cadence against the next wave of Membership Auto-Renewals. Run the QBO / Xero reconcile script the first Monday after every ST sync status screen shows a partial. Run the ServiceTitan Payments / Stripe payout-split reconciliation alongside the reconcile script — the merchant fee lands on the Stripe side but the QBO deposit line carries the gross, and the bookkeeper needs both halves in the same view.

By day 90 the playbook should be the way the team writes ST jobs, estimates, and renewals — not a "tool" they open sometimes. That is when AI becomes part of the business, not part of the software subscription. ServiceTitan's Dispatch Board, Pricebook, Job Costing, Membership, and Customer Communication fields stay the same; what changes is what gets pasted into them.

ServiceTitan plan tiers — what unlocks what

ServiceTitan ships in five public plan tiers — Foundations, Essentials, Starter, Works, and Advanced — and the workflow above changes shape as the shop moves up the stack. The map below is feature-only; consult ServiceTitan's pricing page for the latest dollar amounts:

• Foundations. The foundation tier. The dispatcher-side loop (request → schedule → Dispatch Board → Job → invoice → Membership) is live, Pricebook SKU groupings are populated, and the Customer Fields on jobs, estimates, and customers are populated. This is the tier where the after-hours dispatch prompt (workflow 1) and the tech-on-truck diagnostic walkthrough prompt (workflow 3) start paying off — every ST job and every ST appointment now has the structure to hold the prompt output.
• Essentials. Adds the membership retention loop. Membership Auto-Renewal fires on the anniversary date, Membership dunning runs against the customer's card-on-file with a Twilio-sent SMS escalation, and the ST Customer Communication template slot is wired for the maintenance-plan renewal cadence. This is the tier where the renewal-cadence prompt (workflow 4) starts producing measurable lift — the day-60 SMS template slot holds the nudge and the renewal calendar invitation without a manual send.
• Starter. Unlocks the per-region Dispatch Board + the per-region Membership rollout for the multi-region controller. Skill-matrix-tagged dispatch runs on a single region, tech-specific Pricebook line-item bundles per service truck become available, and the Membership SKU per service line is wired for member retention at shop scale. This is the tier where the parts-ordering prompt (workflow 5) reaches the full-spread form on the single-region shop — the OEM-vs-aftermarket line rides on the estimate template and the ST Customer Communication thread holds the lead-time follow-up.
• Works. Layers Schedule Optimization on top of Starter. Multi-tech assignment rules on the ST Dispatch Board (with geo / drive-time / skill factored in), tech-by-tech Pricebook authoring on the Works+Advanced tiers, and the Schedule Optimization engine ships the morning board in 15 minutes for a 12-visit day across two trucks. This is the tier where the after-hours dispatch prompt reaches its full cadence for the 5–15-truck dispatcher — Schedule Optimization does the day-shape work and the prompt holds the customer-facing lines.
• Advanced. The multi-region enterprise tier. Job Costing audit at the multi-entity level, custom Pricebook / buyers-guide SKU authoring across regions, native QBO job-costing multi-entity sync, the ServiceTitan Payments / Stripe payout-split reconciliation built into the close, and the multi-region ST → QBO / Xero sync with a daily cadence + a weekly summary reconciliation. This is the tier where the parts-ordering prompt (workflow 5) reaches its full synchronized form — the QBO / Xero reconcile script runs the first Monday after every ST sync status screen shows a partial, the ServiceTitan Payments / Stripe payout split lands clean, and the bookkeeper no longer fights a phantom $0.30 per invoice at month-end close.

The right tier for the shop is the one where the workflow lands clean — Foundations for the after-hours + diagnostic pair, Essentials once the Membership Auto-Renewal cadence starts driving renewals, Starter the day the single-region shop needs skill-matrix dispatch and per-truck Pricebook bundles, Works the morning the 5–15-truck dispatcher needs tech-specific assignment rules + Schedule Optimization, Advanced the day the multi-region enterprise controller needs Job Costing audit + native QBO job-costing multi-entity sync.

Get the full ServiceTitan playbook

The contracting playbook this post is drawn from ships with seven workflows — every section above plus the seasonal-tune-up sequencing memo for HVAC, the cross-trade callback cadence for landscapers, the panel-capacity audit memo for electricians, and the diagnostic handoff memo for plumbing — and 30+ copy-paste prompts engineered for the exact moment a ServiceTitan-using service team needs them. Subscribers receive updates and billing details according to the current catalog. Review the refunds and cancellation policy before purchase.

[Open the ServiceTitan playbook](/checkout/service-titan)

The full ServiceTitan surface — ecosystem overview, daily ST Dispatch Board cadence, 30/60/90 rollout (for a 1-truck ST owner-operator, a 5–15-truck ST dispatcher, AND a multi-region ST enterprise), and the failure-mode prompts — lives at /for/service-titan (see /for/service-titan).