Last Updated: October 21, 2026
A single shared pipeline breaks because clinic service lines like a PrEP start, an STD treatment, and a weight-loss consult do not move at the same speed. When every service line sits in one board, staff cannot see which patients are overdue, and reporting collapses into a count of names. (Source: HIPAA-compliant CRM)
The fix is structural: CRM pipelines for clinic service lines work when each service line gets its own opportunity board, its own stages, and its own rebooking cadence. At The Marketing Lab, we build these boards inside VaultStream, our HIPAA-compliant CRM, and the pattern holds whether a clinic runs two service lines or six.
Most practices inherit a generic sales pipeline and rename the stages. That is the mistake. A clinical cadence is not a sales cycle, and the board has to reflect the medicine.
Build one opportunity pipeline per service line: PrEP and HIV care, STD management, weight loss, HRT, mental health, and primary care. Each board carries the same three stages, which keeps staff training simple while letting the timing rules differ underneath.
The standard set is deliberately short. Three stages, one manual move.
Keeping a single manual action is the point. Every extra drag step is a step that gets skipped on a busy Tuesday.
Injectable PrEP needs its own board because its cadence does not fit the three-stage set. The stages are Booked, Tested, Visit 2 at one month, and Maintenance every two months. A lapsed second dose is a clinical event, not a marketing miss, so the card must sit in a visible stage until someone closes it.
Watch Out
An injection given at an appointment that was never checked in leaves no encounter, no note, and no charge. The board shows the visit happened; the billing system shows nothing. Check-in discipline is a pipeline requirement, not a front-desk nicety.
Calendar-to-pipeline mapping means the appointment creates the opportunity, and the opportunity closes only when the next appointment exists. The scheduling system feeds the board; the board does not feed the scheduler. Get this direction wrong and you end up with staff maintaining two calendars that disagree by Friday.
Every stage needs a written entry rule and exit rule, or two staff members will disagree about the same card. Write these down before the first campaign goes live.
In programs we run, the integration does less than clinic leaders expect. Be explicit about the boundary before you promise a dashboard.
Watch Out
A card that silently sits in Follow-Up Booked looks like success on a dashboard while the patient drifts. Set a rule that any card without a future appointment after 48 hours returns to a visible worklist.
A single inquiry can belong to two service lines at once, a patient calling about STI testing who also asks about PrEP. Route by service, location, urgency, and staff capacity, and prevent duplicate outreach.
Pro Tip
Set the rebooking prompt to fire while the patient is still in the room. A card that asks for the next appointment at checkout converts far better than a text message sent two weeks later.
In South Florida, intake and reminder templates need English, Spanish, and Haitian Creole versions before launch. Route the patient to the language they selected at intake, and keep the clinical content identical across all three so consent language does not drift.
Patient follow-up automation should rebook at the interval the clinical protocol requires, not at a generic reminder schedule. Oral PrEP runs every three months with an HIV test and STI screen.
Automation handles the reminder. A named human owns the worklist. In programs we run, automated reminders alone fail silently: the message sends, the patient ignores it, and nobody notices for a month.
A HIPAA-compliant CRM must enforce consent, access control, and PHI boundaries at the system level, not in a policy document nobody reads. If the software lets staff paste a diagnosis into a text message, the software is the problem.
What to require before signing:
VaultStream runs on our partner platform Appbo.io, and the consent and access controls above are configured before the first campaign goes live, not after.
The PrEP patient follow-up workflow starts with an eligible list built from the EHR, not a purchased list. Recent STI positives, HPV history, and high-risk screening results feed the list, and outreach frames the conversation as an invitation to a prevention education program.
The visit model is two steps. A full telehealth session covers education, screening, and pathway choice, and opens the lab order. The patient then stops at any office for labs with the fee waived.
Key Takeaway
The pipeline only works when the clinical workflow is already clean. Fix the two-step visit and the same-day start first; the CRM then records what actually happened instead of papering over a broken process.
Measure each stage, not the board as a whole. A pipeline that looks healthy in aggregate usually hides one service line quietly dying. The KPIs below are the ones we review with practice administrators, and they map to the stages defined above.
Attribution is where most clinic reporting falls apart. Connect marketing to kept appointments through the CRM and EHR, never by putting PHI into ad platforms or analytics. Track patient-level cost per kept visit and per-service-line margin so budget decisions rest on attended visits, not clicks.
Key Takeaway
If a KPI cannot be tied to a named owner and a weekly review, it is decoration. Pick five, assign them, and retire the rest.
Governance is the unglamorous half. Reconcile the board against the EHR monthly, confirm every active service line still has an owner, and retire stages nobody uses. A pipeline reviewed once a quarter is a pipeline nobody trusts.
Watch Out
Reporting that stops at clicks tells a clinic nothing. Without a link from marketing to kept appointments, cost per kept visit and per-service-line margin are guesswork, and the next budget cycle runs on opinion.
The hard part is not choosing software. It is agreeing on stage definitions, naming an owner for every worklist, and holding the line on consent and PHI boundaries while the clinic is running at full volume.
The Marketing Lab builds service-line pipelines inside VaultStream, with two-way SMS and email, patient journeys, and analytics wired to the CRM so reporting shows booked and kept visits rather than clicks.
Book a free 30-minute strategy call at https://thelab.marketing/schedule and map the first pipeline before the next recall cycle starts.
Start with one pipeline per clinic service line rather than a single shared board. Use three stages: Booked, which fires automatically when an appointment is created; Tested, the one manual move your staff makes at the visit; and Follow-Up Booked, which automation sets at the clinical cadence. In our experience, the manual move is what breaks first, so name an owner for it and review the stage weekly. Keep clinical detail in the EHR and only the operational status in the CRM.
For most service lines, Booked, Tested, and Follow-Up Booked cover the whole cycle. Injectable PrEP needs a longer set: Booked, Tested, Visit 2 at one month, then Maintenance every two months, because a missed dose-two window changes the clinical pathway. Mental health and HRT programs often add a screening step between Booked and Tested. Whatever stages you choose, define entry and exit criteria for each so two staff members cannot mark the same patient differently.
Set the next appointment before the patient leaves, then let patient follow-up automation create the follow-up task from the appointment date rather than from a manual note. For oral PrEP, that is every three months; for injectable PrEP, month one, month two, then every two months. Add a weekly recall worklist with a named owner, because automated reminders alone fail silently when a patient ignores them. Pull an HIV test overdue list monthly from the EHR to catch anyone the pipeline missed.
Yes, and it is the highest-value integration you will build. When a booking event creates the pipeline record automatically, Booked stops depending on staff memory. Map each calendar or appointment type to exactly one pipeline so a women's health visit does not land in the STD board. What the integration usually cannot do is move a patient to Tested or write clinical results, so plan a manual step or an EHR-side trigger for that move and test it before go-live.
Bring us your patient acquisition, 340B program, or compliance bottleneck. We will show you what a 30-day launch looks like for your clinic — in English or Spanish, month to month, no long contract.
