Two Patients, One Schedule, and Why Software Has to Tell Them Apart
A dermatology practice runs two businesses through one front desk, and most software behaves as though it runs one.
The medical side is referral and recall driven. A patient arrives because a primary care physician sent them or because a mole needs watching, insurance is involved, and the follow-up interval is clinical rather than commercial. The practice does not need to persuade anybody. It needs to make sure the people who are due actually come back.
The cosmetic side behaves nothing like that. It is elective, it is paid for out of pocket, the patient is comparing you with other practices and often with a med spa down the road, and the decision waits for a moment that has nothing to do with medicine. A consultation is the sale, and a consultation that does not get booked is simply lost.
Run both through the same system and you get one of two failures. Either the medical recall gets treated like a sales pipeline, which is inappropriate and makes the practice sound like it is chasing money, or the cosmetic enquiry gets treated like a recall, which means a polite reminder and no conversation, and the patient books somewhere that actually rang them back.
So the record has to know which kind of patient this is before anybody speaks to them, and the call has to change accordingly. That distinction is the single most useful thing a dermatology practice can ask software to hold, and it is the one thing a generic CRM has no field for.





