Reply Inbox Email Workflow in Mailbase
A product guide to the Mailbase reply inbox for teams that want campaign replies, support context, and follow-up work in one place.
On this page · 7 sections
Overview
Mailbase includes a shared reply inbox with real threads from inbound events. Threads can be tagged, archived, starred, assigned, filtered into saved views, and connected to private notes, follow-up reminders, pipeline stages, and AI task review.
Team workflow
The inbox is built for shared ownership. Teammates can assign threads, leave private notes, save filtered views, and track needs-reply or SLA-overdue work without moving the conversation into a separate CRM first.
Thread-level pipeline fields make hot leads visible with stage, value, and next-step context. Follow-up tasks keep reminders attached to the same conversation.
- Thread assignment
- Private internal notes
- Saved inbox views
- Needs-reply and SLA filters
- Pipeline and follow-up tasks
Safe replies
Reply sending stays workspace-scoped and goes out through the workspace's own sender identity on Amazon SES. Collision detection warns when another teammate is active in the composer.
AI tasks can draft replies from selected threads, but the teammate keeps review control before anything is sent.
- Workspace-scoped reply routes
- Reply collision detection
- AI draft tasks
- Tags and archive controls
Common mistakes
- Choosing a tool before deciding who owns deliverability.
- Treating DNS authentication as a one-time checkbox instead of an operating baseline.
- Mixing product-critical transactional email with experimental marketing sends, with no clear boundary.
- Trusting headline metrics (like open rate) that privacy proxies now inflate.
Related guides
More on reply inbox email workflow and the surrounding product workflow: