Customer intake

ServiceTitan-ready customer intake packet

A no-database onboarding packet for collecting the operating context, screenshots, exports, approvals, and redaction rules needed to build a ServiceTitan-ready website before API access exists.

Intake summary
9
questions
6
artifact requests
5
signoff gates
1
API gated
This packet collects manual inputs only. It does not ask for ServiceTitan credentials, app keys, client secrets, or tokens.

Onboarding questions

Account and operating model

Which trades, brands, branches, and business units should the website promote?

customer input

The site should sell the work the shop actually wants, not every historical service on the old website.

Expected answer: List active trades, brands, branches, and business units with priority order.

Which cities, ZIPs, zones, or neighborhoods are active, paused, or emergency-only?

customer input

Service-area pages and CTAs need to avoid sending demand into unsupported or low-priority areas.

Expected answer: Active, paused, emergency-only, and expansion areas with notes.

When should visitors call, request an appointment, use Scheduling Pro, or avoid booking online?

review required

Capacity-aware CTAs are the practical difference between a ServiceTitan-ready site and a generic lead form.

Expected answer: Business hours, emergency rules, preferred booking path, and exceptions by service.

Services, offers, memberships, and pricebook intent

Which job types and service categories should map to public pages?

customer input

The Titan Map needs a page-to-job-type bridge before campaign pages or drift checks are useful.

Expected answer: Top job types, synonyms customers use, and pages that should exist at launch.

Which offers, coupons, rebates, memberships, or recurring services are active?

customer input

Offer pages should align with what the shop can actually sell and fulfill.

Expected answer: Offer name, eligibility, expiration, membership tie-in, and services included.

Which old services, zones, or promotions should not be promoted anymore?

review required

Removing stale demand is often as valuable as adding new pages.

Expected answer: Inactive services, paused offers, unstaffed zones, and risky claims.

Campaign and proof inputs

Which paid search, email, direct mail, seasonal, or membership campaigns need landing pages?

customer input

Campaign pages need source and UTM plans before revenue proof can be trustworthy.

Expected answer: Campaign names, channels, target services, target areas, and desired call-to-action.

What outcome data can be shared manually for the 30-day review?

review required

Manual proof can start from supplied exports while live revenue matching stays gated.

Expected answer: Lead counts, booked jobs, revenue exports, campaign reports, or redacted screenshots.

Who decides whether a lead, booked job, or revenue match is valid?

customer input

Outcome reports need customer-reviewed match quality, not hidden attribution assumptions.

Expected answer: Named owner and review process for supplied proof.

Manual artifact requests

Job type, business unit, and service category list

customer input
Acceptable formats
CSV exportspreadsheetredacted screenshotscreen-share notes
Used for
  • - Titan Map
  • - service page plan
  • - drift baseline
No customer names, phone numbers, email addresses, addresses, or invoice notes.

Service area, zone, city, or ZIP coverage list

customer input
Acceptable formats
CSV exportspreadsheetredacted map screenshot
Used for
  • - service-area pages
  • - capacity rules
  • - drift baseline
Remove technician names, customer addresses, and route history.

Campaign, source, and UTM reference list

customer input
Acceptable formats
spreadsheetad platform exportMarketing Pro screenshotmanual notes
Used for
  • - campaign pages
  • - source plan
  • - outcome report
Do not include ad account credentials, payment data, or customer-level identifiers.

Active offers, rebates, memberships, and recurring-service programs

review required
Acceptable formats
spreadsheetpricebook screenshotmembership screenshotoffer terms document
Used for
  • - offer pages
  • - membership pages
  • - pricebook intent review
Remove internal margin notes, vendor contract terms, and customer identifiers.

Current booking, Scheduling Pro, phone, and form workflow screenshots

review required
Acceptable formats
screenshotsscreen-share notesworkflow diagram
Used for
  • - booking fallback
  • - CTA rules
  • - support handoff
Blur customer data, technician schedules, and private dispatch notes.

ServiceTitan API credentials, app key, client secret, or tokens

api gated
Acceptable formats
none before approved app flow
Used for
  • - future API mode only
Do not send credentials by email, form, screenshot, or shared document.

Signoff gates

Owner

Approve the launch scope, first mapped services, and first mapped areas.

Evidence: Signed pilot scope or written approval of Launch/Growth package boundaries.

If missing: Keep the account in discovery and do not publish operationally sensitive pages.
Operations

Approve the Titan Map before website copy and CTAs are treated as launch-ready.

Evidence: Reviewed mappings for services, zones, booking path, offers, and drift risks.

If missing: Use conservative phone-first CTAs and label mapping gaps in the launch packet.
Marketing

Approve source, UTM, campaign, and offer copy before launch.

Evidence: Campaign page plan and source table reviewed against active campaigns.

If missing: Launch only evergreen service pages and exclude campaign revenue claims.
ServiceTitan admin

Confirm whether manual exports are enough now and API authorization can wait.

Evidence: Admin contact, eligible modules, and future authorization path recorded.

If missing: Run the product entirely in no-API mode with no live sync claims.
PageToJob

Confirm supplied exports and screenshots are redacted and source-labeled.

Evidence: Artifact manifest with source, date, owner, redaction status, and use case.

If missing: Exclude the artifact from proof reports until source and redaction are clear.

Redaction rules

  • - Do not collect ServiceTitan passwords, app secrets, client secrets, tokens, or app keys during manual onboarding.
  • - Remove customer names, phone numbers, emails, street addresses, invoice notes, payment details, and private dispatch notes from shared exports.
  • - Keep screenshots focused on settings, labels, statuses, and aggregate outcomes rather than customer records.
  • - Label every supplied export with source system, export date, owner, and whether it was redacted.
  • - If redaction is uncertain, use screen-share review notes instead of storing the file.

No-API operating rules

  • - Use customer-reviewed exports, screenshots, and notes as the temporary source of truth.
  • - Capture mappings and proof as local product data, not as ServiceTitan writes.
  • - Do not promise live booking sync, pricebook updates, revenue attribution, or webhook handling before app approval and sandbox validation.
  • - Keep website lead capture and notification fallback working even when ServiceTitan access is unavailable.
  • - Treat each supplied artifact as evidence for a specific deliverable, not as broad permission to automate.

Disclaimer language

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