A functional MVP.
- U.S. telephony and Vapi voice intake
- Structured lead capture
- Cloudflare Queue and Worker pipeline
- Supabase persistence and dashboard data
- Resend email notification
- LeadBackstop dashboard
Products / LeadBackstopCarry the
Carry the
conversation forward.
Automated phone intake for independent U.S. residential HVAC contractors. Capture the caller’s details, review the inquiry and follow up when you are ready.
Functional MVP · Preparing for live contractor pilot
PHORTIX / A MORE SYSTEMATIC TOMORROW
The job in front of you.
The call you can’t take.
For independent U.S. residential HVAC contractors, attention is a limited resource.
LeadBackstop connects automated phone intake to a structured record and human follow-up. It does not diagnose HVAC issues, promise appointments or dispatch emergency services.
Inside the productA conversation becomes
EXAMPLE EXPLORERA conversation becomes
something you can act on.
Follow an illustrative inquiry from the caller’s words to the information a contractor needs. Change the scenario to see what changes—and what still belongs to a person.
Fictional data · browser-only · no call placed
Conceptual presentation, not an actual dashboard screenshot
01 / What the caller says
“The air conditioner is running, but the house isn’t getting cool. Could someone call me back?”
The intake needs a callback number, the service location and the caller’s description. The contractor decides what to ask next and whether to schedule a visit.
03 / The human next step
Review the description, confirm the service area and call the customer to clarify the issue. Scheduling and technical assessment stay with the contractor.
02 / Structured contextSAMPLE RECORD
- Caller
- Example caller
- Callback
- 202-555-0142
- Service location
- Example service address
- Reported issue
- AC running; home not cooling
- Reported urgency
- Caller requests a callback
- Hazard context
- Not reported in this example
EMAIL / FOLLOW-UP CONTEXT
New inquiry · Cooling issue
The email is an alert to review an inquiry. It is not a booking confirmation.
01 / What the caller says
“The heating isn’t coming on. I’m at home this afternoon and would like to speak with someone.”
Capture what the caller reports without turning a symptom into a diagnosis. Availability is context for a conversation, not an appointment reservation.
03 / The human next step
Call back to confirm the details and availability. The intake does not promise a response time, identify a faulty component or reserve a technician.
02 / Structured contextSAMPLE RECORD
- Caller
- Example caller
- Callback
- 202-555-0142
- Service location
- Example service address
- Reported issue
- Heating not coming on
- Reported urgency
- Caller requests contact this afternoon
- Hazard context
- Not reported in this example
EMAIL / FOLLOW-UP CONTEXT
New inquiry · Heating issue
A requested time is a caller preference. It is not a service-level commitment.
01 / What the caller says
“I need someone to take a look at my system, but I don’t have all the details right now.”
The useful distinction is between information that was actually provided and information that is still missing. A plausible guess is not a customer answer.
03 / The human next step
This example does not yet contain enough information for a reliable callback. Missing details need review; automated intake cannot guarantee a usable lead from every call.
02 / Structured contextSAMPLE RECORD
- Caller
- Not provided
- Callback
- Not provided
- Service location
- Not provided
- Reported issue
- Caller requests a system check
- Reported urgency
- Not specified
- Hazard context
- Not established
EMAIL / FOLLOW-UP CONTEXT
Illustrative review · Missing context
This example explains an incomplete record. It does not claim that a separate missing-data alert is a shipped feature.
Illustrative examples show the handoff from caller to contractor. Explore the infrastructure for implementation details.
See the system behind itCurrent architectureA signal enters.
A signal enters.
A useful record leaves.
Explore the six steps in the documented working pipeline.
LEADBACKSTOP / DOCUMENTED PIPELINEInteractive illustration · not live data
01 / Inbound phone call
The conversation begins.
A customer calls while a contractor is occupied. The inquiry enters the automated intake path.
02 / Vapi
Listen with a purpose.
Vapi gathers the information needed for a useful follow-up, without diagnosing an HVAC problem or promising a booking.
03 / Lead record
Give the signal a shape.
Caller name, callback number, service address, issue, urgency and hazard fields form a consistent lead record.
04 / Cloudflare
Carry the context forward.
A Cloudflare Queue and Worker pipeline process the structured output, separating intake from downstream handling.
05 / Supabase
Keep the information useful.
Supabase persists lead information for the dashboard data layer, making the captured inquiry available for review.
06 / Resend + dashboard
Put the next move in human hands.
A Resend email alert and the LeadBackstop dashboard make the lead available for a contractor to review and follow up.
Structured data contractKeep the context.
Keep the context.
Make it inspectable.
Field definitions from the current intake model. No customer records are displayed.
- 01
caller_name - Caller identification.
- 02
callback_phone - A number for returning the inquiry.
- 03
service_address - The reported service location.
- 04
issue_description - The reason for the call, as described.
- 05
urgency - The urgency reported during intake.
- 06
hazard_detected - A hazard flag for safety handling.
A different situation.
A different next step.
Where a hazard is identified, the intake flow directs the caller toward emergency services as appropriate. It does not provide HVAC diagnosis or promise an emergency response.
Hazard identified→Safety guidance→Emergency services where appropriate
Current system / future workBe precise about
Be precise about
what is real.
Validation before expansion.
- Live contractor pilot — preparation stage
- SMS alerts — planned
- Live technician transfer — validation-dependent
- Native field-service integrations — planned
No customer revenue or product-market-fit metrics are claimed.
Product questionsThe details behind
The details behind
the first impression.
A closer look at scope, fit and the current stage of the product.
Who is LeadBackstop being prepared for?
Independent U.S. residential HVAC contractors. The initial focus is the moment an inbound inquiry needs to be captured while the contractor is occupied. This is a specific pilot audience, not a claim that the product has been validated across trades or markets.
Does it diagnose the problem or book the job?
No. The current assistant performs automated intake. The contractor reviews the information, applies professional judgment and handles follow-up. A caller’s requested time does not become a confirmed booking.
Where does the captured information go?
The documented pipeline processes the structured output through Cloudflare, persists lead information in Supabase and makes it available through a Resend email alert and the LeadBackstop dashboard.
Can I use SMS alerts or live technician transfer?
These are future or validation-dependent capabilities. The current delivery channels described here are email and dashboard. Native field-service management integrations are also planned rather than shipped.
What has been validated so far?
A functional MVP and documented end-to-end pipeline exist. A live contractor pilot is being prepared. This website does not present customer revenue, adoption figures or product-market fit as established facts.
How do I discuss the pilot?
Visit leadbackstop.com for the product’s own information, or contact info@phortix.com with your operating context. No enrollment, pricing, pilot start date or availability is promised by this website.
The next useful conversationStart with