Add Microsoft Teams Outreach replies only trigger documentation (TSP-1260)

[claude]

Summary

• Adds a new Advanced trigger settings section to the Microsoft Teams integration page
• Documents the Outreach replies only toggle introduced in PR #14979
• Explains the feature's purpose, how to enable it, the visual indicator (subtitle change to "On replies to outreach messages"), and the resulting behavior change

Changes

integrations/popular-integrations/microsoft-teams.mdx — new section inserted after "Setting up a trigger" and before "How triggered conversations work", modelled on the equivalent section in the Slack integration page.

Linear issue

https://linear.app/relevance/issue/TSP-1260/

Adds documentation for the new 'Outreach replies only' toggle in Microsoft Teams trigger configuration (PR #14979). This feature allows agents to respond only to replies to their own messages rather than all channel messages.

[linear]

TSP-1260

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
relevanceai	🟢 Ready	View Preview	Jun 1, 2026, 7:17 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[github-actions]

🎯 Vibe check

Reviewed: 1 file (1 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	7/10	Product terms "agents" and "workforces" appear lowercase in several places where they refer to Relevance AI Agents and Workforces.
🟢	Technical clarity	9/10	One step in the agent notifications setup is overloaded with content. Otherwise permissions table, troubleshooting, and error state coverage are solid.
🟢	Non-technical clarity	9/10	Prerequisites are well-presented, the two-step setup framing is helpful, and warnings are well-placed.
🟡	Structure	7/10	The "Setup overview" cards use the wrong pattern for sequential steps. The "Outreach replies only" enable flow uses a plain numbered list where the rest of the page uses <Steps>.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5. Scores are a single overall judgment about the whole PR — not per file. The dropdowns below contain the line-by-line specifics.

✨ Overall vibe: This is a thorough, well-structured integration page that covers setup, triggers, tool steps, admin consent, permissions, troubleshooting, and FAQs — a noticeably higher quality baseline than most sibling pages in this directory. The main thing holding it back is inconsistent capitalization of product terms (Agents, Workforces) and a couple of component pattern mismatches that are easy fixes.

🔧 Issues (5)

• integrations/popular-integrations/microsoft-teams.mdx:134 — "users interact with agents right where they already communicate" → "Agents" (referring to Relevance AI Agents, a product term)
• integrations/popular-integrations/microsoft-teams.mdx:136 — "trigger agents and have two-way conversations" → "Agents"
• integrations/popular-integrations/microsoft-teams.mdx:136 — link text [workforces] → [Workforces] (Relevance AI product term)
• integrations/popular-integrations/microsoft-teams.mdx:138 — "Teams triggers activate only on new messages" → "Triggers" (Relevance AI product term; the Slack page uses "Trigger" capitalized in equivalent contexts)
• integrations/popular-integrations/microsoft-teams.mdx:210 — Card title "Workforce triggers" → "Workforce Triggers" (both are capitalized product terms)

🧩 Component suggestions (3)

• integrations/popular-integrations/microsoft-teams.mdx:34–41 — <CardGroup> is used to summarize two sequential setup steps, but CLAUDE.md says CardGroup is not appropriate for sequential steps or considerations — only for parallel choices. These two steps are mandatory and ordered. Replace with a <Note> like: "Setting up Microsoft Teams requires two steps: connecting your Microsoft account (Step 1) and installing the Relevance AI app in Teams (Step 2). Both are required." Or just let the ## Step 1 / ## Step 2 headings below carry the structure on their own and remove the summary block.

• integrations/popular-integrations/microsoft-teams.mdx:182–186 — The "To enable:" sub-section under "Outreach replies only" uses a plain numbered list, inconsistent with every other procedure on this page that uses <Steps>. Wrap in a <Steps> component to match the established pattern.

• integrations/popular-integrations/microsoft-teams.mdx:280–281 — Step 3 "Configure notification settings" packs three distinct actions into a single step description: selecting the platform, choosing a notification trigger with multiple sub-options, selecting an account, and selecting a channel. Split into at minimum two steps — one for selecting platform + trigger type, one for selecting account + channel.

⚠️ Contradictions (1)

• integrations/popular-integrations/microsoft-teams.mdx:150 vs integrations/popular-integrations/outlook.mdx:269 — The Teams page says to navigate to "your agent in Relevance AI" and go to the Triggers section to add a trigger. The Outlook page says to "Click on 'Integrations & API Keys' in the sidebar" and then "Under 'Triggers', click on the Outlook button." These describe meaningfully different UI paths for trigger setup. One appears to be outdated — verify which matches the current product and align the Outlook page.

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2
Total lines processed	~1,115

Files read: integrations/popular-integrations/microsoft-teams.mdx (433 lines), integrations/popular-integrations/outlook.mdx (422 lines), integrations/popular-integrations/slack.mdx (260 lines)

[jordanc-relevanceai]

Consolidated into #657 (Teams outreach + conversation docs). Closing in favor of that PR.