Offline Titan Map Demo
This demo uses local data only. It shows how PageToJob maps pages, CTAs, campaigns, service areas, memberships, booking paths, and revenue proof before a customer connects ServiceTitan.
Customer profile
Website elements mapped to ServiceTitan objects
Campaign pages tied to campaign/source
Booking paths configured with a safe fallback
Capacity-aware CTA rules reviewed
Pages with demo booked-job/revenue reporting
/water-heater-repair still references Water Heater Repair.
Update the page binding or remove the public offer tied to Water Heater Repair.
/water-heater-repair still references Residential Plumbing.
Update the page binding or remove the public offer tied to Residential Plumbing.
/water-heater-repair still references West Valley.
Update the page binding or remove the public offer tied to West Valley.
Service area is paused in the demo taxonomy. The current CTA is "Collect request for manual review".
Confirm the manual capacity rule with dispatch before publishing this route.
Weekdays after 5pm or weekends
Tune-up campaign traffic or membership renewal audience
Service area is paused in the demo taxonomy
88% of required manual mapping fields are covered in the offline profile.
Scheduling Pro is not active; PageToJob appointment request is configured as the safe fallback.
2 high-severity and 2 medium-severity findings detected.
3 demo page outcome rows are available for the sales proof view.
No database or ServiceTitan API is required for this demo; live sync remains gated on app approval and customer authorization.
This offline version does not connect to ServiceTitan, write bookings, sync pricebook records, or assert marketplace approval. It gives PageToJob a sellable manual workflow and a realistic demo layer that can later be wired to approved ServiceTitan API access.
Buyer-safe answers for selling the manual product now while keeping API-backed automation, marketplace approval, and live sync claims gated.
Not in the current manual product. PageToJob builds a ServiceTitan-ready website layer using customer-reviewed mappings, booking fallback, launch proof, drift review, and support runbooks without collecting ServiceTitan credentials or claiming live API access.
API readiness proofNo. If the customer has Scheduling Pro, PageToJob can support the public website placement and fallback path. If they do not, PageToJob uses request-form and phone-first flows so visitors can still convert without pretending live slots are available.
Booking handoff proofLaunch, Growth, and Operations Monitor can be sold as manual-first products: rebuilt pages, Titan Map, campaign/source plan, booking fallback, launch packet, monthly drift review, and customer-safe outcome proof.
Pricing proofThey need a ServiceTitan admin contact, active modules, job types, business units, served areas, campaigns, offers, memberships, booking preference, and any approved exports or screenshots they want PageToJob to use for manual proof.
Intake proofPageToJob treats the Titan Map as the reviewable bridge between public pages and ServiceTitan operating concepts. Drift findings are assigned to owners and become reviewed fixes, not automatic website changes.
Drift report proofAfter approved app access, customer authorization, eligible modules, granted scopes, secure token storage, and sandbox validation, PageToJob can move toward read-only taxonomy imports, persisted sync queues, webhook processing, and outcome matching.
Connection readiness proofThe website lead path stays active first. Support confirms the lead record, fallback notification, Titan Map binding, idempotency key, and customer-safe state before retrying or marking a handoff manual-complete.
Support runbook proofServiceTitan-ready rebuild, Titan Map, booking path setup, launch packet.
Campaign pages, service-area expansion, monthly drift review.
Booked-job and revenue proof once authorized outcome data is available.
Ongoing mapping updates and drift findings for new campaigns, job types, and offers.