Document · Encoding · Protocol · Contract · Recipient state
Faxbot approaches cost reduction across the document, encoding, transmission protocol, carrier contract and recipient’s existing information. That includes transporting original PDFs with their colors, graphics, text and layout intact.
The portfolio spans implemented capabilities, development branches and active research.
One document. Several coupled optimization problems.
A smaller PDF can produce a larger fax stream. A shorter stream can cross the same billing boundary. A cheaper route can cost more after retries.
The useful choice depends on all five layers: what must arrive, what the receiver already holds, what the encoder can legally emit, what the endpoints negotiate, and what the carrier actually charges.
Faxbot’s implemented controls and research portfolio connect those decisions. Exact-byte transport, pixel-preserving encoding and permitted appearance changes solve different problems; each keeps its own fidelity and acceptance requirements.
Optimize within authorization, fidelity, deadline and recipient-policy constraints. Measure payload size, occupied time, billed units and business acceptance separately.
Measured examples from the research portfolio
Information content, protocol overhead and billing units do not scale together.
30 document pages became one encoded fax page. Ordinary fax image data: 1,328,802 bytes. Run-coded payload: 60,588 bytes. Exact-file recovery preserves the original PDF’s colors, graphics, text and layout.
Original-file transport →The same page fell from 29,003 to 5,629 encoded bytes by changing prediction and template settings. Across the 20-file corpus, the aggregate reduction was 25.66%; decoded pixels matched exactly.
Adaptive JBIG optimization →A verified partner already holds the unchanged document body. Send the new header bands and reconstruction data: 2,746 bytes instead of 7,280. Verify the complete intended fax image after reconstruction.
Exact document and header deltas →These reproduced synthetic examples measure different mechanisms and baselines; their percentages do not add together. Original-file transport requires a compatible decoder, JBIG requires endpoint support, and body reuse requires an authorized retained base. Payload reductions are distinct from complete call time and carrier charges.
The technical portfolio
From dynamic programming inside the encoder to the economic value of a missing recipient permission. Each mechanism below names what changes and why it matters.
Implemented — current main-line capability.
Development — implemented on integration or development branches.
Experimental / Research — laboratory implementation or an active design/model, as described.
Change the information carried, then optimize the legal representation of that information.
Carry the original PDF through the fax channel and recover it bit for bit, preserving its colors, graphics, text and layout. In the 30-page synthetic benchmark, one encoded fax page used 95.44% less image data than ordinary fax rendering.
The container compresses original bytes, records a digest, optionally encrypts the payload, and applies Reed–Solomon protection with interleaving. Layouts include visible grid cells, MH code-tree run lengths and shifted halftone dot clusters. A compatible receiver or browser decoder reconstructs the original file, including its original color and graphics, selectable text and document structure. A conventional fax machine prints the encoded raster; the decoder recovers the PDF.
The ordinary 30-page fax used 10,630,416 image-data bits with the smaller of measured MH and MMR encodings. The run-coded page used 484,704 MH bits: 1,328,802 → 60,588 bytes, a 95.44% reduction (about 22× smaller). All three layouts recovered the exact original PDF after Group 4 TIFF storage and rereading. The 55,422-byte source and 37,382-byte container are intermediate sizes. This offline text-document benchmark measures image payload; call overhead and carrier charges are separate. Dense layouts require an exact-raster path and observed ECM/fine-resolution support.
Shape encoded data around the carrier’s charging model: minimize transmitted bits when paying by the minute, or maximize recoverable information per page when paying by the page.
The constrained-channel model assigns different costs to fax code bits and the pixels consumed by run lengths. A cost-weighted run distribution moves the optimum between temporal efficiency and page density. It exploits the legal code alphabet and source distribution; it does not compress arbitrary encrypted data beyond its entropy.
Capacity and raster experiments exist. The proposed invertible arithmetic payload map, equivalent framing overhead and complete protected round trip are still research. Modeled capacity is not yet a production encoder throughput measurement.
Compare the actual output of MH, MR, MMR and JBIG encoders for each document. The smallest source file does not necessarily produce the shortest fax transmission.
Measure encoded page data after rasterization rather than using the upload’s file size as a proxy. The integration line compares MH/MR/MMR; development branches extend the portfolio with JBIG. Select only formats supported by the engine and recipient, and account for what the call ultimately negotiates.
Encoded TIFF strips and JBIG streams are measurable page payloads. Complete wire cost also includes framing, fill, error correction, retransmissions and negotiation. The configured coding can change during negotiation.
Optimize MR reference-line resets against actual byte alignment and minimum scanline padding while preserving every pixel. Across 20 synthetic files, tuned MR reduced encoded data by 20.76% versus fixed MR. Adding it to per-page codec selection reduced data by 6.21% versus the previous non-JBIG portfolio.
Choose each row’s one-dimensional or two-dimensional encoding under the reset-spacing constraint. Each two-dimensional row references the preceding raster row regardless of how that row was encoded. Dynamic programming finds the legal schedule with the lowest cost after byte alignment and minimum scanline fill.
A development branch integrates the schedule with a patched HylaFAX engine. Without scanline fill, fixed MR used 1,487,193 bytes and tuned MR 1,178,491. Adding tuned MR to the best previous non-JBIG comparison reduced 1,186,913 to 1,113,161 bytes, winning on 8/20 files. Against fixed MR, 18-byte and 72-byte minimum line fill reduce the gains to 15.19% and 5.77%. Independent reconstruction recovered every original raster; 1,980 small schedules matched exhaustive enumeration. These are encoder measurements, not complete call timings.
Search prediction and adaptive-template settings that conventional encoders leave fixed, while preserving every pixel. The synthetic tinted form used 80.59% less JBIG data; the 20-file corpus used 25.66% less in aggregate.
The implemented development portfolio evaluates candidate JBIG parameters and checks pixel-exact decoding. Further research searches when and where the adaptive template changes, charging the signaling overhead as well as the image data. This makes encoder configuration part of document optimization.
The tinted form fell from 29,003 to 5,629 bytes; the corpus from 594,970 to 442,307. All 960 encoder/decoder comparisons recovered identical pixels. The corpus has 19 unique rasters and a median reduction of 0.258%; gains are concentrated in particular page types. Per-page search adds 2.11% beyond the improved fixed preset. The engine branch requires a compatible, explicitly enabled endpoint. Search over adaptive-template decision timing remains research.
Account for error-correction block boundaries, acknowledgements and page exchanges when arranging content. A different legal layout can eliminate an entire protocol round trip or billed interval.
An ECM partial-page block holds up to 256 frames, each carrying 64 or 256 octets of fax image data. Crossing a block boundary introduces another control exchange; crossing a page boundary introduces a different exchange. Packing should therefore price encoded bytes, block counts and page transitions together, while respecting document order and fidelity.
The joint cutter, encoder and protocol-state objective is research. Observed timing on one gateway is not a universal acknowledgement cost. Negotiated frame size, speed, error behavior and the carrier’s rounding rules determine the useful boundary.
Identify text, edges and critical details, then reshape permitted background textures into patterns that compress efficiently. A synthetic protected-screen experiment reduced MMR image data by 58.22% on the shaded table and 75.80% on the tinted form, with zero changed protected pixels.
The protected-region implementation freezes text, edges and other protected pixels, then changes suitable uniform shading interiors. Fax-friendly screening can avoid the expensive alternating runs produced by conventional halftones. The objective is the resulting fax encoding, not just visual smoothness.
The recorded h16 screen reduced table MMR payload from 873,336 to 364,880 bits and form payload from 736,160 to 178,176 bits. Against each original’s smallest measured MH/MR/MMR encoding, the reductions are 47.77% and 65.47%. Text/edge protection stayed intact; permitted background pixels changed. This development method requires approval for those appearance changes and retention of the source. Exact-record workflows can use the lossless encoding path.
Use authenticated receiver knowledge to avoid repeating information or completed work.
Use verified knowledge of what the recipient already holds to reduce a packet to new information plus approved references. A recurring case submission can carry five new pages plus a reference index instead of retransmitting a hundred-page accepted history.
Recipient-approved case packets already reference accepted documents. The development ledger adds version, purpose, acknowledgement and expiry to the decision. Conceptually the task is to transmit X given receiver knowledge K: the new information plus authenticated identity, version and repair overhead.
For an illustrative packet with 100 accepted history pages and five new pages, the reference index adds one page: 105 pages become six, not five. Reuse is specific to the recipient and case, requires agreement, and must recover when the retained base is missing or expired. Fax acceptance does not establish chart filing or retention.
Replace repeated form backgrounds with an immutable template identifier and typed field values, allowing the recipient to reconstruct and verify the intended document.
Register a content-addressed background and rendering specification. Exchange the agreed version and field values, then compare exact reconstructed page hashes before filing. The receiver performs deterministic rendering rather than inferring or summarizing the form’s meaning.
The implementation is on the integration line. Both partners need the agreed immutable template and compatible renderer. A version or page-hash mismatch blocks filing.
Separate unchanged document bodies from changing headers and other differences. In a synthetic three-page example, authorized body reuse reduced the transfer from 7,280 to 2,746 bytes—62.28% less—while reconstructing the exact target fax image.
Original-file reuse and bounded binary deltas are in the integration line. A separate branch isolates Faxbot-generated header bands from unchanged fax-image bodies, so a new header can travel without the body. Reconstruction checks the complete intended document or raster digest.
The fax-body branch separates only headers Faxbot generated; it does not assume arbitrary dates, signatures or annotations are disposable. Receiver authorization, an exact retained base and a missing-base repair path are required. The measured example reduces bytes on a partner path that already avoids a carrier call; it is not another independently avoided call.
Send a shared document once to an authorized intake, then distribute it internally while retaining separate recipient identities, filing records and receipts.
A signed common-intake agreement names the exact fax numbers the receiving organization handles. Both administrators approve the coverage. The shared payload keeps a separate delivery identity, receipt and work item for every intended recipient.
Implemented on the integration line. A shared company name, brand or email domain does not establish consent to consolidate. One shared transfer must not collapse distinct recipient obligations into a single success flag.
Assemble exactly the documents required by the recipient’s checklist, using accepted versions and approved references to avoid unnecessary attachments and repeated cover pages.
A deterministic checklist selects unchanged source documents against recorded recipient requirements and acceptance history. Preview included, referenced and missing material before sending. Approved manifests can identify shared evidence without treating every new submission as an entirely new chart.
Checklist selection and version-aware case history are integrated development capabilities. The recipient’s actual requirements and permission to reference earlier documents remain inputs; a model must not silently summarize away required evidence.
Track confirmed pages and verified document chunks, then repair only the missing portion. A ten-page delivery interrupted after six confirmed pages can continue with four when the evidence and receiving path support it.
For verified partners, signed custody checks establish an intact prefix and the receiver verifies the completed document after missing-suffix repair. For supported ordinary-fax outcomes, an administrator can choose continuation using confirmed-page evidence. The original failed attempt remains in the history.
The ten-page example is illustrative. A lost response is not evidence of a missing page. Partner custody and an ordinary sender’s page counter provide different assurances; uncertain outcomes are reconciled before another transmission.
Combine submission identities, immutable delivery attempts and recipient custody checks to distinguish a lost receipt from a lost document, avoiding blind retransmission.
Stable client operation identities recover an already accepted job after a timeout. Immutable attempt and provider bindings preserve transport history independently. Partner reconciliation and custody queries determine whether a receiver durably accepted the original even when its receipt was lost.
Client idempotency and transport reconciliation are implemented; extended partner custody and repair are on the development line. Neither retrying an API call nor receiving an SMTP acceptance establishes human acknowledgement.
Optimize completed delivery against discrete billing, finite allowances and endpoint behavior.
Evaluate carrier price together with expected duration, failure probability, retry expense and recipient compatibility. A cheaper advertised rate can cost more once unsuccessful attempts are included.
Current routing combines rate cards, destination reliability and observed all-attempt cost per delivered fax. The development predictor adds prepared-document measurements and account-plan state. Selection stays inside the allowed provider, mailbox, endpoint and delivery-policy boundaries.
Observed charges, estimates and settlement are kept separate. Charged failures count; unknown cost is not zero. The broader stochastic transaction model extends the implemented empirical routing rule rather than claiming an omniscient optimizer.
Allocate included pages and minutes across competing jobs instead of spending them in arrival order. Use the remaining allowance for the $50 delivery and pay cash for the $0.50 alternative.
A development allocator compares permitted paid alternatives across a queue with finite included capacity. With 100 included pages and two eligible 100-page jobs, assigning the allowance to the expensive alternative leaves $0.50 payable instead of $50. A historical-demand reserve protects part of the remaining allowance for likely future jobs.
The example is a reproduced synthetic allocation problem, not a customer saving. Exact small-queue solutions, a bounded fallback and historical-demand reservation are implemented on a branch. The monthly subscription fee remains payable; a broader stochastic optimizer remains research.
Model minimum charges and per-attempt rounding rather than assuming savings scale smoothly with file size. On whole-minute billing, cutting a call from 61 seconds to 59 removes an entire charged minute.
Apply the contract’s unit, minimum and increment separately to each attempt. Couple document and duration estimates to those discontinuities: reducing 70 seconds to 61 can leave the bill unchanged, while a smaller reduction across the minute boundary changes the charged units.
Rate-card rounding and charge reconciliation are implemented; prepared-document predictions are development work. The 61-to-59 example assumes a one-minute minimum and whole-minute increments, excluding any other fixed fees.
Combine compatible documents into one call so they share dialing, negotiation and setup costs instead of paying that overhead repeatedly.
Recipient-approved batching uses a bounded wait, a page cap and sender-mixing policy. Each document retains its confirmed-page outcome and allocated charge share. Urgent sends can bypass the wait, and separators are included in the page count and cost estimate.
Batching requires recipient agreement. A partial or uncertain shared call does not automatically authorize retransmitting every document in the batch.
Remember successful transport modes, speeds, compression capabilities and negotiation behavior for each route and recipient, with invalidation when relevant configuration changes.
Call measurements record negotiated behavior and destination routing uses observed outcomes. Development work turns supported recipient profiles into transmission choices and extends scheduling intelligence. Separate T.38 relay, G.711 passthrough, SSL Fax and Internet Aware Fax; they are not interchangeable capabilities.
Measurements and reliability history are implemented. Adaptive transmission controls depend on the engine, development build and endpoint. A registered SIP account does not prove that UDPTL can cross the network or that the carrier will accept T.38.
Coordinate capacity before dialing and learn congestion patterns, reducing busy-call storms, wasted attempts and repeated negotiation against an unavailable endpoint.
Current scheduling enforces destination concurrency, trunk channels and carrier call-rate limits. Uncertain calls keep their reservation until settled. Development scheduling learns busy and unanswered hours, considers charged failures, and protects urgent work and deadlines. The research extension lets a cooperating receiver issue authenticated, expiring capacity grants and reserves room for legacy callers.
Local capacity scheduling is implemented. Learned timing is integrated development work; cooperative receiver grants remain research; a capacity grant is permission to attempt delivery, not a document-acceptance receipt.
Confirm document class, version, destination and recipient requirements before moving the payload, preventing technically successful transmissions that still trigger rejection and rework.
Exchange a minimal business envelope before the document: intended recipient, purpose, class, version and required acceptance conditions. A receiver can reject an incompatible submission before the expensive transfer or identify the missing requirement that would make it acceptable.
This builds on existing recipient policy and checklist foundations. The business-envelope protocol is research; transport preflight and endpoint reachability do not establish administrative or clinical acceptance.
Remove avoidable calls, fixed charges and administrative work while preserving existing interfaces.
Use verified direct delivery or established digital channels such as Direct Secure Messaging and FHIR where permitted, removing the telephone leg while preserving delivery identity and evidence.
Verified Faxbot partners already exchange encrypted original PDFs and signed durable-acceptance receipts using familiar fax numbers. The development line adds configured Direct messaging accounts and FHIR R4 DocumentReference delivery with conditional creation and uncertain-outcome lookup.
Direct peers require enrollment and number binding. Direct/FHIR routes require configured trust and confirmed recipient endpoints; simulated-service checks do not establish a native EHR chart-filing integration. Reconcile an uncertain digital outcome before fax fallback.
Run the fax engine over suitable SIP connectivity, separate inbound and outbound providers, and choose among accounts and trunks to avoid unnecessary managed-service page markups.
The fax engine can use an existing carrier or PBX connection while other accounts handle receiving or additional outbound routes. Multi-account and site/trunk composition in the development line expose different contract, capacity and media-path choices without binding every direction to one provider.
Existing Asterisk and optional HylaFAX+ paths have different protocol capabilities. Price the account’s actual calls and fixed costs; an advertised wholesale rate is not the organization’s effective delivered-fax price.
Compare authorized regional termination, origin-dependent rates, approved toll-free alternatives and specialized data-session tariffs. The lowest quoted rate is not always the lowest price for completing the transfer.
Site and account rate rules and recipient-approved toll-free alternatives are integrated development capabilities. Research extends these foundations to additional origin/account-dependent tariffs and data-session services such as Japan’s NTT Data Connect. Compare setup, occupied time, access terms, media compatibility and destination eligibility together.
Only genuine authorized origins and permitted routes qualify. Specific tariff adapters and data-session interfaces require implementation and account-specific validation; no caller-ID manipulation or universal tariff saving is implied.
Analyze number usage, trunk capacity, subscription utilization and dependencies to identify removable rentals, surplus channels and unnecessary fees. Ten genuinely redundant $25 monthly lines represent $3,000 a year.
Current advice compares monthly plans with metered alternatives and identifies quiet numbers and possible receiving pools. Development work adds retirement evidence, migration dependencies and the facts needed before canceling a line or moving a number.
The $3,000 figure is arithmetic, not a measured customer result. A line is removable only after checking seasonal, emergency, broadband and other dependencies. Advice does not cancel a carrier account or assume that zero recent calls proves zero future demand.
Preserve familiar numbers, copier buttons and email delivery while moving compatible traffic onto shared infrastructure, reducing dedicated lines and avoidable replacement equipment.
Email and watched-folder connectors provide development-line entry points for existing applications and device workflows. Copier LAN-fax adapters, SBC routing and migration analysis can consolidate the fax path while retaining the interface staff already use.
Specific copier dialects, number splits and POTS-replacement dependencies need integration. Removing fax traffic saves equipment cost only when the associated port, license or replacement hardware is actually avoidable.
Combine receiving pools, economical number hosting, approved reply-number selection and pre-answer blocking of known unwanted callers to reduce fixed charges and unwanted traffic.
Current receiving advice replays call history to compare shared capacity and metered arrangements. Development work extends number placement and migration, recipient-approved reply identities, and inbound screening. Distinguish a carrier-side rejection from an answered call that already incurred a charge.
Capacity must account for blocked demand and the contract’s overflow behavior. Caller screening, selected reply numbers and portability depend on supported carriers, trusted signaling and explicit policy; they are not automatic changes to every installation.
Track expected correspondence, ownership and acknowledgements independently of fax transmission status, reducing chase calls, missing-work investigations and duplicate processing after outages.
Acquired-document provenance, owned queues, acknowledgement targets and evidence export are implemented. The expected-fax development branch records obligations before arrival, distinguishes strong references from tentative matches, and supports outage reconciliation of completed, new and unresolved business items.
An expected document must come from an entered or imported expectation. Weak matches need review. SMTP acceptance, fax success, owner acknowledgement and completion remain separate events; an outage ledger does not guarantee exactly-once action in another system.
Calculate which unknown price, recipient permission or technical capability would unlock a cheaper route, directing configuration and partner-onboarding work toward the largest recoverable savings.
Reprice historical faxes to rank opportunities from missing permissions, prices and capabilities. The development advice compares automatic fax accounts and verified Faxbot peers using the document-cost predictor, alongside number-move and retirement evidence.
The current comparison does not yet include confirmed Direct Secure Messaging/FHIR alternatives or replay historical mailbox/workflow policy. Treat its ranking as a configuration lead, then check the complete permitted route set. Related facts that unlock the same route are not independent savings.
Automatically signed in for read-only inspection of real routes, carrier costs, fax metadata and call diagnostics.
Live acceptance installation. Read-only access opens automatically. Document downloads, paid sends and administrative changes are unavailable. The live connection depends on the demo host being online.
Inspect actual carrier charges, the route used by each attempt and documents recovered after acquisition failed.
Captured from the real installation. Carrier charges and plan fees shown are its records; they are not a customer savings forecast.
The infrastructure you already administer
One organization can receive over SIP, send through a cloud account, and use the trunk as an additional outbound route.
Keep those choices independent. Use destination preferences, provider capability checks and mailbox permissions. Every accepted fax keeps its attempt history and provider identity, including when a confirmed failure moves it to another route.
Connect a carrier or an Avaya IP Office or Aura phone system. Diagnose registration, NAT, T.38 negotiation and G.711 separately. A successful SIP sign-in is only the start of the fax path.
Inspect the trunk configuration →The development line extends the built-in single-trunk configuration with multiple accounts and trunks, site and direction rules, capacity limits and account-specific pricing.
After the transport says delivered
The PDF arrived. The email was accepted. Who owns the work?
Persist the real acquired document, assign someone who already has access, set an acknowledgement target and backup, and export the evidence. Import a PDF from another system through the same owned queue.
Chart filing, clinician notification and business completion each need their own receipt. EHR connectors, reviewed OCR/AI processing and setup proposals can be scoped around your existing system, processing rules and workflow.
Inspect acquisition, ownership and evidence →Authentic document bytes, provider identity and digest.
Connector result, including an uncertain SMTP outcome.
A named person accepts responsibility.
The work item is completed with its own evidence.
Carrier and PBX versions. Trunk topology. Billing increments. Recipient packet rules. The intake system that still needs manual repair.
Tell us which path you control and what is failing. We can discuss configuration and integration around your existing infrastructure.
Keep credentials and private documents out of the inquiry.
Security and deployment boundaries →