Feature Requests

We would like to be able to change the status when a Flow runs.

AI that can identify trends in client's ticket history. Many times "band-aid" fixes are applied to individual support sessions when those symptoms could be indicative of greater issues. Something that automates this process and potentially reports that to the account managers could go a long way in providing long-term resolutions.

Inactive Companies show up from ConnectWise mudding the view of actual customers. Adding the ability to filter on Status would be more useful.

Members is showing StreamlineIT technicians which aren't part of our team. Showing only active Regular and Subcontractor Members would be helpful and cleaner.

We require more granular admin/member roles for read/edit access—as there's only two role types right now (admin or messenger). We require more control over who has access to Flows, Magic Agents, Messenger Settings, Deployments, etc.

We would like to be able to configure a custom webhook as an action in a flow. Requirements: * Ability to set custom endpoint (e.g. power automate, zapier, etc) * Ability to format the webhook payload * Ability to pass in variables from the thread such as ticket id, summary, etc. Or in the future if there are custom responses from a chat form.

Larger MSPs often require more nuanced permission types than two simple ones (Admin, members). How might we support permissions that more closely mirror's Microsoft's approach? Examples include: Global Admin who can do everything Flows admin who can only do flows Messenger admin Team admin over their pods Global Reader role where they can get in and

Please look into including a legend for the Magic AI Prioritization page. Including the specific terms and phrases we can use to create that auto-prioritization custom rule. Example "if summary description than..." or "if title contains than..." etc.

I would like a flow filter for resource rather than just owner. We want to have a flow for our procurement tickets when a member of the procurement team is assigned as a resource on the ticket. Unfortunately, they are not the owner of that ticket so that flow filter won't work for us. We experimented (and failed) by creating a "Team" and adding them to the team to get around it. Ideally would be just resource, as somebody else will usually be the owner, but logistics needs to track the ticket.