Hacker News new | past | comments | ask | show | jobs | submit login

We (Twilio) are also only charging for successful delivery. Failures to not incur any billing. Retry is (currently) on the customer to implement, but since we don't charge for failures, that doesn't affect cost.

Yes, we're charging per-minute fees, but for US, at least, it's sub-1-cent, and with my testing so far, I haven't seen it go more than a couple minutes per page for something fairly complex, and that's worst case.




Someone else in this business says they see 1 minute for 1 page faxes, but faster for longer faxes...Because the first page has the initial handshake.

http://www.faxage.com/learn_faxing_by_minutes_versus_faxing_...

I'm sure some pages take longer, but it doesn't seem odd that most pages aren't complex.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: