Teams | Collaboration | Customer Service | Project Management

Good customer service runs on good information. Agents need to be ready with an instant answer to any question, or the customer will walk away unhappy — even if the eventual resolution is effective. The information shared with customers also needs to be consistent. No one likes to be bounced around between departments that all say something different. Unfortunately, it’s not easy to ensure your agents have accurate information at their fingertips.

In this series, I explain how to use Twitch EventSub and Courier to automatically send notifications to multiple destinations – Slack, Discord, and more – when your Twitch stream goes live. In part one, we built a Node.js app using Express.js to accept events from Twitch EventSub. In part two, we listened for our event and triggered a notification using Courier. Now, in part three, we're going to use Courier’s List API to send multiple notifications when our event is triggered.

Whether you do it quarterly, annually, or even weekly, running a planning workshop can be challenging. You need to make sure everyone understands the big picture and vision. You also need to ensure each person has a voice in the planning process. Finally, you need to lead the group to alignment and verify that they’re clear on next steps. These are the challenges I confronted while leading a goal-setting session at Miro’s recent Executive team offsite (virtual this year).

Are you finding social media collaboration a challenge within your remote team? This article will guide you through the exact steps and tools you can use to make it easier. Remote working is a necessity that a lot of worldwide companies had to adapt in order to survive. But something that once was a necessity actually turned into a preference for many employees. In fact, studies show that 99% of employees would choose to work remotely, at least part-time, for the rest of their careers.

In theory, the world of integrations is designed to make our life easier. By bringing systems together, teammates can share information more quickly, and managers can have more oversight over performance, deadlines, and budgets. But what happens when this individual software and system integrations become too unwieldy or complicated to manage?

In any transaction where a seller sells equipment or products to a buyer for which periodic servicing or maintenance is required for its proper functioning, it is advisable to enter into an agreement between both parties on the terms of servicing of that equipment or product. These agreements, commonly referred to as an Annual Maintenance Contract (AMC), are essential to formalizing this process.

Our Makefile entry point for developing against the Mattermost Server already tries to simplify things for developers as much as possible. For example, when invoking make run-server, this build tooling takes care of all of the following (among other things!).