The fax + Direct bridge

TakeFax ingests every inbound channel into a single, source-agnostic triage queue. Today that's fax; the same pipeline accepts Direct / HISP messages with no change to your inbox or workflows.

How it works

Every inbound message — a fax from Telnyx/Documo, or a Direct message from a HISP — is normalized to one internal shape (NormalizedInbound), routed to a workspace by its destination address, and triaged identically. The inbox never has to ask which channel a document came from.

Triage branches on what the document actually is:

• Fax → a PDF → read by a vision model for classification + extraction.
• Direct → typically a C-CDA → patient, DOB, MRN, and sender are pulled deterministically from the structured XML, then the AI adds classification, urgency, and a summary.

So structured Direct data stays exact, while messy fax scans still get the full AI read — both landing as the same record type in the same searchable queue.

Routing

A workspace can be reached by a fax number or a Direct address (e.g. clinic@direct.takefax.com). Both are configured on the Setup page and both resolve to the same inbox.

Activating Direct

The Direct channel ships as a documented stub — the seam is built, but it isn't wired to a HISP yet. Why: provider-directory data shows Direct endpoints are still rare and hard to discover, while fax remains the universal address. So we built the bridge and left the second lane ready.

To turn it on:

1. Contract a HISP partner (e.g. DataMotion, Kno2, MaxMD) and complete your organization's identity proofing.
2. Map the HISP's delivery webhook to the normalized Direct shape and verify its signature on /api/direct/inbound.
3. Provision a per-tenant Direct address and set it on the workspace.

Nothing downstream changes — the same routing, extraction, and assignment light up for Direct the moment messages arrive.