Use Cases
One mailbox per agent.
Every team covered.
A marketing agent nurtures trials. A success agent catches churn before it happens. A billing agent recovers failed payments. Different jobs, same pattern: each agent gets its own mailbox with the policies it actually needs.
Customer Success Agent
Watches usage signals for churn risk and reaches out before customers leave. Policy controls cadence so nobody gets spammed with "just checking in" emails.
- Usage drops? Automatic check-in
- Expansion outreach when adoption spikes
- Saved accounts tracked as attributed outcomes
Marketing Agent
Onboarding sequences, lifecycle nurtures, trial conversion. Policy handles dedup, consent, and cadence. Attribution connects every email to activation and revenue.
- Event-triggered onboarding flows
- Trial rescue when a user stalls at setup
- Lifecycle nudges that respect fatigue limits
Sales Agent
Outbound prospecting and follow-ups with cooldown windows, per-prospect dedup, and suppression lists. The agent mailbox handles replies too, classifying intent and routing next actions.
- Cold outreach with policy-checked follow-up cadence
- Reply intent classification (interested, not now, unsubscribe)
- Meeting booking from inbound interest
Support Agent
This one lives in the inbox. Classifies incoming messages, drafts responses, escalates when confidence is low. Every inbound message gets scanned for prompt injection before the agent sees it.
- Inbound triage with auto-response
- Escalation when intent is ambiguous
- Prompt injection scanning on every reply
Billing Agent
Payment failure sequences and invoice reminders. Policy auto-stops the sequence the moment the invoice is paid (no awkward "pay us" email after they already did).
- Dunning sequences that stop on payment
- Invoice reminders with strict per-customer cadence
- Revenue recovered, tracked as an attributed outcome
Build your first agent mailbox
Sign up, create a mailbox, send a policy-checked email. Under five minutes.
$ npx @molted/cli auth signup