For Sales

How to pitch it

You probably won't lead with this — it's plumbing, not a headline feature. But it's a good, concrete answer if a prospect (especially one evaluating security posture for a multi-branch or multi-clinic group) asks a pointed question like "if I reset someone's password or fire a doctor, are they instantly locked out everywhere, including their phone?"

Answer: yes. Resetting a password, disabling two-factor, editing someone's permissions, deleting their permission group, or suspending the whole clinic account all immediately end that person's sessions and stop their phone from receiving any further push notifications tied to that account. It's not just "they can't log back in" — it's "their device stops hearing from us."

Objections and how to handle them

"How do I know this actually works, not just in theory?" It's a server-side change enforced on every relevant action — there's no toggle to leave off, no setting to misconfigure. It's not something the clinic has to opt into or remember to check.

"Does this affect our patients' data at all?" No. This only concerns staff/clinic-user accounts (doctors, receptionists, managers, owners) and their own devices. Patient-facing push notifications (appointment reminders sent to patients) use a completely separate token store and are untouched by this change.

"What about the phone itself — does it get wiped or locked?" No device management is involved. This is purely about which server-side notification channel is still considered "live" for a given phone. The phone itself, and any locally cached app data, are unaffected.

Competitive angle

Frame it as part of a broader pattern rather than a standalone bullet: Dentolize already has permission groups, two-factor authentication, and clinic-level account suspension. This closes a real (if narrow) gap in how thoroughly those controls take effect — worth mentioning if a competitor's sales team is trying to poke holes in your security story, but not worth leading with unprompted.