Sales call script

ServiceTitan-ready sales call script.

A practical call flow for selling the manual ServiceTitan-ready website pilot: diagnose operating mismatch, show proof artifacts, handle integration objections, and close a fixed-scope next step without claiming live API access.

Use this script when a contractor already runs ServiceTitan but the public website, booking path, campaigns, offers, or proof reporting no longer match how the shop actually operates.
Call summary
6
stages
30
minutes
5
objections
4
close steps
9
proof routes
1
boundaries
Do not claim live ServiceTitan integration, marketplace approval, API sync, webhooks, booking writes, or pricebook sync.

Call flow

4 min

Open with operating mismatch

discovery

Frame the conversation around website-to-ServiceTitan alignment, not generic web design.

Questions
  • - Which services, zones, offers, or memberships does the current website promote that dispatch or marketing would change today?
  • - Where do website leads go today when online booking is unavailable, wrong, or incomplete?
  • - Who owns ServiceTitan setup decisions for job types, campaigns, zones, memberships, and pricebook offers?
Talk track
  • - We are not starting with a generic redesign. We are looking for the gap between what the website promises and what ServiceTitan says the shop can sell, schedule, and prove.
  • - The first deliverable can be valuable without API access because the Titan Map gives marketing and operations one reviewed reference point.
Exit criteria
  • - Buyer names at least one website-to-operations mismatch
  • - Buyer confirms the right reviewer persona
6 min

Diagnose the first Titan Map slice

discovery

Identify the first pages, campaigns, offers, or service areas that should be mapped in a pilot.

Questions
  • - Which three pages or campaigns would you want reviewed first?
  • - Are those tied to active ServiceTitan job types, campaigns, business units, zones, memberships, or pricebook services?
  • - What would make a lead from those pages hard for the office or dispatch team to act on?
Talk track
  • - We start with a small mapped slice because that gives us launch proof faster and keeps scope from turning into a broad integration project.
  • - If the first slice is useful, the same method can expand into campaign pages, offer pages, monthly drift review, and outcome proof.
Exit criteria
  • - Buyer selects the first mapped slice
  • - Buyer can name the operational reviewer
8 min

Show the manual proof sequence

proof

Use live artifacts to show what the buyer gets before any ServiceTitan connection exists.

Questions
  • - Would this launch packet help your team approve a site change?
  • - Would the handoff packet make onboarding clear enough for your ServiceTitan admin and operations lead?
  • - Would a monthly drift review be useful even before automated taxonomy sync?
Talk track
  • - The proof path is audit, Titan Map, demo website, proposal, handoff packet, launch packet, and monthly review.
  • - Every artifact separates manual deliverables from future API-backed features so the buyer knows exactly what is included now.
Exit criteria
  • - Buyer understands the no-API pilot deliverables
  • - Buyer identifies the proof artifact most useful to their team
6 min

Handle integration objections

objection

Answer the common ServiceTitan partner, Scheduling Pro, API, and manual-value objections without over-claiming.

Questions
  • - Are you asking whether this is useful now, or whether it can automate later?
  • - Which ServiceTitan module or workflow are you worried this overlaps with?
  • - What would you need to see before trusting a future API-backed version?
Talk track
  • - The current product is a manual ServiceTitan-ready website layer, not a certified live integration.
  • - That is intentional: the site, Titan Map, handoff, and proof packets can be sold before app approval, scopes, and token storage exist.
Exit criteria
  • - Buyer accepts manual-now/API-later positioning
  • - Any remaining integration concern has an owner or follow-up
5 min

Close the fixed-scope pilot

close

Move from interest to a specific package, scope, owner, and next artifact.

Questions
  • - If we map the first three pages or campaigns, who needs to approve the Titan Map?
  • - Which pilot package fits the first outcome you care about: launch, growth, or operations review?
  • - What would make the 30-day proof review worth renewing or expanding?
Talk track
  • - The close is not 'trust us to integrate with ServiceTitan.' The close is 'approve a fixed manual pilot that produces useful website and operations proof.'
  • - If API access becomes worth pursuing later, we use the readiness and sandbox packets as the gate.
Exit criteria
  • - Package selected
  • - Scope owner named
  • - Intake or proposal route opened
1 min

Protect claim boundaries

boundary

End with explicit language about what PageToJob does not claim before API approval.

Questions
  • - Are we aligned that this pilot does not require ServiceTitan credentials or live tenant access?
Talk track
  • - PageToJob is not affiliated with or endorsed by ServiceTitan.
  • - The current pilot does not connect to ServiceTitan, collect ServiceTitan credentials, write bookings, sync pricebook records, process webhooks, or claim marketplace approval.
Exit criteria
  • - No-credential boundary acknowledged
  • - Future API work remains explicitly gated

Objection responses

Is this a live ServiceTitan integration?

Concern: The buyer may expect certified marketplace status, connected tenant data, or automated sync.

No. The sell-now product is a manual ServiceTitan-ready website layer. It maps public pages, CTAs, campaigns, offers, and proof artifacts to the way the shop operates in ServiceTitan without asking for credentials.
Do not say PageToJob is approved, certified, connected, or syncing with ServiceTitan.
Open proof

Does this replace Scheduling Pro?

Concern: The buyer may think the product competes with their ServiceTitan booking module.

No. PageToJob improves the public website layer, page-to-job context, CTA rules, campaign pages, and fallback handoff. If the customer uses Scheduling Pro, the website still needs the right pages, offers, source context, and proof language around it.
Do not position PageToJob as a scheduler, dispatcher, or ServiceTitan module replacement.
Open proof

Why buy before API access?

Concern: The buyer may see manual mapping as less valuable than automation.

The website can be wrong before the API is connected. A manual Titan Map, launch packet, handoff packet, and monthly review fix the operating mismatch now and make future automation safer.
Do not imply manual review is a permanent substitute for durable integration when the customer needs automation.
Open proof

What becomes automated later?

Concern: The buyer wants a roadmap without vague promises.

Later automation can include read-only taxonomy import, durable sync queues, webhooks, booking/job matching, and revenue attribution, but only after customer authorization, eligible modules, approved scopes, secure storage, and sandbox validation.
Do not promise timeline, endpoint availability, scopes, or marketplace approval before evidence exists.
Open proof

Who on our team needs to be involved?

Concern: The buyer may worry onboarding will become a heavy implementation project.

The pilot needs one owner, one marketing reviewer, one operations reviewer, and a ServiceTitan admin contact for artifact review. No credentials are requested for the manual pilot.
Do not ask for admin login access during the manual sales or onboarding process.
Open proof

Close path

Pick the first mapped slice

Which three pages, campaigns, offers, or service areas should PageToJob map first?

Evidence required
Buyer-selected pages or campaignsOperational reviewerKnown booking path
Open next artifact

Pick the pilot package

Is this a Launch, Growth, or Operations Monitor pilot?

Evidence required
Package choicePilot outcomeBudget owner
Open next artifact

Send the proposal packet

Can we send the fixed-scope proposal with customer responsibilities and exclusions?

Evidence required
ScopeTermAcceptance gates
Open next artifact

Start intake

Who should complete intake and approve redacted ServiceTitan artifacts?

Evidence required
Intake ownerServiceTitan admin contactArtifact redaction agreement
Open next artifact

Call disclaimers

  • - PageToJob is not affiliated with or endorsed by ServiceTitan.
  • - ServiceTitan is a trademark of its respective owner.
  • - The sales call should position the current product as manual ServiceTitan-ready website work, not live ServiceTitan integration.
  • - API-backed features require customer authorization, eligible ServiceTitan products/modules, granted scopes, approved app access, secure storage, and sandbox validation.