Build the brand.
Connect the system.

The starting point: one brand, different patient journeys

A multi-location healthcare business does not have one interchangeable campaign. Each office serves a local market, and each service creates a different patient conversation. An IV-therapy inquiry, a wellness question, and a wound-care inquiry cannot simply be treated as the same lead.

NIVA’s records show an engagement spanning brand and website work, acquisition campaigns, and the follow-up systems around the clinics. In September 2026 correspondence, ModFXMedia confirmed that it had helped build the brand and site. The case begins with that foundation rather than an invented zero-revenue baseline.

The brand and campaign layer

The website and brand gave the clinics a shared public identity. Campaign discussions then addressed particular services and markets, including Google Performance Max for IV therapy, Spanish-language Meta advertising, and TikTok.

The June 2025 campaign review focused on how landing pages, lead capture, and the client’s existing workflows would fit together. Its practical concern was avoiding a separate, disconnected process that would create records without notifying the right staff or preserving the information they needed.

Those records demonstrate the scope of the operating work. They do not establish that every proposed channel went live at the same time or produced the same result at every location.

The follow-up layer: testing AI alongside people

NIVA’s 2024 Novi calls document an AI-calling pilot and repeated reviews of response, booking, and the interaction between automation and staff. The team discussed calling windows, message templates, a transfer path, and how to distinguish an AI-influenced booking from one completed by a person.

That attribution question was central. A person might receive an automated call and later book through staff. Counting the appointment as exclusively caused by the AI would overstate what the record showed.

Later discussions introduced a revised calling system and workflow integration. The story is therefore about connecting technology to the clinic’s operating process, with testing and measurement, rather than claiming that automation removed the need for the team.

A dated view of the acquisition funnel

The client’s performance table reported 140 Jacksonville IV-therapy campaign leads and $4,500 in spend for January 26 through April 26, 2026. That yields the reported $32.14 cost per lead. The same table listed 61 bookings and 16 shown appointments.

These figures are a historical campaign snapshot. They are not the whole NIVA business, not all services, and not a current monthly run rate. The booking and attendance stages also show why a lead-generation result should be evaluated alongside the clinic’s follow-up and attendance records.

The reported bookings and attendance are retained as separate counts rather than converted into a success claim about paid patients. A visible funnel can reveal both useful activity and unresolved friction.

Why measurement must stay local and current

Later, overlapping Jacksonville reporting windows showed higher lead costs. The team’s July correspondence called for optimization, and subsequent discussions continued to review individual locations. That record does not support a sustained cost-per-lead reduction narrative.

It supports a different, important lesson: infrastructure is useful because it lets the owner see where performance changes. A brand, advertisements, lead records, staff handling, and attendance need to connect for the team to respond intelligently.

Comparing overlapping windows as if they were independent before-and-after cohorts would obscure that lesson. This case uses one clearly dated snapshot and describes later performance as a reason for ongoing attention.

What another multi-location group can take from this

Build a shared brand while preserving service and location detail in the patient journey. Make sure a new inquiry reaches the right workflow and the right people. Then distinguish contact, booking, attendance, and purchase before assigning credit to a channel or an AI system.

NIVA’s case shows the breadth of a connected engagement and the discipline required to evaluate it. The deliverable is an operating system that can be examined and improved, with the limits of each reported result visible.