Reply Agent

Triages inbound replies to your transactional + marketing emails into one of three actions: auto-respond, draft-for-approval, or route-to-human.

How replies reach PAD

Each outbound email's Reply-To is set to a workspace-scoped inbound address. Resend Inbound forwards incoming messages to /api/webhooks/inbound-email which calls the Reply Agent.

Triage decisions

• auto_respond— common question with a templated answer (e.g. "when does my trial end?") → PAD sends back the canned reply tagged with the original send.
• draft_for_approval — useful but needs a human eyeball; PAD creates an insight with a drafted reply.
• route_to_human — sensitive, off-topic, or a billing dispute → notifies the workspace (Slack / digest) and leaves the message in the inbox view.

Status

Pipeline is wired end-to-end; activation is gated on Resend Inbound being verified for your domain (MX records + Resend dashboard approval).