This Is What We Built & Why
84 reasons we built what we built.
Every application, integration, and leverage in the FxMedSupport suite was born from a specific moment of paying attention to what an independent functional or integrative practice actually needed. This is the complete record — every single one, with the why behind it.
84
Production
Applications
10yrs
Inside the Cerbo
Ecosystem
100s
Of Practices
Running Daily
4
Tiers of
Software Power
Why this page exists
No roadmap meetings.
Just real moments of listening.
FxMedSupport is the official Cerbo integration and development partner. For ten years we’ve been building applications, integrations, and leverages on top of Cerbo — not from a venture-backed product strategy, but from a real moment of noticing what a practice needed and getting excited to build the answer.
This page is the complete record. Every one of the 84 applications in our suite, organized by tier, with the origin story behind it — the practice that inspired it, the workflow that demanded it, the conversation that sparked it.
Cerbo is the brain. We are the nervous system. Every application below extends, optimizes, integrates, automates, or leverages what Cerbo already does brilliantly. Each card has a small play button — listen to that origin story on its own. Or hit the master button up top to hear the entire page.
Tier 01 · The Foundation
Portal Basic
Twenty-one applications that form the foundation of every FxMedSupport practice. These are the tools we believe every Cerbo practice deserves access to from day one.
Cerbo Crypto (ERC-20 + Bitcoin)
Why we built it
Cash-pay practices sell $10K–$50K packages. Credit card fees on those cost thousands. We built an ERC-20 system (USDC, USDT, Ethereum) and a Bitcoin payment system. Funds flow direct to the provider’s wallet. Near-zero fees. Smart contracts enable subscription billing.
Cerbo Tag Info System
Why we built it
Inside the Automation System, you sometimes need to know what tag ID or appointment ID you’re working with. We built a tool to see that tag information. Evolved into Bulk Tag Create — instead of creating tags one at a time in Cerbo, create them all at once.
Outlook Calendar Bidirectional
Why we built it
Bidirectional calendar sync should be in every enterprise EHR by default. Practices live in Outlook for the rest of their professional life. Whatever you put in Outlook flows into Cerbo. Whatever’s in Cerbo appears in Outlook. Calendar trust is business trust.
Admin Desktop Login
Why we built it
Our Phone System originally ran inside a Cerbo browser tab — close the tab, lose the connection. We built a standalone FxMedSupport browser tab. With full browser landscape, our Automation System and Email Templates became deeper, richer, more powerful.
Secure Note
Why we built it
Concierge practices store sensitive patient data — sometimes including credit card numbers — in plain sticky notes. After a real security incident at a client practice, we built password-encrypted, logged, secure storage for the realities of concierge medicine.
Time Card
Why we built it
Your staff is already logged into Cerbo all day. Cerbo’s admin user management already exists. We built a time card that lives where your staff already works. Tracks actual activity time. Auto-sends payroll data to office manager and bookkeeper every two weeks.
Loyalty Program
Why we built it
A client came to us with a specific idea: reward patient loyalty and engagement. Assigns points based on dollars spent or services rendered, tracks current and lifetime points, identifies most-loyal patients. Still evolving with practice input.
Automator Basic
Why we built it
Every mouse click in Cerbo carries metadata: who clicked, what provider, what patient. Event-based triggers + filters + intimate if/then logic. Chained automations that talk to patients based on who they are, not what they did 90 days ago. The firing system of the nervous system.
After Hours Auto Reply
Why we built it
Providers work late into the night on charts. A portal message arrives — they stop everything to respond, breaking deep flow. We built an auto-reply that holds the container of support on the provider’s behalf. The patient feels heard. The provider stays in flow.
Portal Kanban Board
Why we built it
A Trello-style project visualization tool inside FxMedSupport — cards, projects, notes, user assignments. MVP status, evolving based on how practices actually use it. Released early because real practices teach us what features matter.
Portal Auto Reply (Out-of-Office)
Why we built it
A practice wanted to spend July 4th with their family without the portal becoming a black hole. We built a configurable, scheduled out-of-office system that keeps the patient experience warm even when the practice is closed. Your portal should always feel human.
Auto Encounter
Why we built it
One of the very first applications we ever built. The observation: if you schedule an appointment, you’ll need an encounter to document it. Cerbo has since added native Auto Encounter — we are honored it began with us. We’ve since moved upstream to Auto Chart Prep.
Google Calendar Bidirectional
Why we built it
Practices live in Google Calendar for the rest of their professional life. Cerbo holds patient appointments. We built bidirectional sync so they finally talk. Whatever you put in Google Calendar flows into Cerbo. Whatever’s in Cerbo appears in Google. Calendar trust is business trust.
Happy Birthday Notification
Why we built it
A provider in the Cerbo Users community asked: “Can you build a system that sends my patients a birthday message?” We got excited and built it over the weekend. The patient feels remembered. The container of support is held even on days when nothing clinical is happening.
Re-beautify
Why we built it
Cerbo’s Wellness Plan feature is phenomenal. In earlier days, the plan didn’t hold form — you’d have to redo the entire plan to make small edits. We built Re-beautify so you can open an old wellness plan, edit, save, and have your updated plan in seconds. Saves 3–5 minutes per edit.
Encounter Beautify (Sunsetting)
Why we built it
For ten years, Cerbo encounters were plain text. We built rich-text beautification. As of May 2026, Cerbo now offers native rich text editing inside their encounters. Encounter Beautify is being sunset. The platform we love just got better.
Patient Portal Auto Invite
Why we built it
Creating a new patient required three extra mouse clicks to send the portal invite. We thought: why? Now when a patient is created, the invite sends automatically — and the system tracks activation, sending follow-up reminders if needed. Three clicks per patient eliminated.
Bulk Patient Status Edit
Why we built it
Practices sometimes need to bulk inactivate a subset of patients — like everyone who hasn’t visited in three years. Instead of doing it one at a time, select by parameters and bulk adjust status. Originally part of Automator, released as a standalone tool.
Bulk Tag Edit
Why we built it
Part of the Tag Info System. Instead of creating tags one at a time in Cerbo (one per form, one per protocol, one per appointment type), our system lets you create tags in bulk. Massive time-saver for any practice running multiple forms, protocols, or campaigns.
Portal App Basic
Why we built it
We wanted to give basic-tier FxMedSupport practices the ability to offer their patients a mobile app experience. A version of the iOS and Android application with the essentials — secure messaging, appointments, records — for every practice’s patients.
Bulk Email System
Why we built it
A water pipe broke in an IV clinic. The team needed to email only patients scheduled that week. Cerbo’s answer: “Do it one at a time.” So we built it. True bulk email — sends individually to each patient (not a BCC blast). Evolved into beautiful templates, scheduling, newsletters. Replaces ActiveCampaign.
Tier 02 · The Expansion
Portal Pro
Twenty-one applications that take a practice from foundational to fluid. The tools that turn FxMedSupport into a true nervous system around Cerbo.
Provider Template Charting
Why we built it
From our founder’s firefighter and paramedic days. Paramedic charting on a tablet was tap-a-bubble, multi-select, drop-down, narrative — built for speed under pressure. We brought that pattern to functional medicine. Providers tap through pre-built structured templates and end up with a signed document in proper order-type format.
Tags Info & Bulk Create
Why we built it
The Pro-tier evolution of the Tag Info System — not just viewing tag metadata, but creating tags in bulk. If you want a tag for every form, every protocol, every appointment type, you don’t have to do it one at a time in Cerbo.
Patient Transaction Association
Why we built it
Built so we could put it inside the Automation System. When a patient actually purchases something (not just gets it recommended), we can trigger an automation based on that real purchase. Behavior-based automation, not recommendation-based.
PDF Annotate System
Why we built it
Providers work with PDFs constantly. Old workflow: download, open in third-party editor, annotate, upload back. Five or six steps for what should be one click. Our system opens the PDF inside Cerbo via a virtual machine. Annotate, save, it reappears in the chart. One click in. One click out.
Provider Autoblock Scheduling
Why we built it
Scheduling one appointment triggers a cascade — prep time before, documentation after, sometimes a team member blocked for part of it. Pre-blocks, post-blocks, cross-provider blocks, during-appointment blocks — all automatic. The schedule finally understands how the practice actually runs.
Program Management System
Why we built it
A client runs 1–2 week long programs — patients fly in, follow a Mon/Tue/Wed/Thu/Fri schedule. When a patient is added to the trigger appointment, they’re automatically added to the entire weekly schedule. One enrollment triggers a full week of scheduled appointments.
Multi-State License
Why we built it
Many providers are licensed across multiple states via telemedicine. Supervising physician logic via association table. When an order is created, the system pulls the right license for the patient’s state — and the right supervising physician — automatically. Multi-state practice becomes effortless inside Cerbo.
Medication Refill Notification
Why we built it
Compounding pharmacies don’t reach out to patients for refills. The medication record lives in Cerbo, the patient relationship lives with the practice. We built a refill conversation the practice owns directly. When patient is ~10 days from running out: Yes refill. No I’m good. Remind me in X days.
Appointment Form Notification
Why we built it
One of the most powerful applications we’ve ever built. Different appointments need different forms. Some are single-entry (family history). Some are multi-entry (MSQ). Plus version detection. Cadence: 14 days out, 10, 5, 2 — then auto-task for admin. Held container of support from scheduling to appointment.
Mobile App Custom Branding
Why we built it
Portal Messenger Pro works for the 85% of practices. For the 15% that want patients downloading their own custom-branded app from the App Store, we offer fully custom mobile app development with deep Cerbo integration. The 85/15 philosophy applied to mobile.
Auto Chart Prep
Why we built it
After Cerbo adopted Auto Encounter natively, we moved upstream. Using Cerbo’s chart parts plus proprietary FxMedSupport technology, the system auto-prepares the chart in advance of the appointment. Admin walks in 15 minutes before, adds 15% personal touch, chart is 100% ready when provider arrives.
Newsletter Application
Why we built it
Once Bulk Email worked, we asked: “Why don’t we let practices cancel their ActiveCampaign subscriptions?” ActiveCampaign’s least expensive plan costs more than our most expensive plan. Newsletter templates, scheduling, segmentation — replaces an expensive external platform entirely.
MessengerPro Admin Login
Why we built it
The Pro-tier version of Admin Desktop Login. Same architecture: standalone independent browser experience so FxMedSupport tools (phone system, automations, email templates) can run in a deeper, richer environment than a cramped Cerbo tab allows.
Portal Scheduler (No-Login)
Why we built it
Some patients won’t log in until they see something worth logging in for. We used “reverse psychology” on the Cerbo architecture — the patient sees available appointments first, then engages with security to book. Drop-off plummets. Provider’s schedule integrity stays fully protected.
Mobile Form Builder
Why we built it
Cerbo’s patient forms aren’t accessible via API, but Cerbo’s questionnaire system is fantastic. We leveraged it. Build forms that load in the mobile app. Forms that connect to vitals, forms that trigger from Portal Scheduler, forms that pop up based on patient evolution.
Patient Re-Engagement
Why we built it
Operations managers ran reports asking who’s still active — and more importantly, who are we losing? Now: 90 days = warm check-in. 180 days = stronger nudge. 365 days = inactive with dignity. Plus protocol-specific attrition detection for difficult protocols.
Intuitive Messaging
Why we built it
Closed-loop communication — from emergency medicine — brought to patient messaging. The practice sends a message with tap-to-answer options. Patient picks one. That selection triggers a workflow. Choose your own adventure for patient conversations.
Portal Automator Pro
Why we built it
The full visual automator. One of the most powerful tools in the entire Cerbo ecosystem. Event triggers + filters + intimate if/then logic + chained automations + connections to GoHighLevel, HubSpot, Heidi. Cerbo is the brain. This is the firing system.
Med & Supplement Reconciliation
Why we built it
Providers paint a 24-month vision of who the patient could become. The disconnect: provider knows what was recommended, not what the patient is actually doing. Built inside Portal Messenger Pro. Yes, taking it. No, stopped. Yes but different. Patient’s actual reality flows into the Cerbo chart.
Open Orders Notification
Why we built it
Office managers do enormous, careful, invisible work checking orders, labs, follow-ups. We built a system to give them their afternoons back. If a lab order has been open 6–8 weeks, send a gentle reminder. Conditional logic for upcoming appointments. Always graceful.
Portal Messenger Pro
Why we built it
In 2026, every meaningful business interaction lives on the phone. The flagship iOS/Android app for patients and admins. Messaging, records, results, HealthKit integration, payments, mobile-native forms. The brilliant moment: realizing HealthKit access meant continuous biometric data into Cerbo.
Tier 03 · The Ecosystem
Portal Elite
Twenty-eight integrations and applications that turn FxMedSupport into a true ecosystem — connecting Cerbo to the rest of the world’s tools.
Patient Portal Health Insight
Why we built it
Early beta. Visual dashboard showing the patient as a whole system — medications, supplements, and alternative treatment plans overlaid on the longitudinal history. The provider can finally see if the patient is moving in the direction the protocol intended.
Portal Cerbo Visual Reporting System (In Beta)
Why we built it
Cerbo’s reporting engine has always been incredible — powerful, accurate, comprehensive. What was missing was the dimension and the distribution. A fully visual, interactive dashboard built directly on top of Cerbo’s reports — eight lenses (Clinical, Patients, Revenue, Provider, Appointments, Tasks, System, Inventory) plus Auto Reporting Email that delivers beautiful PDFs to the right inboxes on schedule. One unified picture. Every team aligned.
Heidi Health Scribe
Why we built it
An AI medical scribe integration for Cerbo. Bidirectional integration — practices using Heidi for AI-powered documentation pipe dictated notes directly into Cerbo charts. Built because practices wanted Heidi’s AI without losing Cerbo as source of truth.
Google Gmail Inbound
Why we built it
A client used Google for prospective patients with a sales team. They wanted: detect every inbound email. If associated with existing patient, do nothing. If new, distribute to sales team. A distributive Gmail sales-list application.
SpruceHealth
Why we built it
One of the cleanest examples of our thesis. New patient created in Cerbo → automatically created in Spruce. Demographics, phone, contact info. No double entry. Patient receives text communication from day one. One source of truth, multiple downstream systems.
Calendly + Cerbo
Why we built it
A client said: “I use Calendly for prospects. I love it — but I need it to talk to Cerbo.” Bidirectional: Calendly events flow to Cerbo (create patient + appointment), Cerbo blocks flow to Calendly (prevent double-booking). The provider keeps their favorite tool.
GoHighLevel Tunnel
Why we built it
GoHighLevel’s communication module surfaces directly inside FxMedSupport (desktop and admin mobile). Reply through us, our system replies through GoHighLevel. Visual reference without leaving the workflow. Built for high-volume practices using GHL for their pipeline.
Virtual Administration (VAA)
Why we built it
Not a tool — a service. We teach practices to interview and hire virtual assistants directly — pay the VA the full rate, find brilliant, ethical, hardworking people internationally. Mutual respect. Loyal relationships. No agency taking margin.
QuickBooks Online
Why we built it
Practices pay bookkeepers to manually transfer Cerbo transactions to QuickBooks — that’s data shuttling, not bookkeeping. Our integration syncs every Cerbo transaction to QuickBooks in real-time. Pay bookkeepers to manage your books, not to transfer information.
Zoho Books
Why we built it
Same philosophy as QuickBooks Online: a practice came to us using Zoho Books and didn’t want to leave it. Real-time transaction sync from Cerbo to Zoho Books. Stop paying bookkeepers to be the integration.
Zoho CRM
Why we built it
A client used Zoho CRM for lead management. Bidirectional sync between Cerbo and Zoho CRM — new leads convert to patients automatically, patient updates flow back to the CRM. System-agnostic, solution-oriented.
GoHighLevel CRM
Why we built it
A nationally known functional medicine leader was getting hundreds of inbound requests. Staff was manually transferring each “yes I want to be a patient” into Cerbo. We automated it — then evolved to true bidirectional integration.
PayRoc Payment Gateway
Why we built it
Another alternative payment gateway following the same architecture as Authorize.Net and Fluid/KiboPay. Practices choose the processor that fits their needs. We’re agnostic on the financial layer — the goal is keeping billing inside Cerbo.
TypeForm
Why we built it
A provider used TypeForm to collect prospect form data. “If they become a patient, can we automatically pull all those forms into their chart?” Yes. Bidirectional — new TypeForm submissions later flow into the chart automatically too.
JotForm
Why we built it
Same philosophy as TypeForm, different form platform. Practice uses JotForm → forms automatically inject into Cerbo chart on patient conversion → new submissions flow continuously. Three different platforms (TypeForm, JotForm, Gravity) solving the same problem.
Gravity Forms
Why we built it
For practices on WordPress using Gravity Forms. Same logic: form submissions sync to Cerbo on patient conversion. New submissions flow continuously. Built per segment because different practices live in different ecosystems.
Thinkific Course Platform
Why we built it
A client used Thinkific for online courses. “When something happens at Thinkific, they should become a patient in Cerbo with appropriate invites.” Bidirectional: add a tag in Cerbo and the patient gets invited to a Thinkific course automatically.
Portal Phone System
Why we built it
Providers calling with *67 (blocked) so patients don’t answer. Plus practices paying $300–500/month for phone systems. We built a fully integrated system across Cerbo + mobile + VoIP via Twilio. Calls come from the practice’s own number, so patients recognize and answer. Loss leader by design.
QualityMetric (Sunsetted)
Why we built it
An early patient health assessment integration. Deprecated and sunsetted. The FxMedSupport library evolves — some apps grow, some get replaced, some run their course. Honesty about the lifecycle matters.
Zoom Video
Why we built it
Built in 2017 — before telemedicine was widespread. Our second integration into Cerbo. Saves admin staff 3–5 minutes per appointment of creating links, sharing, charting. We leverage your existing Zoom accounts — no upcharge, multiple accounts supported.
Acuity Scheduling
Why we built it
Same as Calendly: “I love Acuity. Don’t want to leave it. Need bidirectional sync with Cerbo.” Patient info flows from Acuity to Cerbo. Cerbo calendar blocks prevent double-booking in Acuity. Schedule integrity preserved across both platforms.
HubSpot Bidirectional
Why we built it
A client used HubSpot as their CRM. Bidirectional integration — leads convert to patients automatically, patient updates flow back. System-agnostic. Whatever you love, we’ll integrate with.
MindBody Bidirectional
Why we built it
A huge enterprise client uses MindBody — the world’s best online scheduling for wellness businesses. They needed MindBody appointments in Cerbo and vice versa. Built for schedule integrity at enterprise scale.
Texting SMS-Reply
Why we built it
FxMedSupport-managed SMS texting (with our resource layer). We recommend Twilio External Account instead — practices own their Twilio account at raw rates. But for fully managed: this is the option.
Cerbo Robo Caller
Why we built it
Built while exploring “what’s possible.” Trigger automated calls that read a script to patients — bulk or via Automation. Practices use it for reminders, holiday closures, urgent broadcasts. One-sided but powerful at scale.
E-Commerce Add-On
Why we built it
The parent category for WooCommerce, Shopify, and BigCommerce integrations. Seamlessly integrate a patient’s supplement shopping cart with the most popular e-commerce platforms. Conversion rates rise dramatically.
Twilio Integration
Why we built it
Zoom charges $9.99/user/month for phone. RingCentral charges $14.99. Twilio charges $1.15. Connect to your own Twilio account, pay Twilio directly. Loss leader for us. We win because you’re in our ecosystem. 90% cost reduction.
Portal Messaging
Why we built it
The unified messaging layer that connects all FxMedSupport communication tools — SMS, email, portal, mobile push — into one coordinated communication experience. Practices stop juggling inboxes. Everything routes through one stream.
Tier 04 · The Deep Stack
Portal Enterprise
Fourteen integrations and applications for practices that have outgrown ordinary — pharmacy integrations, custom apps, advanced payment infrastructure, e-commerce platforms.
NMI Payment Gateway
Why we built it
An enterprise client receives hundreds of new patients per day. NMI lets them intelligently route credit card charges across multiple processors based on metadata. When volume jumps from $30K to $150K/month, processors flag it as risky. NMI distributes load.
Empower Pharmacy
Why we built it
Part of the LifeFile Compounding Pharmacy family. Each compounding pharmacy requires its own integration — different franchises, different rules. Providers stay in Cerbo, prescriptions create in draft mode inside Empower’s system, pharmacy completes verification.
Fluid (KiboPay) Gateway
Why we built it
A client wanted to pass the 3.3% credit card surcharge to their patients. Cerbo didn’t have a way. They wanted FluidPay/KiboPay. We built it. The payment processor handles all compliance logic — state laws, card network rules. We send the encrypted token.
Square Online Payments
Why we built it
Same philosophy as Authorize.Net. A client couldn’t use one of Cerbo’s native payment options, wanted Square, so we built it. Practices stay inside Cerbo for billing, no matter which processor they prefer.
Custom Portal Application
Why we built it
For the 15% of practices that want fully custom mobile apps — completely custom iOS/Android applications with specific features, unique workflows, and deep Cerbo integration. Built per-project for practices that want a real branded app in the App Store.
WooCommerce Point of Sale
Why we built it
A client used WooCommerce POS for in-person sales at their clinic. We built the application to handle their specific POS workflow. If you use WooCommerce POS, this is the integration for you. Built per-client need.
LifeFile Compounding Pharmacy
Why we built it
The parent organization for all FxMedSupport compounding pharmacy integrations. Each pharmacy is its own integration — different franchises, different rules. Providers stay in Cerbo, prescriptions draft inside the pharmacy system, pharmacy completes verification.
Clover Payment System
Why we built it
Same story as Authorize.Net, Fluid, Square. A provider was locked out of Cerbo’s native processors and needed a way back in. They can charge patients inside Cerbo, with payment management inside the mobile app too. Universal pattern across our payment library.
Authorize.Net Payment Gateway
Why we built it
The origin payment integration. Started in NutrimentRx days (our predecessor as a supplement company). Practices started getting locked out of Cerbo’s native processors due to “high risk” designations. We gave them a way back in. Evolution: encrypted token storage now enables mobile app payments too.
Twilio External Account
Why we built it
The recommended Twilio configuration. Practice owns their own Twilio account directly. Pays Twilio rates ($1.15/user/month). No FxMedSupport markup. No resource charges. Full data ownership. The lowest cost path with maximum control.
SendGrid
Why we built it
Built because we needed email infrastructure for our own operations — then made it available to clients. Practices own their SendGrid accounts. Default is Amazon AWS SES (most don’t need deep analytics). For those who do: SendGrid or Twilio email service.
WooCommerce Cerbo Pro
Why we built it
The very first application we ever built. The question: how can we passively listen to what the provider recommends and automatically place those supplements in the patient’s shopping cart? Patient sees what was recommended, taps checkout. Application number one. Everything else evolved from this.
BigCommerce Cerbo Pro
Why we built it
Same architecture as WooCommerce Cerbo Pro. A client came to us using BigCommerce. We built the same passive-listen / auto-populate-cart logic on a different platform. Three platforms (WooCommerce, BigCommerce, Shopify) solving the same problem for different practice segments.
Shopify Cerbo Pro
Why we built it
The Shopify implementation of the WooCommerce Cerbo Pro pattern. Passive listening to provider recommendations. Auto-population of patient shopping carts. One-click checkout through the patient’s normal store experience. 95% of the time supplements — works for any recommended product.
Software built with you.
Not sold to you.
Eighty-four applications. Ten years of building. Hundreds of practices running daily. And we’re not done — every conversation with a practice teaches us what to build next.