Microsoft Teams Integration
A channel full of automated messages is a channel nobody reads.
What is microsoft teams?
Teams integration means bringing information and actions into the place people already work, with the volume restrained deliberately, since a channel that receives everything is one people learn to ignore.
Teams integrations are unusually easy to build and unusually easy to ruin. Posting a message into a channel takes minutes, which is why so many organisations end up with channels nobody opens.
The failure is not technical. It is that every automated message reduces the attention paid to all of them, so an organisation that routes every system event into Teams has effectively turned off its own notifications while believing it improved them.
The integrations that work are narrow. Something a person needs to act on, in the channel where the people who act on it already are, at a volume that keeps each one worth reading.
Why we push back on notifications
Duara builds Teams integrations from Nairobi, and argues for fewer notifications than clients initially want.
We push back on notification volume harder than most suppliers would. Building more is easier and bills better, and the client ends up with a muted channel and a belief that the integration failed rather than that it succeeded too enthusiastically.
Who this is for
- Staff check several systems for updates
- Approvals happen over email
- A previous Teams integration got muted
- Work happens in Teams and information does not
Industries we serve
- Professional services
- Financial services
- Manufacturing
- Public sector
- Education
- Technology companies
Problems this solves
These are attention problems as much as integration problems.
- Channels nobody opens. Every system event was routed into Teams, and the result is a channel people muted within a fortnight.
- Checking several systems. Staff open three systems to find out whether anything needs them, which is time spent looking rather than doing.
- Approvals in email. Requests sit in an inbox while the person who should approve them is working in Teams all day.
- Information in the wrong place. What people need to know lives in a system they visit occasionally rather than where they actually work.
What we deliver
A small number of notifications that genuinely require action, delivered to the channel where the right people already are, with actions available in place and volume kept deliberately low.
A deliberately small set of notifications
Delivery to the channel where the right people are
Actions available without leaving Teams
Approval routing where it suits your process
Volume reviewed after launch
A recommendation to remove notifications that get ignored
Features
- Fewer notifications than requested. Every additional message reduces attention paid to all of them, so restraint is the whole design.
- Only what needs an action. Information that requires nothing is not a notification, and treating it as one is how channels get muted.
- Actions in place. Approving or acknowledging without leaving Teams, since the value is not having to go elsewhere.
- Right channel, not all channels. Delivered where the people who act on it are, rather than broadcast to everybody who might care.
- Volume reviewed afterwards. We check what is being ignored and recommend removing it, which is the opposite of what suppliers usually propose.
Benefits
- Notifications get read. A small number of genuinely actionable messages keeps each one worth opening.
- Less time checking systems. What needs a person arrives rather than being found by looking.
- Approvals move faster. A request reaching somebody where they already work is answered sooner than one sitting in email.
- Attention is preserved. Restraint means the channel still works in a year rather than being muted after a month.
Technologies we use
- Channel and chat messaging. Delivering to the specific channel or person rather than broadcasting.
- Adaptive cards and actions. Allowing approval or acknowledgement without leaving Teams.
- Approval routing. Directing requests to the right person with the context they need to decide.
- Volume measurement. Tracking what gets acted on and what gets ignored after launch.
- System event filtering. Deciding which events justify a notification at all, which is most of the work.
The constraint here is human rather than technical. Notification capacity is finite and shared, so every message added spends attention that the other messages needed.
How the process works, step by step
Teams integrations usually take one to three weeks, and the argument about volume takes longer than the build.
-
Step 1
Free notification review
We look at what you want to send and which of it genuinely requires somebody to act.
-
Step 2
The volume conversation
We argue for fewer, since this is where the integration succeeds or gets muted.
-
Step 3
Channels chosen
Delivery to where the people who act on it already are, rather than to everybody who might be interested.
-
Step 4
Actions built in place
Approving and acknowledging without leaving Teams, which is where the time saving actually is.
-
Step 5
Reviewed after a month
What is being ignored is identified and removed, which keeps the rest worth reading.
Quality assurance and how we work
The commitments attached to sending messages people cannot avoid.
- We argue for fewer notifications. Building more is easier and bills better, and it produces a muted channel and a belief the integration failed.
- Only actionable things become notifications. Information requiring nothing is not a notification, and treating it as one is how channels get ignored.
- We review volume after launch. What is being ignored gets removed, which is the opposite of what suppliers usually propose next.
- We do not broadcast widely. Sending to everybody who might care is how a channel becomes noise for the people who actually needed it.
- We say when Teams is the wrong place. Some information belongs in a report or a dashboard, and putting it in a chat channel serves nobody.
Frequently asked questions about microsoft teams
Why do Teams integrations fail?
Volume. Posting a message takes minutes to build, so organisations route everything into Teams and end up with channels nobody opens.
Is that not a good problem to have?
No. Every automated message reduces attention paid to all of them, so an organisation sending everything has effectively turned its notifications off.
Will you build what we ask for?
We will argue for less first. Building more is easier and bills better, and it produces a muted channel and a disappointed client.
What should become a notification?
Something requiring a person to act. Information that needs nothing is not a notification and treating it as one is how channels get ignored.
Can people approve things inside Teams?
Yes, through cards with actions, which is where the actual time saving sits rather than in the notification itself.
Which channel should notifications go to?
The one where the people who act on it already are. Broadcasting to everybody who might care makes it noise for the people who needed it.
Do you review it afterwards?
Yes, after about a month, and we recommend removing what is being ignored. That is the opposite of what suppliers usually propose.
How quickly can notifications go live?
One to three weeks, and the argument about volume takes longer than the build does.
Can it notify about system failures?
Yes, and those are usually the clearest case since they genuinely require somebody to act quickly.
Can it work with our approval process?
Yes, routing requests to the right person with enough context to decide without opening another system.
Is Teams better than email for this?
For things needing quick action, usually, since people are in Teams all day. For anything needing a record, email or a system is often better.
What if Teams is the wrong place?
We say so. Some information belongs in a report or a dashboard, and putting it in a chat channel serves nobody.
Does it need Microsoft 365 permissions?
Yes, scoped narrowly, and that conversation happens with your IT administrator rather than through a consent click.
Can it post to private channels?
Yes, with appropriate permissions, and private channels are often the right place since the audience is already narrow.
Will it work on the Teams mobile app?
Yes, and mobile is where most notification fatigue is actually felt, which is another argument for restraint.
Can it pull information as well as push?
Yes, so somebody can ask for a status rather than waiting for a message, which reduces notification volume further.
Does it store conversation content?
Only what you ask it to. Teams conversations stay in Microsoft under your tenant policies.
Can we turn specific notifications off?
Yes, and you should. The configuration is yours so you can reduce volume without calling us.
Who can see the messages it posts?
Whoever is in that channel, which is exactly why channel choice matters more than it appears to.
What does a Teams integration cost?
Notification count and action complexity determine it, quoted after the notification review.
Glossary of terms
Teams integration terms in plain language.
- Notification fatigue
- The point at which messages stop being read because there are too many.
- Adaptive card
- A message with actions in it, allowing a response without leaving Teams.
- Channel
- A shared conversation space, where notification volume affects everybody in it.
- Actionable
- Requiring somebody to do something, which is the test for whether it should be a notification.
- Bot
- An application that posts and responds within Teams.
- Mute
- What people do to a channel that sends too much, and rarely undo.
Related services in Integrations
Talk to us about microsoft teams
Ask your team which Teams channels they have muted. Those are the integrations that failed by sending too much.
Start your project