On this page
The pitch, in one breathQualifying questions to ask a prospectObjection handlingWhat's genuinely differentiatedFor Sales
Status: pre-release, beta-gated. This is a briefing for internal prep, not a feature to demo or promise a close date around until it's out of beta for the region/tier you're selling into.
The pitch, in one breath
"Your imaging workstation and Dentolize can now talk to each other directly — a staff member taps Acquire on a patient's chart, the scanner captures the image, and it lands in the chart automatically. No more walking a USB drive across the office." This now includes a real, working desktop application (not a future promise) with a native scanner driver, auto-update, and support for 10 languages.
Qualifying questions to ask a prospect
- What imaging hardware/software do they currently use to capture X-rays? This feature requires installing a Windows desktop application (the "Dentolize Bridge") on the machine connected to the sensor/scanner, and that app talks to the scanner via TWAIN — the industry-standard driver interface most dental sensors support. It is not a universal driver for arbitrary hardware, and physical-hardware validation against real scanner models is still in progress (validated so far against TWAIN's reference test source), so don't commit to a specific device model without checking with product first.
- Are they on Windows? The desktop app currently ships as a Windows installer only.
- How many rooms/operatories have their own imaging setup? The feature is explicitly multi-room aware (each room's desktop app connects independently and can't collide with another room), which is a good fit for larger clinics but overkill to lead with for a single-chair practice.
- Who manages their IT/workstation setup? Someone needs to install the desktop app and paste in an Access Key generated from Dentolize's web app — this isn't a pure end-user, zero-setup feature, though the setup itself is a few clicks once the key exists.
Objection handling
| Objection | Response |
|---|---|
| "We already have a scanner that saves to a folder." | This still works — nothing about manual upload is removed. This is an additional, faster path for clinics whose workflow allows a live connection to the workstation. |
| "Is our patient data secure in transit?" | Yes, with specifics you can speak to: credentials are hashed (not stored in plaintext), revocable instantly, scoped to specific capabilities, rate-limited, and every uploaded image is independently re-verified by the server (size, checksum, and real image-format inspection) before it's accepted — the desktop app's own claim about what it uploaded is never trusted blindly. This has been through an internal security-focused rewrite and re-audit; it has not yet been through an external penetration test or a real-hardware pilot, so avoid absolute claims like "unbreakable" — say "built with defense-in-depth" and loop in product/security for anything more specific a security-conscious buyer asks. |
| "Does this work with [specific sensor brand]?" | Don't commit to hardware compatibility yet. The desktop app uses the industry-standard TWAIN interface most dental sensors support, but validation against real hardware from specific vendors hasn't been completed — check with product before promising a specific brand. |
| "Can we control who's allowed to trigger a capture?" | Yes — it's gated by a permission (ACQUIRE_PATIENTS_XRAYS) assignable per staff role, and managing the Access Keys/devices themselves is a separate, admin-only permission (MANAGE_ACCESS_KEYS) — so front-desk staff can be allowed to use the feature without being able to configure it. |
| "Is this available now?" | No — it's beta-gated behind a feature flag today. Frame any pilot conversation as "let's get you into the beta," not "this ships with your next update." |
What's genuinely differentiated
- Real-time status visibility (most competitors' "integrations" are folder-watchers with no live feedback).
- Per-room connection awareness for multi-chair clinics, with server-enforced protection against two staff members colliding on the same scanner.
- A structured audit log (who requested, who/what fulfilled it, every status change, every credential revocation) — useful in conversations with clinics that have compliance requirements around clinical media handling.
- Server-side verification of every uploaded image, not a "trust the client" model — a specific, technical answer to a security-conscious buyer's questions rather than a hand-wave.