Take the bill chase off your members, and out of your support queue
Your program does its job. The calls come from everything around it — paying cash, getting an itemized bill, submitting it, and waiting. We built the member-facing layer that handles that work, and you can put your name on it.
What comes off your team
- Requesting itemized bills from providers
- Explaining what's shareable and what isn't
- Answering "where's my reimbursement?" for the fourth time
- Chasing members for missing documentation
- Deadline reminders nobody has time to send
Where your support hours go
None of this is a flaw in your program. It's the gap between a plan that works and members who know how to work it.
- × A provider sends a summary bill when your guidelines call for an itemized one.
- × A member doesn't know whether a visit is shareable, so they call your office instead of finding out.
- × A submission sits open for six weeks and nobody tells the member why.
- × A member decides the reimbursement wasn't worth the effort, and doesn't renew.
Your platform administers the program. This is the part that happens at the member's kitchen table, at ten at night, with a stack of bills.
Three ways to get it in front of your members
Same product underneath. What changes is whose name is on it and where members find it.
Bundle it
We run the app and you resell it as part of your offering. Members download HealthShare and find your program inside it.
- Co-branded, live off an eligibility file
- Nothing for your engineers to build
- Per member per month, billed to you
White-label it
Your brand, your colors, your sending domain. Members sign in to your app, whether that's a companion app beside what you already offer or the only one they use.
- Your name in the app stores or on the web
- Your support address on every message
- Your program's guidelines behind the assistant
Embed the SDK
You already have an app your members use. Put our incident tracking, receipt capture, and assistant inside it through our SDK and API.
- REST API and a mobile SDK
- Single sign-on from your existing member login
- Webhooks for incident and reimbursement state
Plenty of partners bundle one group first and move to white label or embed once the pilot numbers are in. Changing routes later doesn't mean starting over.
What your members get
One place for every medical bill, and an assistant that does the legwork most members never get around to.
An assistant that calls providers
Alice emails providers for itemized bills and follows up when nobody answers. When email stalls, she phones the billing department and hands the member a transcript.
Bills captured from a photo
The member takes a picture. Alice reads the provider, date, and amount off it, files it under the right incident, and flags what's still missing.
Incidents tracked to reimbursement
Every visit, procedure, and trailing bill grouped into one incident with a state the member can read: submitted, waiting on a provider, or shared.
HSA and HRA sync
Members connect an account through Plaid once. Transactions import on their own, and Alice follows up by email on anything still missing a receipt.
Deadlines that don't slip
Submission windows and documentation rules tracked incident by incident, with reminders before the window closes rather than after.
Answers about your program
Alice answers questions against your program's guidelines, in plain language, at whatever hour the member is looking at the bill.
What your team gets
The member layer is what your members see. This is the part you live in.
A console of your own
Your groups, your members, your billing, with role-based access for your staff. You see your book and nothing else, and nobody else sees it either.
We take your file format
Eligibility and EOB feeds over SFTP or API. We normalize on our side instead of asking your team to build to our spec.
Per member per month, billed to you
Invoiced monthly against your eligibility file, with volume tiers. Price it to your groups however you like, or fold it into your rate.
Numbers you can take to your book
We instrument the pilot from day one: support tickets per 100 members, time to reimbursement, and the share of bills that arrive itemized the first time.
Your brand in front
Logo, colors, sending domain, and support address. Members experience your program rather than a vendor's.
Support the way you want it
Keep member support in-house, or let us take the first line under your name and escalate what genuinely needs you. Your call, either way.
How we work with partners
A vendor who competes with you isn't a vendor. Here's where we stand, said out loud before anything gets signed.
We don't compete for your groups
We're a software company, paid by you, per member per month. We don't take plan compensation on your business and we don't approach your clients.
We sit on top of your platform, not in place of it
Your sharing administration stays exactly where it is. We're the member-facing layer above it, and we have no ambition to replace the system that runs your program.
We work to your renewal calendar
Renewals decide whether any of this lands, so we scope backward from your dates rather than forward from our quarter. Tell us when your groups renew and we'll tell you what's realistic.
One pilot before any commitment
Start with a single group, instrumented. If the support numbers don't move, you've found that out cheaply, and we'd rather you know than renew on faith.
How a pilot runs
Four stages, scoped against your renewal dates.
Scope
One call to settle which route fits, what your eligibility and EOB files look like, and which program guidelines your members are on.
Configure
We load your guidelines, brand the app, and stand up your console. If you're embedding, this is where your engineers get keys and docs.
Pilot group live
One group, instrumented from the first day. Members onboard in a live session, and you watch what happens to your ticket volume.
Roll out
The pilot numbers become the case you take to the rest of your book, at whatever pace your renewals allow.
Questions partners ask first
Does this replace our sharing platform?
No, and we'd turn down the work if you asked. Your platform handles membership, guidelines, and the sharing itself. We handle what the member does with a bill before it ever reaches you.
Which programs and ministries do you support?
Guidelines are configuration, not code. Ours run deepest on CHM today because that's where we started, and adding a program means loading its guidelines and testing the assistant against them. That work happens during configuration, and we'll tell you honestly what it takes for yours before you sign anything.
Our members already have an app. Do they need a second one?
That's what the SDK is for. If your app is where your members already live, our workflow can run inside it. If you'd rather keep bill tracking separate, a white-labeled companion app under your brand works too, and it ships faster.
Who supports the member?
Whoever you want. Alice takes the routine questions around the clock either way. Past that, some partners keep support in-house because the member relationship is theirs; others hand us the first line under their name. We'll do it your way.
How is it priced?
Wholesale, per member per month, billed to you, with volume tiers and a monthly minimum. What you charge your groups, or whether you fold it into your rate, is yours to decide. Tell us the size and shape of your book and we'll come back with a number.
What happens to member data?
It stays on HIPAA-compliant infrastructure, separated by partner. We don't market to your members, and we don't use one partner's data to serve another. Alice shares only what a provider needs for billing and logs every message she sends.
What does this take from our engineering team?
For a bundle, an eligibility file. For white label, brand assets and a decision about the app stores. For an embed, an integration against our API and SDK, which is the only route that needs real engineering time on your side.
Are you going to end up competing with us?
No. The company that signs partner agreements sells software and is paid by you, per member per month. It doesn't underwrite or administer sharing memberships, it doesn't take plan compensation on your business, and it doesn't approach your clients.
Churches do come to us directly, and when one does we follow a written rule about who writes the plan. You'll hear that rule from us before you sign, not discover it afterward.
Bring it to your members
Tell us the shape of your book and what your support queue looks like on a bad week. We'll come back with a route, a price, and a pilot plan.
Book a partner callHealth sharing is not insurance. HealthShare Technology Solutions is a software company. We don't underwrite or administer health sharing memberships, and nothing here guarantees payment of any medical bill.