Comment by schappim
14 hours ago
I'm 100% for this, but I think you can go even more granular than "gives agents their own inboxes".
Thanks to Action Mailbox in Rails[1], I give all my records email addresses. Eg let ecommerce "order" records accept forwarded emails that are pinned as comments. It opens you up for doing things like forwarding a purchase order and having the PO number pulled out and attached to an order, or forwarding tracking information from a supplier and having it attached to a "supplier order" etc.
In my personal life I have individual email addresses for all my utilities and emails automatically get filed away.
If this idea tickles your fancy, I opensourced Emitt[2], an inbound email processing server with LLM-powered automation.
1. https://guides.rubyonrails.org/action_mailbox_basics.html
That looks really interesting! Thanks for writing and sharing it!
Fancy == tickled
The only problem I have experienced few times with those unique email addresses is, sometimes they/utilities ask me to email from my official email address, and my setup is a catch-all, so I have to log in my pc at home, set up that address, send email.
That's a problem of your provider needing you to have received email at a particular address (or else doing whatever you do on the PC at home) before you can send from it; not something inherent in unique addresses.
I just type in whatever address I want to send from, and then as long as the domain is verified in SES it'll go through.