LeadProc

Overview

Home service contractors miss calls while they are on a job. A missed call is often a job that goes to the next listing. LeadProc is built to intercept that moment: when a call does not connect, the product starts an SMS conversation, gathers context, and hands a structured summary back to the contractor.

What was engineered

Telephony. Telnyx handles call forwarding and SMS. A missed call fires a webhook into the application, which starts the outbound text.

Conversation layer. OpenAI runs a stateful SMS thread using the contractor’s business context and qualification criteria.

Lead handoff. When a conversation ends or times out, the system produces a structured summary — contact details, problem description, and urgency — and stores it for the contractor.

Multi-tenant core. Each contractor has a number, business context, and qualification criteria. Tenants are separated in the data model.

Product surfaces. Public site and product UI built with Astro. Hono serves the webhook-heavy API. PostgreSQL holds the relational data. Stripe is in the stack for billing.

Technical approach

The system is webhook-first: telephony events have to land and produce a conversation, not a dashboard mock. Hono keeps that path small. Telnyx is the telephony provider. PostgreSQL stays deliberately simple.

Status

The core intercept-and-qualify flow is functional: missed call → SMS → conversation → lead summary. Contractor dashboard and billing are in active development. Public product site: leadproc.com.

Interface shown with representative data. Names, phone numbers, and timing values are illustrative and are not measured customer results.

This case study does not claim response-time benchmarks, usage volume, or revenue impact.