3 ms·
If email is broken for sending invoices, then the correct response is to stop sending invoices over email. Banks figured this out already: Stop sending things d
by jdmichal 10y ago
If email is broken for sending invoices, then the correct response is to stop sending invoices over email. Banks figured this out already: Stop sending things directly in email, and instead send notifications. Have the user log into the banking system to see the notification.
So, host invoices on your own domain, and only send links to clients. Clients can confirm they are talking to the correct server when downloading the invoice. Same as they should be used to doing for any email with links regarding money.
- michaelt 10y agoBanks figured this out already: Stop sending things directly in email, and instead send notifications. Yeah, and it sucks and everyone hates it. That's all very well when you're sending someone a bank statement and you don't care if they bother to read it - but when you want to send someone an invoice, and you're keen that they read it and respond in a timely manner, you need a higher standard of customer service.
- abraae 10y agoMost of the world seems happy to click through to read a Facebook notification, so I don't know why someone who gets paid to do it would not click through to see an invoice. The main problem with clicking through is normally clunky authentication systems that make it not just a click through, but a painful dance before you finally get to the target resource.
- jessaustin 10y agoClicking through doesn't solve any problems. It's real easy to spam people with links to www.mybank.com.evil.com. Only training the user to navigate directly can even hope to avoid such attacks.
- gpawl 10y agoThere's no problem with showing a preview of non-secure content. As long as the recipient knows to visit the official secure server for official copies of important information.