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

Customer Engagement Platform vs CRM: Key Differences Explained
A CRM stores customer data: contacts, purchases, support tickets, and pipeline. It answers "who are our customers?" A customer engagement platform (CEP) orchestrates communication across email, push, SMS, in-app, and chat. It answers "what should we tell them next?" CRMs focus on historical records. CEPs process real-time behavior and trigger messages based on actions. Most teams need both, plus a third layer: notification infrastructure for reliable multi-channel delivery. Courier bridges CEP and infrastructure by combining routing, failover, and delivery tracking with engagement features like preference management, visual templates, and in-app notification centers.
By Kyle Seyler
January 07, 2026

How We Investigate Support Tickets at Courier
Courier's support team resolves complex issues 4X faster using parallel investigation. Here's how it works: when a ticket comes in, an AI agent starts exploring the codebase while the support engineer examines actual customer data. The agent traces code paths and searches past investigations. The human reads event logs and forms hypotheses based on real state. Running both simultaneously catches mismatches fast—the agent sees what could cause a problem, the human sees what actually happened. This post breaks down the workflow, tools, and documentation structure that makes it repeatable.
By Thomas Schiavone
December 18, 2025

Top 20 Notification Examples That Actually Drive Engagement
Explore 20 stellar notification examples from industry leaders like Rippling, Slack, FedEx, Crocs, Miro, Trustpilot, OpenTable, and BambooHR that actually drive engagement. From payday celebrations to healthcare reminders, these patterns showcase what makes notifications effective across email, SMS, push, and in-app channels. Courier's enterprise platform enables intelligent routing, multi-channel orchestration, and universal inbox integration to implement these proven patterns at scale.
By Kyle Seyler
September 25, 2025
© 2026 Courier. All rights reserved.