bolna-ai
- 20 skills
- 0 followers
- 9 hours ago last updated
- ▌ Make Call · bolna-ai bundleInitiate, schedule, personalize, retry, and stop outbound Bolna Voice AI calls. Use when the user wants to test an agent, call a recipient, schedule a callback, pass user_data dynamic variables, override a same-provider voice, or cancel a queued or scheduled call.
- ▌ Setup Tools · bolna-ai bundleAdd function tools to Bolna voice agents so they can take real-world action during a live call: transfer to a human, fetch/post data via any HTTP API, fetch and book Cal.com slots, look up current time, or capture DTMF keypad input. Uses the OpenAI function-calling schema with Bolna extensions (`key: "custom_task"`, `value` API config, `pre_call_message`). Use when the agent must do more than speak — escalate, retrieve, book, log, verify, or trigger a workflow.
- ▌ Add Provider · bolna-ai bundleAdd, list, and remove Bolna providers for telephony, LLM, speech-to-text, and text-to-speech services such as Twilio, Plivo, Exotel, OpenAI, Anthropic, Azure, ElevenLabs, Deepgram, Sarvam, Cartesia, Polly, and others. Use when the user wants to bring their own credentials.
- ▌ Create Agent · bolna-ai bundleCreate a Bolna Voice AI agent with the current v2 API, including system prompt, welcome message, LLM, voice, transcriber, telephony input and output, latency tuning, guardrails, knowledge bases, and function tools. Use when the user wants to build, deploy, or clone a Bolna voice agent.
- ▌ Create Batch · bolna-ai bundleCreate, schedule, monitor, stop, and delete Bolna batch calling campaigns using CSV recipients and per-recipient dynamic variables. Use for bulk outreach, surveys, collections, reminders, sales, support callbacks, and campaign execution.
- ▌ Manage Agents · bolna-ai bundleList, fetch, patch, fully update, delete, and stop queued calls for Bolna v2 voice agents. Use when the user wants to inspect agent configuration, change prompts or voices, back up an agent, decommission an agent, or cancel all queued calls for one agent.
- ▌ Setup API Key · bolna-ai bundleGenerate, store, and verify a Bolna API key for BOLNA_API_KEY. Use when starting a Bolna project, configuring authentication, seeing 401 or 403 errors, or checking wallet and concurrency with the user API.
- ▌ Setup Inbound · bolna-ai bundleWire a Bolna voice agent to answer inbound calls on a specific phone number. Covers the `POST /inbound/setup` mapping, IVR menus and digit-collect steps (Plivo-only), caller identification via `ingest_source_config` (Internal API / CSV / Google Sheet), inbound spam controls (`inbound_limit`, `whitelist_phone_numbers`, `disallow_unknown_numbers`), and auto-switch multilingual system messages (hangup, user-online check, tool wait). Use when building a support line, front-desk agent, IVR router, or multi-agent department setup.
- ▌ Setup Webhook · bolna-ai bundleConfigure Bolna webhooks for real-time call status and execution updates, validate webhook URLs, receive payloads, reconcile execution IDs, and build a local receiver. Use for CRM sync, dashboards, post-call automation, Make, Zapier, n8n, or custom backend integrations.
- ▌ Get Executions · bolna-ai bundleFetch and analyze Bolna call execution data, raw logs, transcripts, recordings, costs, statuses, hangup details, extracted data, agent history, and batch executions. Use for debugging failed calls, analytics export, CRM sync, webhook reconciliation, and call monitoring.
- ▌ Bolna Voice Prompt · bolna-ai bundleAuthor production-grade prompts for Bolna outbound and inbound voice agents (Hindi/English/Hinglish), and diagnose-and-fix existing prompts from call transcripts. Use this skill whenever the user describes a calling-bot or voice-agent use case (e.g. lead qualification, recruitment screening, appointment booking, onboarding calls, renewal/collection calls, NPS, surveys), pastes a Bolna or voice-agent transcript and asks for improvements, asks for an Indian-language calling script, or mentions Bolna, GPT-4.1 mini voice agents, IVR scripts, telecaller bots, or similar — even if they do not name "Bolna" explicitly. This skill produces output in a very specific structure (numbered sections, Hindi-first/English-second scripted lines, paragraph-prose instructions, YAML FAQs, JSON context blocks) and that structure is non-negotiable, so always consult this skill before drafting any voice-agent prompt.
- ▌ Setup Sip Trunk · bolna-ai bundleBring your own SIP trunk to Bolna (BYOT) for AI voice agents. Create a trunk with gateways, IP-based or user/password auth, UDP/TCP/TLS transport, optional SDES (SRTP) media encryption, add DID numbers, and wire them to agents for inbound or outbound calls. Use with Twilio Elastic SIP, Plivo Zentrunk, Telnyx, Vonage, Zadarma, DIDWW, or any standards-compliant trunk. Covers IP whitelisting (`13.200.45.61`), origination URI setup, and the classic SRTP-mismatch / UDP-fragmentation / TLS-without-SDES diagnostic flow.
- ▌ Debug Bolna Calls · bolna-ai bundleDiagnose Bolna voice-agent issues: robotic / laggy responses, agent interrupting users or never interrupting, long silences, premature hangups, webhook misses, wrong caller context, batch failures, SIP/SRTP no-audio, agent restricted by content policy, balance-low queueing, and provider connection latency. Maps symptoms to the exact field on the agent (`task_config`, `endpointing`, `incremental_delay`, `number_of_words_for_interruption`), and uses `latency_data` from `GET /executions/{id}` + raw logs to pinpoint which pipeline component (transcriber, LLM, synthesizer) is slow.
- ▌ Manage Violations · bolna-ai bundleList Bolna call violations (paginated, status-filtered), inspect violation details, and submit evidence files (screenshots, documents, compliance proofs) for review. Bolna flags calls that may breach content policy, regulatory rules (DNC, TRAI calling hours, DLT mismatches), or fraud heuristics. Use when monitoring compliance, resolving account warnings, building an ops workflow around violation review, or attaching evidence to dispute a flag.
- ▌ Bolna Graph Agents · bolna-ai bundleDesign Bolna graph agents: node-based voice flows with LLM, expression, unconditional and event edges, static low-latency nodes, silence repeat with escalation, per-node RAG, function tools, and real-time event injection via REST. Use when a single prompt is too fragile for a multi-step voice workflow — appointment booking, lead qualification, collections, IVR with LLM fallback, payment confirmation, or any flow with branches, compliance checkpoints, or external events.
- ▌ Create Disposition · bolna-ai bundleCreate, bulk-create, list, update, test, and delete Bolna dispositions for post-call structured extraction. Use when the user wants typed outcomes (lead_qualified, appointment_time, sentiment, churn_risk, consent_captured) pulled from every transcript and exposed in `extracted_data` on executions and webhook payloads. Covers Free Text vs Pre-defined answer types, validation (timestamp, numeric, boolean, email, regex), confidence scoring, copy-on-write semantics for shared dispositions, and the per-agent test endpoint.
- ▌ Manage Subaccounts · bolna-ai bundleCreate, list, patch, delete, and inspect usage for Bolna enterprise sub-accounts. Sub-accounts provide isolated workspaces with auto-provisioned API keys (prefixed `sa-`), per-tenant agents/calls/phone-numbers/batches, and per-sub-account usage reporting for billing. Use for agencies, multi-tenant platforms, departments, regions, or regulated data boundaries. **Enterprise feature** — requires org admin access.
- ▌ Create Knowledgebase · bolna-ai bundleCreate, list, inspect, and delete Bolna knowledge bases from PDF files or URLs, including multilingual retrieval settings, chunking, overlap, similarity top k, processing status, rag_id and vector_id usage. Use when a voice agent needs RAG over FAQs, policies, product docs, or web pages.
- ▌ Manage Phone Numbers · bolna-ai bundleSearch, buy, list, and delete Bolna-hosted phone numbers (DIDs). Covers US (Twilio) and India (Plivo, Vobiz) regions; pattern / region filtering; `$5/month` flat pricing; the buy → inbound-setup wiring; and India regulated 140/160-series compliance prerequisites. Use when the user wants to purchase a dedicated outbound caller ID, set up an inbound line, inspect their DID inventory, or understand which Indian region/provider to pick. For SIP-trunk DIDs (BYOT), use `setup-sip-trunk` instead.
- ▌