A quiet database can make a broad send look tempting. The count is visible; the reason each person should receive the message may not be. Before volume becomes the plan, establish that contact is appropriate, the records are usable and the offer meets a real customer need.
Check contact status before relevance
Confirm the source of each record, the permitted contact basis that applies, opt-outs and other suppression rules. If status is missing or contradictory, set the record aside for review rather than assuming old contact equals current permission. Requirements vary by jurisdiction and channel; get appropriate advice where the rules are uncertain.
Next, check recency and identity. Can the business tell whether a record is a customer, prospect, former contact or duplicate? Are there open enquiries, current quotes or active service cases that need another route? A database segment should have a definition another person can reproduce.
Prove there is a useful offer
Name the customer situation the message addresses: an upcoming maintenance interval, a replenishment need, an expiring service arrangement or a genuinely relevant product update. If the only rationale is that a person appears on a list, the campaign has not established usefulness.
Make suppression, segmentation, copy review and final approval visible. Keep the audience snapshot, exclusions and campaign version so that a later performance report describes what was actually sent.
A practical inspection
- Record the source and permitted contact status of each segment.
- Apply suppression before selecting recipients.
- Separate customers, prospects, open opportunities and service cases.
- Define a relevant offer for each group.
- Name copy, audience and final-send approvers.