ServiceTitan app approval
api gatedNo partner/app approval is assumed in this demo. API-backed features remain gated until the app, app key, scopes, and customer authorization path are confirmed.
Connection readiness
This page makes the API boundary explicit: what is ready in manual mode, what needs customer input, and what must wait for approved app access, scopes, secure token storage, webhook validation, and a durable sync worker.
No partner/app approval is assumed in this demo. API-backed features remain gated until the app, app key, scopes, and customer authorization path are confirmed.
A real customer admin must authorize access before PageToJob can read or write tenant data.
No ServiceTitan credentials or tokens are stored in this offline product. Encrypted storage is required before live connection work.
Webhook verification, replay protection, and event persistence are design requirements, but no webhook endpoint is treated as production-ready without sandbox validation.
The offline handoff simulator produces queue-shaped sync drafts. A real worker needs durable storage, retries, idempotency, and operator-visible errors.
If enabled, PageToJob can help install or align the scheduler. Without it, the appointment request fallback stays active.
API-backed campaign ROI depends on the customer's purchased modules and granted attribution scopes.
Read-only service and offer alignment depends on approved pricebook access. Writes should remain approval-gated.
Membership and recurring-service growth pages can start manually, then use authorized membership data later.
Revenue proof from invoices and payments requires explicit authorization and eligible accounting access.
Prefer lead/form or booking handoff before direct job creation.
Direct job creation should stay gated behind validated customer, location, job type, business unit, campaign, and appointment rules.
Useful for read-only mapping and drift monitoring.
Manual zone review remains available before API approval.
Manual UTM and campaign plans work now; automated attribution waits for approved access.
Start read-only and diff-based. Avoid writes until explicit approval exists.
Manual membership offers can be mapped in the Titan Map today.
Use supplied exports for manual proof until API-backed revenue access is authorized.
Runs from local demo taxonomy and customer-reviewed mappings.
Use during onboarding and monthly drift reviews.
Booking form captures service, urgency, preferred time, source context, and Titan binding.
Keep active until Scheduling Pro or approved booking sync is available.
Handoff simulator creates structured request, idempotency key, mapped objects, and dry-run payload.
Add durable queue and approved CRM booking/lead endpoint after app authorization.
Manual taxonomy importer turns customer-supplied CSV exports into reviewed Titan Map candidates without API access.
Upgrade manual importer to live read-only API import after sandbox access confirms endpoint availability, scopes, and rate limits.
Manual/demo drift findings compare site bindings against local taxonomy and capacity rules.
Upgrade to imported taxonomy once scopes are granted.
Campaign page plans and launch packet use demo outcomes or supplied exports.
Connect attribution and accounting scopes only after eligibility is confirmed.