Official disclosure: we are the EngageLab Email team. This tutorial uses the EngageLab Email CLI for mailbox ingestion, but the reliability pattern is vendor-neutral: persist the review work and the read cursor in one transaction, then resume from the last committed cursor.
An email agent that reads a support thread usually has a small but dangerous failure window:
It polls a batch of inbound messages.
It creates review tasks from those messages.
It advances the polling cursor.
The process crashes between any two of those steps.
If the cursor is saved first, a crash can make a message disappear from the next poll. If the review task is saved first but the cursor is never saved, the same message can be delivered again. The safe default is at-least-once reading plus durable idempotency , not a claim of exactly-once email sending.
This post builds that boundary for a support agent.…