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... Continue Reading →

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... Continue Reading →

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... Continue Reading →

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... Continue Reading →

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... Continue Reading →

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... Continue Reading →

Website Powered by

Up ↑

%d bloggers like this: