Automate the boring half of practice life

What automating actually buys you

The point of automation isn't speed. You'll only save a few minutes a week from any single workflow. The point is removing the fifty small slip-ups that quietly eat trust with clients, the intake form you forgot to send, the portal invite that sat in your draft folder, the appointment reminder you meant to write but didn't.

Manually, every one of those is a coin flip. Automated, every one of them happens. Your mental load shifts from 'did I send that?' to 'the system did, I can move on.'

The second-order effect is harder to feel until you've worked without it for a month. Clients who get a portal invite the same day you create their record start their relationship with you in a different posture than clients who chase you for one. Clients who get a reminder 24 hours before show up at a higher rate than clients who don't. Intake forms that arrive automatically get completed; intake forms that wait on you get forgotten.

None of this is about working faster. It's about consistency. A solo practice with automation looks, to clients, like a five-person practice with great ops. That gap is what your competitors don't have, and it's almost entirely a function of which workflows you turned on in your first week.

The automation event model

Before you turn anything on, understand the two different things in Workflows because they behave differently and break differently.

Workflows are event-triggered. Something happens in your practice and a workflow fires in response. They sit in four categories. Client and documentation events: a client is created, an intake form is sent, a portal invite goes out. Scheduling events: an appointment is created, received, declined, cancelled, or rescheduled. Communication events: a client sends you an in-app chat message. Billing and payment events: an invoice is paid, a refund is processed, a superbill is sent.

Each workflow runs as a sequence of steps. If a step is disabled, anything downstream, including the email or SMS at the end, doesn't run.

Basic reminders are different. They're scheduled nudges attached to an anchor event. Four anchors exist: appointment reminders fire a set number of hours before the appointment, invoice reminders fire a set number of days before or after the due date, intake reminders fire a set number of days after the intake was sent, and portal invite reminders fire after the invite was sent. You can stack multiple reminders per anchor, for example, 24 hours and 2 hours before an appointment.

One hard rule: reminders only send if the underlying workflow is enabled. They piggyback on the workflow's event. Forget this and you'll be debugging 'why isn't my reminder firing' when the answer is the appointment-created workflow is off.

The Workflows page lives in the main sidebar, it used to be buried in Settings, it isn't anymore.

The minimum viable automation stack

The opening stack for any practice, regardless of size or profession. Resist the temptation to enable more.

Send intake. Auto-sends every form in your default intake folder the moment you add a new client. This is the single highest-leverage workflow in the entire product. It turns intake from a thing-you-have-to-remember into a thing-that-already-happened.

Automate portal invites. Sends the portal invite the moment a client is created. Clients with portal access engage with you between sessions; clients without it don't. Note that both intake and portal-invite workflows apply only to newly created clients, they won't backfill your existing roster, so if you want to invite existing clients you'll need to send those manually.

Appointment reminders, 24 hours before. Email is fine. Add SMS if you're on a paid plan and your client base actually reads SMS, for some professions the bump in show rate is meaningful, for others it's noise.

Invoice reminders, on due day and 7 days overdue. Two reminders, not five. The first is a polite nudge, the second is a real one. Anything past 7 days overdue needs a phone call, not another email, automation isn't going to recover that money.

That's the entire opening stack. Four workflows, three reminders. You can run a whole practice on this.

Things that look tempting but you should not turn on yet: appointment cancellation/reschedule emails (you don't know your tone yet), every invoice reminder slot (clients learn to ignore them), portal invite reminders before clients have a reason to log in. Add these only after you've hit a specific problem they solve.

Default intake folder strategy

The default intake folder holds up to 9 forms. Every form in it gets auto-sent to every new client when the Send intake workflow is on. Nothing about the 9-form ceiling is a target, it's the upper bound of what the system will accept before it gets ridiculous.

Three forms is the right number for most practices.

One main intake form. Demographics, history, presenting concern, emergency contact. Build it once, properly.

One outcome measure. PHQ-9 if you're in mental health, GAD-7 if anxiety-focused, pain VAS for physical therapy, whatever your profession actually uses. One measure at baseline tells you something. Five measures at baseline tells you nothing because clients abandon halfway through.

One consent form. Your terms of service, telehealth consent if applicable, payment terms.

That's it. Practices that load eight forms into the default folder don't get more data, they get higher intake-abandonment rates and clients who arrive at the first session apologising for not finishing.

The folder is starred in your Templates page. Move a form in by hovering it, clicking Move to folder, and selecting Intake. Existing default intake templates migrate in automatically.

If you want certain clients to get a longer intake (say, a comprehensive psych assessment battery for new therapy clients vs. a light intake for medication-management consults), keep those forms outside the default folder and send them manually from the Share button when the case calls for it. The auto-send is for the universal subset everyone gets.

Smart-chip and reminder copy that doesn't sound robotic

Inside any reminder or workflow template, the editor lets you insert smart chips, pill-shaped tokens that pull live values like client name, appointment time, location, practitioner name. They're not curly-brace variables; you click the smart-chip control in the editor toolbar and the token drops into the message body. At send time, the system replaces each chip with the real value for that recipient.

The trap most practices fall into: writing reminders that sound like reminders. 'This is a reminder that you have an appointment on [date] at [time].' Clients ignore those because they sound automated, which they are.

Write reminders that sound like you wrote them once and meant it. A few patterns that work:

*Appointment reminder, 24h before*: 'Hi [client name], just a quick note, we have our session tomorrow at [appointment time]. The link is in your portal. If anything has come up, message me through the portal and we'll find another time.'

*Invoice reminder, day-of*: 'Hi [client name], your invoice for [service] is due today. You can pay it directly from the portal, takes about 30 seconds. Let me know if anything looks off.'

*Intake nudge, 2 days after send*: 'Hi [client name], you'll have a couple of forms in your portal from us. They take about ten minutes and they help me show up prepared for our first session. No rush, but ideally before we meet on [first appointment].'

Three rules. Write like a person. Tell the client what to do, not just what's happening. Hit Preview before you save so you can see exactly how it renders with real data. Reminders reuse the same template across email and SMS. Keep the email longer, the SMS shorter, and let smart chips do the personalisation work in both.

Communication mode rules

Go to Settings → Workspace settings → Communications. Four modes determine who can start an in-app chat with whom, and each one has a different operational consequence.

Reply only (default): clients can respond to staff-initiated conversations but can't start new ones. On this mode, a conversation auto-closes 48 hours after a staff message without a client reply. Most solo practices want this. It keeps your inbox sane and gives clients a real channel to reach you without turning into 24/7 text support.

Never initiate communication: clients can't start chats at all. Use this if you've decided in-app chat isn't a channel for your practice, you'll still send appointment confirmations, invoices, etc., but chat is off as a two-way medium.

Assigned clients only: staff can only message clients assigned to them. This is what most group practices want. It prevents the receptionist from accidentally seeing a clinical chat, and it gives each practitioner a clean view of their own caseload.

All clients: any client can start a chat with any staff member at any time. Only sensible for very small practices or specific concierge models. For most operations, this becomes a noise problem inside a month.

A few things worth knowing. Chat is HIPAA-compliant and encrypted in transit and at rest. Clients receive an email notification when you send a message, you can customise that notification template under the chat-message-received workflow. Clients can't adjust their own preferred notification method (email vs. SMS) from the portal; you set it from their profile via the gear icon → preferred notification method.

Pick a mode in your first week and revisit only if it breaks. Switching modes mid-stream confuses long-tenured clients.

Why automations fail: the troubleshooting matrix

When a client reports they didn't get something, three things are wrong, roughly in order of likelihood.

(1) The workflow is disabled. Go to Workflows, find the workflow that should have fired (e.g. Send intake, appointment created), and check the enable/disable toggle. If it's off, nothing downstream runs, not the email, not the SMS, not the reminders attached to it.

(2) The specific reminder is disabled or wasn't created. Under Workflows → Basic reminders, each category (appointment, invoice, intake, portal invite) has its own list. The workflow being on doesn't mean reminders exist for it, you have to + New reminder under each category and configure the timing.

(3) The client's notification settings don't allow the channel. Go to the client's profile → settings (gear icon) → preferred notification method. If their email is off, no email reminders. If their SMS is off, or if you're on the Free plan, where automated reminders are unavailable, no SMS. Clients can't change these from their portal, so you own the setting.

The tier traps are the fourth thing. Free workspaces can see the Workflows page and look like they have access, but Free users don't have automated email reminders or SMS, and they can't edit workflow or template content. By default, workspace owners and admins can edit workflows and templates; practitioners can't unless you grant them edit permission via Team → Permissions.

If all three boxes check out and reminders still aren't arriving, it's usually a client-side spam filter or a wrong email address, verify the email on the client record and ask the client to whitelist your domain. Don't waste time chasing automation gremlins until you've ruled out the basics in that order.

The next layer: AI prompts inside templates

Once your basic automation runs without you thinking about it, the next layer is AI prompts embedded inside note templates. This is where the time savings stop being marginal and start being substantial.

A template can include three kinds of content the AI uses to generate notes from a session transcript:

Placeholders in square brackets: [Patient Name], [Insert past medical history]. Markers for where information goes.

AI instructions in round brackets: (Describe in detail, only include relevant past medical history if explicitly mentioned in the transcript or contextual notes.). Tells the AI how to handle the placeholder or section.

Verbatim text in double quotes: signature blocks, disclaimers, anything that should appear exactly as written every time.

Combine them: [Insert past medical history](Describe in detail, only include relevant past medical history if explicitly mentioned in the transcript or contextual notes.) produces a populated history section, drawing only from what the session actually covered.

Inside the template editor, type / to open the quick-insert menu, it surfaces AI smart prompts, headings, lists, form fields, and images without leaving the keyboard.

The hard requirement: AI prompts only run when the note has a transcript. No transcript, no AI generation. So this layer compounds with AI Scribe, record the session, transcribe it, apply your prompt-equipped template, and a near-final note appears before you've typed a sentence. Edit, sign, done.

Useful prompt patterns to build into templates: 'Generate a discharge letter from this session's transcript and the last three sessions' notes.' 'Summarise the key takeaways for the patient in plain language.' 'Compare this session to the last session and flag any meaningful change.'

For ad-hoc questions outside templates, use Ask AI, the side panel that takes the current client context, the open note, any uploaded files (PDF, DOCX, PNG, JPG up to 100MB per file), and answers in natural language. It's HIPAA-compliant and only processes information already in your workspace.

Start with one template per common workflow, your standard progress note, your standard intake review, your standard discharge summary. Run each through AI for a few sessions, refine the prompts based on what you keep editing, and within a month your note time per session is half what it was. That's where automation crosses from 'saves admin' to 'changes the economics of your practice.'