Every office in the group reports differently. One runs Dentrix, the one you bought last spring runs Eaglesoft, and the regional manager builds the Monday spreadsheet by hand from six PDFs. Leakage hides in the averages.
What does Calibic do across locations today?
Here is the status of each piece, as it stands, because a DSO buyer deserves the chips and not the brochure.
| Capability | Status |
|---|---|
| One organisation with several offices, an office switcher, per-office settings | LIVE |
| Per-office connector and agent health (which office has gone quiet) | LIVE |
| Action Center, Activity log, Coverage and the weekly recap spanning all offices | LIVE |
| “All locations” roll-up of reports and dashboards | BETA, Group plan only |
| Location leaderboard, outlier detection, group-level alerts, benchmark bands | ROADMAP |
| SSO, API and MCP access | ROADMAP |
| Custom BAA terms | By conversation with counsel |
Each office connects through its own read-only agent. An Open Dental office, a Dentrix office and an Eaglesoft office can sit in one account, and the header shows which system each one runs and whether its agent is live or needs attention. Reports and dashboards show one office at a time unless the roll-up is on.
What is a DSO, in this context?
A dental support organisation owns or manages the business side of several practices: billing, HR, purchasing, marketing. The clinical side stays with the dentists. For Calibic the practical meaning is simpler: several databases, often on different software, and one person who has to answer “which office is leaking” without visiting each.
What does the audit trail do for a group?
Protect watches payment and adjustment changes in each office’s own system: Open Dental’s securitylog, Dentrix’s payment and adjustment views, Eaglesoft’s transaction tables. A completed payment deleted at 2:14 PM on workstation WS-03 shows up with the before and after values kept. It is evidence for a conversation, not an accusation, and the product says so in its own footer. What Protect can and cannot see differs by system; the Coverage page lists it per office.
How does a pilot work?
- Two or three offices, ideally on different software.
- Thirty days.
- The measures agreed before the agent is installed: recall patients rebooked, unscheduled treatment booked and completed, payment changes reviewed. All verified in the PMS, not counted when found.
- A written summary at the end, including what did not work.
What can you give procurement?
What exists: the Security page, a plain description of the data flow, the Business Associate Agreement, and a draft subprocessor list with the status of each vendor’s BAA.
What does not exist yet: a SOC 2 report, an independent penetration test, multi-factor authentication and SSO. We will not imply otherwise. If one of those is a hard requirement, say so in the first email and we will tell you whether the timeline fits.
What does it cost?
Enterprise and DSO pricing is by conversation. The single-location price is public on the pricing page, and group pricing starts from the same per-location basis with the pilot scoped first.
Next step: email hello@calibic.com with your number of locations, the practice software mix and the quarter you want the pilot to start. For the view a regional manager would use day to day, see For DSOs: every location on one screen.