Make sure that your network is working well because the product will work well with a network that is working well. It's a decent all-around product, from what I can see. I keep a log of what goes out. I really don't archive. I set this up a long time ago and I've never really looked at it again. It works and we're done. We stamp it out as a "carbon copy" to everyone. It's doing the job that we want it to do. It requires minimal maintenance. Once in a while we have to restart the server, and sometimes we have to restart the hardware to the server. That might happen twice a year and it takes 10 minutes if we have to do a hard reboot or two minutes if it's just shutting down Faxmaker and restarting it.
The product is okay and working fine. Everything that we want to do with the product, we can do it. We also use GFI MailEssentials. It is possible to use rules within the solution to route incoming faxes based on the sender’s ID and phone number, but we don't use this feature. I would rate the product as an eight or nine (out of 10).
The only rule that we have setup is that an administrator gets an email. I am not sure that we will go on the solution's OCR option. With the faxes sent with the SAP system, we can see the delivery node, invoice, etc. Therefore, we don't need to store it twice. I would rate the solution as a nine (out of 10).
It's easy, especially for the older generation, even though we in IT would like to get rid of it as soon as we could. But that's not going to happen anytime soon. Currently, we're not using the solution’s OCR (optical character recognition) option to convert faxes to editable and searchable text, but that would be an interesting feature for our document integration in the future. We're not using it right now because the number of faxes we receive is declining.
It does what it should. It is stable and you don't have to maintain it that much. Outgoing taxes are handled differently. We don't use FaxMaker for that. We don't send that many faxes anymore. Basically, we use a printer, where we print it out and the printer faxes it out. These are not for personal faxes. I would rate it a 10 (out of 10). It does what we need and is stable.
My advice would be to take your time and make sure you have the setup right. The biggest lesson I've learned from using this solution is that fax is still used today in business, surprisingly. It's an outdated solution, but it's still the most secure for certain things, as crazy as that sounds. I would rate it at about an eight out of 10, only because of the fact that we had quite a few crashes and poor error response. But it works.
GFI FAXmaker is a leading fax server for small to medium-sized enterprises. It makes sending and receiving faxes an efficient, simple and cost effective process and solves the problems with manual faxing: printing out the document, walking to the fax machine, waiting for the fax to go through, not to mention the cost of fax machine supplies and repair. GFI FAXmaker allows users to send and receive faxes directly from their email client.
Make sure that your network is working well because the product will work well with a network that is working well. It's a decent all-around product, from what I can see. I keep a log of what goes out. I really don't archive. I set this up a long time ago and I've never really looked at it again. It works and we're done. We stamp it out as a "carbon copy" to everyone. It's doing the job that we want it to do. It requires minimal maintenance. Once in a while we have to restart the server, and sometimes we have to restart the hardware to the server. That might happen twice a year and it takes 10 minutes if we have to do a hard reboot or two minutes if it's just shutting down Faxmaker and restarting it.
The product is okay and working fine. Everything that we want to do with the product, we can do it. We also use GFI MailEssentials. It is possible to use rules within the solution to route incoming faxes based on the sender’s ID and phone number, but we don't use this feature. I would rate the product as an eight or nine (out of 10).
The only rule that we have setup is that an administrator gets an email. I am not sure that we will go on the solution's OCR option. With the faxes sent with the SAP system, we can see the delivery node, invoice, etc. Therefore, we don't need to store it twice. I would rate the solution as a nine (out of 10).
It's easy, especially for the older generation, even though we in IT would like to get rid of it as soon as we could. But that's not going to happen anytime soon. Currently, we're not using the solution’s OCR (optical character recognition) option to convert faxes to editable and searchable text, but that would be an interesting feature for our document integration in the future. We're not using it right now because the number of faxes we receive is declining.
It does what it should. It is stable and you don't have to maintain it that much. Outgoing taxes are handled differently. We don't use FaxMaker for that. We don't send that many faxes anymore. Basically, we use a printer, where we print it out and the printer faxes it out. These are not for personal faxes. I would rate it a 10 (out of 10). It does what we need and is stable.
My advice would be to take your time and make sure you have the setup right. The biggest lesson I've learned from using this solution is that fax is still used today in business, surprisingly. It's an outdated solution, but it's still the most secure for certain things, as crazy as that sounds. I would rate it at about an eight out of 10, only because of the fact that we had quite a few crashes and poor error response. But it works.