从 Vapi 迁移 Voice
盘点助手、模型与语音设置、自定义工具、转接呼叫行为以及当前的电话连接。确定项目需要更换的是运营商连接、助手运行时还是两者都更换。
梳理呼叫行为
如果仅更换电话连接，保留助手在其运行时中的对话行为，并验证新的 SIP 连接。如果替换运行时，则将工具权限、打断行为和已确认的业务结果作为单独项目来复现。
当集成的 SIP 和媒体需求匹配时，两者可以扮演互补角色。Bird 提供电话连接，助手运行时管理对话。在依赖该方案之前，验证双向呼叫、主叫身份、音频和交接。
准备替换连接
创建 Bird 工作区、中继和呼叫身份，用于受控测试。启用目的地，并在客户端中配置认证和媒体设置。在评估新路径期间保留现有号码路由不变。
号码携转不会迁移其背后的应用程序。确认每个国家和号码类型的可携性及预期的切换流程。在依赖号码迁移之前，先准备好新的呼入路由。
测试完整的客户旅程
使用你控制的号码，验证以下结果：
- 目标客户端完成认证，测试目的地振铃。
- 双向音频正常，通话正常结束。
- 提示音和按键选择到达预期分支。
- 业务工具能区分成功、失败和不确定的结果。
- 通话记录和事件与应用程序中的结果关联。
- 录音或转录（如需要）生成预期的证据。
除成功路径外，还要测试被拒绝的呼叫和业务依赖不可用的情况。仅凭请求被接受并不能证明替换方案可用。
有计划地迁移流量
确认容量、访问权限和最终号码路由。在评估初始流量期间保留恢复先前路由的能力。保存历史供应商记录，并维护与应用程序中客户或任务身份的映射关系。
在通话结束后核对计费成本。比较新工作流时，将所有相关通话段以及独立的语音、录音或模型服务费用一并纳入。
配合编程代理使用
将此提示词粘贴到你的编程代理中，连同你要迁移的集成。编号流程从盘点开始，并明确标注生产环境变更。
代码示例
Help me evaluate a Voice migration from Vapi to Bird.
1. Read https://bird.com/docs/guides/voice/migrate/vapi.md. Use the .md alternatives of linked Bird guides for the steps below.
2. Check for a connected Bird MCP server or an installed, signed-in Bird CLI. Use whichever is available and discover its tools or command help. If neither is available, follow https://bird.com/docs/ai/set-up-your-agent.md. Do not invent operation names or install a second integration.
3. Perform a read-only inventory of my current call sites, numbers, SIP configuration, call-control instructions, event handlers, recordings, speech services and business tools. Identify secrets without printing them. Show the dependencies that stay with Vapi and the ones that need replacement.
4. Read https://bird.com/docs/guides/voice/sip-trunks.md, https://bird.com/docs/guides/voice/placing-calls.md and https://bird.com/docs/guides/voice/receiving-calls.md. Prepare the replacement connection and caller-identity requirements. Use https://bird.com/docs/guides/voice/call-sequences.md for defined menus and https://bird.com/docs/ai/voice-conversations.md for a conversational runtime. Verify each operation against the connected surface before proposing an executable step.
5. Prepare a test of one complete journey: setup, audio in both directions, keypad input, unanswered and failure paths, handoff where needed, and business-tool results. Show the exact target, configuration and expected cost before placing a call or recording audio; wait for my approval. Do not buy numbers, submit a port, change production routing or stop the existing provider without my explicit approval.
6. Use https://bird.com/docs/guides/voice/events.md and https://bird.com/docs/guides/voice/call-log.md to reconcile the outcome. Keep missing evidence and uncertain results visible. A spoken confirmation is not proof that a business action succeeded.
7. Return the integration differences, test evidence, unresolved requirements and rollback plan. Keep the current service running until I approve cutover. If a number port needs support, inspect the available support command or tool, prepare the exact request and ask for approval before submitting it. Return the ticket reference if authorized; a ticket does not schedule or complete a port.