docs(TSP-1258): document Microsoft Teams two-way conversations and outreach-only mode

[claude]

Summary

• Documents two-way conversation flow: agent responses arrive as Adaptive Cards with a Send button so users can reply without @mentioning the bot, and conversation context is maintained across multiple exchanges
• Documents proactive DM capabilities: agents can initiate conversations in Teams DMs, with full context carried through subsequent back-and-forth replies
• Documents the new outreach-only trigger mode, which limits the trigger to replies within agent-initiated conversations and ignores new root-level messages from users

Linear issue: https://linear.app/relevance/issue/TSP-1258/

Test plan

• Verify all headings are in sentence case
• Confirm new subsections render correctly in Mintlify (Adaptive Cards, two-way conversations, proactive DM conversations, outreach-only mode)
• Confirm no broken internal anchor links

[linear]

TSP-1258

[mintlify]

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

Project	Status	Preview	Updated (UTC)
relevanceai	🟢 Ready	View Preview	Jun 1, 2026, 7:15 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	6/10	Product nouns "Agent", "Trigger", and "Workforce" appear lowercase throughout body text and component titles — roughly 15 instances across step titles, accordion titles, card titles, and prose.
🟡	Technical clarity	7/10	Missing support link in the beta Note at line 260; the outreach-only setup path is vague; anchor links referencing headings with - and & may not resolve.
🟢	Non-technical clarity	9/10	Concepts are well defined before instructions start. Adaptive Cards are explained in context. Outreach-only mode has a concrete use-case example.
🟢	Structure	9/10	Logical flow from setup → triggers → tool steps → notifications → admin → troubleshooting → FAQ. Depth layered well. Minor: Prerequisites uses <CardGroup> for a non-navigable checklist.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: This is a thorough, well-structured integration page — good technical depth, clear step-by-step flows, solid troubleshooting and FAQ coverage. The main drag is a systematic failure to capitalize the product nouns "Agent", "Trigger", and "Workforce" in titles and prose; a quick find-and-replace pass would get this close to clean.

🔧 Issues (18)

Capitalization — product nouns (Agent, Trigger, Workforce)

• microsoft-teams.mdx:134 — "your agents respond" → "your Agents respond" (Relevance AI product noun)
• microsoft-teams.mdx:136 — "trigger agents" → "trigger Agents"; "works for [workforces]" → "works for [Workforces]"
• microsoft-teams.mdx:149 — Step title "Open your agent's settings" → "Open your Agent's settings"
• microsoft-teams.mdx:153 — Step title "Add a Microsoft Teams trigger" → "Add a Microsoft Teams Trigger"
• microsoft-teams.mdx:163 — Step title "Configure trigger conditions (optional)" → "Configure Trigger conditions (optional)"
• microsoft-teams.mdx:167 — Step title "Write agent instructions" → "Write Agent instructions"
• microsoft-teams.mdx:172 — "your agent asks before sending messages. Switch to autopilot once you're confident." → "your Agent asks..."
• microsoft-teams.mdx:194 — Card title "Workforce triggers" → "Workforce Triggers" (both are product nouns)
• microsoft-teams.mdx:280 — Step title "Add an agent notification" → "Add an Agent notification"
• microsoft-teams.mdx:393 — Accordion title "Teams trigger option not visible in agent settings" → "...in Agent settings"; body text "in your agent or workforce settings" → "in your Agent or Workforce settings"
• microsoft-teams.mdx:397 — Accordion title "Trigger is configured but the agent isn't responding" → "...but the Agent isn't responding"
• microsoft-teams.mdx:409 — Accordion title "Why don't I see my Teams channel in the dropdown when setting up a trigger?" → "...a Trigger?"
• microsoft-teams.mdx:417 — Accordion title "Do triggers work for private messages?" → "Do Triggers work for private messages?"
• microsoft-teams.mdx:421 — Accordion title "Can my agent access files shared in Teams?" → "Can my Agent access..."
• microsoft-teams.mdx:425 — Accordion title "What's the difference between the pre-built tool steps and the API Call tool step?" → "...Tool steps...Tool step"

Missing support link

• microsoft-teams.mdx:260 — "Please report any issues to our support team." has no link. All other support references on this page link to /get-started/support. Change to "Please contact our support team to report any issues."

Potentially broken anchor links

• microsoft-teams.mdx:23,73,97 — #admin-consent-permissions targets ## Admin consent & permissions. The & in the heading slug may render as #admin-consent--permissions (double hyphen) depending on Mintlify's slugifier. Verify this resolves in the live preview.
• microsoft-teams.mdx:142 — #step-1-connect-the-integration and #step-2-install-the-relevance-ai-app-in-microsoft-teams target headings that include - (space-dash-space). The slug may render with extra hyphens (e.g. #step-1---connect-the-integration). Verify in preview.

🧩 Component suggestions (2)

• microsoft-teams.mdx:15–28 — Prerequisites <CardGroup>: these four items are not navigable and are not parallel choices — they're a checklist of requirements. A <CardGroup> adds visual weight without benefit here. Consider a plain <ul> list, or if you want to keep visual structure, use a <Steps>-less bulleted list under the heading.
• microsoft-teams.mdx:219 — "open your trigger settings and set the trigger mode to Outreach only" — this is the only setup instruction that doesn't specify a navigation path. Add the preceding navigation step: "In your agent's Triggers section, open the trigger you want to modify, then set the trigger mode to Outreach only."

⚠️ Contradictions (0)

No contradictions found between this page and the Outlook or SharePoint pages it cross-references.

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2 (outlook.mdx, slack.mdx)
Total lines processed	~873

Files read: integrations/popular-integrations/microsoft-teams.mdx (437 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.