SYSTEM · TELEMETRY · BOT ONLINE
Diagnostics
Live read of what the bot actually sees — telephony config and AI-provider keys sourced from the database (UI saves) merged with the bot's .env. No on-disk parsing, no stale state.
Dashboard environment
Bootstrap config the dashboard reads from its own .env.local — these can't be set via the UI because the dashboard needs them before it can serve anything.
- DATABASE_URL / POSTGRES_URLdashboardSET
- BOT_API_URLdashboardSET
- DASHBOARD_PASSWORDdashboardSET
- COACHING_AUTH_TOKENdashboardSET
Telephony providers
Which carrier places & carries calls. Bot reports the active one as vobiz. Configure →
- Twilioneeds setup—
- Plivoneeds setup—
- Asteriskneeds setup—
- Vobizactivecredentials set+911171366938
Recording storage
Where call recordings live. S3 is opt-in — when configured, recordings upload after each call and playback falls back to S3 when the local copy is rotated.
- Local recording dirbot/var/spool/asterisk/recording
- Record inbound (global default)env / per-agent overrides winOFF
- S3 bucketdefault region—
AI provider keys
Speech, voice and language model credentials. Manage →
- OPENAI_API_KEYui/dbSET
- ANTHROPIC_API_KEY——
- GEMINI_API_KEY——
- GROQ_API_KEY——
- MISTRAL_API_KEY——
- OPENROUTER_API_KEY——
- DEEPSEEK_API_KEY——
- TOGETHER_API_KEY——
- SARVAM_API_KEYui/dbSET
- DEEPGRAM_API_KEY——
- ASSEMBLYAI_API_KEY——
- ELEVENLABS_API_KEY——
- CARTESIA_API_KEY——
- LLM_PROVIDERbot/.envSET
- STT_PROVIDERbot/.envSET
- TTS_PROVIDERbot/.envSET
Database records
Live row counts pulled with SELECT count(*) on each table.