STRAX Reach · Team and community chat
Microsoft Teams chats through a Reach bot
Corporate clients and staff at partner banks chat with your Teams bot, and the conversation is handled in Reach with full history.
- Personal Teams chats
- Bot Framework tokens
- Replies in the same chat
Enterprise chat with a verified sender
Teams delivers messages through the Bot Framework. Reach checks the signed token on every call, including the issuer, the audience and the service address, before a message is accepted.
Replies go straight back into the chat the client used. For messages your systems start, Reach can also write to a user who has the app installed, using their Teams id.
Corporate IT departments often block consumer chat apps but approve Teams. A Reach bot gives those users a sanctioned way to reach your account managers, while your side keeps one record per client company.
Where it helps
Corporate account managers
Business clients reach their account manager through Teams, and the team sees the thread in Reach.
Reconciliation questions
Finance teams at client companies ask about unmatched payments and get answers with references.
Change notices
Notify connected corporate users about planned maintenance and collect their replies.
Invoice queries
Accounts payable teams at client companies ask about a disputed invoice and receive the answer in the same chat window.
What you need
-
An Azure Bot
With a Microsoft app id and client secret, single or multi-tenant.
-
A Teams app package
Containing the bot and installed for the people who should reach you.
-
A public HTTPS address
The Azure Bot messaging endpoint must reach the install.
-
Reach Core
The records and console the bot files into.
Good to know
This version handles one-to-one chats. Proactive messages need the app installed for the recipient first, which your Teams administrators can do for a whole group.
Questions
How do we match a Teams user to a client?
Reach logs each sender's Azure AD object id. Map it to the client once through the Reach application interface and later messages land on that record.
Can the bot join channels or group chats?
Personal chats only for now, which keeps client conversations out of shared rooms.
What is still missing?
Adaptive cards, attachments, channel and group chats.
Does the bot need admin consent in the client's tenant?
A multi-tenant bot needs the client's Teams administrator to allow the app. Many companies approve it for a named group of finance users first.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add Microsoft Teams to Reach
Tell us which channels your clients use and we will plan the rollout with your team.
Premium Requires STRAX Reach - Core, which is licensed.
About this listing
| Version | 1.1.0 |
| Author | STRAX |
| Category | Communication |
| Published | 2026-09-24 |
What's inside
| Credential | 1 |
| Global variable | 1 |
| Workflow | 2 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the Microsoft Teams channel with Reach Core, disabled until its credentials are entered
Free listing
Install it from Feature Marketplace inside STRAX
It builds on STRAX Reach - Core, a premium package. Ask us for a quote to license it first.
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "STRAX Reach - Teams"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
Microsoft Teams, Azure and Microsoft are trademarks of their owners, named here only to identify the service this package connects to.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.