Built for clinic front desks.
We started TakeFax because the people who actually move healthcare paperwork were the people no one was building software for.
Healthcare ops runs on documents that nobody designed: a fax pile, a paper packet, a scanned PDF dropped into a shared folder. The CIOs have a thousand vendors selling them EHR integrations. The office managers — the people who actually sort the pile every morning — have almost nothing.
We're building for those people first. The free tier exists so they can swipe a card, point their fax line at us, and see whether the AI is real before they have to convince anyone above them. The product they get is the one we'd want to use ourselves if we had to triage a hundred faxes before lunch.
We think the fax stack is the wedge. The job is the workflow it triggers — referrals, prior auths, records requests, intake — and we want to own the inbox those workflows live in.
The inbox you'll still use when fax volume drops.
Fax volume is shrinking — slowly, but it's shrinking. TEFCA, QHINs, Direct Messaging, and payer APIs are eating at it from the modern-interop side. We see those channels as the next wave of inbound for the same queue.
- TEFCA + QHINsQualified Health Information Networks under the Trusted Exchange Framework. As they reach our ICP, document exchange flows into the same triage queue, with the same classification, extraction, and assignment.
- Direct Messaging (HISP)Encrypted clinical messages between providers. Same routing, same patient-matching, same one-line action item per message.
- Payer APIsThe CMS Interoperability Rule + FHIR Bulk Data. We'll pull prior-auth status, eligibility, and member data into the workflow alongside whatever the fax line still brings in.
The fax label on the door is temporary. The inbox is not.