Insights

The CRM inside a psychiatry site holds less than you would think

The CRM inside a psychiatry site holds less than you would think

MindMorph Holistic Psychiatry went live on October 16 with a contact form. Three days later it had a second way in, a sign-up for the practice's Integration Circle, and the two now land in one Messages list in Masha Steiner-Renoir's dashboard. Building the CRM behind them was mostly a list of things it must refuse to do. It holds no patient records, it repeats nothing a stranger typed, and it never lets anyone mistake a form for a crisis line.

What a psychiatry site should not hold

MindMorph is a holistic psychiatry practice that sees patients by telehealth across Colorado and Oregon, in English and in Russian, ahead of a new Lakewood office that opens December 1. Booking runs through IntakeQ, and patient records stay there. The website links out at the right moment and keeps nothing clinical. So its CRM is for the people around the practice rather than in its care: someone with a question about ketamine therapy, someone who wants to join a group.

The harder rule is about time. A contact form is read when someone gets to it, which on a busy day might be tomorrow. The person who lands on a psychiatry site at two in the morning needs something faster than that, and something faster exists. A GAO report from July 1, 2026 counted about 19.1 million calls, texts and chats routed to 988 crisis centers between July 2022 and September 2025, and Pew wrote on July 24, 2026 that the line had passed 23 million contacts in its first four years. The site's job is to point there, plainly, and never to compete with it.

Crisis words come first

The old WordPress site had no crisis line anywhere. The new one carries 911 and 988 on every service and condition page and in the footer. The search box and the chat go further. Before a query is searched, and before any language model sees it, it is checked against a list of crisis phrases in English and in Russian. A match returns a fixed answer with 911, 988 and the Crisis Text Line, and nothing else. No search results, no friendly paragraph, no suggestion to fill in the contact form. The chat's own instructions say why, in a line I wrote for it: "nobody watches them in real time." Questions about doses get a different fixed answer that sends people to their prescriber.

Two doors, one list

The two forms look alike in the dashboard, but what they may carry differs, and that difference is the design.

Diagram titled A message and a sign-up arrive differently, and stay different. Door one, the contact form: someone writes in; it is free text, so a language model screens it for junk; a doubted message is archived with no reply to the sender; the team still gets a notice marked Possible spam; and it can never be filed as a circle sign-up. Door two, the Integration Circle: someone registers; adults only, so a year of birth under 18 is refused; one box per agreement, each saved word for word; no free text, so nothing for a model to screen; and the reply reads back email, phone, year and agreements, never the name. Both arrows lead to a dark panel labelled Messages, one list filtered by type, where each record keeps its own automatic reply and team notice, editable in Settings, and a sign-up from the Russian page is answered in Russian. A footnote says chat and the Ask finder sit outside this list: crisis words get 911 and 988 before any model runs.

The contact form takes free text, so it gets the same junk screen I built for a small clinic's CRM, with one change. At the clinic, a message the screen doubts is archived quietly. At MindMorph, on the day the site went live, I made it send the team a notice anyway, marked Possible spam and saying where to find it. The sender still gets no automatic reply. The comment above that code is the reason in one sentence: a real patient misjudged as junk must never vanish silently. A psychiatry practice gets fewer messages than a clinic, and each one may have taken more nerve to send.

The circle sign-up is stricter in every other direction. It asks for a first and last name, a year of birth, an email and a phone number, and it refuses anyone under 18. Then it shows the circle's agreements, one box for each, and every box must be ticked. When the record is saved, the agreements go into it word for word, along with the date of the circle that was next at that moment, kept as words. If Masha rewrites an agreement next spring or deletes a date, the record of what this person agreed to, and when, does not change.

There is no free text on the sign-up, so there is nothing for a model to screen. That also made the automatic reply simple to write safely. It reads back the email, phone, year of birth and agreements, and never the name. Anything a stranger can type, the reply does not repeat, so the form cannot be used to send someone else a message in the practice's voice. A sign-up from the Russian page gets its reply in Russian.

The doors also cannot be swapped. A review of the build on October 19 found that the contact route would accept a posted type, so a forged request could file itself as a circle sign-up and trigger a registration reply carrying its own words. I closed it the same day: the contact intake now always files as a contact, the reply reads back only agreements the sign-up page actually states, and the site's lead API accepts only the two types it knows.

Writing to everyone at once

A group needs dates and reminders. Masha adds circle dates herself, in Mountain Time, and past ones drop off the public pages on their own. A note that contains a web address is refused, so the joining link never ends up on a page anyone can read. Then there is the button that emails everyone who registered, which is the most dangerous button in her dashboard, so it asks twice.

Diagram titled One button sends to the whole circle, so the button asks twice. Four steps. One, write: compose a subject and message, with a test sent to herself first. Two, review: the exact number it will reach, and if the list changes before she presses Send the review shows again. Three, send: twenty at a time, with a short pause between messages, one email per address, the newest sign-up deciding. Four, history: each mailing and each person it reached, kept in the dashboard. Below, three rules: a stop flag per person, so someone stopped or removed mid-send is skipped by the next batch; caps on all site mail of 300 an hour and 800 a day, counted by the database clock and kept under the mail host's limits; and a way out in every email, which ends by saying why it came and how to stop it. A footnote says it was built October 19, 2026, and on a development machine every one of these emails lands in a local outbox instead.

The composer sends a test to her first. The review shows the exact number of people the message will reach, and if a sign-up arrives or someone is removed before she presses Send, the review shows again with the new count. The send itself goes out one person at a time, twenty per batch, and each batch checks every name again, so a person who asked to stop halfway through a mailing does not get it. Every email the site sends, of any kind, counts toward a ceiling of 300 an hour and 800 a day, measured by the database clock, kept below what the mail host allows. A mailing that would cross the line pauses and says so: press Continue in a while, or tomorrow.

On my machine none of this can reach a real person. Every message the site tries to send while I am building lands in a local outbox addressed to my own sandbox, decided by the environment, not by a setting someone could forget to flip.

Less in the record, more in the guard

Most CRM advice is about what to capture. On a psychiatry site the useful question runs the other way: what can this record live without, and what should the site refuse to say? There is more about that habit in one CRM, five businesses. At MindMorph the answer is short enough to read at the bottom of every circle email, which ends on the same sentence each time: "You are getting this because you registered for the Integration Circle." The next line gives the practice's own address to write to if you want them to stop.

Common questions

Does the MindMorph site store patient records?

No. Booking and patient records stay in IntakeQ. The site's Messages list holds contact messages and Integration Circle sign-ups, and the contact form asks for nothing clinical.

Why does the sign-up save the agreements word for word?

So the record shows exactly what each person agreed to on the day they signed up. If the agreements are rewritten later, earlier sign-ups keep the wording they actually saw.

What happens if someone types a crisis message into the chat or search?

Crisis phrases in English and Russian are matched before any search or language model runs, and the answer is a fixed one with 911, 988 and the Crisis Text Line.

Can people stop the circle emails?

Yes. Every circle email ends by saying why it was sent and how to stop it, and the practice can set a stop flag on a person, which the next batch of any mailing respects.

Related

← All insights