Bolna vs telli

Agent ops

1. ai-native userMy coding agent can provision a complete voice agent end to end — create the agent, attach a number, and place a call — through the API, CLI, or MCP without touching the dashboard

   weight 3 · round to Bolna
   Bolna✓fullprobed8/10

   Bolna offers all three surfaces needed for agent-native provisioning: a documented API quickstart to create an agent, attach a number, and place a call (bolna-docs-14, bolna-docs-15), a native Go CLI to manage agents, calls, and phone numbers from the terminal (bolna-docs-16, bolna-probe-4), and an official MCP server to connect Claude/Cursor/Windsurf clients (bolna-docs-17, bolna-probe-3), all without requiring dashboard interaction. missing for 10: independent/hands-on confirmation that MCP or CLI can complete the full create-attach-call flow end-to-end (only vendor docs), and no OpenAPI spec was resolvable (bolna-probe-2) to verify API completeness.

   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “official MCP server documented at https://www.bolna.ai/docs/build-with-ai/mcp”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.bolna.ai/openapi.json, https://docs.bolna.ai/swagger.json, https://docs.bolna.ai/api/op…”

   proof ↗⚑ flag

   telli~partialprobed5/10

   telli's REST API documents endpoints for scheduling calls and importing/attaching phone numbers (telli-docs-17, telli-docs-19), and the MCP server lets AI tools talk to Charlie, who can 'build and refine agents' (telli-docs-11, telli-docs-22), suggesting agent creation is possible without the dashboard. However, there is no explicit API/CLI 'create agent' endpoint documented, no CLI tool is mentioned at all, and the MCP-driven agent creation is only described as an assistant chat capability rather than a deterministic API call — so a full end-to-end create→attach-number→place-call pipeline via one consistent interface is not clearly evidenced. Missing for 10: a documented create-agent API/CLI endpoint, confirmation MCP/Charlie can fully provision agents without any dashboard step, and an example combining all three steps in one flow.

   • [claimed-docs] “Charlie: Build and refine agents, automate workflows, and analyze your calls with telli's built-in AI assistant.”
   • [claimed-docs] “API Endpoints: Use telli's REST API to programmatically manage contacts, schedule calls, and integrate with your existing systems.”
   • [claimed-docs] “Schedules a call at the earliest opportunity within the dialer window. May occur immediately or on the next business day depending on settin…”
   • [claimed-docs] “Imports a phone number from your own SIP trunk provider. This allows you to use existing phone numbers with telli by configuring custom SIP …”
   • [claimed-docs] “The telli MCP server lets AI tools like Claude, ChatGPT, and Codex talk to Charlie, telli's AI assistant, over the Model Context Protocol.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.telli.com/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://docs.telli.com/integrations/mcp”

   proof ↗⚑ flag

2. ai-native userThe platform's own AI helps me author agents — generating or improving prompts, flows, and test cases from a description

   weight 1 · round to telli
   Bolna—none0/10

   No evidence shows Bolna's own platform AI generating or improving prompts, flows, or test cases from a description; the closest feature (build-with-ai/mcp) is an MCP server that lets external AI clients like Claude or Cursor manage the account via API, not the platform itself authoring agents. Templates can be cloned, but that's static copying, not AI-generated authoring.

   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [claimed-docs] “Clone any template and customize it for your business.”

   proof ↗⚑ flag

   telli~partialprobed5/10

   Charlie, telli's built-in AI assistant, is documented as helping to 'build and refine agents, automate workflows, and analyze your calls,' which supports the core idea of AI-assisted agent authoring, and the MCP server lets external AI tools interact with Charlie too. However there's no concrete evidence of generating test cases from a description, or detailed examples of prompt/flow generation output. missing for 10: documented examples of Charlie generating/improving prompts or flows from a natural-language description, evidence of AI-generated test case creation, and independent/hands-on confirmation of these capabilities in practice.

   • [claimed-docs] “Charlie: Build and refine agents, automate workflows, and analyze your calls with telli's built-in AI assistant.”
   • [claimed-docs] “The telli MCP server lets AI tools like Claude, ChatGPT, and Codex talk to Charlie, telli's AI assistant, over the Model Context Protocol.”
   • [probe] “official MCP server documented at https://docs.telli.com/integrations/mcp”

   proof ↗⚑ flag

Build

1. developerBuild a working phone voice agent — prompt, voice, and phone number — and take my first live call within an hour

   weight 3 · round to Bolna
   Bolna✓fullclaimed8/10

   Docs directly support the story: templates can be cloned and customized, build/deploy claimed under 5 minutes, voice/accent selection, phone number and telephony setup (BYOT/SIP), and a quickstart walking through key verification, agent creation, placing a call, and fetching a transcript in ~5 minutes. This covers prompt (agent config/templates), voice (voice/provider selection), and phone number (telephony/SIP) end-to-end for a first live call within an hour. Missing for 10: independent/hands-on confirmation of the 'under 5 minutes' or 'first call in an hour' claims beyond vendor docs, and no third-party success report.

   • [claimed-docs] “Build and deploy in under 5 minutes”
   • [claimed-docs] “Clone any template and customize it for your business.”
   • [claimed-docs] “You can choose different voices, accents, and speaking styles to match your brand.”
   • [claimed-docs] “Bring Your Own Telephony (BYOT) lets you connect any standards-compliant SIP trunk to the Bolna platform.”
   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “Bolna supports Deepgram, Azure, ElevenLabs, and more.”

   proof ↗⚑ flag

   telli~partialclaimed6/10

   telli provides agent builder, test call feature, voice cloning, and phone number setup (forwarding or SIP trunk import) which together support building and testing a voice agent with prompt, voice, and number, but there's no explicit walkthrough or evidence confirming a full end-to-end setup can be completed within an hour or that phone number provisioning is instant/self-serve for new numbers. missing for 10: a documented quick-start/time-to-first-call benchmark, evidence of instant/native number provisioning (vs SIP/forwarding setup), and independent/hands-on confirmation of the full flow's speed.

   • [claimed-docs] “In the agent builder, click Test call to open the dialog. Pick the agent version (your draft with unsaved changes or any saved revision)...”
   • [claimed-docs] “Use the side-by-side view to listen to the recording while following along in the transcript.”
   • [claimed-docs] “Voice cloning lets you give your agent a custom voice (your own, a colleague's, or a professional voice actor's), so the agent sounds exactl…”
   • [claimed-docs] “Keep your public business number and forward incoming calls to a telli number. You configure the forwarding with your phone provider or PBX.”
   • [claimed-docs] “Connect an existing number and phone system for incoming and outgoing calls. You need SIP trunk access from your provider.”
   • [claimed-docs] “Imports a phone number from your own SIP trunk provider. This allows you to use existing phone numbers with telli by configuring custom SIP …”

   proof ↗⚑ flag

2. developerRun conversations in multiple languages, including detecting and switching language mid-call

   weight 2 · round to Bolna
   Bolna~partialclaimed6/10

   Docs claim the agent "detects and switches mid-call on its own" and marketing mentions "multilingual intelligence" for thousands of calls, directly supporting the story, but there's no detail on supported languages, configuration options, or independent/hands-on verification of mid-call switching reliability. Missing for 10: language list/configuration docs, hands-on or third-party confirmation of switching accuracy, and edge-case handling details.

   • [claimed-docs] “the agent detects and switches mid-call on its own”
   • [claimed-docs] “Power thousands of inbound and outbound calls every minute with human-like, multilingual intelligence”

   proof ↗⚑ flag

   telli—none0/10

   No evidence in the pack mentions multilingual support, language detection, or mid-call language switching for telli's voice agents; all documented features concern scheduling, webhooks, tools, analytics, and MCP integration.

   ⚑ flag

3. founderDesign multi-step conversation flows in a visual builder with branching, states, and handoffs without writing code

   weight 2 · round to telli
   Bolna—none0/10

   Evidence shows Bolna is built around APIs, CLI, and MCP server for defining agents and multi-step outreach sequences (bolna-docs-12, bolna-docs-16, bolna-docs-17), but there is no mention of a visual/no-code builder with branching, states, or handoffs; workflows are described as 'driven entirely through the Bolna API.' Missing for 10: any visual flow-builder UI, drag-and-drop branching/state design, no-code handoff configuration.

   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [github] “Bolna is the end-to-end open source production ready framework for quickly building LLM based voice driven conversational applications.”

   proof ↗⚑ flag

   telli~partialclaimed4/10

   telli has an 'agent builder' with test-call and versioning, and workflow triggers (scheduled, SMS/WhatsApp) suggesting some no-code workflow configuration, plus tool-calls like transfer to another agent implying handoffs. But there's no evidence of a visual flow builder with branching/state diagrams — evidence only shows agent settings, tools, and triggers, not a drag-and-drop conversation flow canvas. missing for 10: explicit visual builder UI with branching/state nodes, evidence of designing multi-step flows with conditional paths, and documentation of handoff logic beyond simple 'transfer tool'.

   • [claimed-docs] “In the agent builder, click Test call to open the dialog. Pick the agent version (your draft with unsaved changes or any saved revision)...”
   • [claimed-docs] “Transfer tools | Move the call to another agent or number.”
   • [claimed-docs] “Choose SMS and WhatsApp workflow recipients from contact properties, collected values, or a fixed number”
   • [claimed-docs] “Workflows can now run automatically on a recurring schedule. Add a Scheduled trigger, choose the interval and start time, and let the workfl…”

   proof ↗⚑ flag

Personalization

1. developerInject dynamic variables and per-caller context at call time so each conversation is personalized

   weight 2 · round drawn
   Bolna—none0/10

   The evidence pack covers agent creation, extraction categories, call summaries, workflows, and providers, but nothing documents passing per-caller dynamic variables or context payloads at call time to personalize a conversation.

   ⚑ flag

   telli—none0/10

   The evidence describes contact properties and collected values being used to select SMS/WhatsApp recipients (telli-docs-5) and APIs to manage contacts and schedule calls (telli-docs-12, telli-docs-17), but nowhere does it document injecting dynamic variables or per-caller context into an agent's voice call script/persona at call time. Missing for 10: explicit documentation of variable placeholders in agent prompts, a mechanism for passing per-call custom data via the schedule-call API, and any example of personalized call content driven by caller-specific fields.

   • [claimed-docs] “Choose SMS and WhatsApp workflow recipients from contact properties, collected values, or a fixed number”
   • [claimed-docs] “API Endpoints: Use telli's REST API to programmatically manage contacts, schedule calls, and integrate with your existing systems.”
   • [claimed-docs] “Schedules a call at the earliest opportunity within the dialer window. May occur immediately or on the next business day depending on settin…”

   proof ↗⚑ flag

2. developerGround the agent on my documents with a built-in knowledge base or RAG so it answers from my content

   weight 2 · round drawn
   Bolna—none0/10

   Bolna is a voice AI agent platform (telephony, TTS/STT, LLM providers, workflows) but the evidence pack contains no mention of a knowledge base, document ingestion, or RAG capability for grounding agent responses in custom content. This axis clearly applies to conversational agent-building platforms, so absence of evidence yields 'none'.

   ⚑ flag

   telli—none0/10

   No evidence of a built-in knowledge base or RAG feature for grounding agents on uploaded documents; the docs describe custom tools for API integration and a web_search tool for public information, but nothing about ingesting documents or content for retrieval-based answers.

   ⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Bolna✓fullprobed9/10

   A probe confirms llms.txt is live and returns 200 with structured agent-oriented doc links (bolna-probe-1), and Bolna also documents an official MCP server for connecting AI clients like Claude/Cursor to its docs/account (bolna-docs-17, bolna-probe-3), directly enabling agent-native consumption of its documentation. Missing for 10: no independent third-party confirmation that agents successfully use llms.txt in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.bolna.ai/llms.txt # Bolna Docs > Quickly build and deploy conversational Voice AI agents - [Home]…”
   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “official MCP server documented at https://www.bolna.ai/docs/build-with-ai/mcp”

   proof ↗⚑ flag

   telli✓fullprobed9/10

   telli hosts a live llms.txt file (confirmed via probe, HTTP 200) plus machine-readable OpenAPI spec explicitly intended for coding agents, and docs also mention agent-oriented context for downloading API specs. missing for 10: no independent/third-party confirmation of an agent successfully consuming llms.txt in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.telli.com/llms.txt # telli Documentation > telli is the AI voice platform for agents that sell, su…”
   • [claimed-docs] “Download them to generate client libraries, import the API into tools like Postman, or give coding agents machine-readable API context”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.telli.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Bolna~partialprobed6/10

   Bolna offers a CLI (single Go binary) for managing agents, calls, phone numbers, and batches from the terminal, plus a REST API for scripted call creation and transcript retrieval — both usable in CI/automation pipelines without a GUI. However, there's no explicit CI/pipeline example, headless-mode documentation, or exit-code/automation-specific guidance. missing for 10: explicit CI integration examples/guides, documented non-interactive/headless flags or exit codes, third-party confirmation of CI usage.

   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”
   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”

   proof ↗⚑ flag

   telli~partialprobed6/10

   telli exposes a full REST API (with OpenAPI spec) to programmatically schedule calls, manage contacts, and trigger workflows, plus webhooks for event-driven automation and scheduled/recurring workflow triggers — all of which support headless, non-UI automation suitable for CI-like pipelines. However there is no explicit CI/CD example, CLI tool, or documented automated pipeline integration beyond the API/webhook primitives. Missing for 10: dedicated CI/CD documentation or examples, a CLI for scripted invocation, and independent confirmation of headless use in production pipelines.

   • [claimed-docs] “API Endpoints: Use telli's REST API to programmatically manage contacts, schedule calls, and integrate with your existing systems.”
   • [claimed-docs] “Schedules a call at the earliest opportunity within the dialer window. May occur immediately or on the next business day depending on settin…”
   • [claimed-docs] “Workflows can now run automatically on a recurring schedule. Add a Scheduled trigger, choose the interval and start time, and let the workfl…”
   • [claimed-docs] “Webhooks push data from telli to your systems in real time. When something happens on a call, telli sends a POST request to the endpoint you…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.telli.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Bolna—none0/10

   Evidence shows Bolna ships an MCP *server* so external clients like Claude, Cursor, or Windsurf can control a Bolna account (bolna-docs-17, bolna-probe-3) — this is the reverse direction from the story, which asks whether Bolna's own agents can plug in external MCP servers to gain their tools. No evidence describes Bolna voice agents consuming or calling external MCP servers.

   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “official MCP server documented at https://www.bolna.ai/docs/build-with-ai/mcp”

   proof ↗⚑ flag

   telli—none0/10

   Telli's documented MCP support only runs in the opposite direction — it exposes an MCP server so external AI tools (Claude, ChatGPT, Codex) can talk to its Charlie assistant (telli-docs-22, telli-probe-3), not a mechanism for telli's own voice agents to consume external MCP servers' tools. Custom Tools (telli-docs-14, telli-docs-20) let agents call external APIs but are described as custom integrations, not MCP-based tool ingestion.

   • [claimed-docs] “The telli MCP server lets AI tools like Claude, ChatGPT, and Codex talk to Charlie, telli's AI assistant, over the Model Context Protocol.”
   • [probe] “official MCP server documented at https://docs.telli.com/integrations/mcp”
   • [claimed-docs] “Custom Tools: Extend telli's capabilities with custom integrations and workflows.”
   • [claimed-docs] “Custom tools allow your AI agents to access external information by connecting to your APIs.”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Bolna✓fullprobed8/10

   Bolna documents an official MCP server that lets Claude, Cursor, Windsurf, or any MCP client connect to a Bolna account, confirmed by both docs and an independent probe hitting the live page. Missing for 10: independent hands-on validation or community confirmation of the MCP server working in practice beyond the docs/probe.

   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “official MCP server documented at https://www.bolna.ai/docs/build-with-ai/mcp”

   proof ↗⚑ flag

   telli✓fullprobed8/10

   telli documents an official MCP server that lets external AI tools (Claude, ChatGPT, Codex) connect over the Model Context Protocol to interact with Charlie, telli's assistant, confirmed both in docs and via a live probe of the integrations/mcp page. Missing for 10: no independent/hands-on corroboration beyond first-party docs and the probe, and no detail on server setup/auth specifics.

   • [claimed-docs] “The telli MCP server lets AI tools like Claude, ChatGPT, and Codex talk to Charlie, telli's AI assistant, over the Model Context Protocol.”
   • [probe] “official MCP server documented at https://docs.telli.com/integrations/mcp”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Bolna
   Bolna✓fullprobed8/10

   Bolna documents an official CLI (single Go binary) letting users manage agents, calls, phone numbers, and batches from the terminal, corroborated by a live docs probe confirming the page exists. missing for 10: no independent/hands-on community usage reports or version/release history confirming real-world adoption beyond first-party docs.

   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”

   proof ↗⚑ flag

   telli—none0/10

   telli offers a REST API, webhooks, and an MCP server for AI assistants, but there is no mention anywhere in the evidence of an official CLI tool for telli. missing for 10: any documentation or reference to a telli CLI, its commands, or installation instructions.

   ⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to telli
   Bolna✓fullprobed8/10

   Bolna provides a documented public API with quickstart, authentication, agent/call/extraction endpoints, and workflow automation entirely through the API, plus a CLI and MCP server built on top of it. Missing for 10: a discoverable OpenAPI/Swagger spec (probe found all standard OpenAPI paths 404) and independent third-party corroboration of API robustness.

   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”
   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.bolna.ai/openapi.json, https://docs.bolna.ai/swagger.json, https://docs.bolna.ai/api/op…”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”

   proof ↗⚑ flag

   telli✓fullprobed9/10

   telli documents a REST API with endpoints (schedule-call, import-phone-number), API key/bearer auth, webhooks, and a downloadable OpenAPI spec (confirmed live at openapi.json), plus an MCP server for AI tool access — enabling full programmatic/agentic control. missing for 10: independent third-party validation of API robustness beyond vendor docs.

   • [claimed-docs] “API Endpoints: Use telli's REST API to programmatically manage contacts, schedule calls, and integrate with your existing systems.”
   • [claimed-docs] “Webhooks: Receive real-time notifications about call events, status changes, and outcomes.”
   • [claimed-docs] “All endpoints authenticate with an API key from the telli app (Settings > Developer), sent as a bearer token”
   • [claimed-docs] “Download them to generate client libraries, import the API into tools like Postman, or give coding agents machine-readable API context”
   • [claimed-docs] “Schedules a call at the earliest opportunity within the dialer window. May occur immediately or on the next business day depending on settin…”
   • [claimed-docs] “Imports a phone number from your own SIP trunk provider. This allows you to use existing phone numbers with telli by configuring custom SIP …”
   • [claimed-docs] “Webhooks push data from telli to your systems in real time. When something happens on a call, telli sends a POST request to the endpoint you…”
   • [claimed-docs] “The telli MCP server lets AI tools like Claude, ChatGPT, and Codex talk to Charlie, telli's AI assistant, over the Model Context Protocol.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.telli.com/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://docs.telli.com/integrations/mcp”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Bolna—none0/10

   Bolna documents API key creation but there is no evidence of scoped or least-privilege credential controls (e.g., role-based permissions, scoped tokens, restricted access levels) — only a single account-wide key generation flow is described.

   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”

   proof ↗⚑ flag

   telli—none0/10

   telli documents a single API key (bearer token) generated in Settings > Developer, but there's no evidence of scoped permissions, role-based keys, or least-privilege credential issuance for agents specifically.

   • [claimed-docs] “All endpoints authenticate with an API key from the telli app (Settings > Developer), sent as a bearer token”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Bolna~partialprobed5/10

   Bolna documents an official Web Call SDK (bolna-docs-18) under a 'developer-resources/sdks' path, plus a CLI and MCP server, giving AI-native builders some official tooling to build against, but there is no evidence of broader language SDKs (e.g., Python, Node, Go client libraries) beyond the browser-based Web Call SDK. missing for 10: multi-language server-side SDKs, independent/hands-on verification of SDK usability, breadth beyond the single web-call SDK.

   • [claimed-docs] “The Web Call SDK connects a browser tab directly to a Bolna voice agent for a live, two-way conversation.”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”
   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”

   proof ↗⚑ flag

   telli~partialprobed5/10

   telli provides a REST API with an OpenAPI spec that can be used to generate client libraries, plus webhooks, custom tools, and an MCP server for agent integration, but there is no evidence of telli-maintained official SDKs in specific languages (e.g., Python/JS packages published by telli) — only self-generated clients from the OpenAPI spec. missing for 10: dedicated first-party SDK packages/repos, language-specific SDK documentation, versioning/release notes for such SDKs.

   • [claimed-docs] “API Endpoints: Use telli's REST API to programmatically manage contacts, schedule calls, and integrate with your existing systems.”
   • [claimed-docs] “All endpoints authenticate with an API key from the telli app (Settings > Developer), sent as a bearer token”
   • [claimed-docs] “Download them to generate client libraries, import the API into tools like Postman, or give coding agents machine-readable API context”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.telli.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to telli
   Bolna—none0/10

   No evidence in the pack mentions webhooks or event subscription for Bolna; the docs cover agents, calls, CLI, MCP, SIP, pricing, and security but nothing about outbound event notifications. Missing for 10: any webhook registration/config API, event payload documentation, or third-party confirmation of webhook delivery.

   ⚑ flag

   telli✓fullclaimed8/10

   telli documents a webhooks system that pushes real-time POST notifications about call events, status changes, and outcomes, explicitly described as event-driven subscription for external systems (telli-docs-13, telli-docs-21). Missing for 10: no evidence of configurable event-type filtering/subscription granularity or independent third-party confirmation of reliability.

   • [claimed-docs] “Webhooks: Receive real-time notifications about call events, status changes, and outcomes.”
   • [claimed-docs] “Webhooks push data from telli to your systems in real time. When something happens on a call, telli sends a POST request to the endpoint you…”
   • [claimed-docs] “API Endpoints: Use telli's REST API to programmatically manage contacts, schedule calls, and integrate with your existing systems.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to telli
   Bolna~partialclaimed5/10

   Bolna offers agent-level call_summary_enabled to auto-generate AI summaries and an extraction-categories API to pull structured insights out of call data, both of which are AI-generated insights derived from user data (calls). However, there's no evidence of broader cross-call analytics, trend insights, or proactive suggestions surfaced in a dashboard beyond per-call outputs. Missing for 10: aggregated/dashboard-level insights across multiple calls, proactive recommendation surfacing, and independent confirmation of quality of generated summaries/extractions.

   • [claimed-docs] “POST /agent/{agent_id}/extraction-categories — create a category (name + model) and attach it to an agent”
   • [claimed-docs] “Call summaries are an agent-level toggle: call_summary_enabled (boolean, off by default) on the agent create and update APIs”

   proof ↗⚑ flag

   telli~partialclaimed6/10

   telli ships a built-in AI assistant (Charlie) that can 'analyze your calls' and help build/refine agents, plus dashboards for reach rate, call duration, success rate, and per-call transcript/outcome analysis, which together provide AI-driven insight into product data. However, the docs don't detail proactive, autonomous 'suggestions' surfaced to the user (e.g., recommended actions, anomaly detection) beyond on-demand analysis via Charlie or manual dashboard review. Missing for 10: concrete examples of Charlie proactively surfacing insights/recommendations, independent user corroboration of insight quality.

   • [claimed-docs] “Charlie: Build and refine agents, automate workflows, and analyze your calls with telli's built-in AI assistant.”
   • [claimed-docs] “Track key metrics like reach rate, call duration, and success rate.”
   • [claimed-docs] “Analyze individual calls, transcripts, and call outcome fields.”
   • [claimed-docs] “Submit feedback on calls to continuously improve your agent.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to telli
   Bolna~partialprobed6/10

   Bolna's workflows feature lets users build multi-step outreach sequences (voice calls, WhatsApp, API calls, waits, retries) driven entirely through the API, which supports background automation, and the CLI can manage batches of calls autonomously. However there's no documented evidence of scheduling/triggers, monitoring/alerting on autonomous runs, or a dashboard for managing long-running background jobs beyond the API-driven workflow primitives. missing for 10: scheduling/trigger mechanisms, autonomous-run monitoring/alerting, independent hands-on confirmation of unattended long-running workflows.

   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”

   proof ↗⚑ flag

   telli✓fullclaimed7/10

   telli supports Scheduled triggers so workflows run automatically without a call event, plus retry/dialing-window configuration, webhooks, and an AI assistant (Charlie) to build/automate workflows — together enabling background autonomous automations. Missing for 10: independent/hands-on verification of scheduled automations running reliably in production, and more detail on monitoring/error-handling for autonomous runs beyond docs claims.

   • [claimed-docs] “Workflows can now run automatically on a recurring schedule. Add a Scheduled trigger, choose the interval and start time, and let the workfl…”
   • [claimed-docs] “Configure dialing windows, calling strategies, and retry behavior.”
   • [claimed-docs] “Charlie: Build and refine agents, automate workflows, and analyze your calls with telli's built-in AI assistant.”
   • [claimed-docs] “Webhooks: Receive real-time notifications about call events, status changes, and outcomes.”
   • [claimed-docs] “Schedules a call at the earliest opportunity within the dialer window. May occur immediately or on the next business day depending on settin…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to telli
   Bolna—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   telli✓fullprobed8/10

   telli documents "Charlie," a built-in AI assistant that can build/refine agents, automate workflows, and analyze calls, and this assistant is also exposed via an MCP server for external AI tools to interact with. This directly matches delegating tasks to a built-in assistant within the product. Missing for 10: independent/hands-on verification of Charlie's task delegation in practice and more detail on the scope of tasks it can autonomously execute.

   • [claimed-docs] “Charlie: Build and refine agents, automate workflows, and analyze your calls with telli's built-in AI assistant.”
   • [claimed-docs] “The telli MCP server lets AI tools like Claude, ChatGPT, and Codex talk to Charlie, telli's AI assistant, over the Model Context Protocol.”
   • [probe] “official MCP server documented at https://docs.telli.com/integrations/mcp”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Bolna
   Bolna✓fullprobed7/10

   Bolna ships an official MCP server that lets AI-native tools like Claude, Cursor, or Windsurf connect to a Bolna account and operate it (manage agents, calls, etc.) via natural-language commands, confirmed both in docs and via a live probe. Missing for 10: independent/hands-on verification that the MCP integration works as described, and no additional natural-language control surfaces (e.g., chat-based dashboard) beyond MCP.

   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “official MCP server documented at https://www.bolna.ai/docs/build-with-ai/mcp”

   proof ↗⚑ flag

   telli~partialprobed6/10

   telli offers Charlie, a built-in AI assistant that can build/refine agents, automate workflows, and analyze calls via natural language, plus an MCP server letting external AI tools (Claude, ChatGPT, Codex) converse with Charlie — both point to natural-language operation. However, most of the product surface (workflows, scheduling, dialing windows, phone number setup) is described as configured through UI/API rather than conversational commands, and there's no independent/hands-on evidence of Charlie's NL command scope or reliability. missing for 10: hands-on evidence of Charlie executing complex natural-language commands, documentation detailing the breadth of actions controllable purely via NL, independent corroboration beyond vendor docs.

   • [claimed-docs] “Charlie: Build and refine agents, automate workflows, and analyze your calls with telli's built-in AI assistant.”
   • [claimed-docs] “The telli MCP server lets AI tools like Claude, ChatGPT, and Codex talk to Charlie, telli's AI assistant, over the Model Context Protocol.”
   • [probe] “official MCP server documented at https://docs.telli.com/integrations/mcp”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to telli
   Bolna—none0/10

   Bolna has an API reference doc listing basics like API key creation, but there is no evidence of an interactive reference with runnable/try-it examples, and a probe for a machine-readable OpenAPI spec (which typically powers such interactive docs) returned 404 on all checked paths.

   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.bolna.ai/openapi.json, https://docs.bolna.ai/swagger.json, https://docs.bolna.ai/api/op…”

   proof ↗⚑ flag

   telli~partialprobed5/10

   telli publishes an OpenAPI spec (openapi.json) and API docs with downloadable schemas for generating client libraries or feeding coding agents, but there is no evidence of an interactive reference with runnable/'try it' examples in-browser. missing for 10: an interactive try-it console, live runnable code samples, or sandboxed request execution within the docs site.

   • [claimed-docs] “Download them to generate client libraries, import the API into tools like Postman, or give coding agents machine-readable API context”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.telli.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “All endpoints authenticate with an API key from the telli app (Settings > Developer), sent as a bearer token”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to telli
   Bolna—none0/10

   A direct probe for OpenAPI/Swagger spec files at all standard locations returned 404s, and no evidence pack item shows a downloadable machine-readable API spec despite having an API reference page.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.bolna.ai/openapi.json, https://docs.bolna.ai/swagger.json, https://docs.bolna.ai/api/op…”
   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”

   proof ↗⚑ flag

   telli✓fullprobed9/10

   telli provides a downloadable OpenAPI spec confirmed live at /openapi.json, and docs explicitly state it can be downloaded to generate client libraries, import into tools, or give coding agents machine-readable API context. Missing for 10: no independent third-party confirmation of spec completeness/versioning beyond first-party docs and probe.

   • [claimed-docs] “Download them to generate client libraries, import the API into tools like Postman, or give coding agents machine-readable API context”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.telli.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to telli
   Bolna—none0/10

   No evidence pack item mentions a sandbox environment, test mode, staging account, or separation from production data for Bolna; the closest concepts (self-hosting, BYOK, data residency) are about deployment/privacy, not a distinct sandbox/test mode. missing for 10: any mention of a sandbox/test environment, test API keys, or safe testing workflow that avoids production data.

   ⚑ flag

   telli~partialclaimed4/10

   telli's agent builder includes a 'Test call' feature that lets users dial a draft or saved agent version and review the recording/transcript before going live, which functions as a lightweight test mode (telli-docs-28, telli-docs-29). However, there is no documentation of a dedicated sandbox environment, separate test dataset, or explicit guarantee that test calls don't write to production contacts/analytics. missing for 10: explicit sandbox/staging environment separate from production, confirmation that test calls don't affect production data/metrics, and any mention of test API keys or isolated test accounts.

   • [claimed-docs] “In the agent builder, click Test call to open the dialog. Pick the agent version (your draft with unsaved changes or any saved revision)...”
   • [claimed-docs] “Use the side-by-side view to listen to the recording while following along in the transcript.”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Bolna—none0/10

   There is a changelog page referenced and an API reference, but no evidence of API versioning scheme or a documented deprecation policy anywhere in the pack; OpenAPI spec probes even returned 404s. Missing for 10: versioned API endpoints/headers, explicit deprecation policy documentation, migration/versioning changelog entries.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.bolna.ai/openapi.json, https://docs.bolna.ai/swagger.json, https://docs.bolna.ai/api/op…”
   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”

   proof ↗⚑ flag

   telli—none0/10

   Evidence shows an OpenAPI spec and API key auth exist, but nothing in the pack mentions API versioning (e.g., v1/v2 paths, version headers) or any documented deprecation/sunset policy for endpoints. Missing for 10: explicit API version scheme, changelog of breaking changes, and a stated deprecation/sunset policy.

   • [claimed-docs] “API Endpoints: Use telli's REST API to programmatically manage contacts, schedule calls, and integrate with your existing systems.”
   • [claimed-docs] “All endpoints authenticate with an API key from the telli app (Settings > Developer), sent as a bearer token”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.telli.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to telli
   Bolna~partialclaimed5/10

   The CLI explicitly manages 'batches' of calls alongside agents and phone numbers (bolna-docs-16), and the platform claims to power 'thousands of inbound and outbound calls every minute' (bolna-docs-22), implying built-in bulk calling capability. However, there is no documentation of a specific bulk API endpoint, CSV/list upload, or bulk agent/category management workflow. Missing for 10: explicit bulk-operation API docs (e.g., batch call creation, bulk agent updates), a documented interface for uploading many items at once, and independent confirmation of bulk throughput.

   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [claimed-docs] “Power thousands of inbound and outbound calls every minute with human-like, multilingual intelligence”
   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”

   proof ↗⚑ flag

   telli~partialprobed6/10

   Telli's platform is built around calling large contact lists (dialing windows, calling strategies, retry behavior, reach-rate metrics) and its REST API lets users 'programmatically manage contacts, schedule calls' at scale, implying bulk campaign operations. However, there is no explicit documentation of a bulk-upload/bulk-schedule endpoint or UI for acting on many items simultaneously — the schedule-call endpoint documented is single-call oriented. Missing for 10: explicit bulk-contact import/schedule endpoint, documented batch size limits, and independent evidence of large-scale bulk execution.

   • [claimed-docs] “Configure dialing windows, calling strategies, and retry behavior.”
   • [claimed-docs] “Track key metrics like reach rate, call duration, and success rate.”
   • [claimed-docs] “API Endpoints: Use telli's REST API to programmatically manage contacts, schedule calls, and integrate with your existing systems.”
   • [claimed-docs] “Schedules a call at the earliest opportunity within the dialer window. May occur immediately or on the next business day depending on settin…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.telli.com/llms.txt # telli Documentation > telli is the AI voice platform for agents that sell, su…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to telli
   Bolna~partialclaimed4/10

   Bolna's workflow feature lets users chain voice calls, WhatsApp messages, API calls, waits and retries via the API, which is a form of automation, but the docs never describe defining conditional 'if event X happens then do Y' rules or an event/trigger system — it's presented as sequential outreach flows rather than rule-based event triggers. Missing for 10: explicit event-trigger/rule definition syntax, conditional branching logic, and any webhook-or-event-driven automation examples beyond the sequential workflow description.

   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”

   proof ↗⚑ flag

   telli~partialclaimed5/10

   telli's workflows can be triggered by call events (implied default) and now by a recurring schedule, and webhooks notify external systems on call events, showing some event-driven automation. However there's no documented rule-definition interface (conditions, event-type selection, if/then logic) for arbitrary events beyond calls/schedule. Missing for 10: explicit rule/condition builder, broader event-type coverage beyond calls, and evidence of user-defined trigger logic rather than fixed schedule/call triggers.

   • [claimed-docs] “Workflows can now run automatically on a recurring schedule. Add a Scheduled trigger, choose the interval and start time, and let the workfl…”
   • [claimed-docs] “Webhooks: Receive real-time notifications about call events, status changes, and outcomes.”
   • [claimed-docs] “Webhooks push data from telli to your systems in real time. When something happens on a call, telli sends a POST request to the endpoint you…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to telli
   Bolna—none0/10

   Bolna's workflow docs describe multi-step outreach sequences with waits and retries (bolna-docs-12), but there is no evidence of a scheduler for recurring/cron-based jobs or workflows that re-trigger automatically over time. missing for 10: recurring/scheduled trigger mechanism, cron-like job definitions, evidence of periodic re-execution.

   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”

   proof ↗⚑ flag

   telli✓fullclaimed7/10

   telli documents scheduled triggers that let workflows run recurringly on an interval/start time without a call event, directly matching the recurring-workflow story, and also supports scheduling individual calls via API. missing for 10: independent/hands-on corroboration of recurrence reliability and detail on editing/monitoring scheduled workflow runs.

   • [claimed-docs] “Workflows can now run automatically on a recurring schedule. Add a Scheduled trigger, choose the interval and start time, and let the workfl…”
   • [claimed-docs] “Schedules a call at the earliest opportunity within the dialer window. May occur immediately or on the next business day depending on settin…”
   • [claimed-docs] “Optional flag to bypass dialing window restrictions for the scheduled call. When true, calls at the scheduled time regardless of dialing win…”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to telli
   Bolna—none0/10

   Bolna is a voice AI agent platform (agent creation, calls, workflows, telephony) but the evidence pack shows no version control, review workflow, or rollback mechanism for automations/agents — no mention of agent versioning, change history, approval flows, or revert capability.

   ⚑ flag

   telli~partialclaimed3/10

   The only hint of versioning is in agent testing, where you can pick 'your draft with unsaved changes or any saved revision' (telli-docs-28), implying saved agent versions exist. However there is no documented review interface for comparing versions, no explicit rollback/restore action, and no versioning mentioned for broader automations/workflows (only agents). Missing for 10: explicit rollback UI/API, version diff/review tooling, and versioning coverage for workflows beyond agent test calls.

   • [claimed-docs] “In the agent builder, click Test call to open the dialog. Pick the agent version (your draft with unsaved changes or any saved revision)...”

   proof ↗⚑ flag

Compliance

1. founderMeet call-recording consent and disclosure obligations with per-call recording controls and configurable data retention

   weight 2 · round to telli
   Bolna—none0/10

   The evidence pack shows security/data-residency features and call-summary toggles, but nothing about call-recording consent, per-call recording enable/disable controls, disclosure/announcement features, or configurable retention periods for recordings/transcripts. No mention of recording consent mechanisms or retention settings anywhere in the docs pack.

   ⚑ flag

   telli~partialclaimed6/10

   telli documents conditional recording based on caller consent and a configurable data-retention policy that auto-deletes contacts and call data after a defined age, directly addressing the founder's compliance need. However, evidence lacks detail on per-call granular controls (e.g., pause/resume, jurisdiction-specific disclosure scripts), audit logging of consent events, or independent verification that these features work as described. Missing for 10: per-call recording toggle/audit trail details, jurisdiction-specific disclosure templates, retention configuration granularity (e.g., per-data-type settings), and independent/hands-on confirmation of compliance behavior.

   • [claimed-docs] “Data retention deletes contacts and call data automatically once they reach an age you define.”
   • [claimed-docs] “In telli, you can easily make audio recording conditional on the caller's consent — so a call is only recorded once they agree.”

   proof ↗⚑ flag

2. platform-engineerRun regulated workloads with HIPAA/BAA support, SOC 2, and data-residency options

   weight 2 · round to Bolna
   Bolna~partialclaimed3/10

   Bolna documents Indian data residency and self-hosting via Docker/Kubernetes for private enterprise deployments, but there is no mention of HIPAA/BAA support or SOC 2 certification anywhere in the evidence pack. missing for 10: HIPAA/BAA attestation, SOC 2 report or certification, broader multi-region data-residency options beyond India.

   • [claimed-docs] “Indian data residency is available for deployments where data must remain in India.”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”

   proof ↗⚑ flag

   telli—none0/10

   No evidence in the pack mentions HIPAA, BAA, SOC 2, or data-residency options; only data retention and consent-based recording are covered, which don't establish formal compliance certifications.

   ⚑ flag

Scale

1. platform-engineerSee documented concurrency limits and scale to many simultaneous calls without manual capacity begging

   weight 2 · round to Bolna
   Bolna~partialclaimed3/10

   Bolna's marketing page claims it can 'power thousands of inbound and outbound calls every minute' and docs mention self-hosting via Docker/Kubernetes for 'scalable enterprise deployments,' but there are no documented concurrency limits, rate-limit tables, or self-serve capacity-scaling mechanisms (e.g., no API rate-limit docs, no autoscaling guide, no numeric SLA). missing for 10: documented numeric concurrency/rate limits, self-serve scale-up process, autoscaling architecture details, independent verification of claimed call volume.

   • [claimed-docs] “Power thousands of inbound and outbound calls every minute with human-like, multilingual intelligence”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”

   proof ↗⚑ flag

   telli—none0/10

   No evidence pack item documents concurrency limits, per-account call caps, or scaling guarantees for simultaneous calls; docs mention dialing windows/retry strategy but not concurrency ceilings or auto-scaling behavior. This is a fair question for a voice-calling platform (scaling many simultaneous calls is core to the product's value), so 'none' applies rather than 'na'.

   ⚑ flag

Self host

1. platform-engineerSelf-host the voice agent runtime from open-source code on my own infrastructure

   weight 3 · round to Bolna
   Bolna✓fullclaimed8/10

   Bolna is explicitly an open-source framework on GitHub, and docs include dedicated enterprise instructions for self-hosting on Docker or Kubernetes for private/enterprise deployments. Missing for 10: independent hands-on reports confirming successful self-host deployment and more detail on infrastructure requirements/limitations of the self-hosted version vs SaaS.

   • [github] “Bolna is the end-to-end open source production ready framework for quickly building LLM based voice driven conversational applications.”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”

   proof ↗⚑ flag

   telli—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Latency

1. platform-engineerSee documented end-to-end voice latency numbers or tuning guidance backing the platform's speed claims

   weight 3 · round drawn
   Bolna—none0/10

   No evidence pack item provides documented latency numbers, benchmarks, or tuning guidance for end-to-end voice latency; only vague marketing claims like 'build in under 5 minutes' or 'power thousands of calls' appear, with no actual latency figures or turn-taking tuning documentation.

   • [claimed-docs] “Build and deploy in under 5 minutes”
   • [claimed-docs] “Power thousands of inbound and outbound calls every minute with human-like, multilingual intelligence”

   proof ↗⚑ flag

   telli—none0/10

   No evidence pack item mentions latency numbers, turn-taking performance, or tuning guidance for voice response speed; documentation covers workflows, API, webhooks, and agent building but nothing on end-to-end latency benchmarks or tuning.

   ⚑ flag

Turn taking

1. developerRely on the agent to handle interruptions (barge-in) gracefully — stopping speech, updating context, and recovering the turn

   weight 3 · round drawn
   Bolna—none0/10

   No evidence pack item mentions barge-in, interruption handling, speech-stop, or turn recovery mechanics; the docs cover extraction categories, summaries, providers, CLI, MCP, pricing, etc., but nothing about turn-taking or interruption behavior. missing for 10: any documentation of barge-in/interruption detection, mid-speech stop mechanics, context update on interruption, turn recovery logic.

   ⚑ flag

   telli—none0/10

   No evidence in the pack addresses barge-in, interruption handling, speech-stopping, or turn recovery mechanics; the docs cover scheduling, workflows, analytics, and integrations but never mention conversational turn-taking behavior.

   ⚑ flag

2. developerEnable noise suppression or audio filtering so the agent stays coherent on noisy real-world calls

   weight 1 · round drawn
   Bolna—none0/10

   No evidence pack item mentions noise suppression, background noise handling, or audio filtering settings for calls; the docs cover extraction categories, summaries, telephony, SDKs, and pricing but not audio quality/noise robustness features. Missing for 10: any mention of noise suppression/audio filtering configuration, VAD tuning for noisy environments, or documented handling of real-world call noise.

   ⚑ flag

   telli—none0/10

   No evidence pack item mentions noise suppression, audio filtering, or any mechanism for handling noisy call environments; documentation covers scheduling, workflows, analytics, and voice cloning but not audio quality/noise handling.

   ⚑ flag

3. developerUse model-based end-of-turn detection beyond simple VAD silence timeouts so the agent doesn't talk over slow speakers

   weight 2 · round drawn
   Bolna—none0/10

   No evidence describes model-based end-of-turn/turn-taking detection distinct from VAD silence timeouts; evidence only covers mid-call model switching, extraction categories, and unrelated features. Missing for 10: any mention of endpointing model, semantic turn detection, or configurable end-of-turn logic beyond silence thresholds.

   ⚑ flag

   telli—none0/10

   No evidence in the pack discusses turn-taking, end-of-turn detection, VAD, or interruption handling in telli's voice agent; the docs cover scheduling, workflows, tools, and integrations but not conversational latency/turn-taking mechanics.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Bolna
   Bolna~partialprobed7/10

   Docs show the platform is API-first — agent creation, extraction categories, call summaries, workflows, and telephony are all described as configurable via the API, and a CLI and MCP server both wrap that same API, implying broad parity. However, there is no explicit documentation stating full UI/API feature parity, and probes found no discoverable OpenAPI/swagger spec (404s), leaving some doubt about completeness of coverage for every UI action. Missing for 10: explicit UI-API parity statement, published OpenAPI/swagger spec, independent confirmation that all UI actions have API equivalents.

   • [claimed-docs] “POST /agent/{agent_id}/extraction-categories — create a category (name + model) and attach it to an agent”
   • [claimed-docs] “Call summaries are an agent-level toggle: call_summary_enabled (boolean, off by default) on the agent create and update APIs”
   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.bolna.ai/openapi.json, https://docs.bolna.ai/swagger.json, https://docs.bolna.ai/api/op…”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”

   proof ↗⚑ flag

   telli~partialprobed6/10

   telli exposes a REST API (with OpenAPI spec) covering contacts, scheduling calls, phone number import, custom tools, and webhooks, and also offers an MCP server so external AI tools can interact with Charlie. However, several UI-native features—agent builder/test-call dialog, live monitoring dashboard, side-by-side transcript/recording view, voice cloning setup, workflow trigger/recurring schedule configuration UI, and analytics dashboards—are not documented as API-accessible endpoints, so full UI/API parity is not evidenced. missing for 10: API endpoints for agent building/testing, live monitoring, voice cloning, workflow scheduling configuration, and analytics/reporting equivalent to UI dashboards.

   • [claimed-docs] “API Endpoints: Use telli's REST API to programmatically manage contacts, schedule calls, and integrate with your existing systems.”
   • [claimed-docs] “All endpoints authenticate with an API key from the telli app (Settings > Developer), sent as a bearer token”
   • [claimed-docs] “Download them to generate client libraries, import the API into tools like Postman, or give coding agents machine-readable API context”
   • [claimed-docs] “Schedules a call at the earliest opportunity within the dialer window. May occur immediately or on the next business day depending on settin…”
   • [claimed-docs] “Imports a phone number from your own SIP trunk provider. This allows you to use existing phone numbers with telli by configuring custom SIP …”
   • [claimed-docs] “Custom tools allow your AI agents to access external information by connecting to your APIs.”
   • [claimed-docs] “Webhooks push data from telli to your systems in real time. When something happens on a call, telli sends a POST request to the endpoint you…”
   • [claimed-docs] “The telli MCP server lets AI tools like Claude, ChatGPT, and Codex talk to Charlie, telli's AI assistant, over the Model Context Protocol.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.telli.com/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://docs.telli.com/integrations/mcp”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Bolna
   Bolna~partialclaimed3/10

   Bolna's API lets you fetch call transcripts (bolna-docs-14) and the platform can be self-hosted via Docker/Kubernetes (bolna-docs-9), with an open-source core framework (bolna-gh-1), which together provide some data portability, but there is no documented bulk 'export all data' feature or guarantee of open, standard export formats covering call recordings, agent configs, analytics, etc. Missing for 10: an explicit full-data export tool/endpoint, documented open format specification for exported data, and independent confirmation that a user can fully migrate away with all their data.

   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”
   • [github] “Bolna is the end-to-end open source production ready framework for quickly building LLM based voice driven conversational applications.”

   proof ↗⚑ flag

   telli—none0/10

   No evidence of a bulk data-export feature or open-format data portability; only API endpoints to manage/read specific records and a data-retention deletion policy are documented, not a full self-service export/leave capability. Missing for 10: documented full-account export tool/endpoint, open-format (CSV/JSON) bulk export, and any explicit data-portability statement.

   • [claimed-docs] “API Endpoints: Use telli's REST API to programmatically manage contacts, schedule calls, and integrate with your existing systems.”
   • [claimed-docs] “Data retention deletes contacts and call data automatically once they reach an age you define.”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Bolna
   Bolna~partialclaimed5/10

   The GitHub repo description explicitly calls Bolna 'the end-to-end open source production ready framework,' supporting that its source is publicly available under an open-license framing, but no specific license (e.g., MIT/Apache) is named or verified, and no independent corroboration exists. Missing for 10: explicit license identification (e.g., LICENSE file contents), confirmation the entire product (not just the framework) is open-sourced, and independent verification.

   • [github] “Bolna is the end-to-end open source production ready framework for quickly building LLM based voice driven conversational applications.”

   proof ↗⚑ flag

   telli—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Bolna
   Bolna✓fullclaimed8/10

   Bolna is explicitly open source (GitHub repo) and documentation provides dedicated on-premise instructions for self-hosting via Docker or Kubernetes for enterprise deployments, directly satisfying the self-host story. Missing for 10: independent/hands-on confirmation of a successful self-hosted deployment and more detail on feature parity between self-hosted and cloud versions.

   • [github] “Bolna is the end-to-end open source production ready framework for quickly building LLM based voice driven conversational applications.”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”

   proof ↗⚑ flag

   telli—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Pricing

1. founderSee published per-minute or usage pricing and estimate cost per call before committing

   weight 2 · round to Bolna
   Bolna~partialclaimed4/10

   There is a dedicated call-pricing doc page and mentions that BYOK/connected providers aren't charged (bolna-docs-19, bolna-docs-10), indicating some usage-based pricing structure exists, but no evidence pack item actually quotes a per-minute rate, tiered pricing table, or a cost calculator a founder could use to estimate cost per call. Missing for 10: explicit per-minute/usage rate figures, a pricing calculator or worked cost example, and independent confirmation that published rates are accurate.

   • [claimed-docs] “When you bring your own keys (BYOK), Bolna does not charge for those components.”
   • [claimed-docs] “We don't charge for any usage for providers that you have connected to Bolna.”

   proof ↗⚑ flag

   telli—none0/10

   No evidence in the pack mentions pricing, per-minute rates, usage costs, or any cost calculator/estimator; the docs cover features (workflows, appointments, API, MCP, etc.) but nothing about published pricing.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Bolna
   Bolna~partialclaimed6/10

   Docs explicitly mention Indian data residency as an available option, and self-hosting via Docker/Kubernetes lets enterprises control where data lives entirely. However, there's no broader multi-region selection (e.g., EU, US) documented beyond India, and no detail on how residency is configured or enforced. Missing for 10: documented multi-region choice beyond India, configuration/UI for selecting region, and independent confirmation of residency enforcement.

   • [claimed-docs] “Indian data residency is available for deployments where data must remain in India.”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”

   proof ↗⚑ flag

   telli—none0/10

   No evidence in the pack mentions data residency, region selection, or data storage location controls; data retention (deletion timing) is covered but that is a different capability from choosing storage region.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Bolna—none0/10

   No evidence pack item addresses a training-data opt-out or policy on AI model training use; security docs cover data residency and IP whitelisting only, not training-data usage controls. missing for 10: any explicit statement on AI training data usage/opt-out policy, data processing agreement terms, or contractual guarantee against training use.

   ⚑ flag

   telli—none0/10

   No evidence in the pack addresses AI training data usage or opt-out policies; data retention docs cover deletion of contacts/call data but not model-training exclusion.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to telli
   Bolna—none0/10

   No evidence of data retention controls, deletion APIs, or user-facing privacy/data-lifecycle settings; only tangential mentions of security (IP whitelisting, India data residency) which do not address retention/deletion. Self-hosting option exists but that's deployment control, not a retention/deletion feature.

   • [claimed-docs] “Indian data residency is available for deployments where data must remain in India.”
   • [claimed-docs] “Whitelist all three IPs on your server or firewall”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”

   proof ↗⚑ flag

   telli~partialclaimed6/10

   telli documents automatic data retention deletion (contacts and call data purged once they reach a defined age) and conditional consent-based recording, giving users some control over data lifecycle and privacy. However, there's no evidence of user-initiated manual deletion, export/right-to-access tools, or granular per-record deletion controls beyond the age-based policy. missing for 10: manual/on-demand deletion controls, data export capability, independent verification of retention enforcement.

   • [claimed-docs] “Data retention deletes contacts and call data automatically once they reach an age you define.”
   • [claimed-docs] “In telli, you can easily make audio recording conditional on the caller's consent — so a call is only recorded once they agree.”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Bolna—none0/10

   No evidence pack item addresses telemetry, analytics opt-out, or usage-tracking controls for the platform itself; existing security/data-residency docs don't cover this. Missing for 10: any documentation of telemetry collection or an opt-out/disable mechanism, privacy policy statement on usage tracking, self-host confirmation of no phone-home behavior.

   ⚑ flag

   telli—none0/10

   telli is a voice-agent platform, not a developer tool where telemetry opt-out is typically discussed, but the axis is still fair to ask (does the product track usage, and can a user disable it). The evidence pack (data retention, consent-based recording, etc.) never mentions any telemetry/usage-tracking opt-out mechanism for the product itself. Missing for 10: any documentation of telemetry collection practices or an opt-out setting/toggle.

   ⚑ flag

Call control

1. developerEscalate a live call to a human with warm or blind transfer, passing context along

   weight 2 · round to telli
   Bolna—none0/10

   No evidence in the pack describes call transfer functionality (warm or blind) to a human agent, or context handoff during a live call; the closest items relate to model switching, summaries, and telephony/SIP trunking but not transfer escalation.

   ⚑ flag

   telli~partialclaimed4/10

   Docs confirm a transfer tool that can move a call to another agent or number, matching the core escalation-to-human idea, but there's no mention of distinct warm vs. blind transfer modes or explicit context-passing to the human recipient. missing for 10: explicit warm/blind transfer distinction, evidence of context/data hand-off during transfer, hands-on confirmation of the feature in practice.

   • [claimed-docs] “Transfer tools | Move the call to another agent or number.”

   proof ↗⚑ flag

2. developerMy agent can send DTMF keypresses, navigate IVR menus, and detect or leave voicemail

   weight 1 · round drawn
   Bolna—none0/10

   No evidence in the pack mentions DTMF keypress sending, IVR menu navigation, or voicemail detection/leaving; only unrelated telephony features like SIP trunking, call summaries, and workflows are documented.

   ⚑ flag

   telli—none0/10

   No evidence in the pack mentions DTMF keypress sending, IVR menu navigation, or voicemail detection/leaving; telli's docs cover scheduling, transfers, web search tool, and webhooks but nothing about touch-tone or answering machine handling.

   ⚑ flag

Campaigns

1. founderRun batch outbound call campaigns with scheduling and throughput controls

   weight 2 · round to telli
   Bolna~partialprobed5/10

   The CLI explicitly manages 'batches' of calls alongside agents/phone numbers, and marketing copy claims support for 'thousands of inbound and outbound calls every minute,' plus a workflows API for multi-step outreach with waits/retries — together implying batch campaign and throughput capability. However, there's no explicit documentation of scheduling controls (e.g., time windows, campaign start/stop) or throughput/rate-limiting configuration for outbound campaigns specifically. Missing for 10: explicit scheduling/calendar controls for campaigns, documented throughput/rate-limit configuration knobs, and any hands-on/independent evidence of batch campaign execution.

   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [claimed-docs] “Power thousands of inbound and outbound calls every minute with human-like, multilingual intelligence”
   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”

   proof ↗⚑ flag

   telli~partialclaimed6/10

   telli documents dialing windows, calling strategies, and retry behavior (telli-docs-9) plus a schedule-call API endpoint that respects dialer windows or can bypass them (telli-docs-17, telli-docs-18) and reach-rate/success metrics (telli-docs-7), which together support scheduled, throughput-controlled outbound calling. However there is no explicit mention of a 'campaign' concept, bulk contact upload, or concurrency/rate limits for large batches. Missing for 10: explicit batch/campaign creation UI or endpoint, bulk contact import for calling, and documented concurrency/throughput limits beyond dialing windows.

   • [claimed-docs] “Configure dialing windows, calling strategies, and retry behavior.”
   • [claimed-docs] “Schedules a call at the earliest opportunity within the dialer window. May occur immediately or on the next business day depending on settin…”
   • [claimed-docs] “Optional flag to bypass dialing window restrictions for the scheduled call. When true, calls at the scheduled time regardless of dialing win…”
   • [claimed-docs] “Track key metrics like reach rate, call duration, and success rate.”
   • [claimed-docs] “Workflows can now run automatically on a recurring schedule. Add a Scheduled trigger, choose the interval and start time, and let the workfl…”

   proof ↗⚑ flag

Numbers

1. developerProvision phone numbers and run both inbound and outbound calls through the platform's API

   weight 3 · round to telli
   Bolna~partialprobed6/10

   Bolna's API/CLI clearly support placing outbound calls and receiving inbound calls (quickstart shows placing a call and fetching transcript via API, CLI manages calls and phone numbers, marketing claims thousands of inbound/outbound calls per minute), and BYOT lets you attach SIP trunks/numbers. However there's no explicit documented endpoint for provisioning/purchasing new phone numbers through the API itself — only CLI mention of managing 'phone numbers' and bringing your own trunk. Missing for 10: explicit phone-number provisioning API endpoint/documentation, independent confirmation of end-to-end inbound+outbound flow.

   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [claimed-docs] “Bring Your Own Telephony (BYOT) lets you connect any standards-compliant SIP trunk to the Bolna platform.”
   • [claimed-docs] “Power thousands of inbound and outbound calls every minute with human-like, multilingual intelligence”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”

   proof ↗⚑ flag

   telli~partialprobed7/10

   telli's docs show a REST API with a schedule-call endpoint for outbound calls, an import-phone-number endpoint to bring SIP-trunk numbers under API control, webhooks for call events, and an OpenAPI spec confirming the API surface. However, inbound handling is documented mainly as manual forwarding/SIP trunk setup rather than a clear 'provision a new number via API' flow, and there's no explicit doc of purchasing/creating a fresh telli-hosted number through the API. missing for 10: a documented endpoint to provision/purchase brand-new phone numbers (not just import existing SIP trunk numbers), and clearer API-driven inbound call handling beyond forwarding.

   • [claimed-docs] “API Endpoints: Use telli's REST API to programmatically manage contacts, schedule calls, and integrate with your existing systems.”
   • [claimed-docs] “Schedules a call at the earliest opportunity within the dialer window. May occur immediately or on the next business day depending on settin…”
   • [claimed-docs] “Imports a phone number from your own SIP trunk provider. This allows you to use existing phone numbers with telli by configuring custom SIP …”
   • [claimed-docs] “Webhooks push data from telli to your systems in real time. When something happens on a call, telli sends a POST request to the endpoint you…”
   • [claimed-docs] “Keep your public business number and forward incoming calls to a telli number. You configure the forwarding with your phone provider or PBX.”
   • [claimed-docs] “Connect an existing number and phone system for incoming and outgoing calls. You need SIP trunk access from your provider.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.telli.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

Sip

1. platform-engineerConnect my own carrier or PBX via SIP trunking (or import Twilio/Telnyx numbers) instead of being locked to bundled telephony

   weight 2 · round drawn
   Bolna✓fullclaimed8/10

   Bolna explicitly documents 'Bring Your Own Telephony (BYOT)' allowing any standards-compliant SIP trunk to connect to the platform, plus IP whitelisting requirements for the connection, directly addressing carrier/PBX independence from bundled telephony. missing for 10: explicit step-by-step Twilio/Telnyx number import walkthrough and independent/hands-on verification of SIP trunk setup working end-to-end.

   • [claimed-docs] “Bring Your Own Telephony (BYOT) lets you connect any standards-compliant SIP trunk to the Bolna platform.”
   • [claimed-docs] “Whitelist all three IPs on your server or firewall”

   proof ↗⚑ flag

   telli✓fullclaimed8/10

   Docs explicitly support importing numbers from a customer's own SIP trunk provider via a dedicated API endpoint, plus general SIP trunk connection for incoming/outgoing calls and call forwarding from an existing PBX/provider number. This directly matches the platform-engineer's need to bring their own carrier rather than being locked into bundled telephony. Missing for 10: no explicit mention of native Twilio/Telnyx number import (only generic SIP trunk import), and no independent/hands-on confirmation of the SIP trunk setup working in practice.

   • [claimed-docs] “Imports a phone number from your own SIP trunk provider. This allows you to use existing phone numbers with telli by configuring custom SIP …”
   • [claimed-docs] “Keep your public business number and forward incoming calls to a telli number. You configure the forwarding with your phone provider or PBX.”
   • [claimed-docs] “Connect an existing number and phone system for incoming and outgoing calls. You need SIP trunk access from your provider.”

   proof ↗⚑ flag

Analytics

1. ai-native userThe platform's AI reviews my calls for me — scoring quality, flagging failures, and analyzing resolution automatically

   weight 2 · round to telli
   Bolna~partialclaimed3/10

   Bolna offers post-call analysis primitives — configurable extraction-categories (bolna-docs-1) and toggleable call summaries (bolna-docs-2) — which could be used to build custom scoring/flagging, but there's no documented automated QA/quality-scoring, failure-flagging, or resolution-analysis feature out of the box. Missing for 10: dedicated call-scoring/QA dashboard, automatic failure detection, resolution-analysis reporting, and independent evidence these extraction fields are used for review purposes.

   • [claimed-docs] “POST /agent/{agent_id}/extraction-categories — create a category (name + model) and attach it to an agent”
   • [claimed-docs] “Call summaries are an agent-level toggle: call_summary_enabled (boolean, off by default) on the agent create and update APIs”

   proof ↗⚑ flag

   telli~partialclaimed5/10

   telli provides analytics like reach rate, success rate, call outcome fields, transcripts, and manual feedback submission for agent improvement, but there's no evidence of automated AI-driven quality scoring, failure flagging, or resolution analysis performed autonomously by the platform's AI — feedback and analysis appear human-driven rather than AI-automated review. missing for 10: automated AI scoring of call quality, automatic failure/anomaly flagging, AI-generated resolution analysis without human review.

   • [claimed-docs] “Track key metrics like reach rate, call duration, and success rate.”
   • [claimed-docs] “Analyze individual calls, transcripts, and call outcome fields.”
   • [claimed-docs] “Submit feedback on calls to continuously improve your agent.”

   proof ↗⚑ flag

2. founderSee call analytics — success rates, durations, outcomes, sentiment — in dashboards without building my own

   weight 2 · round to telli
   Bolna—none0/10

   Evidence only shows API-level features like call summaries (call_summary_enabled) and extraction categories, but there is no mention of a dashboard UI presenting success rates, durrations, outcomes, or sentiment analytics — missing for 10: any dashboard/UI screenshot or docs describing aggregated call analytics views.

   • [claimed-docs] “POST /agent/{agent_id}/extraction-categories — create a category (name + model) and attach it to an agent”
   • [claimed-docs] “Call summaries are an agent-level toggle: call_summary_enabled (boolean, off by default) on the agent create and update APIs”

   proof ↗⚑ flag

   telli~partialclaimed6/10

   telli's docs describe built-in dashboards tracking reach rate, call duration, and success rate, plus per-call analysis of transcripts and outcome fields, and a live monitoring overview—covering most of the story without needing custom tooling. However, there is no explicit mention of sentiment analysis in dashboards. missing for 10: sentiment scoring/analysis in dashboards, independent/hands-on corroboration of dashboard usability.

   • [claimed-docs] “Track key metrics like reach rate, call duration, and success rate.”
   • [claimed-docs] “Analyze individual calls, transcripts, and call outcome fields.”
   • [claimed-docs] “Live Monitoring > Real-time call overview of your contacts”

   proof ↗⚑ flag

Monitoring

1. platform-engineerMonitor live calls in production and get alerts when agents misbehave or error rates spike

   weight 1 · round to telli
   Bolna—none0/10

   Evidence covers call summaries, extraction categories, transcripts, CLI, MCP, and SIP/telephony features, but nothing describes live-call monitoring dashboards, real-time observability, or alerting on agent misbehavior or error-rate spikes. No mention of metrics, alert thresholds, webhooks for anomaly detection, or a monitoring console for platform engineers. Missing for 10: real-time monitoring dashboard, alerting/notification system for errors or misbehavior, error-rate tracking, on-call/integration with observability tools.

   ⚑ flag

   telli~partialclaimed5/10

   telli offers a real-time Live Monitoring call overview (telli-docs-32) and webhooks that push real-time notifications on call events/status/outcomes (telli-docs-13, telli-docs-21), which a platform engineer could wire into an alerting pipeline, plus metric tracking like success/reach rate (telli-docs-7). However there is no documented built-in alerting mechanism, error-rate-spike detection, or agent-misbehavior alerting system. Missing for 10: native alert/notification thresholds, anomaly or error-rate-spike detection, and evidence of alert delivery (email/Slack/PagerDuty) tied to live monitoring.

   • [claimed-docs] “Live Monitoring > Real-time call overview of your contacts”
   • [claimed-docs] “Webhooks: Receive real-time notifications about call events, status changes, and outcomes.”
   • [claimed-docs] “Webhooks push data from telli to your systems in real time. When something happens on a call, telli sends a POST request to the endpoint you…”
   • [claimed-docs] “Track key metrics like reach rate, call duration, and success rate.”

   proof ↗⚑ flag

Testing

1. developerTest agents with simulated conversations or evals before putting them on real phone calls

   weight 2 · round to telli
   Bolna—none0/10

   No evidence of any simulated conversation testing, evals, or pre-production testing framework for agents; the evidence pack only covers deployment, telephony, providers, pricing, and SDKs. Missing for 10: any mention of test/eval tooling, simulated call testing, or conversation quality scoring before live calls.

   ⚑ flag

   telli~partialclaimed5/10

   telli's agent builder includes a 'Test call' feature to trial a draft or saved agent version and review the recording/transcript side-by-side before going live, which covers pre-production testing, and feedback submission helps iterate on agent quality. However, there is no evidence of simulated/synthetic conversation runs, automated eval suites, or scripted test scenarios independent of an actual phone call. Missing for 10: automated evals framework, non-call simulated conversation testing, batch/regression testing tools.

   • [claimed-docs] “In the agent builder, click Test call to open the dialog. Pick the agent version (your draft with unsaved changes or any saved revision)...”
   • [claimed-docs] “Use the side-by-side view to listen to the recording while following along in the transcript.”
   • [claimed-docs] “Submit feedback on calls to continuously improve your agent.”

   proof ↗⚑ flag

Post call

1. developerExtract structured data from every call — outcomes, entities, dispositions — delivered via API or webhook after the call

   weight 2 · round drawn
   Bolna~partialclaimed6/10

   Bolna provides extraction-categories API to attach custom entity/data extraction to agents and a call_summary_enabled toggle for summaries, plus transcript fetch via API — covering entities, summaries, and outcomes. However, there's no explicit documentation of a unified structured 'disposition' field, no clear webhook delivery mechanism for post-call structured payloads (only API fetch is shown), and no example of the combined extraction+summary+disposition JSON schema. missing for 10: webhook-based delivery of extraction results, documented disposition/outcome field, end-to-end example combining all three data types in one payload.

   • [claimed-docs] “POST /agent/{agent_id}/extraction-categories — create a category (name + model) and attach it to an agent”
   • [claimed-docs] “Call summaries are an agent-level toggle: call_summary_enabled (boolean, off by default) on the agent create and update APIs”
   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”

   proof ↗⚑ flag

   telli~partialclaimed6/10

   telli documents webhooks pushing real-time call event/status/outcome data and a REST API for programmatic access, plus conversation views showing appointment/outcome fields and call outcome analysis, supporting structured post-call data delivery. However, there's no explicit documentation of a structured schema for entities/dispositions extraction or example payloads showing the full breadth of structured fields promised. missing for 10: example webhook/API payload showing structured entities and disposition fields, documentation of a dedicated 'call outcomes' data model, independent/hands-on confirmation of data completeness.

   • [claimed-docs] “Webhooks: Receive real-time notifications about call events, status changes, and outcomes.”
   • [claimed-docs] “Webhooks push data from telli to your systems in real time. When something happens on a call, telli sends a POST request to the endpoint you…”
   • [claimed-docs] “Analyze individual calls, transcripts, and call outcome fields.”
   • [claimed-docs] “Conversations now show appointments saved during a call, including the time, status, hosts, and provider link.”
   • [claimed-docs] “API Endpoints: Use telli's REST API to programmatically manage contacts, schedule calls, and integrate with your existing systems.”

   proof ↗⚑ flag

Tools

1. ai-native userMy voice agent can plug in MCP servers as tool sources so one integration grants it whole toolsets mid-call

   weight 2 · round drawn
   Bolna—none0/10

   Evidence only shows Bolna exposing its OWN MCP server so external clients (Claude, Cursor, Windsurf) can manage a Bolna account (bolna-docs-17, bolna-probe-3) — the reverse direction of the story, which asks whether a Bolna voice agent can consume external MCP servers as tool sources mid-call. No documentation shows Bolna agents acting as an MCP client or importing toolsets from third-party MCP servers during a call. missing for 10: any evidence of Bolna voice agents connecting to external MCP servers as tool sources, mid-call toolset loading via MCP.

   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “official MCP server documented at https://www.bolna.ai/docs/build-with-ai/mcp”

   proof ↗⚑ flag

   telli—none0/10

   telli documents custom tools connecting to external APIs (telli-docs-20) and even an MCP server (telli-docs-22, telli-probe-3), but that MCP server lets external AI tools like Claude/ChatGPT talk to telli's Charlie assistant — it is telli acting as an MCP server, not the voice agent consuming external MCP servers as a tool source mid-call. There is no evidence the voice agent itself can plug in MCP servers to gain toolsets during a call.

   • [claimed-docs] “The telli MCP server lets AI tools like Claude, ChatGPT, and Codex talk to Charlie, telli's AI assistant, over the Model Context Protocol.”
   • [probe] “official MCP server documented at https://docs.telli.com/integrations/mcp”
   • [claimed-docs] “Custom tools allow your AI agents to access external information by connecting to your APIs.”

   proof ↗⚑ flag

2. developerMy agent can call external APIs and custom functions mid-conversation and speak the result without awkward dead air

   weight 3 · round to telli
   Bolna—none0/10

   The evidence pack covers extraction categories, call summaries, workflows, and custom LLM providers, but nothing describes an agent invoking external APIs or custom functions mid-call and voicing the result seamlessly. Missing for 10: documentation of a function-calling/tool-use API, examples of mid-call API invocation, and any mention of latency-masking/filler techniques to avoid dead air.

   ⚑ flag

   telli~partialclaimed6/10

   Docs confirm custom tools let agents call external APIs mid-call (telli-docs-20) and built-in tool calls like web_search operate during live calls (telli-docs-30), plus transfer tools show mid-call action execution (telli-docs-31). However, there is no documentation addressing latency masking or filler-speech to avoid 'dead air' while awaiting API responses. missing for 10: explicit evidence of latency-hiding/filler speech during tool calls, independent hands-on confirmation of smooth voice continuity.

   • [claimed-docs] “Custom tools allow your AI agents to access external information by connecting to your APIs.”
   • [claimed-docs] “For a Duo agent, open Tools > System and enable web_search to let the agent search the web for current public information during calls.”
   • [claimed-docs] “Transfer tools | Move the call to another agent or number.”

   proof ↗⚑ flag

Recording

1. platform-engineerRetrieve full call recordings and transcripts programmatically for every call

   weight 2 · round drawn
   Bolna~partialclaimed5/10

   Docs confirm fetching call transcripts via API (quickstart mentions 'fetch the transcript') and call summaries can be toggled, but there is no explicit documentation of a dedicated recordings-retrieval endpoint or bulk/programmatic export for all calls. missing for 10: explicit call-recording download/API endpoint, confirmation that recordings are retained and accessible for every call, and independent verification of transcript completeness/format.

   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “Call summaries are an agent-level toggle: call_summary_enabled (boolean, off by default) on the agent create and update APIs”
   • [claimed-docs] “POST /agent/{agent_id}/extraction-categories — create a category (name + model) and attach it to an agent”

   proof ↗⚑ flag

   telli~partialprobed5/10

   Docs confirm transcripts and recordings exist and can be reviewed in-app (side-by-side view, consent-based recording) and telli exposes a general REST API plus webhooks for call events, but no endpoint is documented that explicitly returns full call recordings or transcripts programmatically for every call. missing for 10: a documented GET/recording or GET/transcript API endpoint, confirmation of bulk/enumerable retrieval, and independent verification that recordings are accessible via the API rather than only in the UI.

   • [claimed-docs] “Analyze individual calls, transcripts, and call outcome fields.”
   • [claimed-docs] “Use the side-by-side view to listen to the recording while following along in the transcript.”
   • [claimed-docs] “In telli, you can easily make audio recording conditional on the caller's consent — so a call is only recorded once they agree.”
   • [claimed-docs] “API Endpoints: Use telli's REST API to programmatically manage contacts, schedule calls, and integrate with your existing systems.”
   • [claimed-docs] “Webhooks: Receive real-time notifications about call events, status changes, and outcomes.”
   • [claimed-docs] “Webhooks push data from telli to your systems in real time. When something happens on a call, telli sends a POST request to the endpoint you…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.telli.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

Transcription

1. developerGet accurate real-time transcription with control over the STT provider, language models, or key terms

   weight 2 · round to Bolna
   Bolna~partialclaimed5/10

   Docs confirm STT provider choice (Deepgram, Azure, ElevenLabs) and full LLM control including custom OpenAI-compatible endpoints, plus transcript retrieval via API, giving developers real provider/model flexibility. However there is no evidence of key-term/vocabulary boosting or accuracy tuning controls, nor any real-time transcription accuracy benchmarks. Missing for 10: key-term/keyword-boost configuration, accuracy/latency benchmarks for real-time transcription, and independent validation of transcription quality.

   • [claimed-docs] “Bolna supports Deepgram, Azure, ElevenLabs, and more.”
   • [claimed-docs] “For custom llm simply keep provider in the llm_agent key as custom and add a openai compatible base_url”
   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”

   proof ↗⚑ flag

   telli—none0/10

   telli documents transcript viewing and side-by-side playback (telli-docs-29) but provides no evidence of developer-facing control over STT provider selection, choice of underlying language models, or custom key-term/vocabulary boosting for transcription accuracy.

   • [claimed-docs] “Use the side-by-side view to listen to the recording while following along in the transcript.”

   proof ↗⚑ flag

Voices

1. founderClone a custom brand voice and use it for my agents, with a documented consent process

   weight 2 · round to telli
   Bolna—none0/10

   Evidence shows Bolna lets founders choose among third-party voices/accents/styles (bolna-docs-8) and integrates providers like ElevenLabs (bolna-docs-6), but there is no mention of a voice-cloning feature for a custom brand voice, nor any documented consent process for cloning. Missing for 10: voice cloning capability, consent/verification workflow documentation, any policy on brand voice usage.

   • [claimed-docs] “You can choose different voices, accents, and speaking styles to match your brand.”
   • [claimed-docs] “Bolna supports Deepgram, Azure, ElevenLabs, and more.”

   proof ↗⚑ flag

   telli~partialclaimed5/10

   Voice cloning is documented as a real feature (telli-docs-27) letting founders give agents a custom voice, but the pack's only consent-related documentation concerns call recording consent (telli-docs-26), not a consent process specifically for cloning someone's voice. Missing for 10: explicit documented consent/authorization workflow for the voice being cloned (e.g., proof of rights from the voice owner), and any legal/compliance guardrails for cloning third-party voices.

   • [claimed-docs] “Voice cloning lets you give your agent a custom voice (your own, a colleague's, or a professional voice actor's), so the agent sounds exactl…”
   • [claimed-docs] “In telli, you can easily make audio recording conditional on the caller's consent — so a call is only recorded once they agree.”

   proof ↗⚑ flag

2. developerChoose from a broad voice library or plug in multiple TTS providers to get the voice I want

   weight 2 · round to Bolna
   Bolna~partialclaimed6/10

   Docs confirm multiple TTS providers (Deepgram, Azure, ElevenLabs, and more) plus voice/accent/style customization, satisfying the 'plug in providers' part of the story. However, there's no evidence of a broad pre-built voice library or catalog to browse/select from, only provider integration. Missing for 10: evidence of a large built-in voice library/catalog, provider-count breadth beyond three named examples, independent/hands-on confirmation of voice quality or selection UX.

   • [claimed-docs] “Bolna supports Deepgram, Azure, ElevenLabs, and more.”
   • [claimed-docs] “You can choose different voices, accents, and speaking styles to match your brand.”

   proof ↗⚑ flag

   telli~partialclaimed3/10

   Docs mention voice cloning to give an agent a custom voice, but there is no evidence of a curated voice library to choose from or the ability to plug in multiple external TTS providers as the story requires. missing for 10: evidence of a selectable voice library, multi-provider TTS integration, developer API/config for switching TTS engines.

   • [claimed-docs] “Voice cloning lets you give your agent a custom voice (your own, a colleague's, or a professional voice actor's), so the agent sounds exactl…”

   proof ↗⚑ flag