Implementation playbook

ServiceTitan-ready implementation playbook and data policy.

A no-API delivery system for taking a contractor from sales call to launch packet, monthly drift review, and future API readiness without claiming live ServiceTitan integration.

Delivery controls
6
phases
4
ready now
1
API gated
5
data rules
3
support
1
customer input
This playbook supports the manual product now and defines what must stay gated until approved ServiceTitan access exists.

Delivery phases

Pilot qualification

Sales call to day 2 · Owner: Shared

ready now

Confirm the account is a fit for a manual ServiceTitan-ready rebuild before API access exists.

Customer inputs
  • - Current website pain and priority services
  • - ServiceTitan modules in use
  • - Primary buyer and ServiceTitan admin contact
  • - Booking path preference: phone, request form, or Scheduling Pro
PageToJob actions
  • - Run the readiness audit
  • - Log the conversation against the validation tracker when it is a discovery interview
  • - Choose Launch, Growth, Operations Monitor, or future Revenue Layer scope
  • - Document API-gated claims separately from manual deliverables
Evidence to close
Readiness scoreRecommended packageNo-API fallback fitPilot scope accepted
No credentials, tokens, or API access requested during qualification.

Manual Titan Map

Week 1 · Owner: Shared

customer input

Map pages, forms, CTAs, campaigns, zones, memberships, and offer intent to the customer's operating model.

Customer inputs
  • - Active job types and business units
  • - Served cities, ZIPs, and zones
  • - Campaigns, memberships, seasonal offers, and pricebook references
  • - Known inactive services, paused zones, and capacity rules
PageToJob actions
  • - Create the Titan Map
  • - Assign coverage gaps
  • - Flag inactive or risky public promises
  • - Prepare booking fallback and source/UTM plan
Evidence to close
Titan Map coverage scoreMapped URL listDrift baselineBooking path decision
Manual customer-reviewed mappings are the system of record until approved read-only imports exist.

Website and campaign build

Weeks 1-2 · Owner: PageToJob

ready now

Build the public website, service pages, service-area pages, campaign pages, and offer pages from the approved manual map.

Customer inputs
  • - Brand assets and photos when available
  • - Priority services and service areas
  • - Offer approval and expiration dates
  • - Phone numbers, financing/rebate language, and emergency policies
PageToJob actions
  • - Generate mapped pages
  • - Install booking request fallback
  • - Add source context to forms and CTAs
  • - Prepare launch packet and sample outcome report
Evidence to close
Demo or live URLsBooking fallback testCampaign/source planLaunch packet draft
The site remains operational without ServiceTitan writes or live scheduler availability.

Launch review

Week 3 · Owner: Shared

ready now

Confirm the site can go live with honest proof, fallback notifications, and reviewed ServiceTitan-ready mapping.

Customer inputs
  • - Final approval on service/offer copy
  • - Notification recipient confirmation
  • - DNS/domain launch approval
  • - Any Scheduling Pro embed details if already enabled
PageToJob actions
  • - Run launch packet review
  • - Verify sitemap, robots, booking path, Titan Map coverage, and drift baseline
  • - Confirm API-gated items are not represented as live
Evidence to close
Launch packetNotification fallback statusDrift baselineApproved go-live checklist
Launch does not require ServiceTitan marketplace approval or customer API authorization.

Monthly drift and proof review

Day 30 and monthly · Owner: Shared

ready now

Keep the website aligned with operational changes and report proof without overstating attribution.

Customer inputs
  • - ServiceTitan changes since launch
  • - Manual job/lead/outcome exports if available
  • - Campaigns, offers, memberships, or zones added or paused
PageToJob actions
  • - Run manual drift review
  • - Update mapping gaps and fix queue
  • - Prepare outcome proof with match-quality labels
  • - Recommend Growth, Operations Monitor, or API-readiness next steps
Evidence to close
Drift reportResolved findingsOutcome reportUpdated Titan Map
Manual outcome reports use supplied exports or demo data until authorized ServiceTitan outcome APIs are available.

Future API upgrade

After app/customer approval · Owner: Shared

api gated

Upgrade manual mappings and proof workflows into authorized read-only imports, handoff queues, and outcome matching.

Customer inputs
  • - Customer authorization
  • - Eligible ServiceTitan modules
  • - Granted scopes
  • - Admin contact and sandbox/tenant validation access
PageToJob actions
  • - Confirm app approval path
  • - Validate token storage, webhooks, retries, idempotency, and disconnect handling
  • - Turn offline queue states into persisted worker records
Evidence to close
Connection readinessScope matrixSync queue proofSandbox validation evidence
Do not sell this as active automation until approved app access, scopes, and sandbox validation are complete.

Data retention and deletion

Lead and contact details

Current: Stored through the existing lead pipeline and used for customer notification.

Retention: Retain while the customer account is active or until deletion is requested.

Deletion: Customer requests lead deletion, account cancellation, or legal/privacy request.

Do not send lead/contact data to ServiceTitan until customer authorization and approved CRM scopes exist.

Structured booking envelope

Current: Non-PII event metadata: source path, service context, UTM fields, Titan binding, idempotency key, and manual sync-review status.

Retention: Retain with analytics events for operational proof and manual handoff review.

Deletion: Delete or anonymize with the related lead/account event history when requested.

Can become a booking_requests row and sync queue item only after database migration and customer-approved connection.

Manual Titan Map

Current: Customer-reviewed mapping between website pages and ServiceTitan operating concepts.

Retention: Retain while PageToJob maintains the site or Operations Monitor relationship.

Deletion: Customer cancellation, replacement map, or deletion request.

Imported taxonomy must remain read-only and reviewed before it changes public website copy.

Supplied ServiceTitan exports or screenshots

Current: Optional customer-provided proof inputs for manual audit, drift review, or outcome summary.

Retention: Retain only as long as needed for the review cycle unless the customer asks PageToJob to preserve the proof packet.

Deletion: End of review cycle, customer deletion request, or account cancellation.

Replace exports with authorized API reads only after scopes and data-retention policy are approved.

ServiceTitan credentials and tokens

Current: Not collected or stored in the offline product.

Retention: No retention before API approval because no credentials are accepted.

Deletion: Future disconnect must revoke tokens, remove encrypted references, and disable API-backed features.

Requires encrypted token storage, rotation, disconnect, deletion, and audit logging before live use.

Support promises

Website visitor submits a booking request while ServiceTitan is unavailable or not connected.

Keep the PageToJob lead path, notification fallback, and manual review active.

No customer lead is lost because ServiceTitan access is missing or API work is blocked.

Customer changes service areas, job types, campaigns, memberships, or offers.

Create a drift finding, update the Titan Map, and change public website content only after review.

Operational changes become reviewed updates instead of surprise website edits.

Outcome or revenue proof is incomplete or uncertain.

Label records as unmatched or needs review and exclude uncertain records from revenue claims.

Proof packets stay defensible and do not overstate closed-loop attribution.

Implementation disclaimers

  • - PageToJob is not affiliated with or endorsed by ServiceTitan.
  • - ServiceTitan is a trademark of its respective owner.
  • - The offline implementation playbook does not require ServiceTitan credentials, tokens, marketplace approval, or API calls.
  • - API-backed features require customer authorization, eligible ServiceTitan products/modules, granted scopes, approved app access, secure token storage, and sandbox validation.