5 Referral Tools for Therapy Practices: Guide 2026

The best referral software for therapy practices is the system that gets an appropriate referral to a named person without creating a second, uncontrolled clinical record. The referral may arrive from a physician, school, payer directory, former client, or another clinician; the workflow must distinguish a request for care from a marketing lead, collect only what is necessary, and show where the intake decision was made.

For a small practice that needs scheduling, documentation, and intake in one operating system, SimplePractice or Jane App deserve the first evaluation. For a larger behavioral-health operation needing specialized intake and billing workflows, TherapyNotes or Valant may fit better. This is an editorial comparison, not a paid ranking. US Tech Automations is relevant only when a practice has settled its system of record and needs a controlled bridge between referral channels.

US adults receiving mental-health treatment: 23.9% according to SAMHSA (2023). That is a reason to reduce intake friction, not a reason to turn sensitive referrals into a volume-marketing exercise.

TL;DR: choose the clinical system that owns the patient record, test intake routing and consent, and avoid sending protected health information through an unvetted form or automation. “Referral software” is a workflow decision, not a substitute for clinical triage.

How we evaluated therapy referral platforms

Referral software is the intake and routing capability that records where a prospective patient came from, what service was requested, who may contact them, and what happens next. It must support a practice’s minimum-necessary approach. The HHS HIPAA Security Rule requires appropriate administrative, physical, and technical safeguards for ePHI, according to HHS (2025); confirm each vendor’s contractual and operational fit with your privacy and legal advisors.

The comparison: clinical platform first, referral layer second

The 1–5 scores below indicate documented buyer fit, not quality grades. Every product needs a practice-specific privacy review, role configuration, and live test. A “HIPAA-ready” claim is not a completed risk assessment or a guarantee that a particular workflow is appropriate.

SimplePractice: best for a unified small-practice workflow

SimplePractice is a strong first trial for a practice that wants digital intake, scheduling, client communication, and documentation within one product. It is not an automatic answer for complex multi-program routing or external referral-network management. Configure two referral sources, one service type, and one access restriction; then test who can view the intake before an appointment is accepted.

Jane App: best for scheduling-led multidisciplinary teams

Jane App is particularly useful where availability, reminders, online booking, and several practitioner types are central to referral conversion. It can be a good fit for a therapy practice that shares administration with related disciplines. Confirm its field configuration and export behavior before assuming it will handle all clinical-intake distinctions your team needs.

TherapyNotes: best for therapy operations and documentation

TherapyNotes deserves a close look when the practice values therapy-specific documentation, scheduling, billing, and a clinical operating record. Its best use is not generic lead capture; it is a governed care-intake workflow. During the proof of work, test a referring clinician’s contact, a pending appointment, a rejected fit, and what becomes part of the retained record.

Valant: best for larger behavioral-health workflows

Valant is the enterprise-oriented candidate for behavioral-health groups that need more structured clinical, financial, and operational workflows. It can be excessive for a three-clinician practice whose bottleneck is simply missed voicemails. Ask the implementation team to demonstrate program routing, permissions, historical export, and a real referral-to-appointment handoff.

IntakeQ: best for a form-first intake layer

IntakeQ is a logical candidate when the immediate gap is secure-looking digital intake, forms, and booking rather than a replacement EHR. Its limitation is important: decide where the authoritative clinical record resides and how duplicate or incomplete requests are handled. Do not let a form tool become a shadow chart because it was easy to deploy.

Budget the handoff, not only the monthly plan

Public plan terms change; prices below are starting points shown by vendors on July 30, 2026. “Contact vendor” means the buyer should obtain a dated scope rather than normalize an uncertain public number.

The primary pricing pages are SimplePractice, Jane, TherapyNotes, and IntakeQ. Jane starting plan: $54/month according to Jane (2026). Ask about BAA availability, telehealth, claims, storage, user roles, implementation, data export, and any per-practitioner or per-message charges before comparing totals.

Work one real intake path end to end

A 12-clinician practice receiving 48 referrals a month can test one request for anxiety treatment, 3 preferred appointment windows, and 2 acceptable contact methods. In an approved Typeform pilot, the intake webhook can carry event_type set to form_response, as shown in Typeform's official example payload. The workflow should match 1 existing client, assign 1 intake coordinator, and hold 1 incomplete consent record for review; the coordinator should see a single next action, not a guessed clinical disposition. These are test conditions, not clinical guidance or productivity promises.

Zapier, Make, n8n, or custom code can move an intake submission between a form and calendar. They become risky when a webhook retries a sensitive record, a clinician changes availability, or an unqualified referral gets placed into the wrong queue. US Tech Automations can check the routing fields against rules approved by the practice, create a task for the intake owner, and place ambiguous records in human review instead of deciding clinical fit.

In a controlled implementation, US Tech Automations can receive form_response, validate the practice's appointment status, service request, contact permission, and intended clinic, then deliver a compact work item to the coordinator. It can write a dated exception to the operating record when required data is missing; it should not diagnose, select a clinician based on clinical judgment, or send PHI to an unapproved destination. See the relevant customer-service workflow capabilities only after privacy and ownership requirements are documented.

Key Takeaways

• Start with the clinical system of record, not a generic referral-marketing tool.

• SimplePractice and Jane fit unified small-practice workflows; Valant fits more complex programs.

• Test permissions, incomplete consent, wrong-clinic routing, and record export with real roles.

• Protect the distinction between administrative routing and clinical judgment.

• Price the BAA, roles, integrations, and migration—not just a public monthly plan.

Who this is for

This guide is for therapy practices with 3–50 clinicians, a named intake owner, digital scheduling, and enough referral volume that calls, forms, and clinician availability are hard to reconcile. It helps teams that need to report referral sources without expanding access to sensitive clinical detail.

Red flags: skip a new platform if the practice is paper-only, receives fewer than 10 referrals monthly, has not chosen an EHR/system of record, or cannot define who reviews incomplete intake.

Before changing intake, resolve related workflow gaps in therapy invoicing, therapy scheduling, referral coordination for psychiatrists, and the Jane versus SimplePractice comparison.

Questions to answer before go-live

Can a therapy practice use a generic referral-program tool?

Possibly for a non-clinical relationship workflow, but it should not become the uncontrolled store for intake or health information. Define the data boundary and the authoritative clinical system first.

Does a signed BAA solve all privacy questions?

No. A BAA is only one part of the arrangement. Access controls, staff practice, data minimization, configuration, retention, and the actual flow of information still require review.

Should referrals be automatically scheduled?

Not without a practice-defined control point. Scheduling can be automated after appropriate administrative screening, but clinical fit, urgency, and service availability may require human review.

When NOT to use US Tech Automations?

Do not use US Tech Automations if the EHR already routes referrals with appropriate permissions, if a low-volume practice can document the work manually, or if data destinations and privacy responsibilities are unsettled. Native configuration and a focused intake-policy review are the better first move.

What should the pilot retain?

Keep the BAA and security review, role map, minimum field list, three anonymized test paths, exception log, export sample, dated price quote, implementation owner, and rollback plan.

Make privacy the constraint that improves the workflow

Use a 30-day pilot with one service line and a limited intake team. The pass condition is not more form submissions; it is that the practice can show who saw a request, why it was routed, what happened when data was incomplete, and where the authoritative record lives.

Put a data boundary in the implementation plan

The implementation team should make a small diagram before switching on any integration: referral source, intake form or phone channel, system of record, scheduler, clinician queue, billing system, and reporting destination. For each connection, state whether it carries administrative contact data, appointment data, or clinical information, and which role can approve a change. This forces the buyer to discover shadow spreadsheets and mailbox rules before they become part of a new automation.

Use plain-language intake questions that collect the minimum necessary information for the current decision. A practice may need a contact method, availability, service preference, location, insurance question, and referral source to route an initial inquiry; it does not need to replicate an entire assessment in an advertising form. The HIPAA Privacy Rule sets national standards for protecting certain health information, according to HHS (2025). The exact data set, vendor arrangement, and workflow should still be reviewed for the practice’s setting.

Give the coordinator a specific safe response for each exception. If a referral has no usable contact permission, the outcome is “hold for approved outreach,” not an automatic text. If the requested clinician has no availability, the outcome is “offer approved alternatives” or “clinical review,” not silently move the person to a different service. If the person already has a record, the task should identify the duplicate and require a trained person to reconcile it. These distinctions protect both experience and record quality.

Vendor terms should be verified in writing. SimplePractice individual entry plan: $29/month according to SimplePractice (2026). TherapyNotes clinician entry plan: $69/month according to TherapyNotes (2026). Those published entries do not settle whether telehealth, claims, team features, storage, migration, or a particular integration belongs in the practice’s actual scope. The Office for Civil Rights breach portal lists reported breaches, according to HHS (2026); it is a reminder to design for containment and response rather than a statistic about any one vendor.

Create an acceptance test that includes administrative staff, a clinician, and the privacy/security owner. The group should walk through a new referral, duplicate record, missing contact permission, wrong clinic, and declined fit. Record the screen seen by each role, the destination of each field, the time of each task, and the export result. A good implementation makes it easy to answer “what happened to this request?” without exposing details to people who did not need them.

After launch, review a small sample monthly rather than waiting for a complaint. Compare the referral source, routing reason, appointment outcome, and exception handling against the policy. Changes to forms, providers, insurance participation, and service areas are normal; they should trigger a bounded configuration review rather than an informal workaround. That maintenance is what keeps a referral workflow from drifting into an unowned second record.

Train against workarounds as explicitly as you train the software. Intake staff should know which channels are approved for a new request, where a referring professional’s message belongs, how to hand off a voicemail, and when to stop rather than improvising a workaround through personal text or email. Clinicians should be able to see the administrative status they need without being made the default owner of every routing exception. This protects clinical time and makes the process more humane for people seeking care.

Before signing, ask the vendor to describe account closure, data export, and role removal in the exact plan being purchased. IntakeQ entry plan: $49/month according to IntakeQ (2026). A low entry price does not establish the cost of migration, additional roles, document storage, telehealth, or the work required to validate a new workflow. Record answers in the decision log alongside the BAA status and implementation assumptions.

Use a small risk register during the first month: duplicate client, missing permission, mistaken location, staff access error, unexpected integration retry, and changed provider availability. For each item, capture the detection point, owner, containment action, resolution date, and configuration change. A recurring issue may signal that a required field, routing rule, or staff instruction needs repair rather than that the team needs to work faster.

The best post-launch metric is explainability: can the practice identify the intake owner, record boundary, consent status, and next administrative step for a sample request without opening several tools? If not, reduce the integration scope and repair the process before adding another automation.

When a chosen platform needs cross-system exception handling, review US Tech Automations pricing after the approved field map and human review point exist. The right referral tool makes the next responsible action clearer while keeping clinical judgment with people.