Release checks
The grouped checklist that must be true before any follow-up email plan is released.
Email permission is recorded before any follow-up email is considered.
Unsubscribed customers are never sent follow-up emails.
Customers marked with a do-not-email rule are never sent follow-up emails.
Customers marked as service messages only are never sent follow-up emails.
Customers with unknown email permission are never sent follow-up emails.
Hard bounces stop all follow-up emails.
Spam complaints stop all follow-up emails.
Basic-to-comprehensive upgrade emails stop when a comprehensive check is bought for the same registration.
Free-to-paid emails stop when a paid check is bought for the same registration.
Bundle top-up emails use the latest bundle balance.
One-check-left emails only send when the balance is exactly one.
No-checks-left emails only send when the balance is zero.
App suggestion emails stop when the customer used the app in the last 30 days.
Pro account emails stop when the customer already has pro access.
Checkout emails stop when payment has completed.
No customer receives more than one follow-up email in 24 hours.
No customer receives more than three follow-up emails in seven days.
Only one email is chosen when more than one could be sent.
The priority order is tested with a customer who could receive several emails.
A blocked email does not count as sent.
A reminder is not sent after the customer completes the action.
Every email has a subject line, preview text, headline, body copy, and button text.
Every email design has all required fields listed.
Vehicle emails include a registration plate panel where a registration is available.
Account emails do not pretend to be about a specific vehicle.
Planning previews are checked against the developer-ready HTML files.
All copy uses plain English.
No email claims a problem has been found unless the data confirms it.
Every email has an HTML file.
Every email has a plain-text file.
Every email has a subject line.
Every email has preview text.
Every email has one main button.
Every email has the required fields listed.
Every vehicle email has a registration field.
Every account email does not require a registration unless needed.
Every email has a support link.
Every email has an email settings link.
Every follow-up email has an unsubscribe placeholder.
Every button URL field is documented.
Checkout email uses checkout_recovery_url.
Upgrade emails use upgrade_url.
App email uses app_download_url.
Bundle emails use bundle_url or topup_url.
Pro emails use pro_url or pro_bundle_url.
All visible copy uses plain English.
All email files contain fake or sample data only.
Sample estimate numbers have been replaced with real internal numbers before decision making.
Every email has a result type.
Every email has a clear result to count.
Every email has a normal result percentage from the not-emailed test group.
Every email has an expected result percentage from emailed users.
Every email has a value per result where relevant.
App email has a way to count app use after email.
App email has a way to estimate saved paid-search visits.
Checkout email has a way to count completed purchases after the saved checkout email.
Upgrade emails have a way to count same-registration comprehensive upgrades.
Bundle emails have a way to count bundle purchases after email.
Pro emails have a way to count free pro account creation.
The live system stores whether the user was emailed or held back as part of the test group.
The live system stores which email was chosen.
The live system stores when the email was sent.
The live system can link later sales or actions back to the email or test group.
Results are reviewed before scaling the email to more users.
Each email has a clear measure of success.
Comprehensive upgrades can be counted after upgrade emails.
Paid checks can be counted after free-to-paid emails.
Bundle purchases can be counted after bundle emails.
Larger bundle purchases can be counted after larger-bundle emails.
Pro account creation can be counted after pro account emails.
App use can be counted after app emails.
Checkout completion can be counted after checkout emails.
No Postmark call is made from this planning app.
Postmark message streams and sender details are checked outside this app before release.
Test sends use safe internal addresses only.
Unsubscribe links are included in production email HTML.
Bounce and spam complaint handling is confirmed before release.
A sample user proves each planned email can be chosen.
A sample user proves unsubscribed customers receive no follow-up email.
A sample user proves hard bounces receive no follow-up email.
A sample user proves active refund or payment dispute cases receive no follow-up email.
A sample user proves the 24-hour send limit works.
A sample user proves the highest-priority email wins.
The developer pack lists required customer actions.
The developer pack lists required customer fields.
The developer pack lists required vehicle fields.
The developer pack lists required order fields.
Open questions for the developer are reviewed.
No real customer data is added to this planning tool.