Customer Portals

ServiceM8 Customer Portal
so the photos arrive before the phone call.

Their booking and where the job is up to, then the completed work with its photos and form responses, on a login in your branding. It reads live from ServiceM8 while your crews keep working the way they already do.

Most of what a customer wants sits in form responses and attachments rather than tidy fields, so getting those out cleanly is the job. Fixed-price scope, an Australian team, support after launch.

On your domain, in your branding, and yours at the end of it.

  • No per-user fee Portal logins do not cost ServiceM8 seats
  • 18+ yrs Building business software
  • Fixed Price scopes, no surprises
  • You own it Code, docs and credentials
Australian owned and operated

Built here. Your data stays here.

  • No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
  • Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
  • Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.

What your customers see

What your customers see in a ServiceM8 portal

Every screen reads live from ServiceM8, so the figures match because they come from ServiceM8 rather than from a copy somebody refreshes.

  • Their booking and where the job is up to
  • Completed work with photos and form responses
  • Quotes awaiting approval, approvable in the portal
  • Invoices and payment
  • History of every job you have done for them

Who logs in

  • Customers
  • Property managers
  • Strata and building managers

What people ask us for

Start with the job your ServiceM8 portal has to do

The same portal gets asked for in six different ways depending on where you are up to. Select any one to read how we approach it.

ServiceM8 customer portals

ServiceM8 customer portal and client portal

A customer portal for ServiceM8 is a login you own, on your domain, where your customers see their own account. A client portal for ServiceM8 is the same build under the name professional services tend to use. Either way it is not the ServiceM8 login: your customers never get access to ServiceM8, and you do not buy them a seat.

The portal reads live from ServiceM8 through the API, so what a customer sees is what ServiceM8 says right now rather than a figure somebody exported on Friday. A ServiceM8 customer self-service portal removes the calls asking where things are up to.

ServiceM8 customer portals

ServiceM8 customer portal development

We are a ServiceM8 customer portal development company, and this is custom work rather than a product with your logo on it. ServiceM8 portal development starts with what your customers should see and what they should be able to do, because that decides everything after it.

A custom ServiceM8 customer portal is worth building when an off-the-shelf tool cannot model how you actually work: property managers with many sites, or strata arrangements ServiceM8 does not model. Where a product would genuinely do the job we will say so rather than quote.

ServiceM8 customer portals

Build a ServiceM8 customer portal, or a customer app

Some clients want a portal on the web, others want a ServiceM8 customer app their customers keep on a phone. The data layer is the same; the difference is how it is delivered and what it costs to maintain, and it is worth deciding deliberately rather than by default.

Either way it is a ServiceM8 customer portal solution scoped and fixed-price before anything is built, running in parallel with how you work now until you agree it is right.

ServiceM8 customer portals

ServiceM8 customer portal integration

ServiceM8 portal integration is the part most projects underestimate. Connecting a customer portal to ServiceM8 means deciding which system is authoritative for each field, how a portal login maps to exactly one ServiceM8 record, and what happens when two things change at once.

Much of what a customer would want to see in ServiceM8 sits in form responses and photo attachments rather than in tidy fields. Getting those out cleanly, and deciding which of them a customer should see, is usually the actual work rather than the portal itself.

If you already have a portal or a website, we integrate the customer portal with ServiceM8 rather than starting again. If you have neither, we build both.

ServiceM8 customer portals

Invoice, payment and account portals

Most ServiceM8 portals start as a ServiceM8 job portal: their booking and where the job is up to. From there it usually grows into completed work with photos and form responses, quotes they can approve, and invoices.

A ServiceM8 customer account portal and a ServiceM8 customer billing portal are the same build seen from different angles. The work is making sure anything done in the portal lands against the right record, first time, without anybody reconciling it by hand.

ServiceM8 customer portals

Orders, quotes, documents and dashboards

The photos and form responses are the part customers value most, and the part that takes the work to extract cleanly. A ServiceM8 customer order portal, a ServiceM8 quote portal for approvals and a ServiceM8 customer document portal are all the same portal with more of the account exposed. A ServiceM8 client dashboard on the front page answers the question before they go looking.

What ServiceM8 does not hold, we fetch from wherever it does live. That is usually the job system, the CRM or a database, and joining those is the same work as any other integration.

One place, one view

Your customers should not need three logins

ServiceM8 holds part of the picture. The rest is in the job system, the CRM, the payment gateway and wherever your documents live. A portal that only reads ServiceM8 hands your customer a fragment and sends them back to the phone for the rest.

We join them. One login, designed to your brand, showing a complete account view built from every system that has a piece of it.

  • Your accounting system, for invoices, statements and payment
  • Payment gateways, so paying in the portal reconciles correctly
  • Document and photo storage, for job evidence
  • Your CRM, so the contact and the site are one record
  • Your website or app, so the login is part of your brand rather than beside it

How it works now

Every question lands on your desk

  • Customers ring or email to ask the same questions
  • Somebody exports from ServiceM8 and sends it out
  • Chasing takes a person the best part of a day a week
  • No record of who was told what, or when

After

Customers look it up, straight from ServiceM8

  • Available any time, straight from ServiceM8
  • Nothing rekeyed, because it is read rather than copied
  • Anything they submit posted back where you want it
  • An audit trail of who saw what and when

Scoped and quoted before you commit. You own the code, the documentation and the credentials at the end of it.

Get a fixed-price scope
Common questions

Questions owners ask about a ServiceM8 portal

Is this the ServiceM8 login?

No. The ServiceM8 login is where you and your staff work. This is a separate portal you own, for your customers, that reads and writes your ServiceM8 data. Your customers never get access to ServiceM8 itself.

What can customers actually see?

Typically their booking and where the job is up to, completed work with photos and form responses, quotes awaiting approval, approvable in the portal. What they cannot see is anything else, because the portal only ever requests the records belonging to that contact.

What is the hardest part of ServiceM8 portal work?

Much of what a customer would want to see in ServiceM8 sits in form responses and photo attachments rather than in tidy fields. Getting those out cleanly, and deciding which of them a customer should see, is usually the actual work rather than the portal itself.

Do we need a licence for every portal user?

No. The portal reads through the API under one connection, so the number of customers logging in does not change what you pay ServiceM8. That is usually the reason a custom portal costs less than the alternative once you have more than a handful of users.

Will it slow ServiceM8 down or put our data at risk?

The portal reads through the API rather than touching your system directly, so day-to-day use is unaffected. Writes are limited to what you approve, and everything is logged so you can see what changed and when.

How long does it take?

A straightforward portal over ServiceM8 is usually weeks rather than months. We scope it and quote fixed-price before starting.

Tell us what your customers keep ringing about

Which ServiceM8 edition you are on, roughly how many customers would use it, and what they most often ring about. We will come back with a straight answer and a fixed-price scope.

Prefer a quick chat? Call 0425 531 127. We answer the phone in Perth.