That's the exact opposite of what I'd want. Most small businesses have the same email problem that I always feel like I do. Too many requests come in via email and it's hard to track, discuss, resolve, and (at a later date) reference all that info.
This is what I wanted on MS365:
- Forward an email to a special address. Ex: ryan29@todo.example.com (the TODO address for ryan29@example.com).
- Use Power Automate to create a Teams channel for the email.
- Use Power Automate to post some cards to the channel; one to (optionally) create a Planner Task, one to resolve the topic.
- Notify @ryan29 about the new topic.
- I deal with the topic. If it's long lived or complex, I create a Task. If I need input, I @mention others that can help. If it's simple 5-15 minute thing, I do the work and click the link to resolve the topic.
- When the topic is closed (by link or by closing the related task), the Teams channel is archived and the original email thread gets a reply saying it's done with a link to the Teams channel.
That way all conversation about the task is consolidated into Teams, long lived tasks are tracked via Planner, email stays relatively clean from internal communication, and I don't waste a bunch of time dealing with some 3rd party's idea of optimal workflows or value adds.
The issues I had were that Teams, Planner, etc. have limits on the number of channels / tasks and Power Automate / Teams lacked some functionality that would make it really streamlined.
However, I was close enough after a few hours of playing around that I can't believe something like "adding Slack chat to email threads" is a $1 billion problem.