Collection workflows start in a billing system, CRM, lender platform, or agent queue. mailbox.bot lets that system generate the letter, pause for policy or human approval, send certified mail through the API, and write delivery events and proof metadata back to the account.
Most collection systems can generate the demand letter, but the postal mailing step still involves manual printing, post office trips, or a separate vendor portal. mailbox.bot eliminates that gap: your collections agent or billing system POSTs a PDF and we handle certified mail fulfillment. Tracking, delivery events, proof photos, and metadata are captured digitally.
An invoice crosses an aging threshold, a payment plan defaults, or a collections queue flags an account. The system decides — not a human remembering to send mail.
A demand letter PDF generated from the account data: balance, terms, cure period, payment instructions, and required legal disclosures.
One API call with mail_class=certified after the account, letter, cost cap, and approval policy are set. mailbox.bot validates the document, prepares the piece, applies certified postage, and hands it to USPS.
USPS certified mail tracking number, proof photos when the piece is prepared or mailed, delivery events, and optional signed return receipt.
Delivery confirmation updates the account record. If no response within the cure period, the system can trigger escalation: second notice, referral, or legal action.
Collections and state-specific workflows often need evidence that a notice was mailed. Certified mail tracking and delivery events provide a stronger audit trail than email alone.
Billing system or collections agent flags the account as eligible for a demand letter based on aging, balance, or payment history.
System assembles the PDF with account details, balance, cure period, payment instructions, and any required disclosures.
POST the PDF to mailbox.bot with mail_class=certified, metadata linking it to the account, and requires_approval=true when policy calls for review. Tracking appears once the piece is mailed.
Delivery events update the account. No response within cure period triggers the next step: second notice, legal referral, or writeoff.
The legal requirement is the same. The operational cost is not.
| Dimension | Traditional mail | Agentic mail |
|---|---|---|
| Letter generation | Staff manually creates or tweaks each letter. | System generates personalized letters from account data automatically. |
| Mailing | Someone prints, stuffs envelopes, and goes to the post office. | One API call per letter. Certified postage applied automatically. |
| Proof of service | Paper receipts filed manually. Easy to lose or misfile. | Digital tracking, lifecycle events, and proof metadata logged to the account record automatically. |
| Follow-up | Someone checks manually whether the debtor responded. | System tracks delivery and triggers escalation rules on deadlines. |
| Scale | Sending 200 demand letters takes days of staff time. | Sending 200 demand letters takes minutes of compute time. |
Use the deeper proof pages for vertical value. Keep the homepage clean. Let the agentic thesis do the framing.