Turning HVAC enquiries into service requests staff can follow up.

An HVAC enquiry needs to become something the office can act on: a customer name, callback number, service address, description of the issue, and a clear next step. Capturing a conversation is only useful if staff can find the request and see whether someone has followed up.

I built HVAC-Automate around that handoff. It brings voice intake and office operations into one product, with a public demo that lets a visitor explore the workflow using fictional customers and requests.

I adapted a separate copy of my existing voice platform for HVAC, reusing its agent configuration and application foundation. The product uses Next.js and TypeScript, Ultravox for the voice-agent layer, Clerk for authenticated access, and Prisma with a dedicated Neon PostgreSQL database.

The staff workflow covers service requests, customer history, request acknowledgement, follow-up tracking, quote progress, and CSV export. Intake captures contact and service details, checks service-area coverage, and requires customer confirmation before saving a request. The dashboard makes staff ownership and the next action visible.

The public demo provides an account-free way to inspect the operations experience. The authenticated application is a separate surface for stored business data; demo records are fictional and changes in the demo stay in the visitor’s browser.

A saved service request is not a confirmed appointment or a dispatched technician. The workflow keeps those responsibilities distinct so that the assistant does not promise an outcome the office has not approved.

I also built staff-notification handling with retry states, so a service request can remain visible in the inbox when an email cannot be delivered. Phone routing and outbound staff emails require deployment-specific configuration and end-to-end validation; they are not demonstrated by the public sample workflow.

Open the demo to explore the service-request, customer, quote, and follow-up views. It demonstrates the application workflow without requiring access to a private business account or placing a real customer call.

This is an independent product build, not a commissioned HVAC deployment. The evidence shows what I built; customer adoption, recovered revenue, and business savings have not been measured. Automated dispatch, calendar booking, and payment collection are outside the demonstrated scope.