Replacing an inbox with a system that remembered

The situation

This project sat within the wider job of runningdigital operations for the group, and it started from close to nothing. Each enquiry was a website form dropping into an email inbox with no UTM tracking or parameters attached, so nobody could say where it had come from, which campaign had paid for it, or which studio it should ultimately belong to.

The follow-up depended on someone remembering, with the email snooze function acting as the reminder system. That setup might work for a handful of enquiries a week. It does not work once a group is fielding enquiries across several studios and several artists at once, because the person who snoozed the email is not always the person who is free to chase it three days later. And nothing flags an enquiry that has gone quiet until a customer has already booked somewhere else.

Reporting on any of it was anecdotal, built from whoever happened to remember how the week had gone, not from anything that could be checked. That meant decisions about where to spend time and where to spend advertising budget were being made on impression, not evidence, which is a difficult way to run one studio and an unworkable way to run several.

The advertising side made the gap most obvious. With no tracking attached to enquiries, spend decisions could only ever be judged on a total lead count - not on which campaign, which studio and which artist that spend was converting for. A pound spent on a campaign that converted well and a pound spent on one that did not looked identical in the only reporting that existed, which is not a position a business managing a serious advertising budget can afford to stay in for long.

The platform

We trialled several CRM platformsbefore settling on HighLevel, chosen as a strong all-rounder rather than the best tool at any one thing. It consolidated a stack of separate tools into one system, which cut setup time, maintenance and cost compared with stitching several specialist products together. The platform alone wasn't necessarily groundbreaking, but what it did provide was the perfect base to build something much more significant on top of it.

What we built on it

None of the five pieces below did much on their own. The real value came from treating enquiry capture, follow-up, confirmation and deposit collection as one connected system, not five separate fixes attached to an inbox. Again, what we were aiming for was automation that genuinely reduces work rather than a set of tools that just move the same manual effort somewhere else.

• Tracked enquiry capture with UTMs and parameters, so origin was known, not guessed, meaning a campaign could be judged on what it brought in against a raw lead count.
• Enquiry origin and studio fulfilment each recorded as separate fields, so a customer contacting one site and booking at another did not corrupt the reporting. Without that separation, a studio could look busy on paper whilst losing enquiries to a neighbouring site - or take credit for demand it never generated.
• Automated follow-up replacing individual memory, so each enquiry got chased and treated equally on a schedule instead of relying on someone noticing it sitting there.
• WhatsApp confirmation reminders with a one-tap reply, so either the customer confirms or the cancellation arrives early enough to refill the slot. A phone call or a form-based reminder gets ignored far more often than a message someone can answer with minimal effort.
• Deposits taken at the point of consultation, while the customer is still keen, instead of chased afterwards when motivation has dropped and the conversation has to start again from a colder position.

What improved

Conversion rates, lead volumes and capacity filling became visible for the first time. That visibility made them much easier to improve, since a problem nobody can see is a problem nobody can fix. Being able to break lead volume down by studio, channel and artist meant advertising spend could be judged on where it converted against a generic total. This meant a slow week could be spotted while there was still time to do something about it, instead of being discovered after the fact as part of the monthly results.

That transition from anecdote to visibility is what made every later decision, including the ones covered in thereporting chapter, possible. None of the reporting work that followed would have meant anything without enquiry data that could be trusted.

It also changed the conversation about lead volume itself. Once conversion and capacity were visible, 'more enquiries' stopped being the automatic answer to a quiet month - because a business that cannot convert or fulfil the leads it already has does not need more of them. Visibility made it possible to ask whether the problem was in fact a 'lead problem' at all.

The mistake

It took three platforms before we landed on the right one. Each move meant migrating automations, historic enquiry data and staff habits all at once. Running two systems in parallel for a period while the switch bedded in is disruptive enough, even when the destination is an improvement. CRM migrations are painful, and because of that, it took longer than it should have to admit the first two were not the right fit and move on, rather than trying to make them work.

Part of what went wrong with the first two attempts was fixating on a 'feature list' instead of just asking what a small team supporting a growing number of studios could realistically maintain day-to-day. A platform that does more but needs more looking after does not save time - it just moves the cost from the customer-facing side of the business to the operational side, making it easier to overlook until the maintenance burden is already established.

Most of these issues are not restricted to tattooing. Any business managing enquiries and bookings across more than one site eventually runs into the same problem of requiring a location field, because it's so easily overlooked until the reporting begins to make no sense. This is a topicwe cover more generally for multi-location businesses. It's only the specifics that change depending on industry. The wider shape of the problem, such as inboxes that cannot scale or systems that have to treat location as data, do not.

Choosing an all-rounder platform over several specialist ones benefitted a smaller team, too. Fewer separate systems means fewer integrations that can break, fewer logins to manage across several studios, and fewer places for a customer record to fall out of sync. That trade-off might not suit every business, but for a group growing quickly across several sites at once - simplicity bought back time that would otherwise have gone on managing the toolset itself.