Reactions and Easier Reporting with Company Communicator

Writing today to let you all know about two new features for the Company Communicator community fork. If you update to the latest version, your users will be able to react to messages sent by the bot and their opinion will be recorded back into the database. You can use the new feature to measure...

Proactive Messages with Logic Apps Limits

I had a good discussion with two colleagues this week on limits and performance when using logic apps to send proactive messages with Teams. Of course the logic apps alternative is not the fastest and most efficient way to send proactive messages, but for sure is one of the easiest ways to workaround the imposed...

Sending Large Number of Proactive Teams Messages with Azure Logic Apps

Here is the problem. You have the need to send a large number of Teams messages for your users and you cannot do that using the standard Power Automate Teams connector as it has a limit on the number of calls you can do per sec/min/hour/day/month. You also cannot use the Graph API as you...

Company Communicator E-mail Fallback

Using e-mail to reach users who haven't read CC messages in Teams Recently my team got an interesting request from a customer with a frontline worker scenario. They are rolling out Teams to all their frontline workers, but at this moment the vast majority is still not running Teams in their mobile phones. They are...

User names on CC community fork reports

I received some requests asking how to include names on the CC reports. By default the reports have only user ids, and I agree only that information is not sufficient to correctly evaluate impact of communications. There are basically two ways to improve the reports to have names and not only user ids. First one...

If you need a branch in the 4.51 version

I received a few messages from partners and customers that are still looking for the 4.51 build. I recommend upgrading as soon as possible to the latest version, but I understand there are some situations where you still need to stay in previous versions for some time. For that reason, I created a branch called...

Company Communicator – v5.1 Merge

Hello everyone, long time no see. Writing this to communicate that I just finished the merge of v5.1 code into the community fork of Company Communicator. So please pay attention: If you are using a setup based on v4.X, you need to follow instructions documented on the v5 migration guide here. Do not sync the...

Company Communicator in S1/Small App Service Plans

We got a few cases where customers were selecting a minimum resource App Service plan when deploying company communicator. The original/standard CC deployment uses a S2/Medium App Service plan by default, but we got a few cases where a smaller plan was being selected during deployment. We all need to understand that the reduction in...

Let’s build a brand new MSX computer – Part 2

PCB and components arrived. So many packages, from US, Spain, Czech Republic and China. I bought two sets of PCBs, and they are slightly different. Checking the components and comparing with the PCB footprints I figured out the DIN8 connectors will not fit and need to order new ones. The rest seems to be OK....

Button Click Tracking for Company Communicator (and updated report)

This week we have an awesome contribution from Mike Francis and Luis Henrique Demetrio, two CEs from our App Consult team. They jumped to the challenge to extend the tracking framework we created for Company Communicator a few months ago to also track button clicks. This is a change requested by multiple customers and is...