Ask a trade business where its customer conversations live and you get an uncomfortable answer. Some on the office landline. Some in an email inbox. Most of them, these days, in WhatsApp on somebody’s personal phone.

That last one is the problem. Not because WhatsApp is bad — customers like it, it is fast, and it is where photos of a leaking valve naturally get sent. The problem is who owns the conversation.

The three things that go wrong

Work gets lost. An enquiry arrives while someone is under a floor. They mean to deal with it later. Later does not come, and you never find out you lost the job.

Nobody else can see it. The customer rings the office to ask about what was agreed. Whoever answers has no idea, because the agreement is in a chat on a van driver’s phone.

It walks out of the door. When someone leaves, the conversations leave with them — along with the customer relationships and, in some cases, the phone number the customers have been messaging for years.

None of these are software problems exactly. They are all consequences of customer conversations living somewhere the business cannot see.

What “bringing it into ServiceM8” actually means

If your jobs are already in ServiceM8, the useful move is to put the messages next to the job rather than in a separate app.

In practice that means three things:

  • A message from a new customer arrives somewhere the office can see it, ready to become a job or a quote.
  • Anyone with the right access can open the job and read the whole conversation, whether or not they were the one having it.
  • Replies go out from the business number, so the customer’s experience does not change at all.

The customer notices nothing. That is rather the point.

When it is worth doing

It is worth doing if more than one person deals with customers, or if you have ever lost an enquiry and only found out weeks later.

It is worth doing if you are the only person now but you intend not to be. Untangling this later, once there are three years of history on a personal phone, is considerably harder than setting it up straight.

When it is not

If you genuinely take all your work by phone and none by message, this solves a problem you do not have. Fix something else first.

And if your ServiceM8 setup is not sound underneath — if jobs are not being raised properly, or the paperwork is not coming back off site — do that first. Better messaging on top of a broken workflow just gets you to the wrong answer faster.

The things to check before you commit

A few questions worth asking of any option you look at, ours included:

Does it use the official WhatsApp Business Platform? Anything built on an unofficial route can have the number cut off, and it will not be your supplier who deals with the consequences.

Do you keep your number? If the answer involves getting a new number and telling your customers, that is a much bigger change than it sounds.

Does the app on your phone keep working? For most trade businesses the answer needs to be yes. You will still want to message from the van.

Who can send, and does anything send by itself? If a tool sends messages to your customers without a person reading them first, you should know that up front and decide whether you are comfortable with it. We are not, which is why ours drafts and a person approves.

What does the messaging itself cost? Meta charges for WhatsApp Business Platform messages on its own published rates, separately from whatever the software costs. Any honest supplier will tell you that without being asked.

What we built

Our WhatsApp add-on for ServiceM8 does exactly what is described above: enquiries land in your ServiceM8 Inbox ready to become jobs, your team replies from the job, you keep your existing number, and optional AI drafts a reply for a person to approve before it goes anywhere.

It is in private beta with UK trade businesses at the moment. If you want to try it, get in touch.