Teardown index

Section 01

Product

A polished scheduling surface, built mobile-first

Cobaltine’s core product is a scheduling view for front-desk staff and a patient-facing booking app. The patient app is the strongest part — three of our own customers mentioned it unprompted, and one asked whether we planned to build something similar.

It shows open slots, lets patients self-book into them, and handles reminders. Everything it does, it does well.

Source — Product walkthrough at Ambulatory Systems Conf, Jun 2026; buyer conversations, Jun–Jul 2026

Waitlist is a list, not an actor

They have a waitlist feature. It stores patients, sorts them by date added, and notifies the clinic when a matching slot opens. A staff member then contacts the patient.

There is no automated offer, no hold, and no confirmation flow. In demo they describe this as “keeping the clinic in control”, which is a reasonable framing of a limitation.

Source — Their public product tour, accessed Jul 24 2026

No write-back to the practice management system

Cobaltine reads from the PMS and pushes patient-initiated bookings through a limited integration, but does not write staff-side or system-initiated bookings back. Their documentation describes the integration as “sync” rather than bidirectional.

This is the structural constraint behind the waitlist gap: without write-back they cannot complete a booking on the clinic’s behalf.

Source — Their developer documentation, accessed Jul 24 2026

Reporting is thin

Fill rate is available at the practice level only. Two buyers who evaluated both products told us they could not get a per-location breakdown, which is the number a multi-site operations director reports upward.

Source — Buyer conversations, Merridew and Halloway evaluations, Jun 2026