Guide
Emails and retries
How participant messages, idempotency, suppression, and bounded retries work.
Participant messages
Verification and status emails are required participant flows. Marketing updates honor unsubscribe, suppression, and deletion state. Template tests go only to the signed-in creator.
Bounded delivery
AgentList uses a platform-owned provider with a stable idempotency key. Failed sends retry at 1 minute, 5 minutes, 30 minutes, and 2 hours through bounded dashboard or maintenance requests; after five attempts the failure remains visible for review.
Provider credentials and retry payloads are kept out of source. Participant links in retry payloads are encrypted at rest.