What ServiceM8 does for a mobile equine business
ServiceM8 is field service software built for people who work out of a van: jobs, scheduling on a map, forms filled in on site, quotes, invoices and card payments taken at the yard. That fits farriery and a good deal of equine ambulatory work better than a salon-style appointment app, because the unit of work is a journey rather than a chair.
It also offers online booking that customers can reach from your website, either as a link or embedded in a page, so a request arrives as a job rather than as an email you have to retype. Feature detail changes, so confirm what your plan supports with ServiceM8 before a page promises it.
The performance question is where the embed goes. The answer is on the page where someone wants to book, never on every page.
The rule
Nothing from ServiceM8 loads until a visitor taps Book. Service pages, the fees page, the yard page and the team page are for reading and deciding, and they link to booking. One page carries the embed.
The booking page
One page, usually /book. Above the embed: a line saying what it asks for and that you confirm the day, the route-day areas, and the phone number. Below it: nothing. Reserve the height so the page does not jump while the widget loads, and preconnect to the ServiceM8 domain in the head.
<link rel="preconnect" href="https://book.servicem8.com">
<div class="booking-embed" style="min-height: 760px">
<!-- ServiceM8 online booking embed -->
</div>Where the embed misbehaves inside a phone's in-app browser, and Instagram and Facebook browsers are where a lot of yard traffic comes from, send visitors to the hosted booking page instead and bring them back with a link.
Configure ServiceM8 before the site links to it
- Services matching your site's service pages exactly, with the same names and durations, so the confirmation says what the page said.
- Booking questions kept short: yard name and postcode, access and gate code, how many horses with names and ages, the work, whether someone will hold, a mobile that will be answered on the day.
- Areas and availability set so a request lands near the right route day rather than anywhere in the week.
- Badges or job categories per service, so route days can be filtered on the map.
- Forms for the on-yard paperwork you actually collect, signed on the device.
- Quote and invoice templates showing the visit fee as its own line, matching the fees page.
- Notifications going to a phone somebody carries between yards.
- Card payment enabled if you take payment at the yard.
Send yourself a test booking from your own phone before anything is linked.
Deep links from service pages
Each service page's button should open booking with that service already chosen where ServiceM8's booking links allow it, so someone reading the shoeing page sees shoeing rather than a menu. Where it does not, take them to the booking page with the service named in the heading above the embed. Either way, the visitor should never have to remember what they came for.
The emergency route stays above the booking
This is the part general advice about embedding booking software gets wrong for equine work. The header on every page carries the emergency number as a tappable link, and on phones a slim bar fixed to the bottom with Call and Book. An owner with a colicking horse must not meet a booking widget. Booking is for the calm day.
Where ServiceM8 stops
ServiceM8 runs jobs, not clinical records. A veterinary practice that needs the horse's clinical history, medicines and passport work will run Provet Cloud or ezyVet for the record and may keep a field tool for scheduling. Farriers and therapists usually need only the job. Be clear which you are before you build the booking around one system, and never ask ServiceM8's public booking form for clinical detail that belongs in a practice system.
Testing and tracking
Test on iOS and Android, in Safari and Chrome and in the Instagram and Facebook in-app browsers. Submit a real booking end to end and check it lands as a job with the right notification. Repeat monthly, because platforms update their customer-facing pages and you want to find out before a client does.
Then track a booking_click event on every Book tap with the page and service as parameters, and compare taps by page against jobs created in ServiceM8. That tells you which service page books and which is read and abandoned.
Common mistakes
- The booking embed on every page, slowing the site for everyone who is only reading.
- Booking above the emergency number.
- Fees on the site that differ from the ServiceM8 quote.
- The hosted booking page as your Instagram link, with no route back to the site.
- Nobody watching notifications between yards.
Where this sits
ServiceM8 is one of the platforms we wire into an equine vet and farrier website most often, alongside Jobber, Provet Cloud and ezyVet, and the same one-page embed discipline runs through our pet business websites. Packages are on pricing. ServiceM8 holds the job and the route. The site gets the owner into it in one tap, without ever getting in the way of the phone.