STRAX Reach · Team and community chat
Post Reach updates into a Microsoft Teams channel
Some updates belong in a team channel: a surge of client complaints, a VIP case that needs eyes, a provider outage. Reach posts them as cards through a Teams Workflows webhook.
- Channel posts
- Adaptive Cards
- Webhook address in the vault
Team notices without a Teams bot
Microsoft retired the old Office 365 connector webhooks in 2026. Teams channels now receive posts through the Workflows app, which gives each flow a signed address that accepts an Adaptive Card.
Reach keeps that address in the credential vault, because anyone holding it can post into the channel. Each message becomes a card with the subject as a bold title and the text below it, and Reach records the post against the escalation contact.
Cards render the same on desktop, web and mobile Teams, so a supervisor walking the floor with a phone sees the notice at the same moment as the analysts at their desks.
This package posts into one channel per install and does not read replies. For one-to-one chat with clients or colleagues, the reach-teams package runs a proper bot.
Where it helps
Complaint surges
Post to the service managers' channel when complaints about one product jump above normal.
VIP case hand-offs
Tell the relationship team that a high-value merchant has written in, with the case summary on the card.
Provider outage notices
Let the whole contact centre know that a messaging provider is failing so agents switch channel.
What you need
-
A Teams channel
Where the Workflows app is allowed by your Microsoft 365 administrators.
-
A Workflows flow
Built from the template that posts to a channel when a webhook request arrives.
-
The flow address
Stored in the STRAX credential vault as the webhook key.
-
Reach Core
Queues the posts and records them beside the rest of the case history.
Good to know
The Workflows flow belongs to the person who created it. Create it with a service account so the posts keep flowing when that person leaves the company.
Questions
Do we still need the old connector webhook?
No. Office 365 connector webhooks were shut down in May 2026, and this package uses the Workflows address that replaced them.
Can we post to several channels?
One channel per install in this version, since the address lives in one credential. Add flows for more channels as a later step.
Who can trigger the flow?
Set the flow to accept requests from anyone, because Reach calls it with the secret address and no Microsoft sign-in.
Will people see a bot name?
Posts appear from the Workflows app on behalf of the flow owner, which is another reason to use a service account.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add Teams channel posts 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.0.0 |
| Author | STRAX |
| Category | Communication |
| Published | 2026-09-24 |
What's inside
| Credential | 1 |
| Workflow | 1 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the Teams channel posts 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 Channel"
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, Microsoft 365 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.


