New ChatGPT Ads are now on the Ultimate plan. Early access most agencies can’t get yet, reach ChatGPT users before your competitors. See plans →

Turn the Mindbody ReferredBy Field Into a Channel Engine

Turn the Mindbody ReferredBy Field Into a Channel Engine

The most valuable field in your Mindbody account is one most studios barely touch: ReferredBy. Used well, it turns Mindbody into a channel-aware system that knows where every client came from and lets you treat each channel differently. Used poorly, or left blank, it quietly erases your ability to track or optimize anything.

What the ReferredBy field actually is

Every Mindbody client record has a ReferredBy field, backed by a list of referral types you define in your settings. Think of each referral type as a channel: Meta Ads, Google Ads, ChatGPT Ads, Website, Walk-in, Member Referral, Event, and so on. When a client is created with the right referral type, Mindbody now knows the origin of that relationship for the rest of its life.

That one tag is what later powers revenue-by-channel reporting, and it is what lets you send a Meta lead a different first message than a member referral.

Treat referral types as a real channel taxonomy

Most accounts have a messy, half-used referral list: a few stale entries, inconsistent spellings, and a lot of blanks. Clean it up and treat it like a taxonomy:

We give you a ready-made channel taxonomy and a UTM-to-ReferredBy map in the playbook below.

The catch: the tag has to be set at creation

A taxonomy only helps if the field is populated correctly and consistently. The reliable way is to stamp the referral type the moment the client record is created, straight from the ad source. Relying on staff to remember to pick the right referral type during a busy shift produces blanks and wrong values, which is the same as having no data. This is exactly why the lead sync step matters so much. See why syncing ad leads into Mindbody is the hard part.

Now tie an automation to each channel

Here is where the field earns its keep. A lead from a Meta ad, a member referral, and a walk-in are at completely different levels of intent and context. They deserve different first touches:

Sending all of them the same generic text leaves conversions on the table. The problem is that Mindbody on its own does not make channel-specific automation easy. You need a CRM layer that reads the ReferredBy value and routes each client into the right sequence.

How HealthdeskAI uses ReferredBy

In HealthdeskAI, each referral type maps to its own pipeline and automation. When a client lands in Mindbody tagged as a Meta Ads lead, they enter the Meta nurture and the AI agent opens with the right angle for that channel, in your brand voice. A member referral enters a warmer sequence. Every channel gets a purpose-built first touch, follow-up cadence, and handling, all triggered off the ReferredBy value and all running seven days a week.

On the Ultimate plan, we set the whole taxonomy up for you, wire the automations per channel, and keep them tuned as your mix changes.

Free playbook: we put the full system, a ReferredBy channel taxonomy, a per-channel automation matrix, and the Analytics 2.0 revenue report recipe, into the Mindbody Channel Attribution Playbook. Ask the Healthdesk team for a copy.

Once each channel has clean tagging and its own automation, you can finally answer the question that matters: which channel actually makes you money? That is a report, and we walk through it in how to see which channels make you money in Mindbody with Analytics 2.0.

Want this configured for your studio without the manual work? Talk to the Healthdesk team about the Ultimate plan.

Back to the Blog

See HealthdeskAI grow your business.

Book a 20-minute walkthrough. We'll show you exactly how the AI agent works for studios like yours.

Book a demo →