Dentolize · Plugin Platform Walkthrough
On this pageThe one-line pitchWhat to lead withWhat NOT to claim yetGood angles for launch content

For Marketing

The one-line pitch

Dentolize now has an open plugin platform — the same integration model as Shopify apps or Slack apps — so the ecosystem of tools a dental clinic already uses (labs, imaging, payments, insurance, marketing) can plug directly into their Dentolize account instead of living in a separate tab.

What to lead with

  • "Extend your clinic with trusted integrations" is the product's own tagline, shown right at the top of the in-app Plugin Hub — reuse it.
  • The consent screen is a genuine differentiator worth screenshotting: before installing anything, a clinic owner sees exactly what data a plugin can touch, grouped from "basic clinic info" up to "patient personal data," in plain language, not legal boilerplate or a vague permissions list.
  • Frame this as choice, not lock-in — the clinic decides what to connect, can see a live delivery log for every integration, and can uninstall anything with one click, immediately revoking access.

What NOT to claim yet

  • Not self-serve. There's no public developer signup or portal in this release — every plugin listing is created by Xolize staff after a partner reaches out (devrel@dentolize.com). Don't imply "any developer can publish instantly."
  • One example integration exists today. The only plugin in the registry as shipped is the internal demo (Demo Appointment Reminders), used for developer onboarding and the sandbox. There is no marketplace of real third-party plugins live yet — don't show marketing collateral implying a populated marketplace.
  • This is unreleased. Everything in this PR is pre-release; nothing here should be described as "now available to clinics" until it actually ships to production and has real partner listings behind it.
  • CRM/loyalty/inventory/BI integrations aren't built. The roadmap document names these as a future "Wave 4" — a proposal, not shipped code. Don't reference specific unbuilt integration categories as current capabilities.

Good angles for launch content

  • Trust and transparency as the product story, not just "we have an API." The scope-tier consent UI, the DPA acceptance flow, and the visible activity/delivery log are the actual differentiators — most competitors' "integrations" are just a webhook URL field with no user-facing consent model at all.
  • The reminders example is a real, working reference, not a mockup — an SDK example app (examples/appointment-reminder-bot) ships in the platform's public repo alongside the seeded sandbox plugin.
  • Saudi-market specificity: the platform explicitly supports Arabic-first plugin listings and settings forms, and the revenue-integration surface (ZATCA e-invoice status stream, insurance claims) is tuned to real Saudi clinic workflows — a stronger regional story than a generic REST API.