Command note: nobody plans to spam a lead. It happens because five workflows each send something reasonable. Every published workflow looks fine on its own. The contact experiences the sum of all of them. The command I run before adding anything new to an account: "List every published workflow in this sub-account, and for each one show me its trigger and every message step it sends. Group them by trigger so I can see which workflows the same contact can enter at once." What usually comes back: • Four workflows that all fire on contact created • Three separate "just checking in" texts inside 48 hours • A nurture sequence still running underneath a booking confirmation • Message steps with almost no wait between them Do this before you build the next automation: 1) Pick one real entry point — a form, a calendar, an ad. 2) Add up every message a contact from that door receives in week one, across all workflows, not just the one you are editing. 3) Write the number down. If it is more than you would tolerate in your own inbox, cut messages. Do not reorder them. 4) Add an exit condition to the sequences that should stop when another one starts. 5) Run one test contact through that door and read the actual thread, in order, the way they will read it. Most accounts do not have a messaging problem in any single workflow. They have a stacking problem nobody has ever added up. Your client does not count workflows. They count messages.

Command note: a merge field that fails doesn't error. It just prints. We sent a campaign where the greeting rendered as "Hi ," for part of the list. No bounce, no warning, nothing in the logs. The field was simply empty on those contacts, and the message went out anyway looking like a template somebody forgot to finish. Three ways this goes wrong: • The token is misspelled or points to a field that was renamed, so it renders as raw text • The field exists but is blank on a chunk of the list, so you get the punctuation with no name • The field only fills from one form, and half the audience never saw that form What we do now before anything goes out: 1) Check fill rate first — count how many contacts in that exact audience have the field populated 2) Write a fallback for every token, and assume the fallback will be the one that prints 3) Send the real message to a test contact with the field deliberately empty, then read it 4) If the fallback reads badly, rewrite the sentence so the field isn't load-bearing 5) Publish only to the segment where the data actually exists The fix is almost never better data. It's usually a sentence that works either way. A merge field is a promise about your data. Don't make one you can't keep.

I noticed that you are using examples of clinics. Is your system HIPAA compliant? I have not done anything with any client with patients involved because I am not sure about this. My understanding is that even collecting information from patient leads could be affected by HIPAA compliance. I know it is possible. I just don't know how to do it, so I thought I'd ask you how you were ensuring compliance.