Join the waitlist when your agent needs its own real mailing address with street address + mailbox number. The live inbound path turns mail from addresses you already control into structured workflow input.
The default mailbox.bot inbound path uses the addresses operators already control. An assistant, office, PO box workflow, or virtual mailbox provider forwards scans, photos, PDFs, and notes to a private alias so the workflow continues after the physical mailbox instead of stopping there. New AI agent real mailing addresses are waitlist-first while they roll out, with planned street address + mailbox number, scan/photo intake, OCR/classification, and agent notifications.
Official correspondence, reply mail, customer documents, legal notices, compliance mail, and any other postal mail that still matters in the real world.
Photos, scans, extracted text, structured metadata, and a trigger for whatever rule or agent should act next.
Classify it, extract data, route it to a workflow, request another action, escalate to a human, or generate a physical response.
Because campaigns, notices, and business mail do not end when they are sent. They end when the reply or resulting paper trail gets handled too.
Most mailbox products are human GUI tools with scans as documents. mailbox.bot treats forwarded scans, PDFs, and notes as workflow input with rules, APIs, and machine-readable state. A new mailbox.bot real mailing address is a separate launching-soon waitlist/private-beta path with scan/photo intake and agent notifications.
Teams managing legal, finance, acquisitions, compliance, or high-value paper flows that still originate or return by mail.
If you need a new mailing address, virtual mailbox, street address + mailbox number, scan-on-arrival workflow, or agent notifications for an AI agent, register that intent on the waitlist first.
Postal mail lands at your business address, PO box, office, home address, assistant, or virtual mailbox provider.
Send envelope photos, opened-mail photos, PDFs, provider notices, and notes to the account's private mailbox.bot alias.
Rules and agents decide who should act, what should be extracted, and whether a human approval step is needed.
The workflow can generate a follow-up letter, record a deadline, update a system, or start the next operational step.
Both can show you scans. Only one is designed to let software keep operating after the scan arrives.
| Dimension | Traditional mail | Agentic mail |
|---|---|---|
| Primary user | A human logging into a dashboard to check documents. | A workflow or agent that treats the mail item as the next event in a process. |
| Scan handling | Scans are files to be read later. | Scans are structured inputs that can trigger rules and actions immediately. |
| Decisioning | Humans decide what to do after reading the scan. | Agents and rules can classify, route, and respond with human checkpoints only where needed. |
| Outbound follow-through | The response mail is a separate manual task. | The system can generate and send the response from the same workflow. |
| Operational memory | Meaning lives in inboxes, notes, and screenshots. | Meaning lives in the workflow state, extracted data, and rule system. |
Use the deeper proof pages for vertical value. Keep the homepage clean. Let the agentic thesis do the framing.