Bilingual intake for South Florida practices  ·  Coral Gables · Brickell · Pinecrest  ·  Se habla español

Skip to content
Practice • Service Lines and the HIPAA Add-on

One pipeline per service line

By Brandon Aday, M.B.A. • Duration: 4 min • Type: reading

You'll be able to: decide which service lines get their own pipeline, and keep each one owned and readable.

Solo runs one pipeline. Practice runs several, because a practice with a team usually sells more than one kind of care, and each kind moves through different steps.

Take a dental office in Coral Gables with three service lines. General and family visits go: new inquiry, carrier recorded, visit booked, forms completed, visit completed, treatment accepted, recall. Orthodontics records the patient and the decision maker (often a parent), then a consult, a plan presented and treatment started. Implants have a consult, a plan presented but not yet scheduled, and treatment scheduled. Put all three on one board and the stages stop meaning anything. "Visit booked" for a cleaning and "visit booked" for an implant consult are different jobs with different owners.

Other examples:

  • A med spa in Brickell with injectables and laser: injectables end in a follow-up visit, laser runs as a series of sessions, and different clinicians own each.
  • A therapy group with individual, couples and child and teen services: different clinicians, a different first conversation (often a parent for the child and teen line), and a waitlist when rosters are full.
  • A concierge medical practice next to a primary care service: the concierge line moves through an intro call and a membership agreement, and renewal is its own stage, because renewal is its own intake.

Each specialty comes with its own pipeline. The pre-built version for your practice type includes, for each specialty, its stages, fields, urgent tag and templates, named so they never collide when a practice uses several: GEN ยท General and family dentistry, ORTHO, IMP, and so on. Every pipeline also keeps the two base exits: "No response / follow-up," and "Not a fit / referred out," which stops every sequence.

When to split, and when to tag. Give a service line its own pipeline when its stages or its owner are different. When only the label differs (two kinds of cleaning, two injectable brands), use one pipeline and a tag. More pipelines are not better; every pipeline is a board somebody has to watch.

One owner per pipeline. The intake coordinator may watch all of them, but each pipeline needs a named person who answers for its stalled cards. In the dental example: the coordinator owns general, the treatment coordinator owns ortho and implants.

What each card still carries. Source, language (EN or ES), owner, and the full history. A card sitting past your threshold turns red; in the first stage that threshold is 24 hours by default.

Keep pipelines logistics only. Stage names and card fields describe where someone is in booking, never what is wrong with them. "Consult scheduled" is a stage. A presenting concern is not a field.

Why it pays off in reporting. Separate pipelines let the reporting in Module 6 show bookings and shows per service line. A practice that sees implants converting well in English and poorly in Spanish can act on it. A practice with one blended pipeline cannot see it.

Do it in TheraCRM

  1. List your service lines. For each, note whether its stages or its owner differ from the others.
  2. Open the pipelines and confirm one exists for each line that needs one, with that specialty's stages.
  3. Name an owner for each pipeline and set it as the default assignee.
  4. Confirm each pipeline has the two base exits.
  5. Read every stage name and card field and remove anything that describes a condition rather than a booking step.

Ask the Guide

Paste this into the AI guide, without patient names or health details:

"We are a [practice type] offering [list service lines]. Which ones should get their own pipeline and which should share one with a tag? Suggest booking stages for each, with no clinical detail in any stage name."