MAILRAFT / PRODUCT

Use cases

MailRaft is built for teams whose email reputation and legal exposure matter: African startup builders shipping production products, agencies running client work, and operational business teams that need auditable outbound communication.

Customer support with cited knowledge

An inbound customer question is read, the AI drafts a reply grounded in the tenant uploaded product and policy docs with chunk citations, the owner reviews the draft against the citations, approves it, and the system sends through the tenant approved provider. The suppression table and recipient allowlist run before any provider call.

• Measurable support quality: every reply ships with the citations the agent used.
• Reviewer workload drops without sacrificing control.
• Tone and policy stay consistent across teammates.

Transactional notifications tied to real actions

Account verification on signup. Security alert on password change or new-device sign-in. Approval-request notification when the owner has configured an approval workflow, with a signed deep-link that cannot be replayed after use.

• Each notification is tied to a specific operation ID.
• Approval, dispatch, provider acceptance and delivery are separate states. The application currently ingests Bounce and Complaint feedback; Delivery and Reject ingestion is not implemented.
• Nothing is sent on a schedule; triggers are explicit tenant actions.

Operations with structured approvals

Procurement, financial confirmations, legal correspondence, invoices and contract follow-ups all run through the same approve-then-send pipeline. Each message carries an operation ID the owner can trace end-to-end.

Research without turning discovery into consent

Lead-research adapters surface public contact information with explicit budget and runtime caps. Research records are never treated as marketing consent; outbound reach-outs still require full approval, suppression check and compliance disclosures.

Developer workflows

Developers call the REST and MCP surfaces from their own tooling under scoped bearer tokens. Provider secrets never travel through a browser; the dashboard uses a same-origin session with host-only cookies.

Multi-mailbox agencies

Tenant boundaries and suppression are enforced server-side. Separate tenant sending identities and DKIM onboarding remain planned; the restricted SES lane uses one platform identity.

What MailRaft is not for

• Not for cold outreach, purchased or scraped lists.
• Not for bulk promotional broadcasts.
• Not for sending on behalf of a tenant without a specific owner-approved operation.