What We Mean by Recovered Revenue — and What We Don't

A recovered job has exactly three parts. The AI answered the call or triggered a text-back. The caller booked an appointment. The appointment was completed and the invoice went out. All three. Not two out of three.

If the AI answered 40 calls last month and 14 callers said "I'll think about it," those 14 are not recovered revenue. They're leads. They're pipeline. They're optimism. They do not count toward your $5,000 threshold.

The guarantee is built on this definition on purpose. "Recovered revenue" means dollars that were already on their way to your competitor — calls that would have hit voicemail, jobs that would have gone to whoever answered next — that the system intercepted and converted into completed, paid work. The definition is tight because the promise has to be honest. A looser definition that counts every call the AI touched, or every appointment scheduled regardless of whether it was ever completed, would let the agency claim wins on jobs that were never started or canceled at the door. We don't count those.

The exact chain: AI answered or texted → caller booked → job completed → invoice sent. If any single link is missing, it does not count. That's the deal, stated plainly before you sign anything.

Here is the full call flow that produces a counted recovered job.

Phone rings at 11 PM. You're asleep. The AI answers on the second ring, identifies a new lead, asks qualifying questions — what's the problem, what's your zip code, are you the homeowner — and offers the next available appointment window. The caller picks a time. The appointment lands in your calendar. You show up, do the work, send the invoice. That is a recovered job.

Every step in that chain is logged with a timestamp: call start, qualification responses, booking confirmation, calendar entry created. When your 60-day statement is compiled, the agency matches each booking timestamp to its completed invoice. If the invoice exists and it traces back to an AI-answered call, the revenue from that job is counted.

The qualification step matters. If the AI answered the call but the caller hung up before booking, that is a handled call — it is not recovered revenue. No booking, no invoice, no count. Same rule applies if the job was scheduled but the appointment was canceled and never rescheduled to completion. The completed invoice is the finish line, not the scheduling confirmation.

Why require a completed invoice? Because booking a job and getting paid for that job are two different numbers. A "booked" job that sits on the calendar and never converts is worth exactly $0. Contractors already know this. The guarantee is built around the same math you use when you close out your week.

You're on a job. Phone rings, you can't answer. Instead of voicemail, the caller gets a text within 60 seconds: the business name, an apology for missing the call, and a prompt to reply with what they need. The caller texts back. An appointment gets booked. The job gets done. The invoice goes out.

That sequence counts toward the $5,000.

The text-back alone does not count. A reply does not count. Even scheduling the appointment doesn't count until the job is completed and invoiced. The text-back is the mechanism that kept the caller from hanging up and dialing your competitor 30 seconds later. The recovered revenue is what sits at the end of that chain.

Attribution is maintained through the conversation thread. The system logs the original missed call, the outbound SMS timestamp (must be within 60 seconds of the missed call to qualify), the inbound reply, the booking confirmation, and the invoice. The agency reconciles those records at day 60.

One thing to know upfront: if the caller texts back and you end up quoting the job manually over the phone and booking it outside the system — without a logged booking confirmation — that job will not automatically appear in your statement. Attribution works off logged system bookings. Jobs booked outside the system, even if a text-back started the conversation, cannot be reliably attributed and will not be counted toward the guarantee.

Here is what does not count toward the $5,000, regardless of how much it improves:

SEO traffic increases. Google review count growth. Reputation score improvements. Leads in your pipeline that were never invoiced. Jobs quoted but not accepted. Calls handled where no appointment was booked. Appointments scheduled but never completed.

None of those. Zero.

We're explicit about this because a guarantee that counts "leads generated" or "pipeline value added" is a guarantee that can never fail — and a guarantee that can never fail is not a guarantee. It's a marketing claim with a number attached to make it sound credible.

The $5,000 threshold is built on a narrow, verifiable definition. Completed, invoiced jobs traced directly to AI-answered calls or text-back sequences. If reputation improvements counted, every customer would clear $5k by week two and the threshold would mean nothing. The specificity is the trust signal. You should be skeptical of any service that promises results in metrics you can't independently verify from your own invoices.

You never pull a report. You never log into a dashboard. You never export a spreadsheet. The agency does the reconciliation and delivers your 60-day statement directly.

Here's what gets cross-referenced: call logs with timestamps and outcomes, text-back records with outbound and inbound SMS timestamps, calendar entries with job type and customer name, and invoice status confirmed through whatever invoicing method you use — that method is established during onboarding so the attribution chain is complete from day one.

The chain is matched record by record. A completed invoice that traces back to an AI-answered call or a text-back thread gets added to your recovered revenue total. An invoice with no corresponding call log or text-back record does not get counted, even if the lead touched the system at some earlier point.

The 60-day statement is produced by the agency. The full compilation methodology is disclosed on the guarantee terms page. If you want to audit the numbers, the underlying call logs and booking records are available on request — you won't need to dig through them yourself, but the data is there if you want it.

On day 60, the agency runs the attribution reconciliation. Recovered revenue from AI-answered calls and text-back conversions gets totaled. If it clears $5,000, the guarantee is met. If it doesn't, the refund process activates — no negotiation, no "let's give it another 30 days" unless that's what you want.

The tight definition makes the evaluation binary. Either the attributed completed jobs hit $5k or they don't. You don't have to argue about whether a lead was warm enough to qualify or whether an open quote should count. The invoice either exists and traces back to the system, or it doesn't.

Before you sign up, run your own number. How many calls did you miss last month? If 10 of those were $500 jobs, the $5k guarantee is one month of normal leakage — and that's a conservative estimate for most HVAC and plumbing operators. The system either stops that bleed or you don't pay.

The full methodology, exclusions, and refund process are on the guarantee terms page. Read it before you commit.