Email verification before a product launch - What to check before you send

Make your next product launch count by checking your email list before you schedule the announcement. Start with permission, address quality and relevance—not the total number of contacts in your database.

For a South African small business introducing a new product range or service, the aim is to reach people who can reasonably expect the update and have a reason to act on it.

BulkMail provides permission-management tools and email address verification to support that preparation. They serve different purposes: one helps you manage permission and subscriber choices; the other checks address quality before sending.

A verified email address is not automatically a permitted recipient. You need to check both.

Use the countdown below as a planning guide, not a fixed technical timetable. Start earlier when introducing a new sending domain, resolving delivery problems or preparing a much larger campaign than usual.

Start by identifying who belongs on the launch list

Before combining spreadsheets, customer records and newsletter subscribers, establish where each group came from and what they agreed to receive.

A person who requested product announcements is different from someone who asked for a quotation. An event registration does not automatically establish permission for an ongoing newsletter. A customer record also needs more context than a name and an email address.

For each group, check the source, the permission record, the type of communication requested and any subsequent opt-out. Then ask whether this particular launch fits those expectations.

BulkMail’s permission policy requires proven permission. Its forms can record the consent wording shown to a subscriber, together with supporting details such as the date and time. Keep equivalent evidence for contacts collected elsewhere; importing an address does not create that evidence.

For South African businesses, POPIA includes a limited existing-customer provision for electronic direct marketing. It has conditions: the details must have been obtained in the context of a sale, the marketing must concern your own similar products or services, and the customer must have been offered appropriate opportunities to object at collection and in subsequent marketing. It is not blanket permission to email every previous customer about anything. Continue to follow BulkMail’s permission policy when preparing your campaign.

Ready to proceed: You can explain why each group belongs in the campaign and produce the supporting records. Contacts with unresolved permission stay out of the launch audience.

Around two weeks before launch: verify the addresses you intend to use

Once permission and relevance are established, review the condition of the selected addresses.

Prioritise older permitted contacts, newly imported lists and groups associated with previous delivery problems. Begin with your existing records and campaign reports so you can identify where additional checking is needed.

BulkMail’s email address verification can identify issues such as invalid address formats, invalid domains, duplicates and potentially risky records. Its reporting helps you decide what to keep, investigate or exclude before the campaign is sent.

Keep the work focused on your intended audience. There is little value in paying to verify records that are unrelated to the launch or that you have no permission to contact.

Verification is a useful pre-send check, not a guarantee of future delivery or inbox placement. It also does not make a purchased or borrowed list acceptable for marketing.

Ready to proceed: Verification results are available and have been reviewed before you finalise the audience size or sending plan.

Ten days before launch: turn the results into clear decisions

A verification report only becomes useful when the findings change your campaign audience.

Use a simple decision framework:

A catch-all result needs particular care: a domain may accept mail for any address without confirming that the specific mailbox exists. Do not treat that result as confirmation of a usable recipient.

Shared business inboxes should not be rejected simply because they are shared. Review their permission, purpose and relevance rather than assuming they behave like an individual subscriber.

Keep suppression separate from deletion. Suppression prevents sending within its applicable scope; deleting a record is a different action. Do not override an unsubscribe or other exclusion when importing an updated spreadsheet.

Ready to proceed: Every unresolved record is either investigated or excluded. Nothing remains in the send merely because the team wants a larger audience.

One week before launch: check the sender and test the email

Address verification and sender authentication are different checks. Verification concerns the recipient address; authentication helps receiving systems assess whether your sending setup is authorised.

Ask the person responsible for your domain to confirm that SPF, DKIM and DMARC are correctly configured for the platform sending your campaign. Leave time to investigate authentication failures or other delivery warnings before launch day.

Check that the sender name is recognisable and that replies go to a monitored inbox. Include clear business identification, contact details and an accessible unsubscribe link in every marketing email.

Then test the complete journey on a phone: read the message, follow the main call to action and check the destination page. For an audience in South Africa, make the email and landing page practical on a mobile connection. Keep images lightweight and put essential information in readable text rather than only inside a promotional image.

Test the unsubscribe process using a test contact and confirm that the resulting preference is recorded correctly.

Ready to proceed: The sending setup has been checked, the message works on mobile, and the main action and unsubscribe process have been tested.

Five days before launch: check how new subscribers join

Do not stop at the existing list. Review the forms that will collect new contacts during the launch.

Make the sign-up promise specific. Someone requesting an announcement about one product should understand whether they are also subscribing to ongoing marketing. Give them a separate, clear choice when offering a regular newsletter, rather than automatically adding it to an enquiry or registration.

Use clear marketing-consent wording, leave optional consent boxes unticked and make the privacy notice easy to access. Collect only the details needed for the stated purpose.

BulkMail’s forms support consent recording and bot protection. Double opt-in workflows can add a confirmation step in which the subscriber clicks a link sent to the supplied address. This helps confirm access to that inbox, but it does not replace clear wording about what they are signing up to receive.

Test the form yourself on a phone. Check where the record is saved, which preferences are applied and what happens next. Where double opt-in is used, confirm that the marketing sequence waits for confirmation.

Review suspicious entries and ask people to confirm suspected address mistakes rather than silently changing an address to a guess. Include newly collected contacts in your pre-send checks before adding them to the launch campaign.

Ready to proceed: A test sign-up creates the intended record, retains the permission details and receives only the communications selected.

Three days before launch: match the message to each audience

Segmentation does not need to become a complicated production exercise. Start with the meaningful differences between the groups you have approved for sending.

For example, a Gauteng distributor announcing a new equipment range could give existing trade customers a concise stock update and quotation request. New subscribers who specifically requested launch information may need a clearer explanation of the range, its intended uses and how to enquire.

Both versions can use the same basic template. Change the opening, the supporting detail and the next step to suit the reader.

For a larger campaign, discuss whether a staged send is appropriate. Starting with an engaged, permission-based group gives the team an opportunity to review delivery before releasing further scheduled groups. Do not use smaller batches as a workaround for unclear permission or unresolved address problems.

Assign someone to approve the final recipients and someone to monitor the campaign. In a small team, that may be the same person.

Ready to proceed: Each audience has a relevant message, a clear next step and a named person responsible for the send.

Launch day: watch delivery, not just opens

Start by reviewing delivery failures and any available complaint signals. Then look at replies, clicks, enquiries and the action the campaign was intended to generate.

Do not rely on open rates alone. Email privacy features can load tracking content without a person reading the message, so an apparent open is not reliable proof of interest.

Compare the results with your recent, comparable campaigns rather than judging the launch only by how many messages were sent. Where several groups are being sent separately, review each group rather than allowing an overall average to hide a problem.

Investigate an unexpected increase in delivery failures or complaints before releasing remaining groups. A successful first group does not establish that every other group is equally suitable.

Keep the monitored reply inbox covered so that genuine questions and requests are not missed while the team watches the campaign report.

Ready to continue: Delivery is behaving as expected, warning signals have been reviewed, and someone is responding to interested recipients.

Forty-eight hours later: improve the list, not just the report

Treat the first review as a starting point. Some enquiries and sales will need a later follow-up before you can judge the wider outcome.

Review performance by contact source. Which sign-up forms produced usable, permission-based subscribers? Which groups generated relevant enquiries? Which imports or forms need attention before the next campaign?

Track new permission-based subscribers, unsubscribes and address-quality exclusions separately. Measure the change in your usable, permission-based audience against its starting size—not simply the number of records added. Excluding invalid or suppressed contacts from the campaign audience should not be confused with a failure to attract new subscribers.

Choose practical improvements that the findings support: fix a weak sign-up form, tighten an import process that loses permission information, or improve the relevance of your newsletter between launches.

Keep acquisition focused as well. Add a clear newsletter invitation to relevant product pages and supporting website articles. Explain the ongoing value, such as product guidance or trade updates, and let visitors choose to subscribe.

Do not automatically move launch-only subscribers into a general newsletter. Invite them to make that additional choice where your existing permission allows the invitation.

Ready for the next campaign: Your team has recorded what needs to change, assigned responsibility and scheduled a later review of enquiries and sales where needed.

Give your launch a prepared audience

Your product-launch email should start a useful conversation, not become an emergency clean-up exercise.

Establish permission, verify the intended addresses, respect subscriber choices and make the announcement relevant to each audience. Keep collecting new subscribers through clear sign-up forms and continue the communication you promised between launches.

BulkMail’s permission-management tools and email address verification support that preparation, alongside the platform you use to organise and send your campaigns.

Planning a product or service launch? Ask the BulkMail team about reviewing permissions and verifying your intended audience before you schedule the announcement.