Onboarding playbooks by use case

Different teams should not onboard the same way. The fastest setup depends on what problem you are trying to solve first.

Playbook: clean an existing list

Use this when you already have a file and want a fast operational win.

1. Verify one known address manually.
2. Upload a small sample file.
3. Run analysis before full verification.
4. Process the full list after the sample looks correct.
5. Export and action the results by status.

Best next reading:

• Upload Your First List
• Results and Statuses

Playbook: recurring hygiene

Use this when the goal is not one cleanup but a repeatable process.

1. Connect the source system.
2. Confirm the right lists or audiences are visible.
3. Define who reviews risky and unknown outcomes.
4. Monitor credits and cadence.

Best next reading:

• Integration Troubleshooting
• Credits and Billing

Playbook: API validation at signup

Use this when you want bad addresses blocked before they enter the system.

1. Create a dedicated API key.
2. Test the single-email endpoint.
3. Add graceful retry and timeout behavior.
4. Decide how the application should handle ambiguous results.

Best next reading:

• Verify Your First Email
• Webhooks and API Quickstart

Playbook: agency or multi-client operations

Use this when one team manages multiple lists or client environments.

1. Separate credentials by environment or client.
2. Define who owns suppression policy.
3. Standardize CSV preparation before every upload.
4. Use the same result interpretation policy across accounts unless there is a reason not to.

This reduces support load and keeps operations predictable across accounts.