> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.meetstream.ai/guides/help/support/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.meetstream.ai/_mcp/server.

# Get Support

> The fastest paths to an answer on MeetStream: the docs MCP server, the dashboard, and support@meetstream.ai for anything the docs do not cover.

## Self-serve first (usually fastest)

* **[Debugging Bots](/guides/help/debugging-bots)** — symptom→cause table for every common failure, plus the full status reference.
* **[FAQ](/guides/help/faq)** — the questions everyone asks, answered.
* **Dashboard** — the [All Bots view](https://app.meetstream.ai/bots) shows every bot's live status and timeline; [Webhooks → Logs](https://app.meetstream.ai/webhooks) shows recent deliveries.
* **Watch it live** — `meetstream listen` pretty-prints your webhook events, and `meetstream bot status <id> --watch` polls a bot to a terminal state. See the [CLI](/build-with-ai/meetstream-cli).

## Ask from your editor

Connect the **docs-search MCP** (`https://docs.meetstream.ai/_mcp/server`) and your AI assistant can search these docs directly — or go further with the [action MCP server](/build-with-ai/meetstream-mcp-server), which can inspect your actual bots and transcripts while debugging. Setup: [Docs for Agents & LLMs](/build-with-ai/docs-for-agents).

## Reach the team

Email **[support@meetstream.ai](mailto:support@meetstream.ai)** with:

1. The `bot_id` (and rough meeting time + platform)
2. What you expected vs what happened
3. The create\_bot payload if config-related (redact your API key)

That's everything needed to trace a session — bot IDs let us reconstruct the full status timeline on our side.

> Meeting bot API documentation for Zoom, Google Meet and Microsoft Teams: create bots, stream real-time audio, transcribe, and run in-meeting voice agents.