Before the call: control who you talk to
Vendors hand you their two happiest logos. Take them, and then ask for one more: a customer at your volume, in your vertical, live for over a year. The pushback you get on that request is itself diligence data. Where possible, find one un-brokered reference yourself (operator communities, LinkedIn, a vendor's public case studies aged eighteen months), because the reference the vendor did not choose is worth two they did.
Thirty minutes is enough if you skip the tour. Send three questions ahead so the reference can pull numbers, and spend the call on the follow-ups, where the real answers live.
Economics: did the price survive contact with reality?
You are not asking references to disclose their rates; you are asking whether the pricing they signed is the pricing they live with. Drift between the two is the single most useful thing a reference call can surface, and references will discuss drift long before they will discuss numbers.
- 1. Did your all-in cost per patient land where the sales process led you to expect, and if not, which line moved?
- 2. What costs showed up that were not on the proposal?
- 3. Have your rates changed since signing, and how did that conversation go?
- 4. If you were negotiating again, what would you insist on in writing?
Operations: ask about the worst week
Every platform performs in the demo and in month one. The information is in the exceptions: the escalation that stalled, the launch-week surge, the holiday coverage, the integration that broke. Ask for stories, not ratings; a reference who cannot produce a worst week has not been live long enough to be a reference.
- 5. Tell me about your worst week on the platform. What broke, and what did the vendor do?
- 6. When a patient issue escalates, how long until a human who can fix it owns it?
- 7. What is visit turnaround actually like at your volume, including nights and weekends?
- 8. What do your patients complain about most, and what does the vendor do with those complaints?
- 9. Which promised feature or integration took longest to become real?
Incidents and compliance: the questions nobody asks
Regulatory posture and incident handling are where platform quality is proven, and references have seen it where prospects cannot. You are listening for whether the vendor communicates early and specifically when something goes wrong, because in this category something eventually does: a product's status moves, a state rule changes, a certification review asks hard questions.
- 10. Has a regulatory or supply change (a product status, a state rule) hit your program, and how did the vendor handle it?
- 11. Were you notified of any security or data incident, and how was that communication?
- 12. Did your storefront pass certification review as built, or was there rework, and who did it?
- 13. Has anything ever made you check what your exit terms actually say?
Results and the exit question
Close with growth and the leaving question. Growth answers tell you whether the platform's retention and conversion machinery is real at a volume like yours; models are the vendor's job, but lived retention curves belong to references. And the exit question is the character question: ask everyone, including the happy references, because the answer describes the vendor's leverage over you.
After the calls, score the divergence: everywhere a reference's answer differed from the vendor's answer to the same question is either a follow-up or a finding. Two references and a diligence checklist beat any review site this category currently has.
- 14. What does patient retention actually look like for you month over month?
- 15. What moved the needle most on conversion, and did the platform or your team move it?
- 16. Do you know anyone who left this platform, and do you know why?
- 17. If you had to migrate off tomorrow, do you know what you would receive and how long it would take?
- 18. Knowing everything you know, would you sign again, and what would you change?
The tell that ends diligence early, in a good way: a reference who volunteers a real failure AND describes exactly how the vendor fixed it. Platforms that create that kind of reference are the ones that treat problems as their job. That is the answer you are actually on the call to find.
The same standard, pointed at us
Run this script against EmbedCare too: ask us for operator references, the worst-week stories, the certification rework question, the exit terms. We publish the model openly (operated stack, owned pharmacy supply, flat product rates fixed in writing) precisely so reference calls can be about whether we do what the agreement says. Book a demo and ask for references before the pitch if that is your style; it is a reasonable style.
Frequently asked
- What should I ask on a telehealth platform reference call?
- Four clusters: economics (did all-in cost per patient land as sold, what showed up uninvited), operations (the worst week, escalation reality, turnaround at volume), incidents (regulatory changes, security communication, certification rework), and results plus exit (lived retention, would-you-sign-again, what leaving would look like). Specific stories beat ratings; ask for the worst week, not the average one.
- How many reference calls should I do before choosing a platform?
- Two per finalist minimum: one vendor-provided at your approximate volume and vertical, and one you find yourself through operator communities or aged case studies. The un-brokered reference is the valuable one; treat a vendor's refusal to connect you with a customer at your scale as diligence data in itself.
- Are there review sites for white-label telehealth platforms?
- Coverage on the major B2B review platforms is thin across this category as of September 2026, which is why reference calls carry most of the review function. Supplement them with public records where they exist (regulatory actions, litigation, incident disclosures) and with each vendor's certification status, which is independently checkable.
- What questions do references usually avoid answering?
- Exact rates (respect that; ask about drift from expectations instead), anything their agreement's confidentiality covers, and criticism of a vendor they still depend on. Listen for routing: a reference who redirects every operational question to praise of the account manager is describing a relationship, not a platform. Follow up where the enthusiasm gets vague.
Want pricing for your program, and the Rx menu that goes with this?
The partner overview in one email; a human follows up with pricing scoped to your program.