Capture the essentials
Equipment type, the customer’s own description of the problem, location, and a preferred time window arrive in one readable request.
Proposed pilot · Lagos, Nigeria
Turn the first HVAC message into a clear next step.
I’m Diamond Anyanwu. I’m proposing an AI-assisted lead-response and booking-coordination workflow for HVAC contractors — capturing the right details while keeping your team in control.
No live contractor system is connected. Nothing on this page diagnoses, quotes, or books.
Workflow concept 01Pilot only
New requestHuman handoff
Structured request
“AC not cooling · Ikeja · Tue afternoon”
Local-only demonstrationFictional details recommendedManual confirmation required
My approach
Less back-and-forth.
More useful first messages.
Based in Lagos, Nigeria, I focus this portfolio on a practical operations problem: turning an incomplete enquiry into a clear staff handoff. This proposed pilot organizes intake without replacing contractor judgment or dispatch decisions.
Keep answers governed
Only company-approved FAQs could be used after launch. Until a knowledge base exists, the workflow does not claim approved answers.
Hand off to humans
Staff review the request, follow up for what is missing, and confirm whether a visit can be scheduled. No automatic appointment promise.
A simple intake path
Make the first message
easy to act on.
01
Customer describes the need
Ask for the equipment type, problem in their own words, service location, and preferred time. Optional photo or voice note can add context.
Customer input
02
Request is formatted for staff
A concise summary makes it easier for a team member to see the request, spot missing information, and decide what to ask next.
Structured handoff
03
Staff review and confirm
A contractor’s team checks availability, gives any approved guidance, and manually confirms or declines a scheduling option.
Human decision
Proposed pilot scope
A careful start,
before any launch.
This is a concept to review with an HVAC contractor — not a live product, client case study, or claim of results.
Included to explore
Lead intake fields · staff-ready summaries · approved-FAQ gating · manual scheduling handoff
Must be agreed first
Contractor knowledge base · escalation rules · data retention · channels · staff ownership · privacy language
Explicitly out of scope
Technical diagnosis · unapproved quotes · automated booking · guaranteed response or appointment
Local-only interactive demo
Shape a staff-ready
request summary.
Use fictional details.This demo formats fields only; it does not run an AI model. It sends no form data, saves nothing, and keeps attachments on your device. No contractor is connected.
FAQ governance
Helpful without
making things up.
A future pilot could answer only questions the contractor has explicitly approved. These examples are illustrative, not live business facts.
What can the demo answer today?+
Nothing about a real contractor’s services, pricing, coverage, or technical advice. It only demonstrates how a request can be organized for staff review.
What happens to an appointment request?+
It stays pending. A staff member would need to review availability and manually confirm the next step. The demo never creates a booking.
Can it diagnose an HVAC problem?+
No. Customers can describe symptoms in their own words, but diagnosis, safety guidance, and recommendations remain with a qualified contractor.
What would need approval before launch?+
A contractor-provided FAQ or knowledge base, escalation boundaries, privacy and retention rules, operating hours, and the team responsible for manual follow-up.
Guardrails first
A workflow should
earn its trust.
01Customer controlNo real details are needed for this demo. Attachments remain local and are not uploaded.
02Clear uncertaintyPreferred times are requests, not slots. Staff confirmation is always required.
03Respect the tradeThe workflow organizes information; it does not impersonate a technician or make a safety-critical call.
Interested in the thinking?