# TelEcho — Conversational AI platform for voice and messaging agents that run customer calls and update connected systems. > Source: The Agents Index — https://theagentsindex.com/telecho (structured, researched, re-verified) > Facts last verified: 2026-09-16 TelEcho is a conversational AI platform from RTC LEAGUE for building voice and messaging agents that handle phone, WhatsApp and WeChat conversations. Agents are assembled in a visual workflow builder and act on connected CRM, calendar and ticketing systems during the call. | Fact | Value | | --- | --- | | Website | https://telecho.io | | Price | from $0.07/minute pay-as-you-go | | Free tier | Partly | Build plan is free to sign up for and covers 1 agent deployment, observability basics and limited team access; Pay-as-you-go includes 20 concurrent calls free, but minutes meter from $0.07/min and no free minute allowance is published. ## What it does **Done-for-you service** · Partly — You run the software yourself in a no-code builder, but the vendor also sells hands-on help: strategy calls, an onboarding meeting and prompt-engineering support appear only in the Enterprise column of the comparison table. > Work with us to design, launch, and scale production-ready AI-powered voice assistants. > — https://telecho.io/pricing · Footer call-to-action band, closing line above the link columns ## How much it does unattended **Runs autonomously** · Yes — Agents run whole calls and write to connected systems without a person on each interaction; escalation rules and human handoff conditions are set during agent setup rather than removed. > They can update CRMs, schedule appointments, trigger workflows, and route calls without needing a human on every interaction. > — https://telecho.io/pricing · Frequently Asked Questions accordion, 'What are AI voice agents and how do they work?', expanded **Agent permissions** · Yes — Scope is bounded at setup rather than per action: guardrails, escalation and handoff conditions, business hours and response policies are configured before an agent goes live, and no per-step approval prompt is described. > Escalation rules and human handoff conditions > — https://telecho.io/how-it-works · Step 02 Agent Setup, configuration checklist _Not established: Multi-agent_ ## Which models it runs on **Claude** · Partly — Claude appears as a place you drive TelEcho from, via the vendor's MCP integration, not as a model the agent can run on; the pricing calculator's LLM selector offers OpenAI models only. > Define and configure your agent directly from ChatGPT or Claude via TelEcho's native MCP integration, without switching platforms. > — https://telecho.io/how-it-works · Step 02 Agent Setup, 'Prefer working inside your AI tools?' callout **GPT** · Yes — GPT is the platform's reasoning layer: the pricing calculator meters GPT-5, GPT-5 Mini, GPT-5 Nano, GPT 4.1 and GPT 4.1 Mini, and OpenAI is the sole LLM provider named in the sub-processor table. > OpenAI LLM reasoning and response generation Call transcripts, workflow context United States > — https://telecho.io/security · Sub-processors table, OpenAI row **Open models** · No — No open-weight option is offered anywhere: the calculator's five LLM choices are all OpenAI, and the vendor's complete sub-processor inventory names OpenAI as the only LLM provider that touches customer data. > TelEcho engages the following Sub-processors to provide the Service. > — https://telecho.io/security · Sub-processors section, sentence introducing the full provider table **Model choice** · Partly — You choose the telephony carrier, the STT engine, the TTS voice and the execution pipeline, but every LLM option in the calculator comes from one vendor, so model choice stops at OpenAI. > We support multiple conversational execution models, depending on latency, compliance, and use case. > — https://telecho.io/features · Real-time voice engine section, opening paragraph ## Where you use it **In a browser** · Yes — The whole product is a hosted web application: a visual drag-and-drop workflow builder, live dashboards, session replay and versioning, with nothing to install locally. > TelEcho's visual workflow builder makes conversational AI design fast and precise > — https://telecho.io/how-it-works · Step 04 Design The Workflow, introductory line _Not established: On the command line_ ## Whose machine it runs on **Open source** · No — The platform is closed and proprietary: the terms forbid decompiling or extracting source, ownership of the Services stays with RTC LEAGUE, and only bundled third-party open-source components are acknowledged. > Reverse engineer, decompile, or attempt to extract source code or the underlying AI models > — https://telecho.io/legal/terms · Section 3.2 Restrictions, prohibited-use list _Not established: Self-hosted_ ## What it costs to run **How it meters** · Yes — Billing follows conversation time, not seats: a platform base fee of $0.08 per minute plus metered telephony, LLM, STT and TTS, with WhatsApp and WeChat messages priced per message. > Transparent pricing = Platform plan + Usage. Use the calculator to estimate your monthly spend. > — https://telecho.io/pricing · Section above the AI Voice Agent Pricing Calculator **Free tier** · Partly — A free Build tier exists for evaluation with one agent deployment and basic observability, and Pay-as-you-go includes twenty concurrent calls, but no free minute allowance is published so real calls still meter per minute. > free 20 calls, can purchase > — https://telecho.io/pricing · Compare Plans table, Voice AI section, Concurrent calls row, Pay-as-you-go column **API access** · Partly — A Voice Agent API exists and carries an uptime commitment, and webhooks, custom REST integration and Enterprise metrics-export APIs are advertised, but the site publishes no endpoint reference, no docs route and no key-issuing flow. > Voice Agent API & Telephony Routing > — https://telecho.io/security · Uptime, Latency & Support table, Service column, first row **MCP server** · Yes — TelEcho documents a native MCP integration letting an agent inside ChatGPT or Claude define and configure TelEcho agents; no server address, tool inventory or auth flow is published to verify scope. > Define and configure your agent directly from ChatGPT or Claude via TelEcho's native MCP integration, without switching platforms. > — https://telecho.io/how-it-works · Step 02 Agent Setup, 'Prefer working inside your AI tools?' callout **Bring your own key** · Partly — You may bring your own carrier by routing calls over third-party SIP and you choose the cloud region your data sits in, but nothing offers your own OpenAI, STT or TTS keys, so inference runs on TelEcho's provider accounts. > Third-party SIP $0.004/min > — https://telecho.io/pricing · AI Voice Agent Pricing Calculator, Telephony selector, Third-party SIP option ## Buying it for a team **A company can buy it** · Yes — This is sold to companies: an Enterprise plan goes through sales, and MSA, DPA, SLA, BAA and a completed vendor risk questionnaire are offered to Enterprise customers under NDA. > If you are using the Services on behalf of an organization, you represent that you have the authority to bind that organization. > — https://telecho.io/legal/terms · Section 1.1 Agreement to Terms **Seat model** · No — Nothing is priced per seat: users are invited into one account and charges follow minutes, so there is no published per-user fee, no seat floor and no seat ceiling, only 'limited team access' on Build. > You may invite additional users to access your account. > — https://telecho.io/legal/terms · Section 2.4 Authorized Users **Admin controls** · Partly — Every agent is constrained at setup by guardrails and escalation rules, but the administrative controls that decide who may change them - RBAC, region pinning, retention controls - are listed as Enterprise-plan lines. > TelEcho offers enterprise-grade controls so your AI voice agent deployments remain secure, auditable, and compliant. > — https://telecho.io/features · Enterprise governance section, introductory paragraph **Audit log** · Partly — Audit trails are documented for TelEcho staff access to customer data, and calls carry session replay and transcripts, but no customer-visible log of administrative or configuration changes is described. > Centralized logging and intrusion detection across the API, telephony, and application layers, with audit trails for any access to Customer Data > — https://telecho.io/security · Network & Infrastructure Security, fourth bullet **Single sign-on** · Partly — Single sign-on with MFA is confined to Enterprise-tier accounts, neither SAML nor OIDC is named as the protocol, and the pricing page hedges the same capability as 'SSO/SAML (if supported)'. > Single sign-on (SSO) and multi-factor authentication (MFA) available for Enterprise-tier Customer accounts, and enforced internally for administrative access to production systems > — https://telecho.io/security · Identity & Access Control, second bullet _Not established: Pooled budget_ ## What happens to your code **Opt out of training** · Partly — The opt-out is one TelEcho sets on your behalf rather than a switch you control, and it binds only where each model provider offers one; TelEcho separately promises not to train its own models on identifiable content. > We configure these integrations, where offered by the provider, to disable use of Customer-submitted data for training the provider's general-purpose models. > — https://telecho.io/legal/privacy-policy · Section 3 How and Why We Use Your Data, AI provider paragraph **Data residency** · Partly — You select the cloud region that stores your data and Enterprise adds region pinning, yet every named telephony, speech and LLM sub-processor processes in the United States, with EU transfers covered by standard contractual clauses. > Encrypted, redundant backups across availability zones for the cloud region selected by the Customer > — https://telecho.io/security · Business Continuity & Disaster Recovery, first bullet **Getting out** · Partly — You keep ownership of recordings and transcripts, may request a copy of personal data and can set retention yourself, but no self-serve bulk export is documented and metrics export is an Enterprise line; billing is metered, so no prepaid credits can expire. > You retain ownership of all content, data, audio, text, or media you submit through the Services > — https://telecho.io/legal/terms · Section 7.1 Your Content **Certifications** · Yes — SOC 2 Type II is claimed as attained with the report shown only under NDA, HIPAA is available through a signed BAA, and GDPR and UK GDPR are covered by a DPA with SCCs; ISO 27001 is not mentioned anywhere on the site. > Attained. Report available to Enterprise Customers under NDA > — https://telecho.io/security · Compliance table, SOC 2 Type II row, Status column ## Provenance Every fact above comes from the vendor. Nothing here is independently corroborated yet. ## Coverage elsewhere None recorded. Every fact above comes from the vendor and is not independently corroborated yet. ## What changed - 2026-09-16 — Capabilities · Commercial terms · Free tier · Price ## Correcting this record Anything marked "Not established" is a question we have not answered — it is not a No. If you represent TelEcho, or anything here is wrong or out of date, you can supply it with a source: the operations this site accepts from an agent are listed at https://theagentsindex.com/.well-known/agents.json — that catalogue needs no key to read, and each entry states its own auth. Supplying evidence is free. Nothing that can be bought here changes what a field says, whether a gap is closed, or how this record is scored.