PLANNING GUIDE · SNAPSHOT COMING SOON
HVAC Votel Snapshot
An HVAC system should turn a service inquiry into an assigned next action. Start by separating repairs, replacement estimates and maintenance, then connect each path to dispatch, scheduling and follow-up.
Review the setup checklist →Plan the build before choosing the assets
This snapshot is planned and has not been built yet. Use this guide to decide which intake fields, routing rules, booking paths and follow-up your business needs. The diagrams and checklists describe a proposed system.
Proposed customer journey
- 01Capture request type and service location
- 02Check coverage and office availability
- 03Assign dispatch or an estimator
- 04Confirm appointment through the agreed calendar
- 05Send appropriate reminders and record the outcome
Components to review before setup
Use this checklist to compare the installed build with your requirements. These are proposed components to consider for your build.
| Component | Proposed role | Configuration to verify |
|---|---|---|
| Intake form | Request type, service area, equipment context and callback preference | Map each answer to a documented field; keep existing customer details intact. |
| Dispatch workflow | Owner assignment, office-hours branch and unassigned-request fallback | Choose actual team members and a monitored fallback queue. |
| Appointment path | Separate service and estimate appointment types | Confirm timezone, availability, service duration and cancellation behavior. |
| Follow-up | Booking reminders and next-step messages for estimates | Define entry, exit and opt-out conditions before enabling delivery. |
| CRM stages | New inquiry, assigned, appointment confirmed and outcome recorded | Choose stage names that match dispatch operations and define who changes each stage. |
Setup checklist
- Record the installed snapshot version and inventory before changing any assets.
- Set business name, service area, operating hours and the owner of each request type.
- Map intake fields and verify required answers in a synthetic contact record.
- Connect the intended calendars and test timezone and unavailable-slot behavior.
- Review every workflow branch, notification recipient and message exit condition.
- Run the acceptance checks below with synthetic contacts before connecting live channels.
Acceptance checks before launch
Use these checks when your system is built. Test with synthetic contacts before connecting live channels, and record whether each expected outcome occurs.
| Test case | Expected outcome |
|---|---|
| Repair request during office hours | The request appears once and has an assigned dispatch owner. |
| Replacement estimate | The estimator path receives the request; repair-only reminders do not run. |
| Out-of-area request | The request reaches review without a confirmed appointment. |
| After-hours request | The configured callback path runs without an unsupported emergency-response promise. |
| Appointment rescheduled or cancelled | Old reminders stop and the contact record shows the current appointment state. |
| Reply, opt-out or completed job | Follow-up stops or changes according to the configured exit rules. |
When is this ready for a client?
Only after the installed inventory is verified, required integrations are connected, business-specific settings are configured, and every critical customer path has a recorded passing test. Keep evidence of branches, cancellation behavior, opt-outs and human handoffs alongside the setup notes.
Read the industry intake guide →
Review HighLevel-to-Votel migration planning →
Editorial guide reviewed September 19, 2026 by All Things Votel. Snapshot status: planned build; not yet available.