Corporate faxing comes in many variations. One can argue that desktop and mail server connectivity is all that a fax setup requires. QBFax proves otherwise - the desktop is just a start.
Being connected to a corporate fax means being able to interact with your applications, including the CRM, ERP or other tailor-made applications. For that purpose, QBFax has extensive document/API connectivity allowing flexible, straight-forward integration with existing application with minimal programming.
- XML Multiple Document Interface
- HTML Documents
- Text Documents
- SMTP Submitting a.k.a. Mail-To-Fax
- Propriety QBIPC API
- Registry API
- INI File API
QBFax has an adaptable fax interface for SAP. Faxing is supported through the SMTP gateway using a specifically developed SAP importer interface. QBFax also associates the SAP user with the fax user and reports the outcome of the fax as if it was submitted from the desktop.
QBFax integrates with e-Tafnit by Matrix in a way that makes it possible to virtually any report. Both character-based Tafnit and e-Tafnit are supported.
Aside from being integrated to the reporting engine, the application can also send mass-faxing(or mailing) or fully automated faxing using custom reports.
- Corporate desktop fax solution
- Centralized administration and user/group management tools
- Interoperability with desktop and information systems (Outlook, ERP,CRM)
- Supports both Fax2Mail and Mail2Fax
- Emphasis on business methods and work flow
- 100% Functional on Windows terminal servers
- Works with and without e-mail
Computer Coprorate Fax vs Paper Fax
QBFax can completely change the way you look at fax software and fax in general.
Take this into consideration: About 80% of the faxes transmitted and received are actually documents generated by a computer. Think how many documents you send/receive come from Microsoft Word or from your ERP/CRM/Accounting software.
It is only natural that you’d want to save the overhead of printing the document, standing by the fax machine and waiting for the fax to get transmitted.
Now think of this: A fax document received by fax is, in general – a message. It could be an order, a request or an invoice. Whatever the message contains, it is very likely that this message will be passed on (or “forwarded”, in terms of messaging) to the person that is responsible of handling it. It seems more like a job a messaging system. One messaging system you probably know of is e-mail. I could be a great idea if you could have the fax send in a matter of seconds to any person who needs to read the fax.
In an office that doesn’t use any computer-fax system, a secretary or a service representative generally receives the fax. The person who picks up the fax them moves the paper into a box or puts it on someone’s desk to attend to it.
This is too, a great overhead. With QBFax, once the message is received, it can be directly sent to any person that can be reached by mail or printed on a network printed. But in addition to that, the QBFax has several features that can save even this process.
For example: If there’s a fax that usually gets handled by a specific person, you could specify that all fax messages from a certain company’s FAX ID will automatically show up on that person’s e-mail, and if this is a top-priority customer, the QBFax can also pop-up a message saying that a fax message from this customer has arrived.
On the other way around – wouldn’t it be nice to finally have a system that can ignore faxes from senders you consider as spammers (businesses or other entities that send promotional material with/without your consent)?
Combine the prior advantages and you will see why more and more businesses use a fax system. In fact, think of it: do you know of a company that threw away its fax system?