Get Support
The fastest paths to an answer
Self-serve first (usually fastest)
- Debugging Bots — symptom→cause table for every common failure, plus the full status reference.
- FAQ — the questions everyone asks, answered.
- Dashboard — the All Bots view shows every bot’s live status and timeline; Webhooks → Logs shows recent deliveries.
- Watch it live —
meetstream listenpretty-prints your webhook events, andmeetstream bot status <id> --watchpolls a bot to a terminal state. See the 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, which can inspect your actual bots and transcripts while debugging. Setup: Docs for Agents & LLMs.
Reach the team
Email support@meetstream.ai with:
- The
bot_id(and rough meeting time + platform) - What you expected vs what happened
- 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.
