LABUSA provides electronic fax services to government and educational organizations in Texas that use email as a familiar interface for sending fax documents. Authorized users can submit documents through approved email workflows without relying on a physical fax machine at their desk.
This page describes that capability in aggregate. It names no customer, and it carries no volumes, dates or deployment sizes, because those are not ours to publish.
The workflow
From the sender's point of view the sequence is short, and from the service's point of view it has seven steps.
- An authorized user prepares an email.
- The destination fax number is represented in the addressing workflow defined for the service.
- The document is attached to the message.
- LABUSA eFaaS accepts and processes the submission.
- The document is converted to a fax-compatible transmission.
- The service attempts delivery to the destination fax endpoint.
- Delivery status can be returned to the user or to the associated workflow.
Nothing in that sequence asks the recipient to change anything. They receive a fax on a fax number, as they did before, which is usually the reason the channel is still in use.
What it changes for the organization
The gains are operational rather than dramatic, and they are worth stating plainly.
- It reduces dependence on physical fax machines.
- It allows staff to use familiar email workflows rather than learning a system.
- It can centralize fax processing rather than distributing it across devices.
- It supports distributed and remote staff on the same terms as office staff.
- It reduces the need to manage fax hardware at each user location.
- It provides a controlled service layer between email and fax delivery.
- It can support centralized administration and troubleshooting.
For an organization with machines in several buildings, the fourth and fifth points usually carry the argument. A device per location means a line per location, a maintenance obligation per location, and somebody at each site who knows how it works.
What email does not do
Email is the interface. It is not a security control, and it does not confer any regulatory status on the documents it carries. That is worth stating directly because it is assumed often: sending a document by email does not make its handling compliant with any rule, and neither does sending it by fax.
Where security is concerned, the outcome depends on the implementation as a whole. The parts that determine it include email security, identity and access controls, service configuration, document handling, encryption where applicable, audit and logging controls, retention requirements, endpoint security, and the organization's own policies. Those are examined in email-to-fax security considerations.
Requirements that have to be evaluated
Organizations in these sectors commonly have obligations under health, education, public records, retention or privacy rules, and each of those must be evaluated during implementation rather than assumed to be satisfied by a service. The obligation stays with the organization that holds the records. What a service supplies is the material that makes an assessment possible: controlled submission, a record of what happened, and retention behavior that can be set to match a schedule rather than a default.
We work through one of those rules in detail in electronic fax and HIPAA compliance, and the Texas-specific records and procurement layer in electronic fax for Texas public-sector organizations.
What we ask before setting it up
The questions are the same each time, and answering them early shortens everything that follows.
- Which numbers must keep working, and which can be retired.
- Who is authorized to send, and how that list is maintained when staff change.
- Where delivery status should go: to the sender, or into a workflow that will act on it.
- Where received documents should land, and who else can read that location.
- What the retention setting should be, and which schedule it was derived from.
Why email rather than a portal
A portal is a better interface by most measures. It can validate a destination against a list, refuse an unsupported attachment before the sender walks away, and put the delivery status in front of the person who caused it.
Email wins anyway, and for a reason worth being honest about: it requires no adoption. In organizations where fax persists because a partner requires it, the people sending are rarely doing it often enough to learn a system, and are frequently doing it under time pressure at a counter or a front desk. An interface people already have open is worth more than a better one they have to be trained on and then reminded about.
Where a system already holds the document and the destination, that reasoning stops applying and the case for an integration is strong. Most organizations end up with both.
What it does not change
The far end is unchanged: a fax endpoint, reached over the fax network, with the same busy signals and the same tolerance for a poor line. Retries are handled rather than left to whoever noticed a failed slip, which is a real improvement, and it is not the same as every transmission succeeding.
Nor does it change who is accountable for the records. Moving a workflow to a service moves the operation, not the obligation.
Where to go next
For the general mechanics of this path, independent of any provider, see how email-to-fax works. For how this path relates to the others, see the architecture page. To discuss a specific environment, tell us what you are working with, or see the feature overview.
Sources
- NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations. The access control and Audit and Accountability families behind the authorization and status points above.
- 45 CFR 164.306, Security standards: General rules, Government Publishing Office. Flexibility of approach, and why an arrangement has to be assessed rather than bought.