Transactional email dispatch

Apps need to send receipts, resets, and confirmations reliably. When an upstream event calls for a message, the agent reads the recipient and context, selects the approved template, and sends it through Resend. It records the send and the returned message id against the source record. Emails missing a valid address, hitting a suppression flag, or falling outside the approved template set are held for a developer rather than sent blind. Routine system mail keeps flowing while risky sends wait for a person to look them over first.

Delivery and bounce tracking

A sent email is not a delivered one. The agent reads the delivery, bounce, and complaint events Resend reports, matches each back to the original message, and updates that record's status. Hard bounces trip your approved rule, so the agent marks the address unusable and, past the retry limit, stops trying it. Repeated complaints or a spike in failures are escalated to a developer with the affected addresses. Teams see true delivery outcomes instead of assuming every send arrived, and dead addresses stop getting hit repeatedly.

Suppression list handling

Sending to people who bounced or complained hurts deliverability. The agent reads bounce and complaint signals from Resend and adds those addresses to your suppression list under the rule your team approved. Before any new send, it checks the recipient against that list and skips suppressed contacts. Requests to remove an address from suppression, or edge cases like a corporate domain block, are routed to a developer to decide rather than cleared automatically. Your sending reputation stays protected while removal decisions remain in human hands.