For ServiceTitan operators

For ServiceTitan.
AI workflows that keep the dispatch → job → cost → invoice loop clean.

The SkillForge AI ServiceTitan playbook is field-service specific on purpose — ecosystem overview, daily ST Dispatch Board cadence, rollout guidance, and failure-mode coverage for the ServiceTitan operator running QuickBooks Online / Xero as the native job-costing-aware sync, ServiceTitan Payments (Stripe-tied) for the merchant deposit split, Twilio SMS for the customer text cadence, Zapier for the side-app connector glue, and Google Reviews request for the post-job review ask. Written for the 1-truck ST owner-operator who needs the morning Dispatch Board to ship in 15 minutes, the dispatcher / ops manager at a 5–15-truck ST shop who needs Tuesday’s Job Costing closeout to land without a partial-sync fire drill, the multi-region ST enterprise operator mapping the rollout to the published Pricing tiers Foundations/Essentials/Starter/Works/Advanced, and the ST-aware bookkeeper who runs both the ST side and the QBO / Xero side. No generic SaaS advice. Just the prompts the ST shop pastes into chat today.

What subscribers say

From the field.

“The first workflow I tried paid for the playbook inside the first week. I did not expect a plain prompt to out-perform the spreadsheet I had been refining for two years.”
— Owner-operator, service-truck shop
“The 30/60/90 adoption plan is the part I actually use. It kept me honest about putting the prompts to work daily instead of letting the PDF sit on a shelf.”
— Service manager, small crew
“The team rollout was easier than I thought. We picked two champions, ran the first workflow for a week, then widened. By day thirty the prompts were part of the morning.”
— Operations lead, multi-trade business

What the playbook covers

Four workflows that run an ST shop.

Built around the moments that decide whether the morning ST Dispatch Board ships with the right tech on the right job with the right Pricebook line items pre-loaded from the estimate, whether a partial ST → QBO job-costing sync drop is caught before the books close, whether the 30/60/90 rollout lands a 1-truck ST operator OR a 5–15-truck ST shop OR a multi-region ST enterprise without a Pricebook SKU re-build, and whether the Membership Auto-Renewal dunning / technician-skill- mismatch / Pricebook SKU drift / ServiceTitan Payments / Stripe split-fee gap is caught before close — not the moments an ST demo likes to talk about.

Pillar 1

Ecosystem overview: what sits around ServiceTitan and what each app actually does.

A ServiceTitan ecosystem map — from the ST core (Dispatch Board → Pricebook → Job Costing → Memberships → Reporting) through the apps that touch it: QuickBooks Online / Xero for the native job-costing-aware sync into the bookkeeper ledger, ServiceTitan Payments (Stripe-tied) for the merchant-side deposit split, Twilio SMS for the customer text cadence, Zapier for the connector glue to back-office tools that ST does not natively bridge, Google Reviews request for the post-job review ask, and the ServiceTitan-to-Zapier connector for the side-app glue (PSA tools, marketing automation, post-job member nurture). Written for the ST operator who needs to know which sync writes to the customer ledger in QBO / Xero, which writes to Undeposited Funds, which writes to the payout side of ServiceTitan Payments / Stripe, and what each app leaves in a side app ST never reconciles. Trade-specific notes call out which Pricebook SKU groupings to wire first (the Wrench → Wrench + Material bundle pattern, the Membership SKU per service line), how Job Costing layers on top of a Pricebook line item, and what stays in a manual monthly entry because no integration does it well yet.

Pillar 2

Daily ST Dispatch Board cadence: morning dispatch, EOD job-costing closeout, weekly unconverted-estimate follow-up.

A daily ST cadence that holds the Dispatch Board → Job → Job Costing → invoice loop clean — morning Dispatch Board run that loads the right tech (matched by skill, capacity, and geo) on the right job with the right Pricebook line items pre-populated from the estimate (not re-keyed by the dispatcher minutes before the truck rolls), end-of-day Job Costing closeout that fires the moment the technician marks the job Complete on the mobile app (so the job-cost write-down lands on the same business day, not at morning coffee two days later, and the QBO job-costing-aware sync gets a clean source row by Tuesday morning), the weekly unconverted-estimate follow-up that ages the estimate from 'Sent' to 'Reminder' at day 14 to 'Follow-up phone' at day 30 so a stale estimate can't quietly age past 60 days, and the monthly QBO / Xero reconciliation handoff that gets the day's Job Costing entries onto the customer ledger by Tuesday morning. The cadence distinguishes what fires from the ST Schedule Engine vs. what fires from a manual trigger in Zapier vs. what fires from ServiceTitan Payments reporting — so the ST shop sees which step needs ST automation vs. a one-off prompt run from the playbook, and crucially distinguishes Membership Auto-Renewal reminders from one-off job reminders so the member retention loop does not contaminate the one-off dispatch loop.

Pillar 3

Rollout guidance: a 30/60/90 for the 1-truck ST operator, the 5–15-truck ST shop, AND the multi-region ST enterprise.

A 30/60/90 adoption plan that ships in the first quarter — three distinct rollout shapes because ST shops are larger on average than HCP / Jobber shops and the multi-region case is a real persona, not a hypothetical: (a) the 1-truck ST owner-operator hits Foundations → Pricebook SKU groupings → Job Costing → Membership Auto-Renewal in four steps; (b) the 5–15-truck ST dispatcher layers in Schedule Optimization on Works+Advanced, skill-mismatch dispatch rules, tech-specific Pricebook line-item bundles, Membership Auto-Renewal on Essentials+, and the ST Payments / Stripe payout split reconciliation before the QBO job-costing sync lands on day ninety; (c) the multi-region ST enterprise runs the rollout as a tier-aware adoption — Foundations for the back-office / reporting side, Essentials for the per-region Membership Auto-Renewal + native QBO job-costing aware sync, Starter for the per-region Dispatch Board, Works for Schedule Optimization + custom Pricebook SKU groups per region, and Advanced for Job Costing audit, custom Pricebook/buyers-guide SKU authoring, and native QBO job-costing multi-entity sync — with the multi-region rollout mapped to the published ST Pricing tier ladder so each regional controller sees the right tier decision for their region. Same playbook family; the milestone shape is ST-tier-specific to the shop size — and Advanced is the tier that unlocks Schedule Optimization, Membership rollouts at the multi-region scale, and the Job Costing audit the multi-region enterprise controller needs once the morning Dispatch Board is shipping clean across all regions.

Pillar 4

Failure modes: silent ST → QBO job-costing partial-sync drops, Membership dunning, technician-skill mismatches.

Failure-mode prompts that catch the five ST failures that hit a field-service shop every quarter: the silent ST → QBO job-costing sync drop on a partial Pricebook line item (the labour line synced cleanly, a materials line stalled mid-export with no error surfaced on the ST side and no error surfaced on the QBO side — so the monthly job-cost margin silently overstates contribution by the missing material); the Membership Auto-Renewal dunning drift (a member's card expired, the auto-renewal quietly failed, the member's next service visit invoice hits a non-renewed customer status, and the ops team realises a week after the customer signed off on the renewal); the technician-skill-mismatch dispatch (the dispatcher assigned the wrong tech to a backflow preventer job because the skill matrix in ST was never kept current, the job went out at the morning board, and the customer got a second truck rolling mid-day to fix what tech #1 could not); the Pricebook SKU drift (the dispatcher mid-quarter quietly edited a Wrench line to bundle a compressor replacement, the silent SKU change bumped the invoice gross by $4,200 and the customer invoice no longer matches the original estimate); and the ServiceTitan Payments / Stripe split-fee reconciliation gap where the merchant fee lands on the ServiceTitan Payments / Stripe side but the QBO deposit line carries the gross, so the QBO / Xero reconciliation picks up a phantom $0.30 per invoice and won't fully close at month-end. Each failure mode ships as a one-page prompt the ST operator runs the first Monday after close.

Plan-to-feature matrix

Which trade-critical ST features sit on which Pricing tier.

Schedule Optimization is gated to ServiceTitan Works and Advanced — not to Foundations, Essentials, or Starter. Membership Auto-Renewal lands on Essentials and up. Job Costing audit, custom Pricebook / buyers-guide SKU authoring, and native QBO job-costing multi-entity sync live on Advanced only. A ServiceTitan operator who already runs ST can scan the matrix below and answer “does my current Pricing tier support the workflow I need?” before the next quarterly Membership renewal cycle hits.

ServiceTitan

Foundations

Price undisclosed by brief

ServiceTitan

Essentials

Price undisclosed by brief

ServiceTitan

Starter

Price undisclosed by brief

ServiceTitan

Works

Price undisclosed by brief

ServiceTitan

Advanced

Price undisclosed by brief

Trade-critical feature

Schedule Optimization

Schedule Engine + optimization pass that re-orders the morning Dispatch Board by tech skill, capacity, and geo/drive-time — the multi-tech dispatch the multi-region ST enterprise needs before the morning board ships.

Get Works →
Get Advanced →

Trade-critical feature

Membership Auto-Renewal

Member retention loop — automatic card-on-file renewal, dunning emails on a failed-payment cadence, and the auto-renewal failed-payment reconciliation the multi-region ST shop runs weekly on the Membership dashboard.

Get Essentials →
Get Starter →
Get Works →
Get Advanced →

Trade-critical feature

Job Costing audit

Per-job cost review pass — labour vs. material vs. commission margin per job, with the audit log the regional controller uses before the monthly job-cost handoff to QBO / Xero; foundational for any multi-region ST shop running on Advanced.

Get Advanced →

Trade-critical feature

Custom Pricebook / buyers-guide SKU

Custom Pricebook SKU authoring + a buyers-guide surface where the regional controller can author SKUs that ship to the dispatcher with a quoted total — unlocks the ST Pricing-tier Advanced buyer-facing rollouts.

Get Advanced →

Trade-critical feature

Native QBO job-costing aware sync

ServiceTitan → QuickBooks Online export that lands Job Costing line items on the right QBO Customer:Job with the right Class — the connector the multi-region ST shop needs so the Tuesday morning QBO reconciliation closes cleanly.

Get Essentials →
Get Starter →
Get Works →
Get Advanced →

Trade-critical feature

Dispatch Board assignment rules

Skill-matrix / capacity / geo rules that assign the right tech to the right job on the morning Dispatch Board — the dispatcher automation the 5–15-truck ST shop layers in before the inventory + Membership loop lands.

Get Essentials →
Get Starter →
Get Works →
Get Advanced →

Common ServiceTitan questions

The questions ServiceTitan operators ask before they buy.

What does the ServiceTitan surface overview actually cover if I'm already a daily ST user?
It maps every app that touches the ST core — QuickBooks Online / Xero for the native job-costing-aware sync, ServiceTitan Payments (Stripe-tied) for the merchant-side deposit split, Twilio SMS for the customer text cadence, Zapier for the side-app connector glue, Google Reviews request for the post-job review ask, and the ServiceTitan-to-Zapier connector for back-office tools ST does not natively bridge — to the moment in the ST daily cadence it actually fires at. Trade-specific notes call out which Pricebook SKU groupings to wire first (the Wrench → Wrench + Material bundle pattern, the Membership SKU per service line), how Job Costing layers on top of a Pricebook line item (the silent materials-line drop and the inspector-rate-labor override are the two ST-specific traps), and what stays in a manual monthly entry because no integration does it well yet. The point is not "here are the apps"; it is "here is what each app actually writes to on the ST side and where the operator needs to check the books after every sync.
How does the playbook help with the morning ST Dispatch Board — assigning the right tech (matched by skill, capacity, and geo) to the right job, with the right Pricebook line items pre-loaded from the estimate?
The ST Dispatch Board prompt walks the operator / dispatcher through a morning run — read the day's assigned jobs, confirm each job has the technician (matched to the skill matrix), the service window (with geo / drive-time factored in), and the Pricebook line items that match the estimate the homeowner signed (not a generic Pricebook bundle that was the dispatcher default), batch-assign the unassigned jobs, fire the morning Twilio SMS to each homeowner with the ETA and the technician name, and confirm Schedule Optimization (on the Works+Advanced tier) did not re-order the board to break a tech's lunch mid-day. The prompt also walks the operator through the Pricebook line-item re-keying trap — the estimate that was sent with a labour + material bundle but the dispatcher created the job with a Labour-Only line, so the Job Costing closeout will silently under-bill the materials unless the dispatcher catches it at the morning board. Designed for the morning the ST shop wakes up to a 14-job day and the dispatcher needs to ship the board in 15 minutes: what to confirm, what to batch, and what to leave for the tech to handle at the truck.
What does the 30/60/90 rollout look like for a 1-truck ST operator vs. a 5–15-truck ST shop vs. a multi-region ST enterprise?
The 1-truck ST owner-operator rollout ships a four-step plan — week one on the Pricebook SKU groupings that matter most (Wrench → Wrench + Material bundle, Membership SKU per service line), day thirty on Job Costing enabled at the per-job level with a clean Pricebook foundation, day sixty on Membership Auto-Renewal wired on Essentials+ for the member retention loop, day ninety on the ST Payments / Stripe payout split reconciliation with the QBO job-costing-aware sync cadence landing a daily invoice push + Job Costing closeout. The 5–15-truck ST shop rolls out Foundations → Starter on week one, then layers in Schedule Optimization on Works+Advanced (the multi-tech dispatch + skill matrix), tech-specific Pricebook line-item bundles per service truck, Membership Auto-Renewal at the shop level (Essentials+), and the unconverted-estimate aging cadence before the QBO job-costing sync lands on day ninety. The multi-region ST enterprise runs the rollout as a tier-aware adoption — Foundations for back-office / reporting, Essentials for per-region Membership + native QBO job-costing aware sync, Starter for the per-region Dispatch Board, Works for Schedule Optimization + custom Pricebook SKU groups per region, Advanced for Job Costing audit + custom Pricebook/buyers-guide SKU authoring + native QBO job-costing multi-entity sync — so each regional controller sees the right tier decision for their region. Same playbook family; the milestone shape is ST-tier-specific to the shop size.
How does the playbook help when a partial Pricebook line-item sync drops silently in the ST → QBO / Xero job-costing handoff?
The partial-sync prompt runs the moment the operator opens ST to the day's Job Costing closeouts — read ST's QBO / Xero sync status for the prior day, identify any job where the sync shows 'Complete' on the ST side but the corresponding QBO job-costing row is missing a Pricebook line item (typically a materials line dropped mid-export while the labour line landed cleanly), post the missing Pricebook line-item manually to the QBO side (with the same job number and the same Customer:Job so the operator's reconciliation script can match it), fire a one-line ServiceTitan Customer Communication message to the homeowner about the corrected Job Costing line so the homeowner is not surprised by the adjusted invoice total, flag the partial sync to the ServiceTitan support queue so the sync retires at the source, and post the same reconcile check the next morning as a recurring task until the partial sync resolves upstream. Trade-specific notes: a partial labour-line vs. partial materials-line drop behaves differently per ST pricing-tier export version — ST Pricing tiers route the job-costing export through different connectors (Starter through native connector, Works+Advanced through the multi-entity connector with audit table), so the operator sees the right shape for their tier.
What failure modes does the playbook cover beyond partial-sync drops?
Five, each with a one-page prompt the operator runs the first Monday after close: (1) the silent ST → QBO job-costing partial-sync drop covered above; (2) Membership Auto-Renewal dunning drift — a member's card expired, the auto-renewal quietly failed, the member's next service visit invoice hits a non-renewed customer status, and the ops team realises a week after the customer signed off on the renewal; (3) technician-skill-mismatch dispatch — the dispatcher assigned the wrong tech to a job because the skill matrix in ST was never kept current, the job went out at the morning board, and the customer got a second truck rolling mid-day to fix what tech #1 could not; (4) Pricebook SKU drift — a dispatcher mid-quarter quietly edited a Wrench line to bundle a compressor replacement, the silent SKU change bumped the invoice gross by $4,200 and the customer invoice no longer matches the original estimate; (5) ServiceTitan Payments / Stripe split-fee reconciliation gap — the merchant fee lands on the ServiceTitan Payments / Stripe side but the QBO deposit line carries the gross, so the QBO reconciliation picks up a phantom $0.30 per invoice and won't fully close at month-end. Each prompt is a quick scan, not a full audit.
How does the playbook roll out across a multi-region ST enterprise with multiple regional controllers and a QBO-aware bookkeeper?
The multi-region ST enterprise rollout ships as a tier-aware 30/60/90 with a QBO-side parallel — week one runs on the back-office / reporting side with Foundations so each region's controller inherits a common reporting surface, day thirty wires the per-region Membership Auto-Renewal + native QBO job-costing aware sync on Essentials+ while the QBO-side bookkeeper stands up the daily job-cost handoff journal entry per region (or the ST Pricing tier multi-entity connector on Advanced lands the multi-entity QBO job-costing sync, picking the right tier for the regional controller), day sixty layers in the per-region Dispatch Board on Starter with skill-mismatch + Schedule Optimization rules on Works+, day ninety lands the multi-region coordination pattern: Schedule Optimization rollout across all regions on a coordinated date, Job Costing audit on Advanced for the regional controller who's ready for it, custom Pricebook / buyers-guide SKU authoring on Advanced for the buyer-facing rollouts, and the ServiceTitan Payments / Stripe payout split reconciliation on each region's QBO side. Same playbook family; the milestone map is enterprise-region-shaped so the per-region controller's daily ST cadence and the multi-region bookkeeper's weekly QBO job-costing reconciliation stay aligned across all regions.

ServiceTitan integration plan

Get the ServiceTitan integration playbook.

The ServiceTitan integration playbook bundles the ecosystem overview (Dispatch Board → Pricebook → Job Costing → Memberships → Reporting), the daily ST Dispatch Board cadence (dispatch → Job → Job Costing → invoice), the tier-aware 30/60/90 rollout for a 1-truck ST operator, a 5–15-truck ST shop, AND a multi-region ST enterprise (Foundations → Essentials → Starter → Works → Advanced), and the failure-mode prompts (silent ST → QBO job-costing partial-sync drops, Membership Auto-Renewal dunning, technician-skill-mismatch dispatch, Pricebook SKU drift, ServiceTitan Payments / Stripe split-fee reconciliation gaps) into one ServiceTitan-specific surface — built for the 1-truck ST owner-operator, the 5–15-truck ST dispatcher / ops manager, the multi-region ST enterprise operator, and the ST-aware bookkeeper feeding QuickBooks Online / Xero.

ServiceTitan integration plan
One trade-specific plan that ships the full ServiceTitan playbook — ecosystem map, daily ST Dispatch Board cadence, tier-aware 30/60/90 rollout (for a 1-truck ST operator, a 5–15-truck ST shop, AND a multi-region ST enterprise), and the failure-mode prompts — for a single-truck ST owner-operator, a 5–15-truck field-service shop on ST, a multi-region ST enterprise controller, or an ST-aware bookkeeper running both the ST side and the QBO / Xero side. Quarterly subscription by default at $199/qtr.
Get the ServiceTitan playbook

Not ready to chat with us yet?

Get the ServiceTitan workflow checklist — free email.

Drop your email and we’ll send the free ServiceTitan workflow checklist straight to your inbox — the same ST-integration prompts (daily Dispatch Board cadence, tier-aware 30/60/90 rollout, failure-mode detection for silent ST → QBO job-costing sync drops and Membership Auto-Renewal dunning) at the front of the playbook. Paste each one into ChatGPT, Claude, or Gemini and run it today. We’ll email again the day the full ServiceTitan integration playbook ships.

The checklist is the requested resource. Any later optional playbook follow-up includes the unsubscribe path described above.

Try the free workflows before you buy

A peek at what the playbook ships -- free.

The same workflows ship at the front of your trade’s downloaded PDF -- paste each prompt into any AI tool, ship a draft today. Lock the rest of the playbook when you’re ready.

Free workflow

Emergency Call -- The 11pm Same-Night Dispatch

A two-step workflow that responds to a weekend emergency call with a calm text, a triage call, and the price anchor the tech reads out at the door.

Time to run: 8 minutes per call

Free workflow

Water-Heater Quote -- The 20-Minute Build

A two-step prompt that turns the kitchen-table review after the water-heater assessment into a fixed-price replacement quote with three option tiers.

Time to run: 20 minutes per assessment

Get the Starter Prompt Pack

Get the Starter Prompt Pack for ServiceTitan Users

Drop your email — the AI Starter Pack PDF lands in your inbox in under a minute, and we'll email you again the day each playbook ships.

The PDF is the requested resource. Any later optional follow-up uses the unsubscribe path described above.

Running a single-truck ST shop, a 5–15-truck dispatcher on ServiceTitan, a multi-region ST enterprise operator, or an ST-aware bookkeeper feeding QBO / Xero? See the plans and try one workflow free before you commit.

See plumbing plans and pricing →Try one workflow free →

Sister /for/* page

Housecall Pro

SMB-side field-service platform (1-truck owner-operator, 5–15-truck dispatcher) — daily HCP Dispatch Board cadence, QBO / Xero sync, and HCP-Payments/Stripe split-fee reconciliation.

Read Housecall Pro →

Sister /for/* page

Jobber

SMB-side field-service platform (1-truck owner-operator, 5–15-truck dispatcher) — daily Jobber Dispatch Board cadence, QBO / Xero sync, and Jobber-Payments/Stripe split-fee reconciliation.

Read Jobber →

Sister /for/* page

QuickBooks

QBO controller + multi-trade services firm — ecosystem map, field-service-platform sync, 30/60/90 rollout for multi-trade firms, and the duplicate-invoice / GL-mapping-drift / unapplied-cash failure mode prompts.

Read QuickBooks →