About ConcludeConclude is a collaboration platform that unifies chat across Slack, Microsoft Teams, Zendesk, and Jira.
Conclude Connect links Slack and Microsoft Teams with real-time, two-way messaging and file sharing – through internal connections for teams in the same organization, external connections for working with clients and vendors, and Bridge for subsidiaries, mergers and acquisitions, and partner ecosystems.
Conclude Apps are no-code apps for customer support, incidents, issues, task tracking, and more in Slack and Microsoft Teams, with optional Jira and Zendesk integrations. Cross-platform ticketing syncs tickets across connected Slack and Teams channels.
Conclude Agents are optional AI teammates you can add to Slack or Microsoft Teams channels, or attach to a Conclude app. They join the conversation like any other team member, answering questions from your company’s knowledge and helping your team resolve tickets.
Read more: About Conclude
Conclude is headquartered in Oslo, Norway, with a hub in Barcelona, Spain, and an office in Palo Alto, USA. CEO and co-founder Haavard Nord is the creator of the industry-standard framework Qt, used by more than a million developers to build apps for everything from home appliances to supercars.
Lars Knoll, who was instrumental in building Qt into a multi-billion euro company, joined in 2022 as CTO. Lars is also known as the creator of the open-source code that became WebKit, the engine that powers most web browsers today, including Safari and Chrome.
Read more: The Engineers Behind Conclude
Conclude offers: Conclude Starter, Conclude Pro, and Conclude Enterprise. The Free Plan is limited to non-commercial use by educational institutions. See our Pricing page for more. Conclude Starter and Conclude Pro offer a free 14-day trial to evaluate Conclude.
Conclude Enterprise provides a tailored package with exclusive features not found in other plans. Please see our Pricing page for more details on what’s included or contact us if you would like an estimate.
The Quickstart Guides, YouTube channel, and Conclude Blog provide useful information. For more resources:
- See our Documentation for more information
- Command Reference Guide for Slack and Teams
- From Slack, type the command
/c help - From Teams, type the command
/conclude help
Customer support:
- From Slack, use the
/c support command to bring up a support form, or email us at support@conclude.io. Our response time is typically one business day. - For any other inquiries, use the contact form, or email us at sales@conclude.io or info@conclude.io
The Conclude API (beta) lets you look up channels, manage connections, and read the audit log from your own systems. See the API documentation to get started.
Conclude is a collaboration platform that unifies chat across Slack, Microsoft Teams, Zendesk, and Jira.
Conclude Connect links Slack and Microsoft Teams with real-time, two-way messaging and file sharing – through internal connections for teams in the same organization, external connections for working with clients and vendors, and Bridge for subsidiaries, mergers and acquisitions, and partner ecosystems.
Conclude Apps are no-code apps for customer support, incidents, issues, task tracking, and more in Slack and Microsoft Teams, with optional Jira and Zendesk integrations. Cross-platform ticketing syncs tickets across connected Slack and Teams channels.
Conclude Agents are optional AI teammates you can add to Slack or Microsoft Teams channels, or attach to a Conclude app. They join the conversation like any other team member, answering questions from your company’s knowledge and helping your team resolve tickets.
Read more: About Conclude
Conclude is headquartered in Oslo, Norway, with a hub in Barcelona, Spain, and an office in Palo Alto, USA. CEO and co-founder Haavard Nord is the creator of the industry-standard framework Qt, used by more than a million developers to build apps for everything from home appliances to supercars.
Lars Knoll, who was instrumental in building Qt into a multi-billion euro company, joined in 2022 as CTO. Lars is also known as the creator of the open-source code that became WebKit, the engine that powers most web browsers today, including Safari and Chrome.
Read more: The Engineers Behind Conclude
Conclude offers: Conclude Starter, Conclude Pro, and Conclude Enterprise. The Free Plan is limited to non-commercial use by educational institutions. See our Pricing page for more. Conclude Starter and Conclude Pro offer a free 14-day trial to evaluate Conclude.
Conclude Enterprise provides a tailored package with exclusive features not found in other plans. Please see our Pricing page for more details on what’s included or contact us if you would like an estimate.
The Quickstart Guides, YouTube channel, and Conclude Blog provide useful information. For more resources:
- See our Documentation for more information
- Command Reference Guide for Slack and Teams
- From Slack, type the command
/c help - From Teams, type the command
/conclude help
Customer support:
- From Slack, use the
/c supportcommand to bring up a support form, or email us at support@conclude.io. Our response time is typically one business day. - For any other inquiries, use the contact form, or email us at sales@conclude.io or info@conclude.io
Plans, Pricing & UsersRegistered educational institutions are eligible and can access up to 20 seats. Please contact us to see if you qualify.Conclude’s pricing is based on the number of active users, depending on the solution you are using.
Internal users are always counted. External users – your customers or partners using the External collaboration solution – are not counted. Bridge users are counted on both sides.
Starter includes up to 5 channel connections in total, across Internal and External Connect.
Pro includes unlimited channel connections.
Enterprise includes unlimited channel connections.
Connecting an existing Microsoft Teams chat also uses one channel connection. Creating new chats through Conclude is available on Pro and Enterprise.
Each Conclude Agent counts as one active user. A monthly AI usage allowance is included, or you can connect your own Anthropic or OpenAI API key.Counting an active user depends on the solution you are using:
Internal collaboration: An active user is someone who did one of these things in the last 90 days: created or changed a link between tools, took an active part in a connected channel, joined a conversation in one of those channels, or took part in a direct chat between internal Slack and Microsoft Teams environments, beyond just reading it. Each user is counted once, even if they take part in several connections. Learn more.
External collaboration: An active user is someone from the inviting company who actively participates in connected channels, sends messages or reactions, or joins direct chats between Slack and Teams. Users are counted only once. External users (outside your organization) are not counted.
Bridge: Any member of a connected channel from either company, regardless of whether they actively participate, is counted.
An external user is someone outside your organization who has been invited to join a channel through the External collaboration solution, e.g., a customer or partner participating via Slack or Microsoft Teams. These external users are not counted towards your billable active users.A Bridge user is a member of a shared channel between two companies that both use Conclude. Bridge creates an approved connection for organizations that work closely together, allowing teams across two Slack or Microsoft Teams workspaces to collaborate in shared channels.Yes. All members of a connected Bridge channel are counted as active users – from both companies. User counts are based on membership of a connected channel rather than activity. A user does not need to send messages or reactions to be counted.Conclude calculates and displays the number of active users in the Admin settings of the web dashboard.
Go to Admin console > Organization > Account to see the number of active and licensed users.
Go to Admin console > Users and access > Users, open the filter menu, and choose Active under Activity to see a filtered list.
In both Channel and Thread modes, anyone who installs or modifies the app, or engages with tickets by commenting or updating attributes, is counted. The difference is channel membership:
Thread mode: members of the main channel where Conclude is installed are counted.
Channel mode: members of a dedicated ticket channel are counted. Members of the main app channel are not counted unless they interact with tickets.
Only your internal team members count. An active user is someone from your company who participates in external-facing channels, is assigned tickets, or collaborates to resolve them. Customers are never counted. Learn more.No. The free trial includes full access to all solutions with no restrictions on users or features.Our standard free trial is 14 days. It can be extended by agreement if further testing is required. Please contact us directly if you need an extension.
Conclude’s pricing is based on the number of active users, depending on the solution you are using.
Internal users are always counted. External users – your customers or partners using the External collaboration solution – are not counted. Bridge users are counted on both sides.
Starter includes up to 5 channel connections in total, across Internal and External Connect.
Pro includes unlimited channel connections.
Enterprise includes unlimited channel connections.
Connecting an existing Microsoft Teams chat also uses one channel connection. Creating new chats through Conclude is available on Pro and Enterprise.
Counting an active user depends on the solution you are using:
Internal collaboration: An active user is someone who did one of these things in the last 90 days: created or changed a link between tools, took an active part in a connected channel, joined a conversation in one of those channels, or took part in a direct chat between internal Slack and Microsoft Teams environments, beyond just reading it. Each user is counted once, even if they take part in several connections. Learn more.
External collaboration: An active user is someone from the inviting company who actively participates in connected channels, sends messages or reactions, or joins direct chats between Slack and Teams. Users are counted only once. External users (outside your organization) are not counted.
Bridge: Any member of a connected channel from either company, regardless of whether they actively participate, is counted.
Conclude calculates and displays the number of active users in the Admin settings of the web dashboard.
Go to Admin console > Organization > Account to see the number of active and licensed users.
Go to Admin console > Users and access > Users, open the filter menu, and choose Active under Activity to see a filtered list.
In both Channel and Thread modes, anyone who installs or modifies the app, or engages with tickets by commenting or updating attributes, is counted. The difference is channel membership:
Thread mode: members of the main channel where Conclude is installed are counted.
Channel mode: members of a dedicated ticket channel are counted. Members of the main app channel are not counted unless they interact with tickets.
Security & Data ProtectionWe collect only the necessary data from Slack, Microsoft Teams, Jira, and Zendesk to operate effectively.
This includes:
- Workspace names, technical identifiers, contact information, channel data, logs of actions within Conclude, and usage statistics
- User info: name, avatar, and email (if accessible)
- Team and channel info: names, IDs, and member lists
- Message metadata: mapping of message IDs for syncing, edits, or deletes
We keep your data while your agreement with Conclude is active, and erase it on request or when your agreement ends, in line with our Data Processor Agreement.
Conclude Connect does not store user messages or files. It only retains message metadata for reconciliation across platforms. If you add a Conclude Agent or a Conclude app to a connected channel, the content storage described in the next question, “How long are conversations stored?” applies to that channel.Conclude stores conversation content only where a feature requires it:
Connected channels (Conclude Connect): message content and files are not stored. They pass through Conclude only while they are converted between Slack and Microsoft Teams. We keep message metadata, such as message IDs, so edits, replies, and deletions stay in sync.
Channels with a Conclude Agent: recent messages are stored briefly so the agent can build prompts for the AI model you selected. These messages are sent to the AI provider (Anthropic or OpenAI) to generate a response. Neither Conclude nor the provider uses your data to train AI models.
Channels with a Conclude app: ticket content, including ticket messages, is stored until the ticket is deleted, or until your data is erased on request or at the end of your agreement.
All data is hosted on Google Cloud infrastructure in the us-central1 region, located in Iowa, USA.Yes. Data in transit is protected with TLS 1.2 or later. Sensitive payloads use AES-256 encryption; data at rest is encrypted (AES-256 standard or higher). Alongside encryption, we employ continuous monitoring and have implemented stringent access controls to safeguard data.
Conclude is SOC2 Type II certified and HIPAA compliant, with regular audits via Vanta Trust.
See our Security page for more information.
SOC 2 Type II: Our latest audit, by independent auditor Johanson Group, covers September 1, 2025 – August 31, 2026 and assessed Security, Availability, and Confidentiality. It resulted in an unqualified opinion, with no exceptions identified during control testing. The report was issued on October 22, 2026.
Penetration testing: Workstreet conducted an independent gray-box penetration test of our production web application, following industry standards including OWASP Top 10 and NIST SP 800-115. The latest report, dated June 15, 2026, identified no critical or high-severity vulnerabilities.
Both reports are available to eligible customers and prospects on request. See our Security page for more.
Conclude can only view messages in channels or direct messages where the app is a member. If Conclude is not in the conversation, it cannot see the content. Conclude requires this access to sync messages to Microsoft Teams.Conclude only subscribes to the channels or chats that are required. If the Teams app is installed into a Team or Chat, Conclude will receive notifications about new messages in that Team or Chat. Any unrelated data is immediately discarded.We keep your data while your agreement with Conclude is active. When you request deletion, or when your agreement ends, we erase it in line with our Data Processor Agreement. You can choose to have your data returned before it is erased.Conclude is committed to ensuring that your data is handled securely and with respect to your privacy rights. When data is no longer needed for service provision or at the request of a user, it is promptly deleted from our systems.
Deletion follows the terms set out in our Data Processor Agreement and covers our production systems; backup copies are erased on our ordinary backup rotation cycle. Our processes are designed to protect against unauthorized access or inadvertent data retention.
Our architecture is designed for resilience, with automatic failovers and redundancy to handle potential outages seamlessly.Security documentation is available to customers upon request. For a full list of Microsoft Teams RSC scopes requested by Conclude to connect platforms and Microsoft Teams delegated scopes requested by Conclude for User Sync, click here.
For the full list of Slack bot token scopes which govern what Conclude can access, and Slack user token scopes that can access user data on behalf of users that authorize them, click here.
We collect only the necessary data from Slack, Microsoft Teams, Jira, and Zendesk to operate effectively.
This includes:
- Workspace names, technical identifiers, contact information, channel data, logs of actions within Conclude, and usage statistics
- User info: name, avatar, and email (if accessible)
- Team and channel info: names, IDs, and member lists
- Message metadata: mapping of message IDs for syncing, edits, or deletes
We keep your data while your agreement with Conclude is active, and erase it on request or when your agreement ends, in line with our Data Processor Agreement.
Conclude stores conversation content only where a feature requires it:
Connected channels (Conclude Connect): message content and files are not stored. They pass through Conclude only while they are converted between Slack and Microsoft Teams. We keep message metadata, such as message IDs, so edits, replies, and deletions stay in sync.
Channels with a Conclude Agent: recent messages are stored briefly so the agent can build prompts for the AI model you selected. These messages are sent to the AI provider (Anthropic or OpenAI) to generate a response. Neither Conclude nor the provider uses your data to train AI models.
Channels with a Conclude app: ticket content, including ticket messages, is stored until the ticket is deleted, or until your data is erased on request or at the end of your agreement.
Yes. Data in transit is protected with TLS 1.2 or later. Sensitive payloads use AES-256 encryption; data at rest is encrypted (AES-256 standard or higher). Alongside encryption, we employ continuous monitoring and have implemented stringent access controls to safeguard data.
Conclude is SOC2 Type II certified and HIPAA compliant, with regular audits via Vanta Trust.
See our Security page for more information.
SOC 2 Type II: Our latest audit, by independent auditor Johanson Group, covers September 1, 2025 – August 31, 2026 and assessed Security, Availability, and Confidentiality. It resulted in an unqualified opinion, with no exceptions identified during control testing. The report was issued on October 22, 2026.
Penetration testing: Workstreet conducted an independent gray-box penetration test of our production web application, following industry standards including OWASP Top 10 and NIST SP 800-115. The latest report, dated June 15, 2026, identified no critical or high-severity vulnerabilities.
Both reports are available to eligible customers and prospects on request. See our Security page for more.
Conclude is committed to ensuring that your data is handled securely and with respect to your privacy rights. When data is no longer needed for service provision or at the request of a user, it is promptly deleted from our systems.
Deletion follows the terms set out in our Data Processor Agreement and covers our production systems; backup copies are erased on our ordinary backup rotation cycle. Our processes are designed to protect against unauthorized access or inadvertent data retention.
Security documentation is available to customers upon request. For a full list of Microsoft Teams RSC scopes requested by Conclude to connect platforms and Microsoft Teams delegated scopes requested by Conclude for User Sync, click here.
For the full list of Slack bot token scopes which govern what Conclude can access, and Slack user token scopes that can access user data on behalf of users that authorize them, click here.
Conclude ConnectConclude Connect is a Slack and Microsoft Teams integration that connects both messaging platforms for better cross-team collaboration. It includes solutions for workplace, customer or client, and intercompany collaboration.
Sync messages and files between Slack and Teams in real-time by linking chats and channels on Teams and Slack. Connect with colleagues, or collaborate with customers and other companies during mergers and acquisitions.
Yes. You can link your Slack or Teams workspace with another company that uses Slack or Teams for seamless cross-company collaboration. Connect – External is a solid solution for agencies, consultants, and service-based businesses, as well as Bridge for established partner ecosystems and mergers and acquisitions. Conclude also supports cross-tenant messaging for Teams-to-Teams or Slack-to-Slack.Key features:
- Send and receive messages
- Edit and delete messages
- Sync threaded messages
- Customizable file sharing
- Use @mentions for collaborators
- Synced reactions (when signed in)
- Connect channels and chats on Slack and Teams
- Create new Teams chats (Pro and Enterprise) and connect existing ones with Slack
- Use emojis (inside messages)
- Rich text formatting
We recommend sharing the External Invitee Guide to help them get started. It provides step-by-step instructions for joining and using Conclude.
If they’re being invited to connect their channel to yours, there’s no cost to them as an external user.
Yes. This solution is excellent for larger organizations with multiple teams or departments on Slack or Teams, or companies undergoing mergers.
Conclude has developed a Slack-Teams Bridge that allows companies to keep communication flowing without switching platforms. Linking important channels and chats on Slack and Microsoft Teams allows teams to work on their preferred platform and stay aligned from Day 1.
See our Quickstart Guide with a video tutorial to learn more.
Key features:
- Synced reactions
- Send and receive messages
- Edit and delete messages
- Sync threaded messages
- Use emojis (inside messages)
- Language translation (60 languages)
- Connect Teams Chats with Slack
- Sync channels on both platforms
- File and document sharing
- @mention your colleagues
- Rich text formatting
Watch: Connect Slack and Microsoft Teams Across Your Organization | Step-by-Step Guide with Conclude
- Slack: You can connect both public and private channels, as long as the user setting up the connection is a member of the channel.
- Microsoft Teams: Standard, private, and shared channels can all be connected, as long as your own organization hosts the channel. A shared channel that another organization hosts and shares with you (Teams Connect) cannot be connected, because Microsoft does not give apps outside the hosting tenant access to the channel’s membership or its message notifications. Teams chats are not affected: a chat hosted by another organization can be connected.
- Guest users: Guest users can participate in synced channels, and their messages will be included. However, guest users cannot set up or manage connections to channels that are not part of their own workspace or tenant. This is due to platform-level security and privacy restrictions. If you’re unsure whether a channel can be connected, check that the user setting it up is part of the Slack workspace or Teams tenant where the channel is hosted.
Admin rights are required to install Conclude on both platforms. We also have a granular permission model that allows customizable file and image sharing at a channel connection level.
See our document on file and image sharing for more.
Only if the translation feature is enabled during setup
- If translations are not enabled, messages are never sent to an external provider
- When enabled, translations are handled by Google Translate
The optional AI-powered translation feature supports up to 60 languages and allows teams to communicate in their preferred language across Slack and Microsoft Teams.
Yes, @mentions generally work across platforms. Internal connections work smoothly when users are signed in on both platforms. For external connections, mentions may sometimes fail if posted via the bot, but reliability improves when you set up an integration account for Microsoft Teams.
Learn more about channel mentions here.
The Quickstart Guides will walk you through how to get started:
Note: You must have Admin permissions to install Conclude in Microsoft Teams. If you are not an Admin and would like more information, you can book a call.
Connection issues in Conclude Connect are usually caused by one of the following:
- Permissions not granted – check that the Conclude app has all required Slack and Microsoft Teams permissions and that a workspace admin has completed the authentication
- Missing access to the channel/chat – you must be a member of the Slack channel or Teams channel/chat to see them
- Channel visibility limits – private or restricted channels in Slack or Teams will not appear unless you’re a member
- Sync delays – occasionally, platform-side delays from Slack or Microsoft Teams can take a few minutes to update
- Guest users – these users cannot set up or manage connections outside their own workspace or tenant
If you’ve checked the above and the connection still isn’t working, please contact support@conclude.io.
First, an admin enables Connect – internal in the dashboard and adds your Slack workspace and Microsoft Teams team under Admin console > Workspaces (installing Conclude in Microsoft Teams requires admin permissions).
Then open the Connect > Channels tab, click New connection, choose the Teams team and Slack workspace, select the channel(s) to link, and click Create. Messages then sync automatically in both directions.
Run the command /conclude connect from Teams to set up a channel link, or, on Pro and Enterprise, use /conclude chat to start a connected chat.
On Pro and Enterprise, you can also create a connected chat directly from Slack by typing /c chat or /c chat create.
No. Conclude requires a paid Microsoft 365 / Teams plan. Free Teams tenants typically don’t support the third-party app installation and tenant-admin consent (Microsoft Graph permissions) that Conclude needs to access and sync Teams channels and chats. Slack, by contrast, works on free workspaces.
Note too that any Microsoft Teams integration account must have a Microsoft 365 license that includes Teams – Teams (free) and Entra ID – only accounts cannot post. See the Troubleshooting guide for more.
An integration account is a generic Teams account used as a fallback to post messages when a real user’s credentials aren’t available. We strongly recommend setting one up.
First, a Microsoft admin creates a generic Microsoft 365 user with a Teams license (e.g., “Conclude Integration” or “External User”), not tied to a real person. Teams (free), Entra ID-only accounts, and shared mailboxes or service accounts without a full license can’t post.
This account serves as a fallback to post messages in channels and chats, ensuring consistent message synchronization and optimal functionality.
To set it up:
- Go to Admin console > Integration account
- Select the pre-created integration account from the dropdown, then click Save
- Select Run diagnostics to check if the account has a valid Teams license and if it is signed in to Conclude
- Sign in to the account when prompted to authorize Conclude to post on its behalf
- Add the integration account to each Team and connected channel – private channels require direct membership.
A step-by-step video can be found here: Integration account.
This is usually one of the following: you’re not a member of the chat (or it’s private/restricted); the chat is owned by another company (a guest or shared scenario); or you have a duplicate identity across platforms.
Check that you’re a member and that your organization owns the chat, then sign out and back in to refresh. If it still doesn’t appear, ask an admin to look for duplicate accounts under Admin console > Users and use Merge users. For Microsoft Teams specifically, a tenant admin must have added Conclude and approved permissions.
See the Troubleshooting guide and Setup tips.
When Conclude can’t post as the real Teams user — because that user’s Teams credentials aren’t available or authorized — it posts under a fallback identity, so the message looks like it came from a different or random user (the real sender’s name still appears in the message text).
This is expected until a Microsoft Teams integration account is configured. To fix it, an admin sets up the integration account, adds it to the Team and the specific channel (private channels require direct membership), and confirms it has a Microsoft 365 license including Teams. Encouraging users to sign in to Conclude also helps.
See the Integration account and the Troubleshooting guide.
See the Connect documentation for Internal connections, External connections, Bridge, and Troubleshooting.
Conclude Connect is a Slack and Microsoft Teams integration that connects both messaging platforms for better cross-team collaboration. It includes solutions for workplace, customer or client, and intercompany collaboration.
Sync messages and files between Slack and Teams in real-time by linking chats and channels on Teams and Slack. Connect with colleagues, or collaborate with customers and other companies during mergers and acquisitions.
Key features:
- Send and receive messages
- Edit and delete messages
- Sync threaded messages
- Customizable file sharing
- Use @mentions for collaborators
- Synced reactions (when signed in)
- Connect channels and chats on Slack and Teams
- Create new Teams chats (Pro and Enterprise) and connect existing ones with Slack
- Use emojis (inside messages)
- Rich text formatting
We recommend sharing the External Invitee Guide to help them get started. It provides step-by-step instructions for joining and using Conclude.
If they’re being invited to connect their channel to yours, there’s no cost to them as an external user.
Yes. This solution is excellent for larger organizations with multiple teams or departments on Slack or Teams, or companies undergoing mergers.
Conclude has developed a Slack-Teams Bridge that allows companies to keep communication flowing without switching platforms. Linking important channels and chats on Slack and Microsoft Teams allows teams to work on their preferred platform and stay aligned from Day 1.
See our Quickstart Guide with a video tutorial to learn more.
Key features:
- Synced reactions
- Send and receive messages
- Edit and delete messages
- Sync threaded messages
- Use emojis (inside messages)
- Language translation (60 languages)
- Connect Teams Chats with Slack
- Sync channels on both platforms
- File and document sharing
- @mention your colleagues
- Rich text formatting
Watch: Connect Slack and Microsoft Teams Across Your Organization | Step-by-Step Guide with Conclude
- Slack: You can connect both public and private channels, as long as the user setting up the connection is a member of the channel.
- Microsoft Teams: Standard, private, and shared channels can all be connected, as long as your own organization hosts the channel. A shared channel that another organization hosts and shares with you (Teams Connect) cannot be connected, because Microsoft does not give apps outside the hosting tenant access to the channel’s membership or its message notifications. Teams chats are not affected: a chat hosted by another organization can be connected.
- Guest users: Guest users can participate in synced channels, and their messages will be included. However, guest users cannot set up or manage connections to channels that are not part of their own workspace or tenant. This is due to platform-level security and privacy restrictions. If you’re unsure whether a channel can be connected, check that the user setting it up is part of the Slack workspace or Teams tenant where the channel is hosted.
Admin rights are required to install Conclude on both platforms. We also have a granular permission model that allows customizable file and image sharing at a channel connection level.
See our document on file and image sharing for more.
Only if the translation feature is enabled during setup
- If translations are not enabled, messages are never sent to an external provider
- When enabled, translations are handled by Google Translate
The optional AI-powered translation feature supports up to 60 languages and allows teams to communicate in their preferred language across Slack and Microsoft Teams.
Yes, @mentions generally work across platforms. Internal connections work smoothly when users are signed in on both platforms. For external connections, mentions may sometimes fail if posted via the bot, but reliability improves when you set up an integration account for Microsoft Teams.
Learn more about channel mentions here.
The Quickstart Guides will walk you through how to get started:
Note: You must have Admin permissions to install Conclude in Microsoft Teams. If you are not an Admin and would like more information, you can book a call.
Connection issues in Conclude Connect are usually caused by one of the following:
- Permissions not granted – check that the Conclude app has all required Slack and Microsoft Teams permissions and that a workspace admin has completed the authentication
- Missing access to the channel/chat – you must be a member of the Slack channel or Teams channel/chat to see them
- Channel visibility limits – private or restricted channels in Slack or Teams will not appear unless you’re a member
- Sync delays – occasionally, platform-side delays from Slack or Microsoft Teams can take a few minutes to update
- Guest users – these users cannot set up or manage connections outside their own workspace or tenant
If you’ve checked the above and the connection still isn’t working, please contact support@conclude.io.
First, an admin enables Connect – internal in the dashboard and adds your Slack workspace and Microsoft Teams team under Admin console > Workspaces (installing Conclude in Microsoft Teams requires admin permissions).
Then open the Connect > Channels tab, click New connection, choose the Teams team and Slack workspace, select the channel(s) to link, and click Create. Messages then sync automatically in both directions.
Run the command /conclude connect from Teams to set up a channel link, or, on Pro and Enterprise, use /conclude chat to start a connected chat.
On Pro and Enterprise, you can also create a connected chat directly from Slack by typing /c chat or /c chat create.
No. Conclude requires a paid Microsoft 365 / Teams plan. Free Teams tenants typically don’t support the third-party app installation and tenant-admin consent (Microsoft Graph permissions) that Conclude needs to access and sync Teams channels and chats. Slack, by contrast, works on free workspaces.
Note too that any Microsoft Teams integration account must have a Microsoft 365 license that includes Teams – Teams (free) and Entra ID – only accounts cannot post. See the Troubleshooting guide for more.
An integration account is a generic Teams account used as a fallback to post messages when a real user’s credentials aren’t available. We strongly recommend setting one up.
First, a Microsoft admin creates a generic Microsoft 365 user with a Teams license (e.g., “Conclude Integration” or “External User”), not tied to a real person. Teams (free), Entra ID-only accounts, and shared mailboxes or service accounts without a full license can’t post.
This account serves as a fallback to post messages in channels and chats, ensuring consistent message synchronization and optimal functionality.
To set it up:
- Go to Admin console > Integration account
- Select the pre-created integration account from the dropdown, then click Save
- Select Run diagnostics to check if the account has a valid Teams license and if it is signed in to Conclude
- Sign in to the account when prompted to authorize Conclude to post on its behalf
- Add the integration account to each Team and connected channel – private channels require direct membership.
A step-by-step video can be found here: Integration account.
This is usually one of the following: you’re not a member of the chat (or it’s private/restricted); the chat is owned by another company (a guest or shared scenario); or you have a duplicate identity across platforms.
Check that you’re a member and that your organization owns the chat, then sign out and back in to refresh. If it still doesn’t appear, ask an admin to look for duplicate accounts under Admin console > Users and use Merge users. For Microsoft Teams specifically, a tenant admin must have added Conclude and approved permissions.
See the Troubleshooting guide and Setup tips.
When Conclude can’t post as the real Teams user — because that user’s Teams credentials aren’t available or authorized — it posts under a fallback identity, so the message looks like it came from a different or random user (the real sender’s name still appears in the message text).
This is expected until a Microsoft Teams integration account is configured. To fix it, an admin sets up the integration account, adds it to the Team and the specific channel (private channels require direct membership), and confirms it has a Microsoft 365 license including Teams. Encouraging users to sign in to Conclude also helps.
See the Integration account and the Troubleshooting guide.
Conclude AppsConclude Apps are workflow apps that allow you to manage support tickets, issues, and incidents directly from Slack and Microsoft Teams.
They are fully customizable, provide structure to conversations and allow teams to deploy in minutes. Conclude Apps integrate with Jira Cloud for smoother issue management and Zendesk for customer support.
Conclude can be used by any team or department looking to bring structure to their conversations inside Slack and Microsoft Teams. All workflow apps are fully customizable.
IT Help Desk and Support Teams most frequently use our Support and Incident Management templates. Our Bug Tracking and Jira Integration templates are also frequently used.
Yes. Give each Conclude app its own email address, and each incoming email opens a summarized ticket in Slack or Microsoft Teams.
From the Dashboard, click on the Settings wheel in the top right corner, then navigate to Email settings for the app you want to adjust.
To approve email sending, select the box Allow access. Here, users can also enable email summarization and translation. See Email integration for more.
In Channel mode, each new ticket gets its own channel. In Thread mode, each new ticket gets its own thread inside the primary channel where the app is installed.
To set the mode, open the app, click the edit (pencil) icon, then go to General > App mode. See the Apps documentation for more.
To conclude a ticket, type /c conclude. For all commands in Slack and Microsoft Teams, see Commands.
The ticket channel is archived and disappears from Slack, but remains visible and searchable from the Conclude Dashboard. To reopen a ticket, click Reopen in the Settings menu.
See the Apps documentation for building an app without code, the editor, templates, and integrations, plus Commands for Slack and Microsoft Teams.
Conclude Apps are workflow apps that allow you to manage support tickets, issues, and incidents directly from Slack and Microsoft Teams.
They are fully customizable, provide structure to conversations and allow teams to deploy in minutes. Conclude Apps integrate with Jira Cloud for smoother issue management and Zendesk for customer support.
Conclude can be used by any team or department looking to bring structure to their conversations inside Slack and Microsoft Teams. All workflow apps are fully customizable.
IT Help Desk and Support Teams most frequently use our Support and Incident Management templates. Our Bug Tracking and Jira Integration templates are also frequently used.
Yes. Give each Conclude app its own email address, and each incoming email opens a summarized ticket in Slack or Microsoft Teams.
From the Dashboard, click on the Settings wheel in the top right corner, then navigate to Email settings for the app you want to adjust.
To approve email sending, select the box Allow access. Here, users can also enable email summarization and translation. See Email integration for more.
In Channel mode, each new ticket gets its own channel. In Thread mode, each new ticket gets its own thread inside the primary channel where the app is installed.
To set the mode, open the app, click the edit (pencil) icon, then go to General > App mode. See the Apps documentation for more.
To conclude a ticket, type /c conclude. For all commands in Slack and Microsoft Teams, see Commands.
The ticket channel is archived and disappears from Slack, but remains visible and searchable from the Conclude Dashboard. To reopen a ticket, click Reopen in the Settings menu.
Conclude AgentsConclude Agents are optional AI teammates for Slack and Microsoft Teams. Deploy one to a Slack or Teams channel, or attach it to a Conclude app, and it joins the conversation like any other team member, answering questions from your company’s own knowledge and helping your team work on tasks or tickets.
Read more: Conclude Agents
Conclude Agents run on models from Anthropic (for example, Claude Opus 5 and Claude Sonnet 5) and OpenAI. You choose the model for each agent when you set it up.Yes. Agents can use Conclude’s included AI usage, or you can add your own provider API key under Admin console > Agents > All agents. Usage is then billed directly by your provider.Conclude Agents are included in the free trial. On paid plans, they’re available with Conclude Pro and Conclude Enterprise. See How are Conclude Agents priced? for more.You can ground an agent in your own knowledge by uploading documents or adding website and FAQ URLs, so its answers are accurate and cited. Agents can also learn from closed tickets and use that knowledge to improve future responses. This ticket-based Learning feature is currently in beta.Yes. Once channels are connected with Conclude Connect, the same agent works across both Slack and Microsoft Teams.An agent responds when it’s @mentioned or addressed by name in the conversation. Depending on its settings, it can also step in on its own when it can help.No. Neither Conclude nor the AI provider uses your messages to train AI models. See How long are conversations stored? for how messages in channels with an agent are handled.Go to Admin console > Agents > All agents. The Agents Quickstart walks you through each step, from choosing a model to deploying the agent in a channel or app.See the Agents documentation and the Agents admin guide.
Conclude Agents are optional AI teammates for Slack and Microsoft Teams. Deploy one to a Slack or Teams channel, or attach it to a Conclude app, and it joins the conversation like any other team member, answering questions from your company’s own knowledge and helping your team work on tasks or tickets.
Read more: Conclude Agents