← ALL CASE STUDIES27 July 2026

Every enquiry answered in under a minute, in the owner's own voice

Written by Raghav Chegu, founder at Odyssey, who built the system described here. Client anonymised pending their approval to be named.

Summary. A Melbourne HVAC installation business was losing jobs because the owner is on the tools all day and enquiries sat unanswered. Odyssey built a system that captures every enquiry, replies in his own voice inside a minute, qualifies the job against his own checklist, and routes anything sensitive straight to him with no automated reply at all. A working end to end demo, including a real missed call turning into a real SMS conversation, existed five days after the first information pack landed.

The problem in the owner's words

He runs the business himself. A customer calls, he is under a ceiling or in a roof cavity, so the call goes to a reception service or to voicemail. The reception service emails him a name, a phone number, a postcode and a reason. That capture works. Everything after it stalls.

The email sits until he is off the tools, sometimes a full day. After hours and weekends went to voicemail, which he described as a black hole where leads were lost outright. By the time he replied, a competitor had already answered and the customer had anchored elsewhere.

The quality of his replies was never the issue. When he does reply, he wins. The problem was purely that one person was the entire pipeline, and there was nothing between an enquiry arriving and him picking up his phone.

What we ruled out first

Off the shelf AI receptionist products were the obvious answer and we rejected them. He had already tried one and hated it. It sounded robotic, and a large share of his customers are elderly, hard of hearing, or speaking English as a second language. A generic bot was a worse experience than a slow human.

We also ruled out no code glue tools, which he had already burned time on, and hiring an office person, which contradicts a deliberate decision he had made to run lean.

The decision that mattered: keep the human reception service as the first touch, and put the automation immediately after it rather than in place of it.

What we built

A capture to response pipeline running on infrastructure Odyssey owns and maintains.

  1. A watcher on the lead mailbox picks up website form enquiries and forwarded reception emails. Anything unparseable still becomes a lead card. Nothing is ever dropped.
  2. A classifier sorts each message into new enquiry, thread reply, complaint, warranty, or other. Complaints and warranty cases are a hard stop. No draft is generated, an urgent flag is raised, and the owner handles it personally. When the classifier is uncertain it defaults to treating the message as a complaint, because the expensive mistake is an automated reply to an angry customer.
  3. An acknowledgement goes out in his voice, always after hours, which closes the voicemail black hole.
  4. The enquiry is qualified against an eleven field minimum drawn from his own quoting patterns. Larger commercial systems route to a phone or site consultation rather than a written quote.
  5. Replies are drafted against a voice profile built from his real sent emails. The system asks only for the fields that are missing, never quotes a price, and signs off the way he does.
  6. A missed call now triggers an SMS conversation. The customer replies by text and the system carries the qualification from there.

What is proven, and what is not

We do not describe systems as working until they have run end to end against real infrastructure.

  • The missed call path is proven live. A real inbound call went unanswered, a real SMS was delivered, the customer reply came back in, and the system answered it. Signature validation and a number allowlist are enforced and fail closed, verified against both valid and forged requests.
  • The guardrails are covered by a pinned fixture matrix. Complaints, warranty cases, prompt injection attempts and unusual enquiries all escalate with no draft produced. Duplicate enquiries from the same phone number on the same day collapse into one. Tests assert that no price and no em dash ever appears in an outbound message.
  • Seventeen of seventeen tests green on the current build, on top of the thirteen scenario fixtures from the first cut.
  • The owner reviewed a live walkthrough and rated it around sixty five percent of the way there. The gap he named was pricing and question accuracy plus tone, not the concept. That work is in progress. We publish the number he gave us rather than a rounder one.

What it replaced

Voicemail as an after hours fallback, gone. Gut feel triage of an inbox, replaced by lead cards with urgency flags. Quotes going out with no follow up at all, replaced by a scheduled chase. The reception service stays for now, because a human voice answering a live call is still worth paying for, and the data will decide later whether it can be downgraded.

Why this is repeatable

None of it is HVAC specific. Any owner operated trade or service business with one person answering everything has the same shape of problem: capture works, response does not, and the owner's judgement is the bottleneck rather than the product. The voice profile and the qualification checklist are the only parts that change per business.

Have a version of this problem?

Odyssey builds AI-powered automation for Australian businesses. We map the workflow, build the system, and keep it running.

GET A FREE AUDIT →