How to introduce an AI coach in Microsoft Teams meetings

You can add Pascal to a Microsoft Teams meeting, and he will join you and provide feedback afterward. Pascal works with your real everyday meetings, so a clear introduction to the colleagues in those meetings matters. A short, consistent explanation helps people understand why the coach is there and how coaching conversations are handled.

Tell people before the meeting starts

A meeting invitation or agenda note is a natural place to mention that Pascal will be joining. A sentence explaining that you are working on your own leadership skills gives colleagues context before they arrive, for example: "Pascal, my AI coach, will join this Teams meeting. I'm working on how I invite input, and his feedback afterward comes to me." Nobody should first learn about the coach from an unfamiliar name in the participant list.

Pascal is an AI coach for every manager: a leadership companion who accompanies them in their meetings and work, and coaches from what actually happened. That description is a helpful starting point when a colleague asks what the coach is for, and an overview of how Pascal joins Teams meetings covers the details of the integration.

For a first meeting with a new group, add a line about the behavior you hope to improve. Colleagues then understand that the feedback concerns your own part in the conversation. Keep the note brief so the agenda itself stays the focus of the invitation.

Explain the purpose in plain words

Framing coaching around your own growth gives colleagues a clear reason for the coach's presence. You might say that you want feedback on how clearly you run meetings or how well you invite input from others. Keeping the focus on your own behavior makes the purpose easy to understand for everyone present.

Choose language that matches the culture of your team and the type of meeting. A weekly team meeting may only need a brief mention, and a first meeting with a new group may call for a fuller explanation. In both cases, name the behavior you are working on so people can connect the coaching to something specific.

Invite questions after your explanation and answer them with the same wording each time. Consistent answers help people understand the arrangement, especially across a team that meets often. Keep a short written version you can paste into invitations or chat messages when it is needed.

Share the coaching boundary consistently

Each person's coaching conversations with Pascal stay private. HR and executives see aggregated, anonymized insights, and only for groups large enough to protect anonymity.

Use that wording exactly when colleagues ask what happens with coaching information. Colleagues will also want to know what they can do in the room if a topic turns sensitive, and the answer is simple. When Pascal joins, he explains how to remove him, and anyone in the meeting can type 'Pascal pause' to stop transcription for a sensitive part of the conversation and 'Pascal resume' to continue. Typing 'Pascal remove' makes him leave and deletes that conversation from his memory.

Managers who lead several teams can keep one shared explanation for all of their meetings. That way every group hears the same boundary and the same reason for the coach joining. A single version is also easier to update if the people responsible for the rollout share new guidance.

Make the introduction part of a routine

Once colleagues know the coach may join, the introduction can become a brief habit in recurring meetings. A one-line reminder at the start of a meeting keeps the purpose visible and takes only a few seconds. After a few meetings, the question your team asks shifts from why the coach is there to whether you followed through.

After the meeting, Pascal sends you feedback, and turning that feedback into a practice intention gives the next meeting a clear focus. You might mention the behavior you intend to practice next time, which keeps the conversation with your team open. Sharing that intention is also a good moment to ask your team members for feedback on the same behavior.

Return to your introduction every few months and check whether it still describes your goals. A new focus behavior, a new team or a new meeting format may call for updated wording. An introduction that still names last quarter's goal tells your team the coaching has gone quiet.

Key takeaways

• You can add Pascal to a Microsoft Teams meeting, and he provides feedback afterward.
• Mention the coach in the invitation or agenda so colleagues know before the meeting starts.
• Frame the coaching around your own leadership growth and the behavior you are practicing.
• Share the coaching boundary in the same exact words, and tell colleagues anyone can type 'Pascal pause' or 'Pascal remove'.
• Turn the feedback after each meeting into a practice intention for the next conversation.