Context

Slack thread: https://slack.com/archives/C0AE8A81LE6/p1770829426570839

The thread shows team members updating channel topic metadata with key contacts/agents, which suggests operational contact points are being managed in Slack rather than easily found from docs.

Problem

Current documentation does not make support/escalation entry points easy to discover. Users and operators may not know where to find:

• who to contact for incident reproduction/debug support
• where support workflow starts (Cloud vs self-hosted)
• which docs page to check first for troubleshooting vs FAQ

This creates friction and pushes critical routing info into Slack-only tribal knowledge.

Suggested Fix

• Add a short, searchable "Get Help / Escalation" section to high-traffic entry pages (for example intro/FAQ/troubleshooting entry points).
• Include clear keywords users are likely to search: support, escalation, incident, reproduce, troubleshooting, who to contact.
• Add cross-links between Cloud intro/FAQ and troubleshooting pages so users can navigate quickly to the correct path.
• Add one concise decision flow: "I have an outage", "I need product usage help", "I found a potential bug".
• Ensure page titles and headings include support-oriented terms to improve site search results.