Create policy exclusions before any spend
An exclusion produces excluded/skip with the selected reason, performs no provider work, and uses zero credits.
Choose a type
Exact email matches one normalized address, domain matches a complete domain, and TLD matches a normalized top-level domain.Choose the scope
Use this workspace for a client-specific rule, or every workspace for an organization-wide policy.Add a useful reason
Explain the policy decision without placing sensitive personal data in the note.Save and audit
Future eligible imports and verifications apply the rule before capacity or credit reservation. Rules remain searchable, exportable, and removable.
Import or export exclusion rules
The exclusion importer accepts UTF-8 CSV up to 1 MB.
kind,value,reason,scope
EMAIL,[email protected],Prior opt-out,workspace
DOMAIN,example.invalid,Internal suppression,organization
TLD,.test,Test-only domain,workspacekindandvalueare required.kindisEMAIL,DOMAIN, orTLD.reasonis optional.scopemay beworkspaceororganization; the dashboard’s selected import scope is used when appropriate.- Existing normalized rules are counted rather than duplicated.
- Exports use the same
kind,value,reason,scopecontract.
Schedule an all-or-nothing hygiene run
Schedules repeat a saved list every 30, 60, or 90 days at a chosen local time and timezone.
Choose a saved list
Only one active run is allowed per list, so overlapping work cannot double-spend.Set recurrence and local time
Choose 30, 60, or 90 days, then confirm the IANA timezone shown in the dashboard.Set maximum credits
The maximum must cover the entire candidate snapshot. It is a hard ceiling, not a target.Authorize automatic spending
Check the explicit confirmation that allows this schedule to spend up to the displayed maximum per complete run.Enable and monitor
Review next-run time, last-run state, credits used, skip reason, and the change report.
Understand schedule behavior and change reports
- Candidates are snapshotted before provider execution.
- Missed intervals collapse to one run, then advance to the next future occurrence.
- Transient provider or capacity failures are retried.
- Three consecutive permanent failures automatically pause the schedule.
- Deleting or archiving the source list pauses future work.
- Completed runs report newly invalid, newly risky, recovered, unchanged, and excluded records.
Pause a schedule before a major list-policy change, membership transition, or client offboarding. When you resume it, recheck the maximum credits and next-run time.
Configure useful, privacy-safe alerts
Messages contain deep links and aggregate counts—never submitted addresses or source columns.
| Preference | Default | Behavior |
|---|---|---|
| In-app | On | Retained for 90 days. |
| Failures | On | Jobs or exports that need attention. |
| Low credits | On | At most once per UTC day after crossing the threshold. |
| Skipped schedules | On | A cap, balance, or source policy prevented the full run. |
| Completions | Off | Optional successful-work summaries. |
The default low-credit threshold is 20% of the current allowance or balance with a 20-credit minimum. Notification delivery failures never change the originating job or financial record.
Troubleshoot automations
An exclusion did not match
Check the rule type, normalized value, organization/workspace scope, and active workspace. A subdomain is not the same complete domain unless that is the value you added.
A run was skipped
Read the run’s skip reason, then compare the candidate estimate with both the schedule maximum and current available credits.
A schedule paused itself
Confirm the list still exists and is active, review the three most recent failures, correct the permanent cause, then resume deliberately.