Close handles sequences and CRM together. Bad records damage both.
Close is a CRM built specifically for outbound sales teams β it combines contact management, calling, and email sequencing in a single interface. That unified model is efficient, but it introduces a compounding risk: a bad email record does not just affect one campaign. It sits in the CRM and can be enrolled in future sequences, imported into other tools, and counted in pipeline data until someone actively removes it.
When a contact bounces in Close, the damage is double. The sending domain takes a reputation hit, and the CRM contact record is now a piece of dirty data that requires cleanup. Sales teams using Close often do not separate their "CRM hygiene" work from their "sending health" work β they are the same problem.
Verifying before a sequence runs in Close is not just about protecting deliverability. It is about keeping the contact database accurate from the moment records enter it.
What to check before Close sequences run.
Close contacts come from multiple sources β manual entry, CSV import, CRM migration, lead enrichment, and API integrations. Each source carries a different risk profile. Before any contact enters a sequence, these fields should be checked.
| Field | Why it matters |
|---|---|
| The address that enters the sequence β needs to be valid and deliverable | |
| Domain | Determines catch-all status, MX validity, and whether the company domain is active |
| Source | CSV import, API sync, manual entry, migration from another CRM β staleness varies by origin |
| Suppression status | Prior bounces and opt-outs should be flagged before sequence enrollment |
| List age | Contacts added to Close more than 90 days ago should be re-verified before sequence enrollment |
The risk each signal type creates.
Sequence enrollment in Close is often driven by Smart Views or filtered contact lists. Understanding what each signal type does to your campaigns helps you build the right filtering rules before enrollment.
| Signal | Delivery behavior | Risk to Close sequences |
|---|---|---|
| Invalid | Permanently rejected | Hard bounce β reputation damage to your sending domain |
| Catch-all | Domain accepts all addresses, mailbox uncertain | Uncertain delivery β inflates bounce risk and distorts sequence performance |
| Role-based | Shared inbox (info@, sales@, hello@) |