Aydrian Howard
October 14, 2020

Table of contents
Check out the video below to watch us:
Be sure to Like the video and Subscribe to our YouTube channel.
Unfortunately, Tony and I were not successful in sending a message during this stream, but we were correct as to why sending to a channel was not working. The bot we created had not been added to any of the channels in our Microsoft Teams instance.
I decided to start again from scratch with a new bot. After a few Google search, I came across the Beginners Guide to MS Teams Development #2: Bots guide by Tomomi Imura. I used this to create my bot using App Studio available inside the Microsoft Teams client. I recommend checking out the post if you are looking to get started working with Microsoft Bots.
After creating the Reverse Bot from the post and seeing it work, I added the Team scope and found the option to add my bot to a channel in a team. In App Studio, when you click Install in the Test and distribute section, you can click the dropdown arrow on the Add button and select Add to a team. This will prompt you to select a team and channel to install the bot to.

Once I had done that, I was able to use the methods Tony walked me through on the stream to locate the channel_id and successfully send the message to that channel.
I'm still working on successfully sending a proactive message to a user. I believe we were close and just have to find the correct user_id. I'm going to continue working on it and will include any solution in a follow up post.
To learn more about our Microsoft Teams integration, check out our integration docs.
Is there something you’d like to see us do using Courier? Let us know and it might be the subject of our next Courier Live. We stream a new Courier Live every Wednesday at noon Pacific. Follow us on Twitch to be notified when we go live.
-Aydrian

The $5.9 Billion Rebuild: Why Healthcare Is Replacing Its Notification Infrastructure
The clinical alert and notification market will reach $5.9 billion by 2032, growing at 12.3% annually. That number represents hardware, software, and services combined. It also represents healthcare's admission that pagers and overhead speakers aren't enough anymore. Healthcare organizations are rebuilding how critical information moves through their systems. Regulatory pressure, workforce shortages, and value-based care economics are forcing the investment. The software layer is where outcomes are won or lost.
By Kyle Seyler
February 02, 2026

Vibe Coding Notifications: How to Use Courier with Cursor or Claude Code
Courier's MCP server lets AI coding tools like Cursor and Claude Code interact directly with your notification infrastructure. Unlike Knock and Novu's MCP servers that focus on API operations, Courier's includes embedded installation guides for Node, Python, Flutter, React, and other platforms. When you prompt "add Courier to my app," your AI assistant pulls accurate setup instructions rather than relying on outdated training data. OneSignal's MCP is community-maintained, not official. Courier supports 50+ providers, native Slack/Teams integration, drop-in inbox and preference components, and a free tier of 10,000 notifications/month. Configure in Cursor with "url": "https://mcp.courier.com" and "headers": { "api_key": "YOUR_KEY" }.
By Kyle Seyler
January 22, 2026

The Complete Guide to B2B Customer Engagement
Courier provides the notification infrastructure layer for B2B customer engagement, routing messages across email, SMS, push, in-app, Slack, and Teams based on user preferences and product events. Unlike building notification systems in-house—which takes months of engineering time for features like multi-channel routing, preference management, and delivery tracking—Courier handles this infrastructure so product teams can focus on engagement strategy. B2B customer engagement requires multiple layers: notification infrastructure (Courier), customer data platforms (Segment), product analytics (Mixpanel/Amplitude), and channel-specific tools. Companies with strong engagement programs see 15-25% churn reduction. The key is connecting product events to customer communication at the right moment through the right channel, handling complexity like multiple users per account with different notification needs across work channels.
By Kyle Seyler
January 20, 2026
© 2026 Courier. All rights reserved.