Practices (medical, dental, veterinary, legal, financial) have a specific version of this question, because the wrong automation is not merely unhelpful, it is a compliance problem.
Safe and high-value
Appointment logistics. Confirmations, reminders, rescheduling, waitlist filling. Highest return, lowest risk, and the no-show number alone usually justifies it.
Recall and intervals. Telling people when they are due. Reliable, low-risk, and one of the largest revenue effects available in a practice.
Intake and forms. Collected before the visit rather than in the waiting room. Saves time on both sides and improves the data.
Routine logistics. What to bring, where to park, what to expect, arrival instructions.
Payment and billing reminders. Routine, repetitive, and consistently under-done.
Internal reporting. Utilization, no-shows, recall compliance, aging balances.
Requires care
Anything containing clinical or case detail. The rules on what may be sent through which channel are specific and non-negotiable, and the safe pattern is a notification that something is waiting in a secure place rather than the content itself.
Anything a patient or client might read as advice. Keep automated messages logistical.
Triage. Automated urgency assessment is a serious undertaking with real consequences, and it should be treated as one.
Never
- Anything that decides, or appears to decide, clinical or professional matters.
- Anything that puts protected information into an unsecured channel.
- Anything that prevents somebody reaching a person when they need one.
- Anything that continues contacting somebody who has asked it to stop.
The design principle
Automate the logistics around the professional relationship, never the relationship itself. Every item in the safe list is administrative. Everything in the never list touches the substance of what the practice does.
That line is easy to state and worth writing down explicitly before anything is built, because the pressure to blur it comes later and usually with good intentions.
The compliance conversation happens first
Whatever framework applies, the answer to "may we send this, through this channel, to this person" is determined before design, not after. Retrofitting is expensive and occasionally impossible.