Fixed quote after a free call

Therapist CRM automation for a kinder, faster enquiry pipeline

People who reach out for therapy have often waited a long time to do it, and an unanswered enquiry can send them elsewhere or nowhere. We connect your website, directory profiles, voicemail and referrers to one therapist CRM pipeline, send an immediate acknowledgement with crisis resources, flag risk language to a clinician and track every enquiry from first contact to first session. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why therapy enquiries go unanswered

A therapist in back-to-back sessions cannot answer enquiries until the end of the day. A message sent at 11am may wait until 7pm, and a person who finally found the courage to ask for help may contact the next profile on the directory instead.

Group practices add a matching problem: which clinician has space, the right specialty, the right fees or insurance and the right hours. Without a pipeline, enquiries live in an inbox and nobody can say how many came in, how many were matched or which directories and referrers bring clients who start.

What we build

What our therapist CRM automation includes

Every source in one pipeline

Website forms, directory profile emails, voicemail transcripts and professional referrals flow into one CRM.

Safe acknowledgement

An immediate reply that says when to expect a response, that the inbox is not monitored for emergencies, and where to get urgent help.

Risk language flagged

Words your clinical team lists as possible risk indicators alert the designated clinician at once. The system never replies further or judges.

Matching fields

Specialty, fees or insurance, location or telehealth and availability captured so a coordinator can match quickly.

Minimal forms

Contact forms that ask only what is needed, so long trauma accounts do not land in an ordinary inbox.

Source report

Monthly enquiries, consultations and first sessions by directory, referrer and channel.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Enquiry arrives

    A form, directory email, voicemail or referral creates a CRM contact.

  2. 02 Automated

    Acknowledged

    The person gets the practice's approved reply with urgent-help guidance.

  3. 03 Automated

    Risk check

    Listed risk language alerts the designated clinician immediately.

  4. 04 Coordinator review

    Coordinator matches

    The coordinator matches the enquiry to a clinician and offers a consultation.

  5. 05 Therapist or clinical director decides

    Fit and risk

    Clinical fit and any risk response are decided by a therapist, never the CRM.

How it behaves

How the enquiry pipeline behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the client sees

  • An immediate, kind acknowledgement with a reply time
  • Clear guidance on where to get urgent help
  • A consultation offer from a person who has read their message

What the practice sees

  • One board with every enquiry and its stage
  • Immediate alerts for listed risk language
  • A monthly report by source

What the automation does

  • Captures enquiries from every source
  • Scans for listed risk terms and alerts
  • Never replies to risk or gives advice

Edge cases and fallbacks

Risk language in an enquiry
The designated clinician is alerted at once; the person has already received urgent-help guidance.
Long, sensitive message
Stored only in the BAA-covered system and not copied into emails or alerts.
Existing client uses the enquiry form
Routed to their own clinician's admin queue, not the pipeline.
Workflow outage
Forms still reach the practice inbox, and the owner is alerted.

Architecture

A therapist CRM enquiry pipeline at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Website form Minimal fields Directories Profile emails Referrers GPs, EAPs, peers n8n Capture, risk scan Therapist CRM Stages, matching Acknowledgement Urgent-help info Clinician Risk alerts Source report Monthly
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Enquiries arrive from the website, directory profiles and professional referrers.
  2. 2 n8n captures each one and checks it for the risk language your clinical team listed.
  3. 3 The person gets a safe acknowledgement; risk matches alert the designated clinician at once.
  4. 4 Coordinators match and book consultations, and a monthly report shows sources that lead to first sessions.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Therapist CRM & enquiry pipeline project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Enquiry sources, current replies, matching criteria, risk process and reporting needs.

  2. 02

    Design

    2 to 3 days

    Acknowledgement and urgent-help wording, risk term list with the clinical lead, stages and fields.

  3. 03

    Build

    1 to 2 weeks

    Source connections, risk alerts, pipeline, matching fields and report.

  4. 04

    Shadow run

    About 1 week

    Enquiries flow in while the coordinator still replies by hand, and the clinical lead checks every flag.

  5. 05

    Launch

    1 to 2 days

    Switch over and walk the team through alerts and the board.

  6. 06

    Support

    Ongoing

    Wording, risk list and source changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n HubSpot CRM or a BAA-covered CRM Website form with minimal fields Directory profile email parsing Voicemail transcription where covered by a BAA Slack, Teams or SMS alerts for the designated clinician

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Time with the practice owner or coordinator, wording, data flows and a written specification.

    $200 – $400

  • Build

    The n8n workflow, rules, logging and error handling.

    $500 – $1,300

  • Integrations

    Practice software, forms, calendar, messaging and alerts.

    $150 – $400

  • Testing and shadow run

    Acceptance tests and a parallel run before real clients see anything.

    $100 – $250

  • Launch and training

    Go-live, a short walkthrough and a run book.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. CRM, messaging and n8n are billed to you directly. Solo practices often sit at the lower end.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • CRM licence: Your CRM vendor's own plan.
  • n8n: Free self-hosted Community edition on your own server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing). A BAA needs Twilio's Security or Enterprise Edition if client information is in the messages.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: crisis resources in replies

The 988 Suicide and Crisis Lifeline can be reached by call, text or chat, 24/7. Our acknowledgements point to it in the US and to local services elsewhere, such as Samaritans on 116 123 in the UK.

Source: 988lifeline.org

US: HIPAA and CRM vendors

A CRM holding client information for a covered practice needs a business associate agreement; otherwise clinical detail stays out of it. General information, not legal advice.

Source: www.law.cornell.edu

EU and UK: mental health data

Information about mental health is special category data under Article 9 GDPR and UK GDPR, so forms collect the minimum.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Therapist CRM & enquiry pipeline questions, answered.

A CRM for therapists tracks enquiries from first contact to first session: who reached out, who was matched, who booked a consultation and where they found you. It sits beside your practice management software, which holds notes and appointments.

That depends on the vendor signing a BAA and how you use it. We either use a CRM that signs one or keep the CRM free of clinical detail, holding only contact and matching fields.

Your clinical team writes the list of risk terms and the response process. A match alerts the designated clinician at once; the system never replies with advice or decides anything about the person.

It captures the fields that matter, such as specialty, fees or insurance and availability, and suggests clinicians with space. The coordinator and clinician decide.

Directory enquiries usually arrive as emails, which the workflow can parse into the CRM. We confirm the format for each directory you use.

Time to first reply, enquiries matched, consultations booked, first sessions and sources by month.

Free 20-minute call

Want this for your therapists & mental health?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call