Fixed quote after a free call

Therapy waitlist management that is fair and kind

Waitlists usually live in a spreadsheet, so when a slot opens nobody can quickly see who fits. We build a structured waitlist with preferences, fees or insurance and availability, offer freed slots to suitable people in order, check in with people who are still waiting and include guidance on where else to find support. A typical build costs $1,000 to $2,500 and takes about three to four weeks.

The problem

Why therapy waitlists stall

When a client finishes or a clinician adds hours, the coordinator scrolls a spreadsheet trying to remember who wanted evenings, who needs telehealth and who has already found help elsewhere. The slot sits empty for days.

People on a waitlist can feel forgotten. A periodic check-in that confirms they are still waiting, and reminds them where to get help in the meantime, matters as much as the offer itself.

What we build

What our therapy waitlist automation includes

Structured waitlist

Preferences such as specialty, clinician, fees or insurance, telehealth and availability recorded for each person.

Fair offers in order

Freed slots offered to suitable people in waitlist order, with a time limit to accept.

Check-ins while waiting

Periodic messages confirming they still want a place, with guidance on other support.

Auto-tidy

People who found help elsewhere or stop replying are moved off the list after confirmation.

Capacity view

Waitlist length and wait times by clinician and specialty.

Risk stays with people

Replies suggesting risk alert the designated clinician immediately.

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

    Person added

    A matched enquiry with no space goes onto the waitlist with preferences.

  2. 02 Automated

    Slot opens

    A freed slot triggers offers to suitable people in order.

  3. 03 Automated

    Check-ins

    People still waiting get periodic check-ins with support guidance.

  4. 04 Coordinator review

    Coordinator confirms

    The coordinator confirms the match and books the first session.

  5. 05 Therapist or clinical director decides

    Clinical fit

    The therapist decides whether the match is clinically right.

How it behaves

How the waitlist behaves

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

What the client sees

  • A confirmation they are on the list
  • Regular check-ins with support guidance
  • An offer with a clear time to accept

What the practice sees

  • Who fits each freed slot
  • Waitlist length by clinician
  • Offers accepted and booked

What the automation does

  • Matches slots to preferences in order
  • Sends offers and check-ins
  • Alerts a clinician on risk replies

Edge cases and fallbacks

Nobody accepts in time
The next suitable person is offered the slot.
Two people accept
First confirmed acceptance wins; the other stays at the top of the list.
Reply suggests risk
The designated clinician is alerted at once.
Calendar sync fails
Offers pause and the coordinator is alerted.

Architecture

A fair therapy waitlist at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Matched enquiry No space yet Waitlist Preferences, order Slot opens Calendar event Offer sent Time to accept Coordinator Confirms booking Therapist Clinical fit
  • Input
  • Data
  • Logic and services
  • Output
  • People

How it flows

  1. 1 Matched enquiries with no space go onto the waitlist with preferences.
  2. 2 When a slot opens, suitable people are found in order.
  3. 3 Offers go out with a time limit; check-ins go to everyone still waiting.
  4. 4 The coordinator confirms the booking and the therapist confirms the fit.

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.

Waitlist management project plan

Typical time to launch: about 3 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Current list, criteria, offer practice and check-in wording.

  2. 02

    Design

    2 to 3 days

    Fields, ordering rule, time limits and support guidance.

  3. 03

    Build

    About 1 week

    List, slot detection, offers, check-ins and capacity view.

  4. 04

    Shadow run

    About 1 week

    Offers are prepared but sent by the coordinator while we compare.

  5. 05

    Launch

    1 to 2 days

    Migrate the old spreadsheet and switch on.

  6. 06

    Support

    Ongoing

    Rule changes and new clinicians.

What it runs on

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

n8n Airtable, Google Sheets or the CRM for the waitlist Calendar or platform availability Twilio SMS and your email provider Coordinator task list Clinician alerts

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. Often combined with the CRM and reminder workflows.

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.

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 check-ins

Check-ins include the 988 Lifeline (call, text or chat, 24/7) in the US and local services elsewhere.

Source: 988lifeline.org

EU and UK: storage limits

Waitlist entries hold mental health data under Article 9 GDPR and UK GDPR, so we keep only what matching needs and remove people who leave the list.

Source: gdpr-info.eu

UK: no marketing in check-ins

Check-ins are service messages; newsletters or offers to waitlisted people would be marketing under PECR.

Source: www.legislation.gov.uk

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

Waitlist management questions, answered.

Record what each person needs, offer openings in a fair, written order to people who fit, and check in regularly. Ours does all three and keeps the list tidy.

We build the list from your current spreadsheet and criteria, so you keep what works and gain the automation around it.

You choose the rule, such as date added within each specialty, and the workflow applies it the same way every time.

Every check-in includes where to get urgent help, and any reply suggesting risk alerts the designated clinician.

Only after they confirm they no longer need a place, or after a set number of unanswered check-ins and a final message.

Waitlist length, average wait by specialty, time from slot opening to booking and people who found help elsewhere.

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