---
title: "HVAC Lead Recovery Metrics | Efficient Automate"
description: "See the lead states, timestamps, handoffs, stop conditions, and limits Efficient Automate uses to verify an HVAC lead recovery workflow."
canonical: "https://efficientautomate.com/what-we-measure/"
---

Source: [https://efficientautomate.com/what-we-measure/](<https://efficientautomate.com/what-we-measure/>)

evidence contract // HVAC

# Measure the workflow before claiming the outcome.

This public measurement contract separates observable workflow evidence from booking, revenue, and completion claims that need independent confirmation.

[Book a 20-Minute Fit Call](<https://cal.com/efficientautomate?utm_source=efficientautomate&utm_medium=website&utm_campaign=upstate-hvac-lead-recovery&utm_content=measurement-fit-call>)[See the observable states](<https://efficientautomate.com/what-we-measure/#states>)

// observable states

## Which states do we actually measure?

### received

The inquiry or missed-call event reaches the agreed record.

### acknowledged

An approved acknowledgement is recorded with its timestamp.

### qualifying

The workflow is collecting only the approved service and timing details.

### human review

A person owns the next decision or exception.

### booking requested

A handoff asks for a booking action; it is not a booking outcome.

### booked only when externally confirmed

Booking is recorded only when a separate, verifiable source confirms it.

### stopped

A reply, opt-out, attempt limit, or other agreed stop condition ends the sequence.

### failed

An error or incomplete path remains visible for follow-up rather than being treated as success.

// fields and timestamps

## Keep the review record specific.

### Event record

source; received timestamp; acknowledgement timestamp; supplied service area; issue category; urgency flag.

### Ownership record

owner; current status; booking-handoff status; stop reason; error status.

// public measurement sequence

## How is recovery measured without inflating it?

**Why not just report booked jobs?**

A booking is only reported when an owner-controlled source confirms it. Anything else is a requested next step, and it is labeled that way.

**What if an automated message fails to send?**

Failures are recorded as their own state and stay visible to the assigned person. They are never folded into a success number.

**Can the counts be audited later?**

Yes. Every state carries a timestamp and an owner, so a month of activity can be replayed event by event during a review.

**Public measurement sequence:** landing page -\> workflow viewed -\> fit-call clicked -\> Cal.com opened -\> confirmed booking when verifiable

Clicks are not bookings. Handoffs are not revenue. Customer revenue requires separate evidence. Completion attribution is unavailable when no owner-controlled confirmation exists.

[See the illustrative workflow →](<https://efficientautomate.com/how-it-works/>)[Review pricing →](<https://efficientautomate.com/pricing/>)[Field notes: the full baseline-and-rates model →](<https://efficientautomate.com/blog/measuring-missed-call-recovery/>)

// sample records

## See the definitions in a usable worksheet.

The [HVAC measurement worksheet](<https://efficientautomate.com/blog/measuring-missed-call-recovery/#worksheet>) includes the documented synthetic cohort and space for your own period and source records. For restaurant campaigns, the [worked example](<https://efficientautomate.com/restaurants/#worked-example>) keeps delivery status and staff-recorded redemptions separate.

## Define the evidence before implementation.

Use a fit call to identify the current record, handoff owner, confirmation source, and visible stop conditions.

[Book a 20-Minute Fit Call](<https://cal.com/efficientautomate?utm_source=efficientautomate&utm_medium=website&utm_campaign=upstate-hvac-lead-recovery&utm_content=measurement-fit-call>)

## Structured data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebPage",
      "@id": "https://efficientautomate.com/what-we-measure/#webpage",
      "url": "https://efficientautomate.com/what-we-measure/",
      "name": "HVAC Lead Recovery Metrics | Efficient Automate",
      "description": "See the lead states, timestamps, handoffs, stop conditions, and limits Efficient Automate uses to verify an HVAC lead recovery workflow.",
      "isPartOf": {
        "@id": "https://efficientautomate.com/#website"
      },
      "about": {
        "@id": "https://efficientautomate.com/#hvac-lead-recovery"
      },
      "inLanguage": "en-US"
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://efficientautomate.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "What we measure",
          "item": "https://efficientautomate.com/what-we-measure/"
        }
      ]
    }
  ]
}
```