Case Study

Case Study: Therapy Practice Intake & Scheduling Automation

We built a connected set of automations for a group therapy practice: an enquiry pipeline with safe acknowledgements and risk alerts, self-booked consultations and portal intake, session reminders with careful no-show follow-up, a fair waitlist and superbill and good faith estimate tracking. The coordinator now works from one board, and therapists spend their evenings on notes instead of paperwork.

Practice type
Group therapy practice, in person and telehealth
Team involved
Clinical director, therapists, intake coordinator, billing administrator
Systems connected
Practice platform, CRM, booking tool, Twilio, Stripe, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

Enquiries from the website and directory profiles waited until a therapist had a gap. Evening and weekend messages waited until Monday, and nobody had a consistent way to spot a message mentioning risk.

Consultation calls were booked by email, and intake paperwork was sent and chased by hand, so first sessions often began with forms.

No-shows were handled differently by each therapist, and freed slots rarely reached the waitlist, which lived in a spreadsheet.

Superbills were prepared at month end in a rush, and good faith estimate deadlines were tracked from memory.

Goals

What the project had to change

  • Every enquiry gets a safe acknowledgement at once, and risk language reaches a clinician immediately.
  • People can book consultations themselves, and intake is complete before session one.
  • Reminders are consistent and every no-show is reviewed by the therapist.
  • Freed slots are offered fairly to the waitlist within the day.
  • Superbills go out on schedule and every good faith estimate is sent before its deadline.

What we built

What we built, as one connected system.

01

Enquiry pipeline

We connected the website form and directory emails to one CRM pipeline with a safe acknowledgement, a risk term list owned by the clinical director and immediate clinician alerts.

Service details
02

Consultations and intake

A consultation booking page per therapist, intake paperwork through the platform's portal once session one is booked, gentle chasing and a day-before list.

Service details
03

Reminders and no-shows

Neutral reminders by each client's agreed channel, telehealth links on time, consistent policy wording and a no-show review list for each therapist.

Service details
04

Fair waitlist

A structured waitlist with preferences, offers in written order when slots free up, and check-ins with support guidance.

Service details
05

Superbills and estimates

Monthly superbill drafts from billing data and good faith estimate drafts with business-day deadlines tracked.

Service details

Architecture

How the practice's workflows connect

Enquiries Web, directories Practice platform Sessions, billing Booking tool Consultations n8n Five workflows CRM and waitlist Board, order Texts and emails Neutral wording Draft documents Superbills, GFEs Coordinator Matches, checks Therapists Risk, no-shows Logs and reports Monthly summary
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Enquiries, the practice platform and the booking tool feed one n8n instance.
  2. 2 Five workflows update the CRM and waitlist, send neutral messages and draft billing documents.
  3. 3 The coordinator matches and checks; therapists handle risk alerts and no-show follow-up.
  4. 4 Every step is logged and a monthly summary shows the measures the practice agreed to track.

How it behaves

How the system behaves day to day

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

What clients see

  • An immediate, kind acknowledgement with urgent-help guidance
  • Easy consultation booking and portal paperwork
  • Neutral reminders and the right telehealth link
  • Superbills on a predictable schedule

What the practice sees

  • One enquiry board and one waitlist
  • Risk alerts the moment they happen
  • No-show review lists and GFE deadlines

What the automation does

  • Captures, books, reminds, offers and drafts on schedule
  • Keeps clinical detail out of messages
  • Alerts the clinical director if anything fails

Edge cases and fallbacks

An enquiry mentions risk
Urgent-help guidance has already gone out and the designated clinician is alerted at once.
A client asks for no texts
Email only, applied across every workflow.
Two waitlisted people accept a slot
First confirmed acceptance wins and the other stays at the top.
A GFE deadline is near
The tracker escalates to the billing administrator and clinical director.
Platform export or n8n fails
Nothing is sent from stale data and the coordinator is alerted.

Integrations

What we connected

All integrations

SimplePractice

Practice management (US)

Booking, reminders, intake and superbills stay in SimplePractice; we build around them.

No public API for practices that we could confirm; its own features and exports, confirmed per project.

Calendly

Scheduling

Free consultation booking and reminders.

Calendly API and its Zapier listing.

HubSpot

CRM

Enquiries, matching fields and pipeline stages.

HubSpot CRM REST API.

Stripe

Payments

Payment links and receipts outside the practice platform.

Stripe Payment Links and the Stripe API.

Twilio

SMS

Neutral reminders, waitlist offers and clinician alerts.

Twilio Messaging API, under Twilio's BAA for client data.

n8n

Automation platform

Runs the workflows, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We met the clinical director, coordinator and therapists, mapped enquiry, intake, reminder, waitlist and billing steps, agreed the risk process and signed vendor agreements.

  2. 02

    Design and access

    Week 2

    Acknowledgement and crisis wording per country served, risk term list, consent and channel rules, platform exports, Twilio number and A2P 10DLC registration.

  3. 03

    Sprint 1: enquiries

    Week 3

    Built and shadow-ran the enquiry pipeline and risk alerts; the clinical director checked every flag.

  4. 04

    Sprint 2: intake

    Week 4

    The pipeline went live. Built consultation booking, portal intake triggers and the day-before list.

  5. 05

    Sprint 3: reminders

    Week 5

    Intake went live. Built neutral reminders, telehealth links and no-show review lists.

  6. 06

    Sprint 4: waitlist

    Week 6

    Reminders went live. Migrated the spreadsheet and built offers and check-ins.

  7. 07

    Sprint 5: superbills

    Week 7

    The waitlist went live. Built superbill drafts and the GFE deadline tracker.

  8. 08

    UAT and handover

    Week 8

    The team ran acceptance tests on every workflow, then we switched everything on, handed over the run book and trained the team.

  9. 09

    Support

    Ongoing

    Weekly check-ins during stabilisation, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Acknowledges every enquiry with urgent-help guidance
  • Scans for listed risk terms and alerts a clinician
  • Books consultations and sends portal paperwork
  • Sends neutral reminders and waitlist offers
  • Drafts superbills and good faith estimates and tracks deadlines

The team does

  • Match enquiries to therapists
  • Book first sessions and help with paperwork
  • Confirm waitlist bookings
  • Check and send billing documents

Therapist or clinical director decides

  • Responds to every risk alert
  • Decides clinical fit for each new client
  • Follows up missed sessions in their own way
  • Confirms codes, expected services and any fees

Compliance handled

Privacy, consent and safety, built in.

No therapy by automation

Workflows are administrative only, in line with Illinois' ban on AI therapeutic decision-making, applied everywhere.

Source: idfpr.illinois.gov

Crisis resources

Every acknowledgement and check-in includes urgent-help guidance, such as the 988 Lifeline in the US.

Source: 988lifeline.org

Good faith estimate deadlines

The tracker uses the CMS business-day timeframes.

Source: www.cms.gov

Texting limits

Reminders stay within the FCC healthcare exemption and carry no billing content.

Source: www.law.cornell.edu

Notes stay out

No workflow reads psychotherapy notes; billing documents use billing data only.

Source: www.law.cornell.edu

Outcomes

What changed for the practice

  • Every enquiry gets a safe acknowledgement within minutes, day or night.
  • Risk language reaches a clinician the moment it arrives.
  • Most first sessions start with intake already complete.
  • Freed slots reach the waitlist the same day.
  • Superbills go out on schedule and estimates are sent before their deadlines.

What we track

The measures the practice watches.

Enquiry response

Time to acknowledgement and to a personal reply.

Consultation to first session

Share of consultations that become first sessions.

Intake complete

Share of first sessions with complete intake the day before.

Waitlist flow

Time from slot opening to booking and average wait.

Billing on time

Superbills sent on schedule and GFEs sent before deadline.

Cost estimate

What a project like this costs

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

    Process mapping, risk process, wording and the backlog for all five workflows.

    $1,000 – $2,000

  • Enquiry pipeline module

    Capture, acknowledgement, risk alerts and report.

    $700 – $1,700

  • Intake module

    Consultation booking, portal triggers and day-before list.

    $700 – $1,600

  • Reminders module

    Reminders, links, policy wording and review list.

    $600 – $1,500

  • Waitlist module

    List, offers and check-ins.

    $600 – $1,500

  • Superbill and GFE module

    Drafts, deadline tracker and receipts.

    $700 – $1,700

  • Integrations

    Platform exports, CRM, booking tool, Twilio and Stripe.

    $300 – $1,000

  • Testing, UAT and launch

    QA, acceptance testing, launch and training.

    $400 – $1,500

  • Total project estimate

    $5,000 – $12,500

Optional monthly care after launch is quoted with your proposal. Typical range for this scope: five workflows at our fixed per-workflow range. Every practice gets its own fixed quote after a free call.

Monthly running costs you pay directly

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

  • 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.
  • n8n: Free self-hosted Community edition on your own server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • CRM and booking tool: The vendors' own plans.
  • Stripe: Stripe's published processing fees.

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

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.

Free 20-minute call

Want this built 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