Feature Requests

Currently, the SSO integration in Thread Inbox only supports authentication with the tenant it was originally registered with. Users attempting to login from other tenants receive errors, causing disruptions for co-managed users. This limitation hinders the seamless experience for organizations managing external users. Proposed Feature: Implement a feature that allows Thread Inbox to support multi-tenant SSO. This feature should recognize when a user belongs to an external tenant and correctly handle the authentication loop, enabling both internal and external users to log in without encountering errors.

It would be great if we could search/filter/sort the whole sheet however we'd like. Currently only being able to search by client name makes the rest of the data on the sheet pretty useless especially since the pagination is so limited.

We need a way to backup everything in one swoop before making changes to triage rules, flows, intents, etc.

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

Partner is inquiring whether Thread has plans to expand their support team to provide 24/7 support coverage. This represents a request for extended support hours beyond current availability.

As an admin I should have the ability to review/edit ALL skills that have been created on both a personal and shared level for all users. Perhaps need a Super Admin title within the portal for this. The admin portal could use more global power to manage our team members end experience. I.E their settings, notifications, their skills, etc.

In AutoTask Company Classification is how we would sort customers by Contract type, thus is how we would activate all the intellgence and magic agents. It is tedious to go through All 5 intelligence agents and the two magic agents have to update the customer list 7 times anytime we add or remove. There should be a way to create a Customer group in the system and use the filters of classifications to do that. Then assign these groups to the Agents and Intelligence rather than manually assigning.

Workspace admins need the ability to disable or restrict the NinjaOne integration connection on a per-technician level within Super Magic Chat. Currently, each technician can connect or disconnect NinjaOne individually, but there is no centralized admin control to prevent specific technicians from using the NinjaOne connector. This would improve access management and allow admins to control which technicians have NinjaOne integration enabled.

We need more granularity in syncing options. Specifically, users should be able to: Restrict Syncs by Company/Contact Type: Allow admins to specify which types of companies and contacts are included in syncs. Control Company Status Sync (Active/Inactive): Provide options to manage whether the sync includes inactive companies or is restricted to active ones. This feature should adapt to the specific capabilities of each PSA (company statuses in ConnectWise Manage for instance). Use Case: Larger MSPs require this functionality for better onboarding and management workflows. These controls ensure more precise data handling, reduce clutter, and allow for a tailored experience based on their unique operational needs. Impact: Enhances day-to-day management of data syncs. Reduces errors and unnecessary data clutter (seeing inactive companies/contacts in Thread Inbox).