The latest articles on DEV Community by Rayhan Mahmood (@nevermiss). https://dev.to/nevermiss https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3861281%2F19248822-57de-47d1-a831-fab63bfe0380.png https://dev.to/nevermiss en Rayhan Mahmood Sat, 04 Apr 2026 17:05:11 +0000 https://dev.to/nevermiss/how-i-built-an-ai-phone-agent-that-actually-books-jobs-for-contractors-21p9 https://dev.to/nevermiss/how-i-built-an-ai-phone-agent-that-actually-books-jobs-for-contractors-21p9 <h1> How I Built an AI Phone Agent That Actually Books Jobs for Contractors </h1> <p>Home service companies lose billions from missed calls every year. 78% of customers go with the first company that responds. For HVAC plumbing and roofing companies every unanswered call during peak season is $300-500 walking out the door.</p> <p>Traditional answering services charge $1-2 per minute and the operators dont know anything about the trades. AI voice agents fix this but most of them are built for generic businesses not contractors.</p> <p>I built NeverMiss to solve that. Let me walk through how the tech works and what I learned along the way.</p> <h2> The stack </h2> <p>Vapi handles voice AI orchestration. ElevenLabs does the voice synthesis. OpenAI powers the conversation intelligence. Twilio handles telephony. Make.com runs the workflow automation. The whole thing plugs into whatever CRM the contractor already uses whether thats ServiceTitan Housecall Pro Jobber or just Google Calendar for smaller shops.</p> <h2> Why generic AI receptionists fail for contractors </h2> <p>Most AI answering services treat every call the same. Collect name number and reason for calling. Transfer or take a message.</p> <p>That works for a dentist office. It doesnt work for a plumber at 2am when someones basement is flooding.</p> <p>Trade calls need triage. The AI has to figure out if its an emergency or routine, new customer or existing, service request or just a quote, and whether its something the company even handles. An HVAC company doesnt want their AI booking a call for ductwork installation when they only do residential service.</p> <h2> The prompt engineering challenge </h2> <p>The biggest technical problem wasnt voice quality or latency. It was getting the AI to ask follow up questions without sounding like a robot reading a checklist.</p> <p>Early versions would rapid fire questions. Whats your name whats your number whats your address whats the problem. Real receptionists dont talk like that. They have a conversation.</p> <p>The fix was structuring the prompt as a conversation flow instead of a data collection form. The AI acknowledges what the caller says, asks one question at a time, and uses natural transitions like "got it and whats the best number to reach you at" instead of "please provide your phone number."</p> <h2> Edge cases are where the real work lives </h2> <p>What happens when the caller says "my water heater is making a banging noise and theres water on the floor"? Thats an emergency. The AI needs to pick up on urgency without the caller explicitly saying the word emergency.</p> <p>What about pricing questions? Most contractors dont want pricing disclosed over the phone. But saying "I cant help with that" kills the call. The AI needs to give a range or explain that pricing depends on the situation and theyll get a quote when the tech comes out.</p> <p>What about Spanish speakers? Heavy background noise from a job site? Someone who puts the phone down mid conversation to deal with a leak thats flooding their kitchen right now?</p> <p>Each of these required specific handling in the prompt and sometimes in the voice config itself.</p> <h2> Voice quality is the whole game </h2> <p>In testing the biggest factor in whether callers trusted the AI wasnt how smart the responses were. It was the voice.</p> <p>Early versions sounded too perfect too smooth too obviously synthetic. Callers would immediately say "am I talking to a computer" and either hang up or get hostile.</p> <p>The fix was counterintuitive. Make the voice slightly less perfect. Add natural pauses. Vary the speed. Use a voice with character instead of the generic default.</p> <p>ElevenLabs gives you control over stability, similarity, style, and speed. The sweet spot for contractor calls is stability at 0.7, style at 0.1, and speed at 0.8. This sounds like a calm competent receptionist instead of a text to speech engine.</p> <h2> The math </h2> <p>The system answers every call within one ring 24/7/365. It handles emergency triage, appointment booking, lead qualification, and FAQs. After each call it logs everything to the CRM and sends a summary via text and email.</p> <p>For an HVAC company doing $3-5M the math is simple. They miss 3-5 calls per day during peak season. At a $400 average ticket and 60% close rate thats $720-1,200 in lost revenue daily. The AI costs and pays for itself in the first week.</p> <h2> Try it </h2> <p>Theres a live demo at nevermisshq.com/demo. Enter any business name and phone number and the AI calls you back in under 60 seconds. Test the conversation, throw weird scenarios at it, hear the voice quality.</p> <p>If youre building voice AI for any industry the biggest lesson I learned is that the technology is the easy part. Understanding the domain deeply enough to handle the edge cases is what turns a demo into a product.</p> <p>nevermisshq.com</p> <h1> ai #voiceai #startup #automation #homeservices </h1> ai webdev startup