Contents

  1. Overview

  2. Prerequisites

    1. Verify Your Microsoft Organization Role

    2. Allow Third-Party Apps in the Teams App Store

    3. Allow The Receptionist App in the Teams App Store

    4. Allow Teams Users to Install The Receptionist App

    5. Avoid App Setup Policies

    6. Verify Email Addresses Match

  3. Getting Started

    1. Authorizing the Integration

    2. Connecting Your Contacts

  4. Additional Help

Overview

Our Microsoft Teams integration can notify your account's contacts when their visitors or deliveries have arrived.

Clicking the details link in the notification will take you to the visit details page on our site where you can see responses to visitor fields filled out by the visitor, find any agreements they signed, and even have a chat with the visitor if Two-Way Chat is enabled for the button that was used.

Speaking of chat, if you have added Quick Replies to your account, the Microsoft Teams notification message will include buttons for each quick reply to send to your visitor without even needing to go to the details page.

And any responses a visitor sends from the iPad used to check-in will be delivered to their employee contact in Microsoft Teams.

If this is something you want to enable for your organization, follow the steps below.

Please note that once the Integration is turned on, it can take 30-60 minutes for messaging rules to appear for your contacts.

Prerequisites

Before setting up the Microsoft Teams integration, please first ensure the following requirements are in place to avoid complications during setup.

Please note any changes made to your Microsoft organization's environment (in Azure Portal or Microsoft Teams Admin Center) may take several hours to come into effect. We recommend waiting one day after saving changes before enabling The Receptionist integration for Microsoft Teams.

Verify Your Microsoft Organization Role

In order to authorize our integration, a Global Administrator role is needed. You can see if you are a global administrator by going to the "Roles and administrators" area of your Azure Portal. If your role shows up as "Global Administrator", then you will be able to consent to our integration. If you cannot access this page or are not a Global Administrator, you will need to find someone else in your organization to enable the integration.

Allow Third-Party Apps in the Teams App Store

To receive notifications from The Receptionist in Microsoft Teams, our app must be available for installation and uninstallation from the Microsoft Teams App Store. Please have your organization's Teams administrator visit the Microsoft Teams Admin Center, navigate to Teams apps > Manage apps, and then click on the "Org-wide app settings" button in the upper right. Toggle the "Allow third-party apps" setting to "On" and then click "Save".

Allow The Receptionist App in the Teams App Store

Also in the Microsoft Teams Admin Center, go to Teams apps > Manage apps, search for "The Receptionist" in the table at the bottom, click our app name, and then click the "Allow" button.

Allow Teams Users to Install The Receptionist App

Go to Teams Apps > Permission policies, and check each policy covering users who will be receiving notifications from The Receptionist in Microsoft Teams. Under "Third-party apps", ensure that "Allow all apps" is selected and then click "Save".

Alternatively, your Teams administrator may choose "Allow specific apps and block all others". If so, then make sure to click "Allow apps" and search for "The Receptionist" to allow it and then click "Save".

Avoid App Setup Policies

Please do not add The Receptionist app to any Teams app setup policy covering users who will be receiving notifications from The Receptionist in Microsoft Teams. Doing so will prevent our app from uninstalling itself, which is sometimes necessary in the process to set up receiving notifications from The Receptionist.

To ensure an app setup policy does not include The Receptionist, go to Teams apps > Setup policies. For each policy, make sure "The Receptionist" is not in the list of installed apps, and then click "Save".

Verify Email Addresses Match

This integration uses email addresses to match your account's contacts with users in your Microsoft organization. Note that we do not use your Teams users' "User Principal Name", which is the username used to sign into Teams, to match.

If the email address field between a Teams user and their corresponding contact do not match, they will not be able to receive notification from The Receptionist in Teams. You can check that these two fields are the same for any contact with the following process:

  1. Go to your account's Contacts page and edit one of your contacts. Note the email address entered.

  2. Go to the Users area of the Azure Portal, find the user corresponding to the contact you edited in Step 1, and verify that the "Email" field (in the "Contact info" section) matches the address from Step 1. Ignore the "User Principal Name" field.

  3. If these don't match, then either edit the contact on the Receptionist or the Microsoft user in the Azure Portal such that they do match.

  4. After making changes, remove and then re-add the Microsoft Teams integration to restart the synchronization process.

Getting Started

For most organizations, setting up our Microsoft Teams integration is as easy as simply enabling it from your account's Integrations page with the Add button.

Authorizing the Integration

After clicking the Add button, you will be taken to Microsoft's consent page. To connect to your Microsoft organization, a Global Administrator of your Microsoft organization will need to sign in and click the Accept button.

Connecting your Contacts

Once you accept the authorization request, we will install our notification bot and set up a Teams notification preference for each contact we match to someone in your Microsoft organization. We send a welcome message when the app is installed to let your contacts know they will now receive notifications there when visitors and deliveries arrive for them.

Do you have questions about setup, security, or additional troubleshooting?

We've put together a Frequently Asked Questions article that provides even more detail about this new integration!

Did this answer your question?