Live data from Hacker News

Programmable Fax – API for sending and receiving faxes

twilio.com

51–60 of 174 posts

Re: Programmable Fax – API for sending and receiving faxes

#51

Earlier quoted context omitted.

it's amazing that phaxio have gotten away with such high prices for so long.

All the eFax providers have been doing this.

When your user-base is comprised of doctors, lawyers and blue-chip companies with ancient business processes you can get away with charging what you like.

Re: Programmable Fax – API for sending and receiving faxes

#52
post #34

Earlier quoted context omitted.

> I see all sorts of things I shouldn't see when searching the pile of papers on the fax machine at a large company for my fax. That's not an issue of the security of fax as a transmission method, it's a problem with your company's security at the fax endpoint.

Does it matter? The point is that fax isn't inherently a great idea for confidential info. There's also the issue that many fax endpoints that are fax to email gateways. Or fax to non https website gateways. Edit: Nobody is arguing for using email instead of fax. The argument is to use something better. Like paypal or stripe instead of full cc info + cvv2 on a piece of paper.

> Does it matter?

When it comes to liability for breaches of confidentiality, yes, it matters very much whether the sender chose an poor channel or the recipient had choose poor practices around what was done with information once it was received.

Re: Programmable Fax – API for sending and receiving faxes

#53
post #21

Earlier quoted context omitted.

Guessing this will kill Phaxio. Compare the pricing: https://www.twilio.com/fax/pricing https://www.phaxio.com/pricing/

it's amazing that phaxio have gotten away with such high prices for so long.

I'm not sure the Phaxio pricing is all that much higher than Twilio. They're covering failed faxes, cancelled faxes, faxes that require multiple retries, and faxes that just take a long time — only charging per page delivered. Those will all eat up minutes that you'll pay for with Twilio.

In any case, their pricing model has been far preferable to their old competitor, Interfax: https://www.interfax.net/en/prices

Re: Programmable Fax – API for sending and receiving faxes

#54
post #21

Earlier quoted context omitted.

Guessing this will kill Phaxio. Compare the pricing: https://www.twilio.com/fax/pricing https://www.phaxio.com/pricing/

it's amazing that phaxio have gotten away with such high prices for so long.

Phaxio founder here.

Our pricing might seem higher (and may be in certain situations), but it works a bit differently that Twilio's. Twilio charges you the 1c _plus_ the costs of the call. Phaxio is an "all in" rate _including_ retrying the call. And, at Phaxio, if the calls all fail there's no cost to you.

I'm not saying that we won't adjust our pricing (#competition), but there's a difference in the actual unit cost.

Re: Programmable Fax – API for sending and receiving faxes

#56

now if they could implement barcode recognition for inbound faxes and plug into taskrouter they would have a very compelling offering.

What's the use case for barcode recognition? Sorry I've never had to use faxes much myself so I'm curious.

For us — we send out requests for medical records to doctors' offices. When doctors send records back to us, they usually include the cover sheet we sent over. Since that cover sheet has a barcode on it, we know which record request the incoming records are for.

Re: Programmable Fax – API for sending and receiving faxes

#59
post #26

If Twilio will sign a business associates agreement, this could be huge in the healthcare field. EMRs have terrible interoperability so doctors and health systems typically fax health records to one another. However, this service does not look HIPAA compliant based on the sparse documentation. It doesn't look promising that they will sign a BAA according to this document. https://support.twilio.com/hc/en-us/articles/…

They might have not considered this to be a big enough business opportunity when they penned this section.
Post reply on HN