We're consolidating our Help Centers to enhance your experience. During the migration period (April 29 to May 1), you might notice some temporary inconsistencies. No action is required on your side. Please contact Support if you need any assistance.

Booking meetings for Perform & Engage 365 conversations in Microsoft Teams

As part of a conversation workflow in Perform & Engage 365, it is possible to automate the booking of meetings at specific stages. This is currently only supported if you are using Microsoft Teams.

There are two options to allow Perform & Engage 365 to manage meetings:

  • Fully synchronized O365 calendar integration (requires AAD permissions to be granted by an admin). Using this option Perform & Engage 365 will select a time that is available for all attendees - view set-up instructions
  • Notification to attendees to book a meeting (no AAD permissions required). In this option the attendees will receive a notification prompting them to arrange a meeting and Perform & Engage 365 will open a meeting maker in Microsoft Teams for the attendees to select an appropriate time. This is the default option if the O365 connection has not been set-up.

To use either of these options, follow the steps below.

Set stage to require a notification

From the Conversation Template editor screen.

  • Select 'Edit' next to 'Custom Workflow'
  • Add a new stage or select 'Edit' on an existing stage
  • Select 'Book meeting invite for this stage'
  • Select length of meeting
  • Click 'Save'

book-meeting.png

When this workflow runs, Perform & Engage 365 will start a 'Meeting booking process' for employees on that conversation at the start of that stage. If using O365 Calendar Integration then a meeting will be booked automatically for attendees (under the manager's name). If not using this integration, then Perform & Engage 365 will send a notification to the manager suggesting a meeting time in the Microsoft Teams meeting maker.

Was this article helpful?
0 out of 0 found this helpful

Comments

Article is closed for comments.