# Deployment launch plan for CoolRoute Command 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. Repository: Idea-R/ideas-realized-page Preview domain: hvac-dispatch.ideas-realized.com Production domain: hvac-dispatch.ideas-realized.com JSON manifest: /demo-library/hvac-dispatch/deployment-launch.json OpenAPI implementation spec: /demo-library/hvac-dispatch/openapi.json ## Hosting Model Single Next.js application deployed from GitHub to Netlify, with demo subdomains rewritten into app-only routes and canonical SEO pages kept on ideas-realized.com. ## Branch Strategy Ship from a reviewed feature branch into the existing Netlify production site, then attach the selected client subdomain as a named domain alias after acceptance gates pass. ## Environments ### Sales preview URL: https://hvac-dispatch.ideas-realized.com Status: complete Purpose: App-only demo surface used in sales calls and embedded from the canonical landing page. Data mode: Seeded client-side preview data only; no tenant secrets or live customer records. ### Deploy preview URL: Netlify deploy preview URL from the feature branch Status: in progress Purpose: Review branch before domain aliasing, schema checks, browser QA, and stakeholder sign-off. Data mode: Seeded demo data plus import template samples. ### Pilot production URL: https://hvac-dispatch.ideas-realized.com Status: queued Purpose: Field service dispatch software pilot package launch for the first buyer cohort. Data mode: 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. ## Domain And DNS Records - [ready] CNAME hvac-dispatch.ideas-realized.com -> Ideas Realized Netlify site alias or wildcard domain. Owner: Ideas Realized technical lead. Keeps the app-only demo available as the sales URL while the canonical page remains on ideas-realized.com. - [needs client] CNAME hvac-dispatch.ideas-realized.com -> Client DNS points to the approved Netlify site alias. Owner: Client DNS owner. Use dispatch.clientdomain.com or service.clientdomain.com for production and keep hvac-dispatch.ideas-realized.com as the sales preview. - [needs client] TXT _netlify.hvac-dispatch.ideas-realized.com -> Netlify verification token issued during domain setup. Owner: Client DNS owner. Required before SSL issuance and production cutover when the domain is client-owned. ## Environment Variables - [template] NEXT_PUBLIC_SITE_URL (Build and runtime). Owner: Ideas Realized technical lead. Set to https://hvac-dispatch.ideas-realized.com for pilot production and keep canonical demo routes pointed at ideas-realized.com. - [ready] NEXT_DISABLE_IMAGE_OPTIMIZATION (Netlify runtime). Owner: Ideas Realized technical lead. Use when the host requires unoptimized Next images for generated poster assets and demo previews. - [needs client] AUTH_PROVIDER_CONFIG (Runtime secret). Owner: Implementation lead. Staff email login for pilot dispatch, with SSO and technician mobile auth added after field-service ownership is confirmed. - [template] NOTIFICATION_SENDER (Runtime secret). Owner: Implementation lead. In-app: Customer ETA message ready - [template] ANALYTICS_WRITE_KEY (Runtime secret). Owner: Growth lead. Instrument dispatch landing CTA, app preview, job search, reassignment, ETA draft approval, parts hold review, route view, and spec download. ## Release Gates - [complete] Reassign same-day job and preserve route context. Owner: Dispatcher. Evidence: Dispatch board and route panel show technician load and sequence changes. - [queued] Send ETA message draft from comms queue. Owner: Service manager. Evidence: Message queue data is present; SMS provider not selected. - [complete] Hold a job for unavailable parts. Owner: Parts coordinator. Evidence: Parts hold workflow shows ETA, risk, and owner. - [complete] Canonical and noindex routing verified. Owner: Technical lead. Evidence: Main-domain landing pages remain canonical while app-only routes are used for subdomain launch URLs. - [queued] Client proposal and implementation spec approved. Owner: Client sponsor. Evidence: CoolRoute Command pilot proposal and JSON/Markdown implementation spec are reviewed before production domain cutover. ## Monitoring Signals - Demo app availability: Homepage and app route return 200 from production domain after DNS cutover. Owner: Technical lead. Response: Rollback DNS alias to preview or pause launch announcement until the route passes. - Urgent jobs assigned with approved ETA or parts status before service window risk: Pilot usage is visible in the buyer dashboard within the first review cycle. Owner: Growth lead. Response: Review analytics key, event mapping, and privacy guardrails before widening access. - Confirm scheduling source of truth and technician calendar rules.: No open launch blocker can affect first user workflow. Owner: Implementation lead. Response: Hold go-live and keep the app in preview mode until the blocker has owner-approved evidence. ## Rollback Plan - Keep the sales preview subdomain live until the client production domain passes route, SSL, auth, and acceptance checks. - If client DNS or SSL fails, remove the production alias and route users back to the preview subdomain. - If data import fails, restore the last approved seed/import snapshot and hold workflow edits until the exception report is reviewed. - If notification or integration credentials fail, disable outbound automation and continue with manual review queues. - Document the rollback decision in the operations ledger and add the next action to the live ops command center. ## Go-Live Sequence - Merge the reviewed branch after typecheck, lint, build, schema validation, and browser QA pass. - Create or confirm the Netlify domain alias for the sales preview subdomain. - Request client DNS records for hvac-dispatch.ideas-realized.com and verify ownership before SSL issuance. - Load tenant brand tokens, roles, launch assets, import templates, and acceptance evidence. - Run release gates, verify monitoring signals, and approve the first pilot user cohort. - Publish SEO/AEO links for HVAC dispatch software and route launch CTAs to the canonical demo landing page. ## Support Handoff - Pilot support scope: $1.2k-$4k/month recurring for hosting, support, and workflow tuning. - Daily job import template - Technician roster and skill map - ETA message templates - Pick pilot dispatch window: Service manager; Start with weekday same-day calls before after-hours workflows. - Approve ETA message templates: Operations lead; Customer-facing SMS copy needs final tone and compliance approval. ## SEO Launch Checks - /demo-library/hvac-dispatch remains the canonical landing page for HVAC dispatch software. - https://hvac-dispatch.ideas-realized.com remains app-only and noindex for thin duplicate prevention. - Confirm internal links mention HVAC scheduling app. - Confirm internal links mention technician dispatch board. - Confirm internal links mention field service route management. - Answer target: What should HVAC dispatch software include? - Answer target: How do HVAC companies manage same-day technician schedules?