# CoolRoute Command search-to-pilot attribution map

Connect HVAC dispatch software traffic to live app proof, buyer evidence, pilot package interest, and launch details so the demo can be sold and improved from real intent data.

North star metric: Urgent jobs assigned with approved ETA or parts status before service window risk
Instrumentation phase: Instrument dispatch landing CTA, app preview, job search, reassignment, ETA draft approval, parts hold review, route view, and spec download.
Canonical page: https://ideas-realized.com/demo-library/hvac-dispatch
Live app: https://hvac-dispatch.ideas-realized.com

## Attribution Stages

### 1. Industry search entry
Route: https://ideas-realized.com/industries/hvac-dispatch-software
Event: industry_page_viewed_hvac_dispatch
Trigger: HVAC dispatch software visitor lands on the indexable industry page.
Owner: Growth lead
Destination: Search console, analytics landing report, and CRM first-touch source
Success signal: 2 qualified HVAC service inquiries per quarter
Proof asset: HVAC dispatch software helps service companies schedule jobs, assign technicians, monitor work order status, sequence routes, and manage recurring maintenance visits.
Next action: Route engaged visitors into CoolRoute Command instead of a generic contact form.

### 2. Live app launch
Route: https://hvac-dispatch.ideas-realized.com
Event: demo_opened_hvac_dispatch
Trigger: Prospect opens the HVAC dispatch app preview.
Owner: Growth lead
Destination: Analytics event stream and CRM source field
Success signal: Dispatch pages produce 30 percent of qualified demo opens from the HVAC cluster.
Proof asset: 14/14 clickable flows in the demo app.
Next action: Tag the session with demo slug, source page, buyer role, and selected workflow.

### 3. Workflow proof interaction
Route: https://ideas-realized.com/demo-apps/hvac-dispatch
Event: job_reassigned
Trigger: Dispatcher changes technician assignment or opens assignment workflow.
Owner: Dispatch manager
Destination: Product analytics funnel and operations ledger
Success signal: Assignment workflow is visible in every dispatch sales demo.
Proof asset: Authenticated dispatch board with job statuses, priority, and technician assignment.; Calendar and route views that share the same work order data.; Technician detail panel with load, next stop, skill context, and open exceptions.
Next action: Use the touched workflow as the first follow-up proof point.

### 4. Proof and ROI review
Route: https://ideas-realized.com/roi-calculators/hvac-dispatch-roi-calculator
Event: eta_message_approved
Trigger: ETA or delay message is viewed, approved, or marked ready to send.
Owner: Customer service lead
Destination: Customer communication dashboard
Success signal: Qualified buyers can see how ETA approval avoids accidental sends.
Proof asset: /case-studies/hvac-dispatch-pilot-case-study plus ROI calculator and production evidence export.
Next action: Attach ROI, case-study, and proof-pack links to the buyer follow-up.

### 5. Pilot package qualification
Route: https://ideas-realized.com/pilot-packages/hvac-dispatch-pilot-package
Event: pilot_package_viewed_hvac_dispatch
Trigger: Buyer opens Field service dispatch software pilot package after live app or ROI review.
Owner: Sales lead
Destination: CRM opportunity score and deal desk queue
Success signal: Buyer can provide one dispatch territory, technician schedule data, job status export, and approved customer message templates.
Proof asset: $24k-$42k setup, $1.2k-$4k/month recurring, 1 week job import, 2 weeks board and notification workflow, 2 weeks same-day dispatch pilot..
Next action: Confirm One service manager, one dispatcher, technician roster, sample work orders, and customer-message approval.

### 6. Launch details handoff
Route: https://ideas-realized.com/implementation-intake/hvac-dispatch-implementation-intake
Event: parts_hold_reviewed
Trigger: Parts hold workflow is opened for a job.
Owner: Parts coordinator
Destination: Parts blocker dashboard and audit ledger
Success signal: Parts blocker proof is used in at least half of follow-up proposals.
Proof asset: The current app already has board/calendar views, technician assignment, route context, customer message queues, parts exception holds, recurring plans, and job detail. A production version would add technician mobile views, SMS/email notifications, customer records, forms, and service platform integrations.
Next action: Collect required assets, source-data owner, approval gates, and production-domain decision.

## CRM Fields
- source_route
- demo_slug
- buyer_role
- workflow_touched
- proof_asset_opened
- pilot_package_viewed
- implementation_intake_started
- next_sales_action

## Dashboards
- HVAC acquisition dashboard (Sales and marketing)
  - Dispatch keyword traffic
  - App preview opens
  - Assignment workflow views
  - ETA workflow views
- Dispatch operations dashboard (Dispatcher and service manager)
  - Urgent jobs
  - Queued ETA messages
  - Open parts holds
  - Route-risk count

## Privacy Guardrails
- Customer addresses: Address analytics should use service-zone buckets, not raw street addresses, until buyer approval.
- Technician performance: Technician analytics are framed around capacity and assignments, not individual performance scoring during the pilot.
- Customer messages: Message template names and approval states can be tracked; customer phone and email values remain out of analytics.