# CoolRoute Command tenant clone package

A rebrand-and-launch packet for turning HVAC Dispatch into a client-specific tenant: brand, workflow spine, import plan, permissions, procurement, SEO/AEO routes, deployment, and support cutover.

Package: CoolRoute Dispatch Launch Kit
Product: CoolRoute Command
Tenant: Evergreen Mechanical
Preview URL: https://hvac-dispatch.ideas-realized.com?screen=route
Preview screen: Route (route) - dispatch route board and technician schedule proof
Production domain: hvac-dispatch.ideas-realized.com
Canonical page: https://ideas-realized.com/demo-library/hvac-dispatch
Industry page: /industries/hvac-dispatch-software
JSON manifest: /demo-library/hvac-dispatch/tenant-clone-package.json
Pilot offer: Field service dispatch software pilot package
Commercial snapshot: $24k-$42k setup / $1.2k-$4k/month recurring / 1 week job import, 2 weeks board and notification workflow, 2 weeks same-day dispatch pilot..
Clone package score: 81/100
Buyer decision: Ready for buyer review once brand, tenant, and domain receives client input.
Next implementation move: Buyer must approve live ETA, delay, and parts-message language before notifications are enabled.
Primary risk: Confirm scheduling source of truth and technician calendar rules.

## Clone Readiness Lanes

### 1. Brand, tenant, and domain
Owner: Implementation lead
Status: Buyer input
Score: 67/100
This kit adapts the HVAC dispatch app for service businesses by packaging technician language, route board copy, ETA messaging, parts-hold labels, and launch variants for trades with mobile crews.

Proof: Evergreen Mechanical is configured for hvac-dispatch.ideas-realized.com; 3 white-label variants are mapped.
Next action: Buyer must approve live ETA, delay, and parts-message language before notifications are enabled.

Assets:
- [Company name] Dispatch Desk, [Service line] Command, or [Market name] RouteBoard.
- Use dispatch.clientdomain.com or service.clientdomain.com for production and keep hvac-dispatch.ideas-realized.com as the sales preview.
- Service command identity: Logo, fleet-safe color accents, dispatcher screen mark, and customer-message footer.
- ETA message tone set: Approved arrival-window, delay, and parts-delay copy for dispatch review.
- Route board labels: Capacity states, priority names, skill tags, and service territory labels.

### 2. Workflow spine and data import
Owner: Implementation lead
Status: Buyer input
Score: 86/100
The first pilot can sit beside the field-service platform. Import jobs and technician capacity, then use the board to expose assignment risk, parts blockers, and ETA message readiness.

Proof: 3 reusable product-spine modules and 3 data sources are mapped for first-tenant launch.
Next action: Start with a read-only job and technician import, reconcile service categories, then allow dispatchers to update pilot board status while the source platform remains system of record.

Assets:
- Dispatch board: Job cards, technician load, route sequencing, map-style panel, and urgent-status actions.
- ETA messaging workflow: Trigger rules, templates, escalation paths, and owner assignments.
- Readiness cockpit: Import dry-runs, permission groups, acceptance tests, and blocker list.
- Service jobs export: 40 to 160 open jobs
- Technician roster: 8 to 60 technician records
- Parts holds: 10 to 80 parts-held job rows

### 3. Access, procurement, and buyer approval
Owner: Dispatch manager
Status: Buyer input
Score: 85/100
A buyer-facing approval packet for turning HVAC Dispatch into a paid pilot: commercial scope, data boundaries, access model, hosting plan, support coverage, automation limits, and sign-off evidence.

Proof: 8 procurement sections, 3 roles, and 3 permission scopes are documented.
Next action: Territory and schedule accepted: Pilot territory, technician roster, skill tags, and schedule windows validated.

Assets:
- Identity: Staff email login for pilot dispatch, with SSO and technician mobile auth added after field-service ownership is confirmed.
- Session model: Service-zone sessions with dispatcher, technician, and manager role claims.
- Commercial approval: ready
- Data handling and import: needs-client
- Access and role boundaries: scoped
- Hosting and domain launch: scoped

### 4. Integrations and automation boundaries
Owner: Product lead
Status: Buyer input
Score: 74/100
The pilot should keep urgent jobs moving by turning schedule risk, route blockers, and parts holds into visible dispatcher actions.

Proof: 4 setup integrations, 3 automation rules, and 5 environment variables are scoped.
Next action: Depends on ServiceTitan, Housecall Pro, Jobber, or custom records.

Assets:
- Customer ETA messages: SMS/email wording and triggers are scoped for same-day dispatch.
- Service platform sync: Depends on ServiceTitan, Housecall Pro, Jobber, or custom records.
- Map routing: Can be connected after technician and address data are live.
- CSV job import: Work order fields map cleanly to a pilot import.
- Unassigned urgent job alert: ready
- ETA message preparation: needs-client
- Parts hold route block: template

### 5. SEO/AEO demand capture
Owner: Growth lead
Status: Ready
Score: 88/100
The HVAC dispatch demo can anchor pages for service companies that need job boards, ETA messages, route risk, parts holds, and field-service handoff controls.

Proof: /industries/hvac-dispatch-software anchors 3 content briefs, 3 answer blocks, and 2 comparison pages.
Next action: Publish the highest-intent route for HVAC dispatch software, then link it to /demo-library/hvac-dispatch and the pilot package.

Assets:
- Primary intent: HVAC dispatch scheduling software
- HVAC dispatch scheduling software for same-day service teams: /industries/hvac-dispatch-scheduling-software
- HVAC parts hold workflow for dispatch teams: /resources/hvac-parts-hold-workflow
- HVAC dispatch board vs field service software customization: /compare/hvac-dispatch-board-vs-field-service-customization
- What should HVAC dispatch scheduling software show?
- How can dispatchers manage parts delays without losing the route?

### 6. Deployment, support, and cutover
Owner: Dispatch launch thread
Status: Buyer input
Score: 83/100
A production handoff plan for taking HVAC Dispatch from sales preview to a client-owned launch domain with Netlify hosting, environment gates, monitoring, rollback, and canonical SEO/AEO checks.

Proof: 3 environments, 5 release gates, and 2 support levels are ready for cutover planning.
Next action: Merge the reviewed branch after typecheck, lint, build, schema validation, and browser QA pass.

Assets:
- Preview: https://hvac-dispatch.ideas-realized.com
- Production: https://hvac-dispatch.ideas-realized.com
- Dispatch launch thread: Same or next business day for schedule-blocking issues
- Weekly dispatch review: Scheduled

## Clone Targets

### Plumbing service dispatch board
Segment: Residential plumbing service companies
Target keyword: plumbing dispatch software
Launch path: /industries/plumbing-dispatch-software
Fit score: 92/100
Launch effort: Low
Risk control: Confirm emergency-call triage and after-hours escalation rules before pilot launch.
Rebrand moves:
- Swap HVAC equipment terms for plumbing fixtures
- Adjust job types and SLA labels
- Load plumber skill tags and territory names

### Appliance repair scheduling desk
Segment: Appliance repair operators
Target keyword: appliance repair dispatch software
Launch path: /industries/appliance-repair-dispatch-software
Fit score: 85/100
Launch effort: Medium
Risk control: Separate parts availability from appointment readiness before enabling customer notices.
Rebrand moves:
- Swap systems for appliance categories
- Add model/serial fields
- Add parts-needed and return-visit labels

### Pool and spa service route board
Segment: Pool and spa maintenance teams
Target keyword: pool service route scheduling software
Launch path: /industries/pool-service-route-scheduling-software
Fit score: 79/100
Launch effort: Medium
Risk control: Add recurring-route templates before promising automated schedule generation.
Rebrand moves:
- Rename technicians as route techs
- Add recurring service frequency fields
- Swap closeout details for service log and chemistry notes

## SEO/AEO Route Map
- /industries/hvac-dispatch-software
- /industries/hvac-dispatch-software
- /industries/hvac-dispatch-scheduling-software
- /resources/hvac-parts-hold-workflow
- /compare/hvac-dispatch-board-vs-field-service-customization
- plumbing dispatch software: /industries/plumbing-dispatch-software
- What should HVAC dispatch scheduling software show? Proof source: Assignment change history and ETA message approval queue
- How can dispatchers manage parts delays without losing the route? Proof source: Parts hold blocker report

## Rebrand Moves
- Technician -> Field tech, installer, plumber, mechanic, crew, or maintenance lead
- Job -> Call, work order, appointment, ticket, or service visit
- Parts hold -> Material hold, supply blocker, equipment hold, or warehouse check
- Swap HVAC equipment terms for plumbing fixtures
- Adjust job types and SLA labels
- Load plumber skill tags and territory names

## Export Links
- Live app preview: https://hvac-dispatch.ideas-realized.com?screen=route - App-only sales surface opened to Route: dispatch route board and technician schedule proof.
- Canonical landing page: /demo-library/hvac-dispatch - SEO/indexable proof page on the main Ideas Realized domain.
- Industry page: /industries/hvac-dispatch-software - Primary SEO/AEO route for buyer-intent capture.
- Pilot package: /pilot-packages/hvac-dispatch-pilot-package - Commercial package page for the first paid setup.
- Implementation intake: /implementation-intake/hvac-dispatch-implementation-intake - Buyer qualification and asset collection route.
- Procurement pack: /demo-library/hvac-dispatch/procurement-pack - Approval packet for security, commercial, data, and support review.
- Sample data package: /demo-library/hvac-dispatch/sample-data-package - Buyer-ready sample data package with CSV templates, seed rows, validation gates, and cutover notes.
- Sample data package JSON: /demo-library/hvac-dispatch/sample-data-package.json - Machine-readable sample-data manifest for implementation automation and dry-import planning.
- Tenant clone package: /demo-library/hvac-dispatch/tenant-clone-package - Downloadable rebrand-and-launch packet for implementation handoff.
- Clone package JSON: /demo-library/hvac-dispatch/tenant-clone-package.json - Machine-readable tenant clone manifest for automation and implementation handoff.