The front desk owns the follow-up
They are checking in patients, answering the phone and arguing with insurance. Follow-up happens when the day allows it. The day rarely allows it.
Greenway DeveloperApproved API access
Healthcare automation that talks to your EHR.
Your practice management system holds the entire patient relationship — the visits, the no-shows, the treatment plans nobody scheduled. Cadre Crew builds on the Greenway Health developer platform, so the follow-up finally runs off that record instead of sitting next to it.
GoHighLevel AI underneath. Fixed install price, quoted before we build. No hourly billing, no open-ended retainer.
- Greenway developer API access
- Appointments read from your live schedule
- Reviews, recall and reactivation in motion
Where the money leaks
Your EHR records the visit. It never follows up.
A practice can run a perfect chart and a dead pipeline at the same time. The patient who no-showed in March, the treatment plan that was quoted and never booked, the recall that lived on a sticky note — all of it is already in the system. None of it is in motion.
Marketing owns a list
The ad platform knows somebody clicked. It has no idea that lead became a patient, or that the patient stopped coming in eight months ago.
Nobody owns the gap
No system watches both sides. So the practice pays for the patient twice: once for the ad, and again for the visit that never came back.
The record was never the problem. Nothing could act on it.
How it is wired
Three systems. One connection we own and maintain.
We sit in the middle and do the unglamorous work: authentication, field mapping, error handling and monitoring. Nobody on your team becomes an integration engineer.
Greenway Health
System of record
Intergy and Prime Suite hold the patients, the providers, the appointments and the schedule. That stays the source of truth. We never fork it and we never ask you to migrate it.
The Cadre integration layer
Where we build
Greenway’s FHIR API for reading clinical and scheduling data, plus the proprietary API behind the developer program for the practice-management actions a workflow has to take. Every connection is scoped to the workflow and nothing more.
GoHighLevel
Where the work happens
Workflows, AI voice, SMS, email, review requests, pipelines and reporting. This is the engine that sends, waits, decides and escalates to a person when it should.
Straight answer on writes. Greenway’s FHIR surface is read-first; actions that change a schedule or a record need the proprietary API and the correct access level. We confirm what your version exposes in week one, before you commit to a build. If a workflow needs a write Greenway does not allow, we say so up front.
The build list
The workflows we build first.
Every one of these reads from your EHR and lands in a conversation. Start with two, prove the numbers, then stack the rest.
Review generation
A completed visit triggers the request. Happy patients get a direct review link. Unhappy ones land with your practice manager before anything reaches Google.
No-show recovery
A missed appointment becomes a text sequence and a live call the same day, and the open slot gets filled from the waitlist instead of written off.
Patient reactivation
Lapsed patients pulled straight from the record — six, twelve, eighteen months out — into a campaign with the offer and the provider they actually saw.
Recall and recare
Hygiene, annuals and follow-ups that are due. The sequence runs on the schedule the chart says, not the one somebody remembered.
Missed-call text back, plus AI voice
A call that rings out gets a text in seconds and a callback that books. Every inquiry gets answered, including the ones that come in after close.
Intake before the visit
Forms, history and insurance captured days ahead, so the first ten minutes of the appointment belong to the patient instead of the clipboard.
Unscheduled treatment plans
The plan that was quoted and never booked gets a follow-up sequence with financing options and a real slot to pick from.
Referrals and new-patient speed to lead
Web forms, phone calls, texts and DMs answered in seconds, screened, and booked onto the right provider’s calendar.
Ask us about the rest: benefit reminders, post-op check-ins, membership and package renewals, referral-source tracking, and per-location reporting for groups on multiple schedules.
Who this fits
Practices that already run on Greenway, and are done paying for leads they cannot convert.
The offer is medical automation with real teeth: your record, your schedule, your patients, driven by AI that never forgets a follow-up.
- Med spas and aesthetics
- Dental and orthodontics
- Dermatology
- Orthopedics and chiropractic
- Primary care and specialty clinics
- Multi-location groups
Install path
Four weeks from access to live, on one location first.
We do not switch on a whole group at once. We prove the workflow on one provider, one schedule and real patients, then roll it out.
-
Day 0
Access and audit
Developer credentials, a read-only scope, and an honest look at where the leaks actually are in your schedule and your record.
-
Week 1
Map the record
Which fields, which appointment statuses, which visit types fire which workflow. You sign off on the map before we write anything.
-
Week 2
Build
The Greenway connection, the GoHighLevel workflows, the AI voice agent, the offers, the review routing and the reporting.
-
Week 3
Test on one location
One provider, real patients. We measure booked appointments and recovered revenue, not messages sent.
-
Week 4
Live and managed
We monitor it, fix what breaks and tune it every month. You get the numbers, not a status meeting.
What we do not do: hand over a Zapier template and a login. No DIY glue, no hourly invoices, no “it worked in testing.” If it stops working at 7 a.m. on a Tuesday, we are the ones who fix it.
Questions, answered
What practice owners ask us first.
What does being on the Greenway developer program actually give you?
Approved access to Greenway’s developer platform and the APIs behind it, which is what lets us read your practice data and act on it inside a workflow. Without that access, every agency on the internet is guessing at your schedule. With it, our workflows run on the real record.
Do we have to replace our EHR or our practice management system?
No. Greenway stays exactly where it is, doing what it does. We add the automation layer around it. Your staff keeps the same screens they use today.
Which Greenway products does this work with?
Intergy and Prime Suite are the platforms we build against. What a specific workflow can read or write depends on your version, your modules and the access level Greenway grants. We confirm that in week one and put it in writing before anyone signs a build.
How do you handle patient data and privacy?
The chart stays in the chart. Our layer works with identifiers, appointment status and visit context, not clinical notes, and each connection is scoped to the minimum a workflow needs. Access is granted per practice, with the permissions Greenway and your team control. Anything that touches protected health information runs under an agreement signed before the connection goes live.
Our practice is not on Greenway. Can you still help?
Yes, on the GoHighLevel side — reviews, missed-call text back, reactivation, recall and AI voice all run without a Greenway connection. What changes is the depth: without API access the workflows work from what you can export or feed in, not from the live record. Tell us your system on the call and we will tell you honestly which half of this you can have.
How fast can this be live?
Roughly four weeks from access to a live workflow on one location, assuming Greenway credentials and a decision maker on the map. SMS registration can add a few days; the other channels run in the meantime.
What does it cost?
There is a fixed install price for the build and a managed monthly for running it. The install is quoted up front, before work starts, and it does not move — scope depends on your Greenway version, the number of workflows and the number of locations. No hourly billing, ever.
Who actually does the work?
Cadre Crew, a Florida-based operations company running since 2012. You get a named build lead, and David Howard, the founder, is on the strategy call. No account-manager relay.
We have several locations on different schedules. Does that break it?
No. Each location gets its own number, its own schedule rules and its own reporting, with one view on top. Most groups start with one location and add the rest once the first set of numbers is in.
Book a strategy call
See this mapped to your practice.
Bring your Greenway version and where the follow-up breaks today. We will show you which workflows your access level supports, what we would build first, and what it costs before you commit to anything.
- A 30-minute call with David Howard, founder of Cadre Crew
- What your Greenway version exposes, confirmed in plain English
- The first two workflows we would build, and the fixed install price
Every patient in motion.