docs(TSP-1228): document meetings widget for Super GTM

[claude]

Summary

• Adds a Meetings widget section to the Super GTM introduction page explaining the unified calendar view, meeting details (subject, location, attendees, Teams links), and automatic matching of meeting prep/summaries across providers
• Updates the Google Calendar integration entry to note that connected events appear in the meetings widget
• Updates the Microsoft Calendar integration entry to note that connected events (including Teams meetings) appear in the meetings widget

Changes

• get-started/chat/super-gtm/introduction.mdx — new ## Meetings widget section
• get-started/chat/super-gtm/integrations.mdx — added bullet point to Google Calendar and Microsoft Calendar "Things to know" sections

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

[linear]

TSP-1228

[github-actions]

🎯 Vibe check

Reviewed: 2 files (2 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟢	Consistency	9/10	integrations.mdx:44 uses "the builders app" — non-standard term that doesn't match any heading or UI element name used elsewhere in these docs. No banned words, British spellings, or heading-case violations found.
🟡	Technical clarity	8/10	integrations.mdx:85 references "Explorer" (a built-in Agent) with no link or explanation — a reader outside the beta has no way to look it up. integrations.mdx:44 tells admins to manage settings "in the builders app" without clarifying what that means.
🟢	Non-technical clarity	9/10	Super GTM is defined clearly up front, the persistent-context sentence is a strong orientation, and the quick-start prompts are approachable. No issues for a non-technical reader.
🟡	Structure	7/10	introduction.mdx is an overview page but has no closing CTA — it ends on a meetings widget description and a one-line feedback note. Two <CardGroup> usages across both files are better served by simpler components (see below).

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

✨ Overall vibe: Solid, well-structured content — the per-integration setup accordions in integrations.mdx are thorough and the Salesforce troubleshooting walkthrough with screenshots is genuinely useful. The two gaps are both small: the introduction page needs a closing CTA to give readers somewhere to go after the overview, and two spot references (Explorer, "builders app") need a link or a word of clarification to be self-contained.

🔧 Issues (2)

• get-started/chat/super-gtm/integrations.mdx:44 — "the builders app" is not a term used elsewhere in these docs and doesn't match any UI element name. Suggest "the Relevance AI app" or the specific nav path (e.g., "from the left sidebar in Relevance AI").
• get-started/chat/super-gtm/integrations.mdx:85 — "Certain built-in Agents (like Explorer)" — "Explorer" is dropped with no link, no explanation, and no context for a reader who isn't already in the beta. Either link to an Explorer page if one exists, or name the constraint more generically (e.g., "read-only built-in Agents").

🧩 Component suggestions (2)

• get-started/chat/super-gtm/introduction.mdx:49–56 — <CardGroup cols={2}> holds only two non-linked cards ("By user" / "By domain"), each with a single sentence of content. CLAUDE.md flags CardGroups for items that aren't navigable and don't have enough substance. A two-item bulleted list is cleaner here:

  - **By user** — provide a list of email addresses to your AE
  - **By domain** — enable for all users with a specific email domain
  

• get-started/chat/super-gtm/integrations.mdx:56–66 — <CardGroup cols={3}> for the three connection states (Connected and enabled / Connected but disabled / Not connected). These are status descriptors for a reference lookup, not navigable feature cards. A small markdown table would be more scannable:

  | State | What it means |
  |-------|--------------|
  | Connected and enabled | Integration is active and the agent can use it |
  | Connected but disabled | Credentials exist but you've toggled it off |
  | Not connected | No credentials stored — a **Connect** button is shown |
  

🏗️ Page structure (1)

• get-started/chat/super-gtm/introduction.mdx — No closing CTA. This is an overview page: readers who reach the bottom just learned what Super GTM is and how to access it, but there's nowhere to go next. The feedback line at line 134 isn't a substitute. Suggest a short closing section:

  ## Next steps
  - [Connect your integrations](/get-started/chat/super-gtm/integrations) — link your CRM, calendar, email, and call tools
  - [Create your first skill](/get-started/chat/super-gtm/skills) — turn a repeatable workflow into a reusable skill
  

🔋 Credit usage

Item	Count
Files reviewed	2
Context pages read	2
Total lines processed	~870

Files read: get-started/chat/super-gtm/integrations.mdx (530 lines), get-started/chat/super-gtm/introduction.mdx (135 lines), enterprise/user-level-authentication.mdx (197 lines), get-started/core-concepts/api-integration.mdx (109 lines)