The System Behind the Website
What started as rebuilding the High Country Detailing website has gradually turned into something much bigger.
From the outside, it still looks like a detailing business website. Customers can look at services, find information and make a booking. But underneath that website I’ve been building an entire custom business platform specifically around how High Country Detailing operates.
Rather than trying to force the business into half a dozen generic systems, we’ve progressively built our own booking platform, vehicle database, CRM, payment infrastructure, communications system, marketing automation, customer portal, diagnostics platform and mobile app — with WordPress essentially acting as the foundation connecting everything together.
The Custom Booking System
Probably the biggest part of the entire project is the booking system.
I didn’t want a normal WordPress form that basically says name, phone number, what do you want? and then sends an email.
The HCD booking system is a structured booking application.
The customer is taken through the process step-by-step, starting with their vehicle and then moving through the appropriate services, booking information, customer details, availability and payment.
The important part is that the information isn’t just being emailed to us. It becomes structured data that the rest of the HCD system can actually use.
Australian Registration Lookup
One of my favourite additions is the registration lookup.
Instead of expecting every customer to know and manually enter all their vehicle information, we’ve integrated registration lookup into the booking process.
The customer can enter their registration number and the system can use that to assist with identifying the vehicle and populating its details.
Where lookup information isn’t available, we’ve also retained manual vehicle entry so the booking isn’t stopped because an external lookup couldn’t identify something.
That vehicle then becomes more than just text written on a booking.
It can become an actual vehicle record associated with that customer.
That means we’re gradually building a garage for every customer: their vehicles, registration information and the work associated with them.
For a detailing business, that’s incredibly useful because the vehicle is almost as important to the database as the customer.
Services Built Into the Booking Journey
The system has its own service structure rather than simply linking customers off to an external appointment page.
Customers can select the detailing service they actually want, and the booking system can capture additional options and add-ons as part of the same journey.
We’ve designed the customer-facing side to remain clean and straightforward even though considerably more is happening behind it.
The booking can contain the customer, vehicle, selected service, add-ons, preferred date and time, notes, pricing and payment information as structured records.
It also means the services shown to customers can be controlled from the HCD system rather than hard-coded into random pages throughout the website.
Availability and Appointment Management
Availability has also been built into the architecture.
The system has been designed around actual detailing appointments rather than generic e-commerce orders.
Bookings can be connected to dates, times, services, vehicles and customers, and the administration side gives us an operational view of those appointments.
Earlier development also included staff-based scheduling concepts so appointments could be allocated according to who was actually available and capable of performing particular services rather than treating every hour of the day as identical.
Where an appointment can be confirmed through the connected booking infrastructure, the system can record the external booking reference and keep that information associated with the HCD booking.
If something can’t simply be confirmed, the architecture also supports different booking statuses and rescheduling workflows rather than losing the booking altogether.
Customer Accounts Without Making Booking Painful
Another major focus has been removing unnecessary friction.
I don’t want someone to have to create an account, verify twelve things and remember another password just because they want their car detailed.
The booking experience therefore needs to work for a normal customer while the system quietly builds the useful customer information behind it.
At the same time, customers can have accounts and access their information through the customer portal.
That gives us the beginnings of something much closer to the account experience you’d expect from a larger company rather than a typical small-business WordPress site.
Customer Profiles and the Vehicle Garage
Behind all of this is the HCD customer database.
A customer isn’t simply an email address attached to an order.
The Core maintains structured customer records, and vehicles can be associated with those customers.
Bookings can then be associated with both.
So instead of:
Peter booked a $220 detail.
The system can understand something much closer to:
This is Peter → this is Peter’s vehicle → these are the services associated with that vehicle → these are his bookings → these are his transactions → these are the communications we’ve sent → and this is his history with HCD.
That fundamentally changes what we can build on top of it later.
Bookings From Outside the Website
Not everybody books online, so I didn’t want the database to only work for website customers.
The system has been designed so bookings originating through the website, phone, email or messages can ultimately live within the same booking/customer structure.
For bookings created outside the normal online journey, we’ve also developed the concept of secure payment links.
That means someone can speak to us, have their booking created, receive a secure link, review the relevant booking information and make their payment without being forced through the entire public booking process again.
Square Payment Integration
Payments are integrated directly into the HCD architecture using Square.
This was particularly important because I didn’t want to build our own payment handling or have payment information disconnected from the booking database.
The system can associate payment records and transaction information with bookings and customers and maintain provider/reference information for reconciliation.
We’ve also developed Square API connectivity, webhook handling and payment-status synchronisation so the HCD platform can respond to payment events rather than relying on somebody manually checking Square.
A successful payment can trigger the next stages of the system, including updating the booking and generating the appropriate customer communication.
Booking Terms Without Another Annoying Step
We’ve spent quite a bit of time working on the legal/operational side of bookings as well.
HCD has specific payment and cancellation conditions, but I didn’t want to solve that by adding another horrible compulsory Review & Confirm screen that hurts conversions.
Instead, the terms are being integrated naturally into the existing booking/payment process.
For phone bookings, agreement can be handled verbally. For email bookings, it can be incorporated into the normal correspondence. For online bookings, the relevant terms can form part of the existing booking/payment journey.
The principle throughout the project has been that the complicated stuff should happen behind the scenes, not become the customer’s problem.
Automated Booking Communications
The booking system doesn’t stop once somebody presses Book.
We’ve built communication templates and automation around the booking lifecycle.
That includes booking confirmations, payment confirmations/receipts, reminders, cancellation notices and other transactional email and SMS communication.
Those communications can include relevant booking information, payment summaries, booking links and cancellation information.
Most importantly, the long-term architecture is about connecting those messages back to the customer rather than having them disappear into an external email provider where the rest of the HCD system knows nothing about them.
Abandoned Booking Recovery
One of the latest additions is abandoned booking recovery.
If someone starts the booking process, gives us enough information to identify them, but doesn’t finish the booking, that doesn’t necessarily have to become a lost customer.
The system can capture the abandoned booking and place it into an automated recovery workflow.
It can then send carefully timed SMS and email reminders encouraging the customer to come back and finish.
Those messages aren’t intended to become aggressive spam. They’re designed as useful reminders for somebody who has already demonstrated that they were trying to make a booking.
And those automated communications are being connected back into the customer database so we can see what the system has actually sent.
HCD Messages
Communications have grown into another major project of their own.
We’ve been building HCD Messages, essentially a communications centre inside the business platform.
The aim is to stop having customer communication fragmented between the website, emails, SMS providers, phones and different applications.
Instead, customer communication can increasingly be associated with the actual HCD customer record.
That means when looking at a customer we can ultimately see not only their bookings and vehicles, but the communication surrounding those bookings.
SMS integration is part of that system, with Crazytel infrastructure also being used for the telecommunications side of the platform.
Business Calling
We’ve taken that even further by building business calling into HCD.
Rather than the business phone simply being a completely separate mobile number, we’ve been integrating SIP/VoIP calling into the system.
HCD Messages includes calling functionality that allows a business call to be initiated from within the HCD environment using the business telecommunications infrastructure.
We’ve been working through SIP authentication, registration, outgoing calls, incoming calls and two-way audio as part of that development.
That’s a fairly ridiculous distance from where this project originally started — which was basically “I need a better detailing website.”
The HCD iPhone App
And that led naturally into building an actual High Country Detailing iPhone application.
The app isn’t intended to just be a WebView showing the website.
It’s being developed as another interface into the HCD business platform, particularly around communications and business calling.
We’ve already been through work associated with Apple’s App Store review requirements, device testing and demonstrating the application’s functionality.
Incoming business calling is also part of the ongoing mobile development.
So we’re now at the point where HCD isn’t simply a WordPress website anymore. There is a web platform and a native mobile component being developed around the same business infrastructure.
Automated Email and SMS Marketing
Another complete system we’ve built is HCD’s marketing automation.
Rather than paying for another separate marketing platform and constantly exporting customer lists, we’ve built marketing capabilities around the customer database we already own.
Campaigns can use email and SMS and have been designed around actual detailing customer behaviour.
That includes things such as service reminders, re-engagement, promotions, seasonal campaigns, Christmas campaigns and softer long-term customer retention messages.
The idea isn’t to hammer people every week with 20% OFF!!! BOOK NOW!!!
It’s to keep HCD familiar and relevant so when somebody looks at their car three months later and thinks “this thing needs cleaning,” High Country Detailing is already in their head.
Email Tracking and Campaign Monitoring
The marketing side also includes monitoring.
We’ve been developing tracking so the system can record engagement with emails, including link clicks.
That provides actual information about whether campaigns are working rather than simply saying:
“We sent 1,000 emails.”
Sending them is meaningless if nobody interacts with them.
The broader system is designed to let us understand what was sent, who received it and what engagement occurred while maintaining unsubscribe and marketing-preference controls.
Promotions
Promotions are integrated into the marketing ecosystem as well.
Rather than manually editing website pages every time we want to run something, promotions and campaign codes can be managed through the system and connected to the campaigns promoting them.
We’ve already used this structure for things such as ceramic-coating promotions and seasonal marketing.
Gift Cards and Wallet Infrastructure
There is also a Wallet & Gift Cards component.
Gift cards aren’t treated simply as a PDF somebody manually emails out.
The system has been developed around gift-card purchasing and delivery workflows, with the wider architecture supporting store-credit/wallet concepts as well.
Again, because it’s connected to HCD rather than existing as an isolated plugin, it can ultimately form part of the customer’s overall relationship with the business.
Reviews
We’ve also built review functionality into the modular HCD platform.
That gives us the ability to connect the post-service customer experience back into the wider system instead of relying entirely on a disconnected reviews plugin.
It creates opportunities for intelligent post-booking workflows — completing the service, communicating with the customer and then requesting feedback at the appropriate point.
Reports and Operational Data
A Reports component has also been developed so the information being collected by HCD can actually be useful operationally.
Because customers, vehicles, bookings and payments are structured records rather than random WordPress form submissions, they can be reported on properly.
That architecture becomes more valuable the longer the system operates because the business begins accumulating its own structured operational history.
Activity & Diagnostics Suite
Then there is the part customers will hopefully never see.
Because so much of the business now relies on the platform, I wanted much better visibility when something goes wrong.
So we’ve built our own Activity & Diagnostics Suite.
The system records events and provides administrative tools for investigating what happened.
We’ve used it to investigate customer login attempts, payment/API problems, plugin events, communication failures and other issues.
Diagnostic data can be exported as event CSVs, JSON diagnostic reports and complete support bundles for deeper investigation.
We’ve also added bulk management functionality so old diagnostic records can be selected and managed together rather than dealing with them individually.
System Test Centre
The HCD Core also contains its own testing infrastructure.
The Test Centre can check whether critical parts of the platform are functioning, including the Core itself, required database tables and external integrations.
For example, it can identify Square API reachability problems rather than waiting until a customer tells us that something isn’t working.
That’s become increasingly important because this is effectively production business software now.
System Guard and File Integrity
Security and integrity monitoring have also become part of the platform.
System Guard monitors important areas of the environment, including changes to plugin files and the health of shared integrations.
That gives us another layer of visibility when something changes unexpectedly.
The shared configuration for critical services such as Square, SMS, email and other integrations is increasingly centralised through System Core rather than having credentials and configuration duplicated throughout unrelated plugins.
A Modular WordPress Architecture
One of the parts I’m probably most proud of is that this hasn’t ended up as one gigantic WordPress plugin containing 100,000 lines of unrelated code.
The HCD ecosystem has been developed as a series of connected modules.
There is a System Core, Bookings Suite, Customer Portal, Reviews Suite, Reports Suite, Wallet & Gift Cards, App Suite, Abandoned Booking system, Activity & Diagnostics, System Guard, communications infrastructure and other supporting components.
The Core provides the shared foundation and the specialised components build on top of it.
The database includes structured concepts for customers, vehicles, bookings, payments, transactions, notifications and other operational records.
So WordPress is effectively being used as the application framework and administration environment rather than merely as a page builder.
What the Customer Actually Sees
The funny thing is that I don’t want the customer to realise how complicated any of this is.
They should just think:
Enter my rego → there’s my car → choose what I want → choose when I want it → enter my details → pay → booked.
That’s it.
They don’t need to know that behind that simple interaction the platform may be identifying or creating their customer record, identifying their vehicle, associating the two, recording their service selection, creating the booking, processing a Square payment, recording the transaction, applying the relevant booking conditions, generating notifications and maintaining the information for future visits.
That’s the whole point.
The technology can be complicated.
Using it shouldn’t be.
What High Country Detailing Has Become
So when I say I’ve been rebuilding the High Country Detailing website, website probably isn’t really the right description anymore.
It’s becoming our own vertically integrated business platform built specifically for a detailing company.
It combines elements of a CRM, vehicle database, online booking platform, appointment manager, payment system, customer portal, marketing automation platform, email system, SMS platform, VoIP business phone, gift-card system, reporting platform, diagnostics suite and iPhone app.
And because we’ve built the underlying customer and vehicle architecture ourselves, all of those systems can increasingly share information instead of behaving like completely separate pieces of software.
The customer who enters their registration number into the booking form today can become the same customer record associated with their vehicle, booking, Square transaction, confirmation email, SMS reminder, future marketing, communication history and next booking.
That’s the part that I think is genuinely impressive.
I didn’t just build High Country Detailing a new website.
I ended up building the software that runs High Country Detailing.