This is the product surface you use when the system already knows what should be mailed and just needs a reliable way to turn that decision into a physical piece.
Submit a PDF, postcard creative, or batch mailing job through an API and mailbox.bot handles printing, stuffing, postage, and mailing. The key difference from legacy mail vendors is that this can live directly inside an agentic workflow instead of behind a separate portal process.
Any system event, agent decision, queue item, schedule, or campaign rule can create a physical mail action.
Single letters, postcards, legal notices, document packets, certified mail, and higher-volume mail jobs.
The send is an API call, so your existing workflow owns approvals, timing, payload generation, and retries.
Submitted, ready, mailed, delivered, and related fulfillment proof can return as structured status changes.
Teams automating outreach, follow-up, compliance mail, legal operations, customer notices, and direct mail workflows.
Because the moment a human has to switch tools, the mail lane becomes slower, harder to personalize, and harder to attach back to the system of record.
An agent, internal service, or operator workflow assembles the document, address data, and any approval context.
mailbox.bot accepts the mail request directly from software instead of requiring a manual portal session.
The system gets status updates and proof so the physical step stays visible inside the workflow.
A follow-up task, CRM update, or second touch can depend on the mail status instead of waiting on human checking.
The difference is not just developer convenience. It changes what kinds of workflows are practical.
| Dimension | Traditional mail | Agentic mail |
|---|---|---|
| Send path | Operators upload files through a GUI or a separate campaign tool. | Mail is just another operation in the workflow stack. |
| Approvals | Approval happens outside the system in ad hoc email or chat. | Approval rules can stay inside the same workflow that generated the send. |
| Personalization | Personalization is constrained by the vendor interface or batch structure. | The payload is generated by your own logic before the API call. |
| Status handling | Teams check a dashboard later to see what happened. | The workflow can listen to status and react immediately. |
| Future loop closure | Inbound responses are a separate problem. | The outbound surface is designed to pair with inbound mailbox automation later. |
Use the deeper proof pages for vertical value. Keep the homepage clean. Let the agentic thesis do the framing.