In many companies, the team now has two kinds of members: coworkers, and AI agents. An agent handles a task from start to finish without waiting to be asked: it reads a form, generates a document, updates a customer record.
At some point, almost all of these agents need the same thing: to let someone know. Send the invoice, confirm the appointment, follow up on the quote. And that's often where things go wrong: an agent sending from a personal mailbox ends up in spam, doesn't handle unsubscribes, and nobody knows what it sent. That's Mailpro's role: giving your agents a real sending service.
Here are ten ideas, starting with the most useful: transactional messages, the ones a single recipient is waiting for, at the right moment.
Transactional messages: where agents shine
1. The invoice, sent as soon as it's generated
Your billing agent creates the invoice at the end of an order or a month of service, then sends it to the customer with a clear message. There are two ways to do it:
- through the MCP server, the email contains a link to the invoice (stored in your billing software or customer portal): the MCP server doesn't send attachments, for security reasons;
- through the Mailpro API, an agent built by your team can attach the PDF directly (up to 10 MB per file).
2. Appointment confirmations and reminders by SMS
An appointment booked online: a confirmation SMS right away, then a reminder the day before with the time. Fewer missed appointments, and nobody had to think about it.
3. Following up on an unsigned quote
Seven days after a quote goes out, the agent checks whether it has been signed; if not, it sends the customer a short, personal follow-up that mentions what the quote was for.
4. The unpaid invoice reminder
On the due date, the agent checks your accounting and sends a polite reminder only to the customers concerned, with the payment link. A second, firmer reminder can follow, which you approve before it goes out.
5. Replying to a contact request
A form comes in at 10 p.m.: the agent replies within a minute with the information requested, adds the contact to the right list and lets the sales rep know.
6. The satisfaction survey after delivery
Three days after delivery, an email with a single question. Negative answers go to the team; positive ones get an invitation to leave a review.
Follow-up and relationship sends
7. Welcoming a new customer
New account, new order: the agent adds the contact to the Customers list and sends them the welcome template. Mailpro's automated emails already handle fixed sequences very well; the agent adds personalization based on context.
8. Back in stock
A product is available again: the agent finds the customers who were waiting for it and writes to them, and only them.
9. The Monday report for the team
Every Monday, the agent reads the week's statistics (opens, clicks, unsubscribes) and sends a five-line summary to the marketing team.
10. The newsletter, prepared but not sent
The agent puts together the monthly newsletter from your news, creates the campaign… and stops there: it waits for your approval. That's the right rule for bulk sends.
Why your agents need a real sending service
| What an agent needs | What Mailpro provides |
|---|---|
| Reaching the inbox | Sending from your domain, SPF, DKIM and DMARC, managed IP reputation |
| Staying on track | Approval before sending, or direct sending within a daily cap you set, assistant by assistant |
| Leaving a trail | A log of each agent's sends, and one click to suspend all sends |
| Following the rules | Unsubscribes and bounces excluded automatically |
| Email and SMS | Both from the same account, with the same contacts |
| Protected data | Hosted in Switzerland |
How to connect your agents
- No coding: in n8n, the MCP Client Tool node gives your agent Mailpro's tools; in Copilot Studio, Mailpro is added as an MCP tool for your agents.
- In your own code: the Mailpro API (email, SMS, contacts, webhooks) plugs into your own agents, with attachments and delivery tracking. Your developers can even work with help from a connected assistant: Claude Code, Cursor, VS Code, Codex.
- In-house: a model installed on your own servers can send too, see self-hosted AI.
Our advice: keep each new agent in approval mode for a few days. You see what it wants to send before letting it work on its own, with a cap suited to its job.
Everything on the topic: AI in Mailpro.
