Surveys delivered inside Teams

Reach people with a private bot message in the tool they already have open, on one tenant-wide consent that never touches the contents of a chat or a file.

Book a free, no-obligation product demo call with our experts.

What does connecting Microsoft Teams to CultureMonkey involve?

Connecting Teams touches your Microsoft 365 tenant, so it is an admin action rather than a settings toggle. A CultureMonkey account admin starts the flow from Integrations, then Channels, and a Microsoft 365 administrator grants consent. Those can be two different people working together, which is worth lining up before you begin.

Consent covers the minimum needed to do two things, match people and message them:

  • Read your directorySo CultureMonkey can look up users by email and pair each Microsoft 365 account with the right employee.
  • Install the app for usersSo the CultureMonkey bot can open a private, one-to-one chat with each matched person.
  • What is not coveredReading the contents of your employees' chats or files. The bot sends only the invitations and reminders you configure.
  • Scope of the connectionTenant-wide and stored against your whole account, which is why it is done once rather than per survey.
  • Matching keyEmail, in every version of the app. A connection can succeed while individual sends still fail if an employee's email does not match Microsoft 365.
  • App versionEither a package published into your own app catalog or CultureMonkey's shared app. Decided by account settings, not chosen in the connect screen.
How it works

What the Microsoft Teams connection covers

Type of integrationDelivery channel
ConnectionTenant-wide Microsoft admin consent
Employee matchingWork email to Microsoft 365
AvailabilityPlan-gated per account
Illustrative product view. Values shown are sample data.
Key capabilities

One consent, then a channel you choose per survey

Teams is a strong route to people standardised on Microsoft 365. It works best treated as one channel in a mix, because guests, external accounts and email mismatches all leave gaps a second channel covers.

A private message, not another email

For organisations standardised on Teams, a bot message reaches people in the tool they already have open, which is usually the difference between a reply today and a reply next week for any engagement survey.

  • The invitation arrives as a private one-to-one chat from the CultureMonkey bot.
  • Reminders ride on the same connection, so there is nothing extra to authorize for them.
  • Delivery is reported per channel, so a survey's notification metrics show Teams success and failure counts alongside your other feedback routes.
Illustrative product view. Values shown are sample data.

Consent your Microsoft admin can read in one screen

The consent screen is where an administrator sees exactly what they are approving. It is two capabilities, and neither one touches content.

  • Read your organisation's users, so people can be matched by email.
  • Install the app for users, so the bot can message each matched person privately.
  • Nothing that reads chats or files. Survey answers stay in CultureMonkey under its anonymity rules, never in Teams.
Illustrative product view. Values shown are sample data.

Connecting is not sending

Connecting the tenant makes Teams available. It does not route every survey through it, which is deliberate: you stay in control of which surveys go where, including lifecycle sends.

  • Teams appears as a delivery channel while you build a survey, and you turn it on per survey.
  • If people are not getting messages, confirm Teams is selected on the survey itself before anything else.
  • Email mismatches are the most common reason a send fails once connected, so keeping the roster clean via an HRIS sync pays off here too.
Illustrative product view. Values shown are sample data.
Channel mix

How the delivery channels compare

Chat lifts participation for the people who live in it. It works best as one channel in a mix, because no single route reaches everyone.

ChannelBest forHow it works
EmailThe default for most workforcesAlways on. CultureMonkey manages delivery for your domain end to end
SlackTeams that live in SlackA CultureMonkey bot DMs invites and reminders and collects anonymous responses
Microsoft TeamsOrganizations standardized on TeamsThe CultureMonkey bot delivers surveys inside Teams
SMSDeskless staff without regular emailText-message invites and reminders
WhatsAppReaching people on their phonesEmployees can also message in to raise anonymous feedback
Recognition & compliance

Built for enterprise security, recognized for performance

Security & compliance
AICPA SOC compliance badgeGDPR compliance badgeISO 27001 compliance badge
Rated 4.7/5 on G2
G2 High Performer Enterprise badgeG2 Momentum Leader badgeG2 Fastest Implementation badge
Explore more

Connect the rest of your stack

SlackThe same bot delivery in Slack, connected by OAuth rather than tenant consent.BambooHRKeep the employee list Teams delivery depends on in sync.KekaSync employees plus teams, locations and business units.Security and complianceSOC 2, ISO 27001 and GDPR posture, and how employee data is handled.
FAQ

Frequently asked questions

Who can connect Microsoft Teams?

A CultureMonkey account admin starts the flow, but the Microsoft consent step must be completed or approved by someone with Microsoft 365 admin consent rights for your tenant. Those can be two different people working together, so line it up early.

What permissions is CultureMonkey asking for?

Enough to match employees to their Teams accounts by reading your directory, and to message them by installing the app for users. CultureMonkey does not read your employees' chats or files. Exactly which Microsoft Graph scopes appear depends on the app version your account uses.

Do I need to connect Teams for every survey?

No. Connecting is a one-time, account-wide setup. Once it is done you choose Teams as a channel on whichever surveys you want, without reconnecting each time.

I connected Teams but people are not getting messages. Why?

Connection and delivery are separate. First confirm Teams is actually selected as a channel on the survey. Then check for an email mismatch between CultureMonkey and Microsoft 365, which is the most common reason a matched send fails. A survey's per-channel notification metrics flag Teams failures.

Which version of the Teams app will we get?

That is determined by your account settings, not something you pick in the connect screen. Most newer accounts use CultureMonkey's shared public app; some legacy accounts use the classic per-tenant app published into your own catalog. In every version, email remains the matching key.

What about guests and external accounts?

People who are not full members of your Microsoft 365 tenant may not appear in the directory, so they may not be reachable over Teams. Keep another channel in the mix for them rather than treating Teams as the only route to everyone.

How do we disconnect Teams?

There is no self-serve disconnect button on the Teams card. An administrator revokes CultureMonkey's consent and removes the app on the Microsoft side, and you contact support to deactivate the channel on the CultureMonkey side. If you only want to pause sending, leave Teams unselected on your surveys instead.

The Teams card is missing from our Channels page. Why?

Microsoft Teams is a plan-gated channel. If the card is not there, it is not enabled for your account yet, and your CultureMonkey contact can switch it on.
Get started

See survey delivery running in your own tenant

Book a free, no-obligation product demo call with our experts.