Five criteria decide it, and a demo answers none of them
A demo shows the inbox, the templates and the dashboard, and every platform's demo looks good. The five criteria are answered in writing, by email, before the demo, because each one is a question about ownership and record-keeping rather than about screens. The rules the messages must follow, consent, quiet hours, opt-outs and what may be said by text, are in the med spa texting rules guide. Confirm with counsel which apply to your practice.
The A2P registration carries your name, or the number is on loan
Carriers ask a business that texts at volume to register the business, the use case and sample messages before they deliver the traffic reliably; the registration is called A2P 10DLC. Ask whose legal name and tax identifier are on the registration and who holds the campaign. A registration in the practice's own name, tied to its brand, is yours. A shared registration under the vendor's brand means your messages travel on their standing, and leaving means registering from zero. What the registration requires of your practice is for the vendor and counsel to confirm.
Consent is logged against the patient record, or it cannot be found
Send a marketing text only to a patient whose consent is on record, and ask the platform to store the four things the texting rules guide lists for every consent. Whether a given message needs consent, and what counts, is for counsel to confirm. Ask to see the export of that log for one patient. A platform that keeps a consent flag with no wording and no date gives you a checkbox and no record. The log should sit on the patient record, or write back to it, so the filter before every send reads one source. What counts as consent is for counsel to confirm.
Two-way texting needs a handoff to a person, and the thread stays in one place
Jess replies to a comeback text with a question about bruising. The platform has to route that reply to Dana, keep the whole thread in one place, and let Dana answer from the same number. Anything clinical goes to a provider, never to an automated answer. Ask how a reply reaches a person, how fast, on which device, and what the patient sees while they wait. A platform that sends well and receives into a shared inbox no one watches is a one-way platform with a reply button.
The connection to the record system is what makes the message timely
The comeback is timed from the last visit date, and that date lives in the record system. Ask which connection exists between the two: an API that reads visit dates, a scheduled export, or a booking link only. Each is workable, and each changes what the platform can do on its own. A platform with no connection sends what it is told, and somebody has to tell it every week. The chart, the consents and the photos stay where they are either way; the growth system is built around the record, never away from it.
The number is the one patients saved, so it has to be yours
The number on your website, your profile and every patient's phone is the number the practice texts from. Ask, in writing, whether the number is registered to the practice, whether it can be ported out, how long porting takes and what it costs. A vendor that owns the number owns the relationship with every patient who saved it. Leaving a platform should never mean a new number on the sign.
The scoring table, 0 to 2 per criterion, out of ten
| Criterion | The question to ask in writing | What a 2 looks like | What a 0 looks like |
|---|---|---|---|
| A2P registration | Whose legal name and brand are on the registration and the campaign | The practice's own, with the confirmation shown | A shared registration under the vendor's brand |
| Consent logging | Show the consent export for one patient | Wording, date, number and source, on the patient record | A flag with no wording or date |
| Two-way with handoff | How does a reply reach a person, and how fast | Routed to a named person's device, in one thread | A shared inbox with no owner |
| Record connection | What reads the last visit date from our record system | An API or a scheduled export that runs on its own | Someone uploads a list by hand |
| Number ownership | Is the number ours, and what does porting out take | Registered to the practice, portable, in writing | The vendor holds it |
How to score one in a week
- Send the five questions to each vendor by email on Monday, so the answers exist in writing.
- Take the demo with your own number as the patient's phone, reply with a question, and time how long a person takes to answer.
- Text STOP from that phone and clock the halt on every sequence.
- Score each criterion 0 to 2 from the written answers, never from the demo.
- Give the written answers and your scores to counsel before signing anything.
What to do next
NorthCore's Bring patients back solution builds the texting engine on whichever platform scores, with the registration in your name, the consent log on the record and the handoff to Dana. Scoped in writing and covered by the promise on this site: results in 90 days, or we keep working until you have them.
