We're Owen and Jessica.

We build AI automation and phone systems for service businesses across New Zealand. We started Easy AI Agents after seeing how often good businesses lose work through a phone nobody could answer. But the longer we've worked in voice AI, the clearer one thing has become.

The voice isn't really the point.

It's what happens behind it: what the agent knows, what it checks, what it books, what it sends to your team, and when it knows to bring a person back in.

Owen Chau speaking at the M2 AI Summit
Owen Chau
Jessica Layburn graduating from the University of Canterbury
Jessica Layburn

Two different paths

On paper we have nothing in common. In practice we think the same way.

Jessica trained as an engineer and came through the university route. Owen spent five years helping a family friend grow a construction company, from being on the tools to running the operation, doing concrete, waterproofing, fireproofing and epoxy floors.

Good systems start with the outcome. What are we trying to achieve? Where does it usually go wrong? What does the person doing the work know that nobody's written down yet? That way of thinking matters more in AI than people expect, because the model is never the whole system. The real work is turning the way your business runs into something clear enough for AI to follow.

Why we started

It started with a leaking tap. Jessica was working for a startup at the time and got tasked with organising a plumber. She spent the better part of a day calling around. Most went to voicemail. The rest couldn't give a straight answer without coming out to look first.

None of them seemed like bad businesses. Probably the opposite: busy, skilled, and already stretched. But from the customer's side, the front door was a phone nobody could reliably answer.

That stuck with us. Service businesses lose work in quiet ways. A missed call. A slow reply. A lead that lands after hours. A customer who needed one clear answer before they'd book.

ChatGPT didn't even have voice back then, but the gap was obvious, so we started building. Voice AI looked like part of the answer. Then real calls showed us why most of it lets people down.

What the demos hide

We're wary of polished AI demos. They show one clear caller, perfect audio, a simple question, no consequences. The agent sounds effortless because the situation has been made effortless.

Real calls aren't like that. People interrupt. They mumble. They call from bad reception. They change their mind halfway through.

One call taught us this better than any demo could. We'd built an agent for a client based in Auckland, so it answered the way the business would: "Hi, this is Auckland Services, how can I help?" The caller asked the usual things. Services, pricing, when someone could come out. It went smoothly. Then, right as the agent moved to book the job, they mentioned they were in Invercargill.

And it's never just one moment. On a real call, the agent has to handle:

Auckland Invercargill About 1,600 km away. Slightly outside the service area.
Wrong suburbs Bad audio Misheard contact details Quote corrections Ambiguous yes/no answers Unavailable times Slow or failing tools Stale tool results After-hours judgement calls Human-transfer consent Changing their mind mid-sentence

That's where the work is. Not making an agent sound clever in a demo, but making it useful when the call gets messy.

The voice is the easy part

A voice on its own is just a smarter voicemail. It can answer and sound natural, but if it doesn't understand your business, it can't do much that matters.

A useful agent needs two things: the operating knowledge behind the call (your services, prices, service areas, booking rules, common exceptions, and handover points) and the systems behind the conversation (your calendar, CRM, inbox, and job management tools).

No model arrives knowing that Tuesdays are full or that one suburb sits outside your area. That knowledge lives in your business.

This is the part we care about most. The best agents don't come from throwing a generic bot at your phone and hoping the model works it out. By the time you read this there'll be another dozen models and a hundred new tools, with more next month. The bottleneck was never the technology. It's clarity: how a good staff member handles the call, what they ask first, where mistakes usually happen, and what should never be promised.

Once that's clear, the agent earns its keep. It answers the common questions, captures the right details, qualifies the lead, books the job, and sends your team a clean summary. We build the AI around how your business actually runs.

Where AI earns its place

AI earns its place where the work repeats, the rules are clear, the information exists somewhere, and a person can step in when it matters.

The phone is the sharpest example, and it's our specialty. A missed call becomes a missed job; a rushed one becomes a messy booking. Handled properly, the agent becomes a reliable front door: not a replacement for your people, but a layer that answers, filters, books, and hands over cleanly.

The same thinking runs through the quieter work behind the scenes, the lead follow-ups, the quote reminders, the admin nobody should have to type twice. The phone is where most businesses feel the pain first. The real value comes from connecting that call to everything that happens next.

A human stays accountable

We're firm on one rule: a human stays accountable. AI can't own a mistake, and "sorry, the AI did that" isn't a line your customer wants to hear twice. So we build systems you can understand, review and improve, not black boxes.

On custom builds, the work doesn't stop at launch. We review real calls after they happen, with tooling that flags the moments where the agent hesitated, misread someone, overpromised, or left a gap in the workflow. We tighten it from there, week after week. That's how it gets better over time: not by pretending it's perfect on day one, but by learning from real calls without putting your business at risk.

The Workflow Clarity Map

Because clarity is the hard part, we built something to make it easier and gave it away at the M2 AI Summit. It's a short tool that tells you how clearly you've described a task, before you spend a cent trying to automate it.

01

Answer nine questions

About a task you would like to automate, shaped by the same ORDER framework we use on our own builds: Outcome, Repetition, Data, Exceptions, Risk.

02

Get a clarity score

It rates how plainly you have explained the work and gives you a straight read on where the gaps and edge cases are hiding.

03

Walk out with a plan

Take a pre-filled prompt into ChatGPT, Claude or Gemini, or answer one more question for a full 30-day build plan that's yours to keep.

No email required, and free while it's open. We can't keep it free forever.

Two ways to work with us

Some businesses want an affordable way to start. Others want it built properly around how they already operate. We do both.

Self-managed

Set it up yourself

Our self-managed dashboard is a practical way to start. You set up an agent yourself, no custom build required, and it answers your common questions, captures caller details, and hands you a clean transcript of every call.

For businesses with straightforward, repeatable enquiries, it's a low-cost way to get going and see where voice AI fits.

Custom build

Built around your business

This is our deeper work. We sit with you, map how your calls and workflows actually run, build the agent around your rules, and wire it into the systems your team already uses.

Then we keep improving it from real calls. The goal was never a good first demo. It's an agent that still holds up on the thousandth call.

We treat every build like it's our own phone ringing.

We're based in Christchurch and we work with service businesses across New Zealand. If you're looking at voice AI but don't want another generic bot, we should talk.