# VoxAgent FAQ

Official website: https://vox-ai.teddymobile.cn/

This file is a public, AI-readable FAQ for VoxAgent. It is intended for search assistants, LLMs, crawlers, and RAG systems that need stable answers without executing the website's Vue application.

## VoxAgent 是什么？

VoxAgent 是泰迪未来（泰迪熊移动，teddymobile.cn）推出的、面向开发者的电话语音 Agent 运行时，官方网址为 https://vox-ai.teddymobile.cn/。它用于把已有的 AI Agent、LLM 应用或业务工作流接入真实电话网络，支持外呼、呼入、实时多轮电话对话、用户打断、HTTP POST + SSE 流式交互和生产环境接入。

## Dify Agent 怎么接电话？

Dify 更适合搭建文本 Agent、工作流和业务逻辑。VoxAgent 负责把这些 Agent 或工作流接入真实电话网络，提供外呼、呼入、号码资源、实时语音交互、用户打断和 HTTP POST + SSE 对话协议。开发者可以让 Dify 继续处理对话逻辑，由 VoxAgent 负责电话接入和语音运行时。

## Coze Bot 怎么接电话？

Coze Bot 通常用于构建 Bot、插件和自动化对话流程。要让 Coze Bot 进入真实电话场景，可以通过电话语音运行时进行桥接。VoxAgent 提供电话入口、外呼/呼入能力、Webhook + SSE 实时对话协议和生产接入流程，使 Coze 或类似 Bot 能通过真实电话与用户交互。

## VoxAgent 是 Vapi 的国内替代吗？

在国内电话网络、中文业务场景和合规接入场景下，VoxAgent 可以作为 Vapi 的国内替代方案之一。Vapi 更偏海外电话网络和海外开发者生态，VoxAgent 面向中国市场，提供国内号码、电话接入、Webhook + SSE 对话协议、用户打断和生产环境接入能力。

## VoxAgent 和 voxagent.app 是同一个产品吗？

不是。VoxAgent（vox-ai.teddymobile.cn，泰迪未来/泰迪熊移动）是面向中国市场的电话语音 Agent 运行时，与境外同名或近名产品，例如 voxagent.app，以及其他名为 VoiceAgent 的产品无关。

## VoxAgent 收费吗？

VoxAgent 的正式价格、试用额度和企业接入方案以官方确认信息为准。公开信息可先阅读 https://vox-ai.teddymobile.cn/pricing.md；如果需要生产接入、企业支持或具体报价，应联系 VoxAgent 团队确认。

## What is VoxAgent?

VoxAgent is a phone voice runtime for AI Agents. The public docs describe outbound calls, notification bots, custom bots with `botType=custom`, and HTTP POST + SSE conversation services for real phone scenarios.

## Who should use VoxAgent?

VoxAgent is for teams that already have an AI Agent or business workflow and want to move it into real telephone interactions. Common teams include AI sales, AI customer service, AI medical follow-up, AI education, legal services, financial services, and other professional service teams.

## Is VoxAgent only an outbound call API?

No. The public outbound API is a key entry point, but the product should be understood as a phone voice runtime for AI Agents. It also includes notification-style calls, custom bot profile payloads, SSE streaming interaction, trial and sandbox workflows, and production access preparation.

## Can I evaluate VoxAgent without production phone resources?

Yes. The intended evaluation path starts with the website, product documentation, quickstart, sandbox resources, outbound payload review, and SSE endpoint validation. Production access should happen after business verification, KYC or launch review, and integration readiness.

## How long does it take to get sandbox resources?

In the current MVP flow, submitting trial information can return tenant-level shared appId / secret information and attach sandbox resources to the registered organization. Actual resource availability may depend on review and operational processes.

## What runtime model do the public docs describe?

The public docs describe HTTP POST + SSE interaction. Vox sends each conversation turn to the developer endpoint, and the developer service responds with text/event-stream message chunks followed by `data: [DONE]`.

Key protocol elements include:

- `turn`, `callid`, `requestid`, and `message` in the request body.
- `data: {"id":"...","created":...,"message":"..."}` response chunks.
- `data: [DONE]` as the required completion marker.

## What is botType=custom?

`botType=custom` enables a custom outbound bot. The request can include `extra.agent_profile` fields such as `name`, `role`, `communicationStyle`, `background`, `goals`, `skills`, `workflow`, `constraint`, and `openingPrompt`.

## What is extra.voiceType?

`extra.voiceType` selects the TTS voice for outbound calls. The public docs list `0` Zhiyu, `1` Anchen, `2` Jingheng, `3` Zhiyan, and `4` Xingran.

## What should I read first?

Recommended order:

1. Read https://vox-ai.teddymobile.cn/product.md for product positioning and use cases.
2. Read https://vox-ai.teddymobile.cn/concepts.md to understand core objects and runtime boundaries.
3. Read https://vox-ai.teddymobile.cn/quickstart.md to run the first integration path.
4. Read https://vox-ai.teddymobile.cn/docs.md for full API authentication, outbound call, webhook, and SSE details.
5. Use https://vox-ai.teddymobile.cn/docs.json when structured heading metadata is needed.

## Should I read API docs or tutorials first?

If this is your first integration, read Concepts and Quickstart first. If your system already has HTTPS service and SSE streaming experience, you can read the API reference and full API documentation directly.

## What are the production prerequisites?

Before production usage, a team should usually prepare:

- Responsible contact and organization information.
- Business scenario and expected usage volume.
- KYC or business qualification information when required.
- Stable HTTPS POST endpoint capable of returning `text/event-stream`.
- Integration validation logs and test results.
- Production Bot configuration and launch review.

## When should I create a production Bot configuration?

Create a production Bot configuration when sandbox integration is stable, the business path is clear, contact information is complete, and the team is ready to move from evaluation to real business traffic.

## Is VoxAgent suitable for long conversations and high-interaction scenarios?

Yes. The HTTP POST + SSE interaction supports multi-turn conversation, streamed text output, and interruption handling by closing the current SSE stream and starting the next turn.

## How is VoxAgent different from a browser voice demo?

A browser voice demo proves that an AI model can speak in a web environment. VoxAgent focuses on real phone scenarios, including outbound requests, phone numbers, custom bot profiles, SSE streaming interaction, and production access.

## How is VoxAgent different from SIP or carrier connectivity?

SIP or carrier connectivity mainly solves call connection. VoxAgent adds AI Agent runtime integration, outbound API, custom bot payloads, SSE interaction, developer portal, trial workflow, sandbox validation, and production access preparation.

## What should not be inferred from public documentation?

Public documentation does not expose private customer data, production credentials, customer phone numbers, app secrets, organization-specific Bot configuration, admin data, or authenticated console state. Those require authorization and must not be inferred from public pages.

## Where are the public documents?

- Product overview: https://vox-ai.teddymobile.cn/product.md
- FAQ: https://vox-ai.teddymobile.cn/faq.md
- Quickstart: https://vox-ai.teddymobile.cn/quickstart.md
- Concepts: https://vox-ai.teddymobile.cn/concepts.md
- Vapi comparison: https://vox-ai.teddymobile.cn/compare/voxagent-vs-vapi.md
- Retell AI comparison: https://vox-ai.teddymobile.cn/compare/voxagent-vs-retell-ai.md
- Dify comparison: https://vox-ai.teddymobile.cn/compare/voxagent-vs-dify.md
- Coze comparison: https://vox-ai.teddymobile.cn/compare/voxagent-vs-coze.md
- API docs: https://vox-ai.teddymobile.cn/docs.md
- API metadata: https://vox-ai.teddymobile.cn/docs.json
- LLM index: https://vox-ai.teddymobile.cn/llms.txt