New Signed fax intake — referrals land structured, automatically Flat pricing from $150/mo — unlimited providers BAA included at every tier 68% of leaked referrals die at intake — ours don't Month-to-month — no contract, no setup fee

Home / Features

Built for the receiving end

Every referral in one queue, every status accounted for.

Faxes, portals and Direct messages land in the same worklist. From there a referral can only move through states that make sense — and the referrer finds out what happened without needing an account.

Start free See pricing →

Signed fax intake

A fax arrives. A structured referral appears.

Inbound faxes come in through an HMAC-signed API, so the request is proven to come from your fax vendor rather than from anyone who found the URL. The PDF is checked for real PDF magic bytes and size before anything touches it, and an unknown fax number creates the referring provider automatically instead of dropping the referral.

  • HMAC-signed endpoint with a replay window — not an open URL
  • PDF magic-byte and size validation before storage
  • Referring provider auto-created from the sending fax number
  • Vendor-agnostic — the adapter is a payload translator, not a rebuild

One queue, every source

Stop logging into four portals.

Portal sources are polled every fifteen minutes and land in the same worklist as your faxes. Credentials are encrypted and never echoed back, results are matched by external reference so nothing arrives twice, and a portal that breaks is quarantined on its own rather than stalling every other source.

  • Fax, portal and Direct sources in a single worklist
  • Polled every 15 minutes, idempotent by external reference
  • Credentials encrypted at rest and never displayed again
  • A broken portal is quarantined, not allowed to stall the rest

Enforced workflow

A referral cannot skip a step.

Every referral moves through five states in order. The system refuses illegal jumps rather than trusting everyone to remember the process, and terminal states are frozen so a closed referral cannot quietly reopen. That is what makes the aging report trustworthy: a referral sitting at "received" really is still sitting there.

  • Received → triaged → scheduled → seen → report sent
  • Illegal transitions are refused, not logged and allowed
  • Declined is a first-class outcome, with a reason attached
  • Every transition timestamped in an append-only event timeline

Closing the loop

Your referrers don't have to join anything.

Networks only close the loop when both practices have signed up for the same network. Most of the people sending you referrals never will. A printable status letter goes back the way the referral came — by fax or on paper — so the referring office learns what happened without an account, a login or a training session.

  • Printable status letters — no referrer account required
  • 48-hour aging alerts on referrals that have not moved
  • A referrer who hears back sends the next one to you
  • Documents stored on a private disk, never a public URL

Also included

The parts that make an intake queue trustworthy.

BAA at every tier

Signed inside the signup flow from $150/mo up — not a negotiation reserved for enterprise buyers.

PHI encrypted at rest

Patient details are encrypted, and referral documents live on a private disk rather than a guessable URL.

Append-only audit trail

Hash-chained and enforced at the database level, so history cannot be quietly rewritten after the fact.

Leakage & aging reporting

See where referrals stall by referrer and by stage, instead of guessing which relationship is going cold.

Unlimited staff logins

Every person who touches intake gets their own account. Shared logins are how audit trails stop meaning anything.

White-label partner portal

Networks and vendors onboard practices under their own branding with roll-up invoicing.

Put this week's faxes in one queue.

Start free, point your fax line at the signed endpoint, and watch the aging report fill itself in.

Start free Book a walkthrough →