Skip to main content
Clever Ops

Case studyReal job

How we connected an AI phone agent to ServiceM8

We built an AI phone agent that answers the calls the team can't get to, and a chat on their website that does the same job in writing.

  • TwilioAI line and texts
  • ElevenLabsThe voice agent
  • ClaudeThe language model
into
  • ServiceM8Inbox and Tasks

The call in the film is made up, and every screen shows sample data.

Transcript

This is a made-up breakdown call, answered by an AI phone agent we built for a refrigeration and air conditioning business. While the caller is still on the line, the on-call phone gets a text. When the call ends, the enquiry goes into the business's ServiceM8 Inbox, with the transcript in it.

They're a refrigeration and air conditioning business in regional Australia, and they'd worked with us before. They came back to us about the phones. Like a lot of trade businesses, their phone rings when everyone's busy or out on a job.

Calls the team couldn't get to went through to voicemail. A voicemail often missed the site, the fault or how urgent it was. Someone then had to write each message up and key it into ServiceM8 by hand. And there was no record of what people were ringing about.

Here's how it works now. The office line rings the team first. If nobody picks up, the call diverts to a new number, and the AI agent answers. It says straight away that it's an AI and that the call is recorded. Then it takes a name, the site, the fault and how urgent it is.

It asks for the best number to call back on and reads it back. A diverted call can show the office's own number, so the agent doesn't rely on caller ID.

Every enquiry is sorted into a category and posted into the ServiceM8 Inbox, with an email copy to the office. If the caller quotes a job number that matches exactly one job, it becomes a Task on that job instead.

Breakdowns don't wait for the call to end. Once the caller has confirmed their number, the agent raises the alert, and the on-call mobile gets a text with the name, the number, the site and a summary. After the call, the caller gets a text too, if they gave a mobile.

The website got the same thing as a chat. It answers from content the team has approved, and it doesn't quote prices or book jobs. For an ordinary enquiry, the visitor checks a summary and presses Send before anything goes to ServiceM8.

The team has a dashboard with every call and chat, the transcripts, and whether each delivery went through. They edit what the assistant knows there too. A person still calls the customer back and turns an Inbox message into a job. The system doesn't create a job, a client or a quote.

Now the detail. The new number is a Twilio number, connected to an ElevenLabs agent through ElevenLabs' own Twilio integration. The agent's language model is Claude. It has one tool of ours, the urgent alert, which calls our system in the middle of the call.

When the call ends, ElevenLabs sends the transcript to our system as a webhook, signed so we can check it came from them. We store it and answer straight away, and a separate worker does the rest. Another job looks for any call whose webhook didn't turn up.

Each enquiry is saved with one delivery record for every place it has to go, all in one transaction. The worker sends each one on its own. So a failed email can't hide a failed ServiceM8 post, and the dashboard shows each one's status.

ServiceM8's Inbox takes a subject, a plain-text message and a sender name. There's no category field, so the category goes in the subject. It also doesn't take an ID from us. So if a response gets lost, the system doesn't send it again and risk a duplicate. It parks it for a person, and the office email still goes.

The texts go out through Twilio, from the AI line's number. ServiceM8 lists sending SMS among the things a public add-on can do over OAuth. This build connects to one account with an API key, which is how ServiceM8 sets up a private connection.

It went live in November 2026, so it's new. We haven't measured anything yet. There was no count of missed calls before it went in, so there's no before and after to show you.

If your calls are going to voicemail while the team's on the tools, and messages are being keyed into ServiceM8 by hand, get in touch.

Each enquiry is sorted into a category and posted into the ServiceM8 Inbox, with an email copy to the office. When a caller reports a breakdown, the on-call mobile gets a text while the caller is still on the line.

How and why they came

They'd worked with us before, and came back to us about the phones. When the team was busy or out on a job, calls went to voicemail, and each message had to be written up and keyed into ServiceM8 by hand.

We scoped two things: an AI phone agent for the calls nobody could answer, and a chat on their website, both feeding ServiceM8.

The problem

  • Calls went to voicemail when the team was busy or on site.
  • A voicemail often missed the site, the fault or how urgent it was.
  • Messages were keyed into ServiceM8 by hand.
  • There was no record of what people were ringing about.

What we built

  1. 1
    Twilio

    The call chain

    The office line rings the team first. If nobody answers, the call diverts to a new Twilio number, where the AI agent picks up. After hours, calls go straight to the agent. The divert lives in the business's own phone system, so their phone provider set it up at our request.

  2. 2
    ElevenLabsClaude

    The phone agent

    It says up front that it's an AI and that the call is recorded. Then it takes a name, the best number to call back, the site, the fault and how urgent it is. It reads the number back, because a diverted call can show the office's own number as the caller ID. It doesn't give prices, book times or say a technician is on the way.

  3. 3
    ServiceM8Resend

    Into ServiceM8

    Each enquiry gets one of seven categories: breakdown, air conditioning service, new installation quote, scheduled maintenance, parts or supplier, accounts, or existing job follow-up. It's posted to the ServiceM8 Inbox with the category in the subject, and a plain-text message with the caller's details, their request, the transcript and a link to the dashboard. If the caller quotes a job number that matches exactly one job, it becomes a Task on that job instead. The office gets an email copy.

  4. 4
    ElevenLabsTwilio

    Urgent breakdowns

    Once a caller reporting a breakdown has confirmed their number, the agent calls our system mid-call, and the on-call mobile gets a text with the name, callback number, site and a summary. After the call, a caller who gave a mobile number gets a text confirming what was passed on.

  5. 5
    Claude

    The website chat

    It answers from content the team has approved, doesn't give prices or book jobs, and fills in an enquiry summary as it goes. For an ordinary enquiry, the visitor checks the summary and presses Send. If a visitor leaves contact details but doesn't press Send, the office gets an email instead.

  6. 6

    The dashboard

    Staff see each call and chat with its transcript, call recordings, and the status of each delivery. They edit and publish what both assistants know.

A made-up breakdown call, on sample data

  • The made-up call's transcript in the staff dashboard.

    Staff dashboard, run locally. Sample data.

  • The message the system builds for the ServiceM8 Inbox.

    The system's own output. Sample data.

  • The urgent text for the on-call phone, raised mid-call.

    The system's own output. Sample data.

  • The website chat's summary, waiting for Send enquiry.

    Website chat, run locally. Scripted sample visitor.

What a person still does

Staff call the customer back and decide what happens next. They turn an Inbox message into a job, choosing its job category in ServiceM8, and they check anything the system has parked. The system doesn't create a job, a client or a quote.

The technical detail

What each system allowed

Twilio, ElevenLabs and Claude

  • ElevenLabs connects an agent to a Twilio number through its own Twilio integration, and sets the number up for you.1
  • Claude models are among the language models an ElevenLabs agent can use.2
  • An agent can also call outside systems during a conversation through webhook tools.3
  • Ours has one, and it raises the urgent alert.

ElevenLabs post-call webhooks

  • After a call, ElevenLabs can send the full conversation, including the transcript, to a webhook.1
  • Webhooks are authenticated with HMAC signatures, checked through the ElevenLabs-Signature header, and a failed webhook can be retried.1
  • The system checks the signature, stores the event and answers before doing anything slow.
  • A separate job looks for calls whose webhook didn't arrive.

Documentation

  1. 1Post-call webhooks

The ServiceM8 Inbox

  • Creating an Inbox message takes a subject and a plain-text message, with an optional sender name.1
  • The request has no category field, and it doesn't take an ID we choose.1
  • So the category goes in the subject, and a reference of our own goes in the subject and the message so staff can match it to the dashboard.

ServiceM8 Tasks

  • A Task can be created with an ID we supply, linked to an existing record such as a job.1
  • The system uses a Task only when a quoted job number matches exactly one job.

Documentation

  1. 1Create a task
Twilio

Connecting to ServiceM8, and the texts

  • ServiceM8 offers API keys for connecting to your own account, and OAuth for public applications, and lists sending SMS among the things public applications can do.1
  • This build connects with an API key.
  • The texts go out through Twilio's messaging API, from the AI line's own number.2

Vendor links checked 15 November 2026.

Design decisions

  • One record per destination

    Each enquiry is stored with one delivery record for each place it has to go, in a single transaction, and a worker delivers each one on its own. A failed email can't hide a failed ServiceM8 post, and the dashboard shows each status.

  • No blind resends into the Inbox

    If ServiceM8 doesn't answer a create, the system doesn't send it again and risk a duplicate. It parks the item for a person, who checks ServiceM8 and either marks it delivered or resends it. The office email goes either way.

  • Categories of our own

    The business's ServiceM8 job categories didn't map one to one onto the kinds of enquiry, so the seven categories are the system's own labels, written into the subject and the message. Staff choose the job category when they convert the message. Urgency is stored separately, so a follow-up can be urgent too.

  • Caller ID isn't a callback number

    The agent asks for a number and reads it back, and the system won't take the business's own numbers as a callback.

The hard parts

  • Getting calls to the agent

    The divert lives in the business's phone system, not ours. The rules were: staff first, the AI before any voicemail, and no loops between numbers. We set those out, and their phone provider made the change.

  • Alerts that can't wait for the call to end

    The alert is raised by the agent's tool during the call, before the transcript exists. When the transcript arrives afterwards, it's added to the same enquiry, so the on-call phone isn't texted twice.

Where it stands

Live since

November 2026

  • The agent answers the calls the team can't get to.
  • The chat is on the website.

It's new, and nothing has been measured yet. There was no count of missed calls before it went in, so there's no before and after figure on this page.

Questions

Can an AI phone agent put enquiries straight into ServiceM8?

On this job, yes. Each enquiry is posted to the ServiceM8 Inbox through ServiceM8's API, with the category in the subject and the caller's details and transcript in the message. A follow-up quoting a job number that matches exactly one job becomes a Task on that job.

Will the AI book jobs or quote prices?

Not on this job. It takes a message, flags breakdowns and tells callers the team will call back. It doesn't give prices, book times or say a technician is coming.

Does every call go to the AI?

No. The office line rings the team first. Calls nobody answers divert to the agent, and after hours calls go straight to it.

How does the on-call person hear about a breakdown?

By text, sent through Twilio while the caller is still on the line, once the caller has confirmed their number. It carries the name, callback number, site and a summary.

What happens if ServiceM8 doesn't respond?

The item is parked for a person to check instead of being sent again, and the office email still goes.

Calls going to voicemail, and messages keyed into ServiceM8 by hand?

Book Free Assessment

Product names and logos belong to their owners and are shown to identify the systems connected.