Community & Resources
Slack Community
Ask questions and get real-time help from the Bolna team and other builders.
Documentation
Search these docs from the bar at the top of any page, or browse the sidebar by topic.
FAQs
Quick answers to the questions we hear most often — pricing, concurrency, phone numbers, and more.
Agent Templates
Ready-made prompts and configs for common use cases — lead qualification, support, scheduling, and more.
YouTube
Tutorials, demos, and walkthroughs for building and deploying voice agents.
Status Page
Check real-time platform status, ongoing incidents, and maintenance notices before filing a report.
Direct Support Channels
What to Include When Reporting an Issue
The faster we can reproduce a problem, the faster we can fix it. Include the following details depending on the issue type.Agent behavior issues
Agent behavior issues
- Agent ID and agent type (single-prompt or graph agent)
- What you expected the agent to do vs. what it actually did
- Steps to reproduce, including any inputs or user_data variables passed
- The relevant
execution_idand conversation transcript, if the issue happened on a live or test call
Call quality issues
Call quality issues
- The
execution_id(call ID), phone number, and timestamp of the call - Direction (inbound/outbound) and telephony provider used
- A description of the issue — latency, dropped audio, wrong transcription, premature hangup, etc.
- Raw logs for the call, pulled via Get Execution Raw Logs or the debug-bolna-calls view in the dashboard
Platform / dashboard issues
Platform / dashboard issues
- Browser and version
- Steps to reproduce
- Screenshots or the exact error message shown
- The account email associated with your Bolna workspace
Batch calling issues
Batch calling issues
- The
batch_idand affected recipient row(s) from your CSV - Expected vs. actual outcome for those recipients
- Whether the issue affects the whole batch or specific recipients — see Batch Calling

