Access checklist

ServiceTitan access checklist for manual-first pilots.

A customer-safe checklist for confirming admin contacts, modules, acceptable manual artifacts, and future authorization gates without collecting ServiceTitan credentials before approved access exists.

Checklist summary
6
access items
6
modules
4
boundaries
5
customer
3
review
3
gated
This checklist confirms who can approve future access, but it does not request ServiceTitan credentials or live tenant authorization during the manual pilot.

Access checklist items

Name the ServiceTitan admin

Owner: ServiceTitan admin

customer required

Future API work needs an admin who can confirm tenant eligibility, modules, scopes, app review, and authorization.

Admin name and roleBest contact channelAuthorization decision owner
No admin login, password, token, app key, client secret, or screen-share of secrets.

Confirm enabled ServiceTitan modules

Owner: Operations

customer required

Scheduling Pro, Marketing Pro, pricebook, memberships, dispatch, and accounting availability determines which claims are manual-now versus future API-gated.

Module listScreenshots with secrets and customer data redactedAdmin confirmation notes
No live tenant connection or broad export of customer records.

Choose the launch booking path

Owner: Shared

ready now

The website needs a safe conversion path whether the customer uses Scheduling Pro, phone-first CTAs, or PageToJob's request fallback.

Booking path decisionFallback recipientAfter-hours ruleEmergency routing rule
No ServiceTitan write access or Scheduling Pro webhook setup.

Approve manual artifact sources

Owner: Shared

review required

The first pilot can run from redacted exports, screenshots, and review notes while API access remains gated.

Redacted job type listService-area or zone listCampaign/source listOffer or membership notes
No unredacted customer records, invoice notes, payment details, or dispatch schedules.

Map future features to minimum scope intent

Owner: PageToJob

api gated

The product should request only the access needed for purchased features after partner and customer approval.

Feature-to-scope matrixPurchased packageEligible modulesSandbox validation result
No OAuth authorization, app credentials, app key, token exchange, or broad tenant access.

Confirm partner/app review path

Owner: PageToJob

partner gated

Marketplace, app key, sandbox, webhook, and scope details must come from the actual ServiceTitan approval path.

Partner category decisionSandbox access requirementsApp review requirementsSupport/security requirements
No claim of marketplace approval, certified app status, or live tenant access.

Module checks

Scheduling Pro

customer required

Manual use: Install or align existing scheduler embeds when the customer already has them.

Future API use: Webhook and scheduler event handling after app approval, signature validation, replay protection, and sandbox proof.

Ask: Do you use Scheduling Pro on the current website, Google, or campaign landing pages?

Marketing Pro / Marketing Ads

customer required

Manual use: Create UTM/source plans and campaign landing pages from customer-provided campaign references.

Future API use: Read approved campaign and attribution data for campaign revenue proof where licensed.

Ask: Which campaigns, sources, phone numbers, and attribution reports matter for the first 30-day proof packet?

Pricebook

review required

Manual use: Map offer and service pages to customer-reviewed pricebook intent without exposing sensitive pricing details publicly.

Future API use: Read services/categories for drift checks and offer alignment. Writes stay approval-gated.

Ask: Which services, categories, coupons, rebates, or replacement offers should the site promote or avoid?

Memberships and recurring service

review required

Manual use: Build maintenance plan and recurring-service pages from approved membership offers.

Future API use: Read eligible membership and recurring-service data for reactivation or tune-up campaigns.

Ask: Which memberships or recurring programs should have launch pages or campaign pages?

Dispatch zones and service areas

customer required

Manual use: Use customer-reviewed zones, ZIPs, cities, and capacity notes for service-area pages and CTA rules.

Future API use: Read dispatch/zone data for drift monitoring and capacity-aware CTA checks where scoped.

Ask: Which areas are active, paused, emergency-only, low priority, or expansion targets?

Invoices, payments, and revenue

api gated

Manual use: Use supplied aggregate reports or redacted exports for proof packets with visible match-quality labels.

Future API use: Read approved invoice/payment outcome data for closed-loop revenue attribution where authorized.

Ask: Can revenue proof start from an aggregate export while accounting access remains gated?

Access meeting flow

Owner: Shared

Preflight access call

Outcome: Confirm admin contact, modules, booking path, pilot package, and first manual artifacts.

If missing: Keep the customer in no-API Launch scope if admin or module answers are incomplete.
Owner: PageToJob

Artifact and redaction review

Outcome: Record which redacted exports, screenshots, or notes can be used for Titan Map, launch packet, drift report, and outcome proof.

If missing: Use screen-share notes instead of storing files when redaction is uncertain.
Owner: ServiceTitan admin

Module eligibility decision

Outcome: Separate manual-ready features from module-dependent and API-gated features.

If missing: Exclude module-specific automation from sales copy until eligibility is confirmed.
Owner: Shared

Future API authorization plan

Outcome: Identify the later authorization path, minimum scopes, sandbox evidence, support owner, and disconnect/deletion requirements.

If missing: Do not request credentials or authorization during the manual pilot.

Access boundaries

Do not collect ServiceTitan passwords, app keys, client secrets, tokens, or tenant secrets during manual onboarding.

The offline product is designed to sell and deliver value before approved app access exists.

Do not claim live ServiceTitan sync, webhooks, marketplace approval, pricebook writes, or revenue attribution until evidence exists.

Sales copy must stay aligned with actual authorization, scopes, sandbox validation, and customer eligibility.

Tie each future feature to the minimum eligible ServiceTitan scope and module before requesting access.

The partner product should be narrower than the roadmap and defensible in security review.

Keep booking fallback, lead notification, manual Titan Map review, and drift review active even when API work is blocked.

The website should not stop converting visitors because ServiceTitan access is unavailable.

Access disclaimers

  • - PageToJob is not affiliated with or endorsed by ServiceTitan.
  • - This checklist does not request or accept ServiceTitan credentials, app keys, client secrets, tokens, or admin logins.
  • - Manual artifacts are customer-supplied review inputs, not live ServiceTitan API authorization.
  • - API-backed features require customer authorization, eligible ServiceTitan products/modules, granted scopes, approved app access, secure token storage, and sandbox validation.