AI & automation
Can Your Software Send Physical Mail Automatically?
Stop retyping documents and addresses when you prepare physical mail. Keep approval, order charges and delivery records connected through Iris Postal Forms.

The short answer
Let your software prepare the document and mailing details, then have a person approve the PDF, addresses, service and price. Keep the order ID and carrier records with that approved version. If a submission is uncertain, check it before retrying so a dropped connection doesn't turn into a second paid mailing.
- Approve the document, recipient, service and total together.
- Treat a prepared order and a submitted mailpiece as different things.
- Check uncertain submissions before retrying.
Choose the required mailing service
A physical letter is a paper document delivered to a postal address. Your software can prepare the PDF and order details. A printing and mailing service handles the paper.
Even when a letter is ready, your team may still copy its address into another system, pick mailing options and dig up the tracking record later. Connecting those steps cuts that repeated handling, as long as the document and the mailing evidence stay together. Start by writing down why you're mailing the letter and what proof your process needs. A physical mailpiece, ordinary correspondence, carrier tracking and a signed return receipt each serve a different purpose depending on the business or legal situation.
USPS describes Certified Mail and Return Receipt as separate services, so name the option you need instead of calling everything 'tracked'. The process owner should set the document and timing requirements before a developer picks the integration. A software event alone can't tell you whether a particular notice is appropriate.
Connect the workflow to Iris
Iris Postal Forms offers browser, REST API and MCP workflows for preparing physical letters. Iris arranges printing through Lob and delivery through USPS. Place a browser order first so you know which fields and review screens your connected workflow has to keep. Record the document version, sender, recipient and selected options as a proposed order.
Before you use the API or MCP connection, read its current documentation and check your account permissions. Give the tool only the preparation and submission actions you've agreed on. A chat message telling an agent to mail something is not an approval policy. Keep test records clearly separate from orders that can cost money.
Review the order before submission
An MCP-connected application can prepare your document, address and mailing options. Before anything is submitted, an accountable person reviews the content, their authority to send it, the address suggestions, the service and the calculated price. Show the full PDF next to the proposed address and the itemized total.
Missing pages, conflicting recipient details or an unavailable mailing option should hold the order. An address suggestion stays a suggestion until the reviewer confirms the recipient. If the PDF or the service changes after approval, cancel the old approval so the order that goes out is the one the person actually looked at. Keep the final decision and the version it approved.
Keep mailing records together
Eligible orders can include Certified Mail and electronic return receipt. Store the approved document, the order record, tracking information and any carrier events under your record policy. Use separate states for prepared, approved, submitted, awaiting carrier information and needs investigation. Save the provider's order reference as soon as you have it.
If the connection times out after submission, check the provider's record before you resend. A retry can buy a second mailing. Carrier events tell you where the mail is. The source document tells you what the organization approved sending. Give unresolved events an owner instead of leaving them in an error list nobody watches.
This is also where avoidable cost shows up. Someone has to rebuild the order history, fix an address or investigate a duplicate charge. Measure preparation and reconciliation time per completed mailing, then add provider fees, review, integration charges and maintenance. Any margin gain comes from less handling or fewer repeat costs after those expenses are counted.
An illustrative workflow
An office prepares a routine account letter from an approved template. The reviewer spots a new suite number and corrects the address before approving the PDF and price. The order request then times out. An operator checks the provider, finds the order exists, links its ID and resumes status monitoring. Nobody assumes that a missing response means no order was created.
Checks before using the workflow
An online order still needs physical printing and carrier delivery. A checkout confirmation is not USPS acceptance or delivery. Whether a mailing is legally sufficient, and by what deadline, depends on the matter itself, so get that guidance outside the integration. Keep documents and carrier records under your access and retention policy.
- The final PDF, sender and recipient are visible during approval.
- The selected service and total are confirmed for this order.
- Submission has a traceable status and a provider reference when one exists.
- An operator can investigate an uncertain order without blindly resubmitting it.
Sources and further reading
Make this useful for my team.
Bring us a task you spend too much time on. We can look at where the time goes, what AI could handle, and whether the benefit would cover the cost. We reply within one business day.


