Feature Requests

More google clients are starting to use this as an alternative to Slack when they are a google client. It would be great if we could have an integration here like we do for Slack and Teams.

We'd like Thread to integrate into NinjaOne RMM

Currently, when a new company is created through Thread’s sales integration with Autotask PSA, it is always assigned the company type 'Customer', regardless of Autotask’s default settings. Users have no option to set or select 'Prospect' during the creation process, which overrides their preferred configurations. This behavior causes unintended downstream effects, such as automatic company creation in IT Glue and inaccurate reporting, and disrupts workflows where technicians rely on company type to indicate contract status. The requested feature would allow administrators to specify or default the company type when creating companies via sales threads, ensuring Autotask’s settings are respected and reducing manual corrections.

Todd Daigle requests the ability to selectively sync clients from Halo into Thread, rather than automatically syncing all clients. This would help reduce the number of clients managed in Thread and provide more manual control over which clients receive responses. Currently, there is no way to mass select or disable clients in Thread, making manual management difficult.

Request for a seamless, real-time integration so that knowledge base articles created in Thread are automatically available in IT Glue, and vice versa. The goal is to provide a unified source of information, reducing the need to search across multiple platforms and improving workflow efficiency for MSP teams. No specific requirements for tags, permissions, or formatting at this time—just a general need for automatic, bidirectional sync.

Integrate with Zoom Team Chat similar to what we do with Messenger across Teams, Slack, etc. https://www.zoom.com/en/products/team-chat/

Currently, Thread generates TimeZest scheduling links using a URL-based format (user URL + appointment type + ticket number). This approach does not allow for proper association with tickets in ConnectWise Manage unless the TimeZest plan is upgraded, resulting in inconsistency between bookings created via Thread and those created directly from the TimeZest pod in ConnectWise. Supporting TimeZest’s system-generated scheduling URLs, or enabling Thread to pass enough context for automatic ticket association, would keep scheduling consistent across tools and significantly streamline the workflow for IT Operations. This enhancement would reduce manual steps and improve integration reliability for MSPs using Thread and ConnectWise.

Add an option in Thread's admin settings to require all users to authenticate via Microsoft Single Sign-On (SSO) each day, automatically signing them out at the end of a session. This would prevent users from remaining logged in overnight, block alternative sign-in methods such as code-based login, and provide administrators with greater control over session duration for security and compliance purposes.

Create an outlook extension to allow me to add the E-Mail or reply to our PSA under the company as a ticket without notifications to capture the conversation. So, Thread can have that information if they reference it later or to allow me to assign me a follow up item in my psa.

The ability to pull liongard data from either ITGlue or Liongard directly would answer many technician questions in real time.