4 ms·
Sure, this could be a critical customer requirement. Use case: A client has signed up for a service and is paying to receive a report. In this case, they rec
by zhte415 7y ago
Sure, this could be a critical customer requirement.
Use case: A client has signed up for a service and is paying to receive a report. In this case, they receive a link to download. No tracking embedded in emails.
Verification: 2 review cases. Monthly review.
Case 1: Email bounces from server.
Case 2: Email doesn't bounce but not checking report.
In both cases, sales/customer service get in contact with the customer.
For Case 1, to check an appropriate email address (client contact leaving, mailbox full/disused, etc).
For Case 2, largely to check if reporting can be more useful (i.e. actually look at the report) which can result in interesting ideas about better integrating into their workflow/needs, though spam-whitelisting is also sometimes a factor here.
I tried the links you provided with an email address on my personal domain that I know not to be deliverable, and it was reported as deliverable.
- federiconitidi 7y agoInteresting use case, have you seen this adopted in practice in your experience? Also, what validation provider did you use for your test?
- zhte415 7y agoYes, it was implemented globally after being trialed in a region. It should be standard practice but I know a lot of peers that don't do it. Was implemented internally, using internal APIs, basically API'd logs. I'd call it less a test than as being part of client workflow/relationship management.