June Portal vs. Weave, NexHealth, RevenueWell & Dental Intelligence
June Portal is the only patient platform for dental practices with no monthly subscription. June earns a small share of the patient payments it processes, so it only gets paid when it's working. The app patients download carries your practice's branding, not a vendor's, and shows them their own X-rays. June also writes your clinical notes from the visit, suggests your front desk's replies, and charts perio by voice, all under a signed BAA.
Have questions before you read the tables? Read the June Portal FAQ for pricing, PMS integrations, HIPAA and BAA coverage, and the AI features.
The comparison table
| June Portal | Weave | NexHealth | RevenueWell | Dental Intelligence | |
|---|---|---|---|---|---|
| Monthly subscription | None. Share of patient payments processed | Yes | Yes | Yes | Yes |
| Whose brand the patient sees | Your practice | The vendor's | The vendor's | The vendor's | The vendor's |
| App on the App Store & Google Play | ✅ Branded to your practice | Vendor-branded | Vendor-branded | Vendor-branded | Vendor-branded |
| Booking writes back to your PMS | ✅ Right operatory, right provider | Varies by PMS | ✅ | Varies | Varies |
| Scheduling configured to your booking rules | ✅ Your appointment types, providers, operatories, blockouts | Limited | Limited | Limited | Limited |
| AI clinical notes from a recorded visit | ✅ Draft written for you to review and sign | No | No | No | No |
| AI patient visit summary in plain language | ✅ Separate write-up for the patient | No | No | No | No |
| AI smart reply suggestions for patient messages | ✅ Staff approve before sending | Varies | Varies | Varies | Varies |
| AI runs under a signed BAA | ✅ HIPAA-covered infrastructure | Ask them | Ask them | Ask them | Ask them |
| Ask your practice numbers in plain English | ✅ | No | No | No | Varies |
| Voice periodontal charting with PMS write-back | ✅ | No | No | No | No |
| Push reminders from your own branded app | ✅ Plus one-tap add to calendar | Texts from a vendor number | Varies | Varies | Varies |
| Automated waitlist outreach to fill cancellations | ✅ Texts the list in order, first to accept takes it | Varies | Varies | Varies | Varies |
| Digital forms + e-signature | ✅ Built from a scan of your paper form | ✅ | ✅ | ✅ | ✅ |
| Two-way texting | ✅ App messaging with SMS fallback | ✅ | ✅ | ✅ | ✅ |
| Online bill pay | ✅ Posts back to the record | ✅ | ✅ | ✅ | ✅ |
| Reviews engine | ✅ | ✅ | ✅ | ✅ | ✅ |
| Signed treatment-plan acceptance | ✅ Codes and fees frozen on signature | No | No | No | Partial |
| In-house membership plans | ✅ Per-code discounts, family pricing, auto-billing | No | No | No | No |
| Insurance cost estimator | ✅ Patient portion before treatment | No | No | No | No |
| Records transfer between practices | ✅ Patient-initiated, admin-approved, expiring | No | No | No | No |
| Practice analytics | ✅ 8 categories from synced PMS data | Basic | Basic | Basic | ✅ Their core strength |
| Built by | Practicing dentists, used daily in their own office | SaaS company | SaaS company | SaaS company | SaaS company |
Things the alternatives generally don't have at all
Every row here is live in June today. Several are per-practice options you switch on rather than defaults.
| June Portal | The others | |
|---|---|---|
| Patients see their own X-rays and intraoral photos | ✅ Radiographs and photos viewable in your app | Not offered |
| Post-op instructions delivered to the patient's phone | ✅ | Not offered |
| Digital check-in the day before the visit | ✅ History, insurance, and consents confirmed in advance | Varies |
| One-tap add to phone calendar | ✅ | Varies |
| Alerts forwarded into your old system's inbox while you switch | ✅ See "Switching" below | Nobody does this |
| Privacy blur for operatory screens | ✅ Per-workstation, hover to reveal | Not offered |
| Chart readiness checked before the appointment | ✅ Missing or stale X-rays, perio data, sequencing | Not offered |
| Catches procedures posted to the wrong provider | ✅ Compares the ledger against who actually saw the patient | Not offered |
| Learns what each insurance plan actually pays | ✅ From your own claims history and EOBs, per code, per plan | Not offered |
| Chairside treatment-plan signing | ✅ Sign on the presenting screen | Not offered |
| Card-present payments on a countertop terminal | ✅ Posts into the PMS ledger with allocation rules | Varies |
| Specialist referral packets scoped to one tooth | ✅ X-rays filtered to the referred tooth, expiring links | Not offered |
| Patients can revoke records they shared | ✅ | Not offered |
| Month-end KPI scorecard against benchmarks | ✅ 12 KPIs, tier alerts, printable report | Varies |
| One "C" confirms the whole family's appointments | ✅ From a shared handset | Not offered |
| See exactly what a patient sees | ✅ Read-only, audited, shown in the patient's access history | Not offered |
| Payment plans and installments | ✅ | Varies |
The AI, and why the BAA matters more than the feature list
June writes the clinical note from your recorded visit, and separately writes the plain-language summary the patient reads afterward. It suggests replies to patient messages for your front desk to approve. It reads insurance EOBs, builds a digital form from a scan of a paper one, records perio depths by voice, and answers questions about your practice numbers asked in plain English. All of it runs on HIPAA-covered infrastructure under a signed Business Associate Agreement.
That last sentence is the one to ask every vendor about. AI in a dental product means patient information going to a model, and under HIPAA the company running that model is a business associate that has to sign a BAA before a single real patient's data reaches it. June's does. When you evaluate anyone else's AI, ask who processes the data and whether they've signed. It's a fair question and the answer should be immediate.
The clinical note and the patient's summary are worth separating out, because they're written for two different readers from the same recording. One is the chart. The other is what the patient shows their spouse that evening when they're deciding whether to go ahead with the crown.
The part that isn't a feature: how June is paid
Every product in the table above is a monthly software bill. You pay it in a slow month and you pay it in a busy one. June has no monthly subscription at all. June earns a small share of the patient payments it processes for your practice, which means June is only paid when it is collecting money for you.
This is the difference that survives any feature list. A subscription vendor has already been paid by the time you find out whether the product worked. June hasn't. If patients don't book, don't pay, and don't use the app, June doesn't earn. Everything we build is pointed at the same outcome you are: appointments on the schedule and money collected.
It also changes the arithmetic of adopting it. Most practices reach June already paying for a texting service, an online-forms tool, a payment link, a review-request tool, and sometimes a membership-plan vendor. June covers those. So the question isn't whether June is worth a new line in the software budget. It's how many lines you get to remove.
Switching: June forwards alerts into the system you're leaving
The hardest part of changing software is the couple of weeks where your front desk has to remember to check two places. June removes it. During onboarding, June forwards its actionable alerts as batched texts or email into the inbox your team already watches, including the phone number from your current vendor. Staff carry on looking where they always look, and June's alerts arrive there until they're ready to switch.
No other vendor in this category builds a bridge into a competitor's inbox, for obvious reasons. We built it because we've done the migration ourselves and know which week is the one that makes staff give up on a new system.
June Portal vs. Weave
Weave is a communications platform built around phones, texting, and reviews, sold as a monthly subscription with the vendor's branding on the patient experience. June Portal is a patient app carrying your practice's branding, with scheduling configured to your own booking rules, clinical AI, membership plans, and no monthly subscription.
What June puts in your patients' hands is a different category of thing. Your practice's app, on the App Store and Google Play, where a patient books a real appointment for real treatment, sees their own X-rays, gets an insurance estimate before saying yes, signs the treatment plan, pays the balance, and messages the office. Reminders arrive as push notifications carrying your name, and the appointment goes into their phone calendar in one tap. Behind it, June writes the clinical note from the visit recording, writes the plain-language summary the patient reads afterward, suggests the front desk's replies, and charts perio by voice. That AI runs under a signed BAA on HIPAA-covered infrastructure.
Patients don't walk in asking their dentist for an app. They've never been offered one. That's exactly why the practices that have one are remembered, and it's why we built June around the app rather than around the phone system.
June Portal vs. NexHealth
NexHealth is a scheduling and synchronization layer known for its range of PMS integrations, sold as a monthly subscription. June Portal covers the same booking, forms, messaging, payments, and reviews, and adds clinical AI, membership plans, signed treatment-plan acceptance, and an insurance estimator, with your practice's branding on the patient app and no monthly subscription.
June is compatible with roughly 95% of dental practice-management systems, with Dentrix and Open Dental live in production today and others activated on request. Bookings land in the right operatory under the right provider, and the availability patients see comes from your real schedule.
Where June goes further is past the booking. The treatment plan is presented, priced against the patient's insurance, and signed, with codes and fees frozen at signature. Membership plans run in-house with per-code discounts and auto-billing. Records transfer between practices without a fax machine. And the AI writes the clinical note, the patient's visit summary, and the draft replies your front desk sends, all of it under a signed BAA, which is not a given in this category and worth asking any vendor about.
June is also built by dentists who run it in their own practice every day. Workflow decisions get made by people who have to live with them at 8am on a Monday.
June Portal vs. RevenueWell
RevenueWell is a dental marketing and communications suite, sold as a monthly subscription. June Portal is the app the patient actually uses to run their relationship with your practice: booking, forms, treatment-plan acceptance, payments, membership, and messaging, with clinical AI behind it and no monthly subscription.
Marketing software emails your patient list. June is where the patient goes afterward. They open your app, see what they owe, pay it, see what treatment was recommended and what it will cost against their insurance, accept it, and book the appointment. Every one of those actions lands in your practice-management system.
And the reviews engine that sits inside June now does more than manage reputation. Review volume and recency are a large part of how Google and AI assistants choose which dentist to recommend, so a steady stream of recent reviews is a new-patient channel.
June Portal vs. Dental Intelligence
Dental Intelligence pairs practice analytics with a separate patient-engagement product, sold as a monthly subscription. June Portal includes analytics across eight categories computed from your synced PMS data, in the same product as the patient app, the clinical AI, and the membership plans, with no monthly subscription.
June's analytics cover production, scheduling, hygiene, new patients, treatment acceptance, A/R, insurance, and patient adoption, and you can ask about them in plain English rather than building a report. The numbers come from the same synced data the rest of June runs on, so the analytics and the app agree with each other by construction.
The clinical AI is the piece worth comparing directly. June drafts the visit note from a recording, produces the patient's plain-language summary, extracts insurance EOBs, and builds a digital form from a scan of your paper one. It runs on HIPAA-covered infrastructure under a signed BAA.
June Portal vs. the patient tools bundled with your PMS
The patient portals bundled with practice-management software are typically limited and dated: basic reminders, a generic web login, and little or no real online booking. June Portal is a modern app on the App Store and Google Play, branded to your practice, that works with your PMS rather than replacing it.
This is where most owner-dentists actually start. You already get something with Dentrix, so why add anything. The answer is in what your front desk did this morning: confirmed appointments by phone, handed out clipboards, re-typed the clipboards, and chased a balance that could have been paid from a text link. With June there's no monthly fee to weigh against that.
Closing
Every product above is a monthly software bill with another company's name on your patients' screens. June Portal has no monthly subscription and carries your practice's branding. It writes your clinical notes and your patients' visit summaries, suggests your front desk's replies, charts perio by voice, shows patients their own X-rays, fills cancellations off the waitlist on its own, and includes membership plans, treatment-plan acceptance, and insurance estimates. It's built by practicing dentists and runs in their own office every day. See it on your own schedule: