The short answer
Commune gives you three layers of visibility: a dashboard with per-inbox metrics, webhook events for every email lifecycle event, and API endpoints to query delivery data programmatically. For production systems with multiple agents, build a monitoring webhook handler that tracks key metrics and fires alerts when something goes wrong.The Commune dashboard
Every inbox in the Commune dashboard shows real-time delivery health:- Messages sent — total outbound over the last 24h, 7d, 30d
- Delivery rate — percentage of emails that reached the recipient’s mail server
- Bounce rate — hard bounces (invalid address) and soft bounces (mailbox full, temporary failure)
- Complaint rate — recipients who marked your email as spam
- Warmup progress — if the inbox is still warming up, current daily limit and utilization
Webhook lifecycle events
Commune fires webhook events for every stage of an email’s lifecycle. Subscribe to these on your inbox:message_id, inbox_id, timestamp, and event-specific metadata. Bounce events include the bounce type and diagnostic code. Complaint events include the feedback type.
Building a monitoring handler
Here’s a webhook handler that tracks metrics per inbox and fires alerts when thresholds are exceeded:Key metrics and thresholds
These are the numbers that matter. If you track nothing else, track these:Audit logging pattern
For compliance and debugging, store every outbound email with enough context to reconstruct what happened:TypeScript
context field is the most valuable one for debugging. When an agent sends an email, record why: “Replying to support ticket”, “Sending follow-up after 24h no response”, “Escalation to manager”. Six months from now when you’re investigating a complaint, this field tells you what the agent was thinking.
Health checks across all inboxes
If you’re running multiple agent inboxes, run a periodic health check:Related
Delivery Monitoring
Full delivery monitoring API reference and dashboard guide.
Webhooks
Webhook event types, payload schemas, and signature verification.
What happens if my agent sends too many emails?
Rate limits, burst detection, and automatic reputation protection.
Per-agent inboxes
Isolate reputation per agent so one bad sender doesn’t take down the rest.

