[{"data":1,"prerenderedAt":984},["ShallowReactive",2],{"navigation":3,"search":38,"guides":268},[4,9,13,18,23,28,33],{"title":5,"path":6,"stem":7,"icon":8},"文档中心","\u002Fdocs","1.docs\u002Findex","i-lucide-book-open",{"title":10,"path":11,"stem":12},"翎影产品概览","\u002Fdocs\u002Foverview","1.docs\u002F1.overview",{"title":14,"path":15,"stem":16,"icon":17},"渠道接入准备","\u002Fdocs\u002Fchannel-setup","1.docs\u002F2.channel-setup","i-lucide-plug",{"title":19,"path":20,"stem":21,"icon":22},"AI 翻译","\u002Fdocs\u002Fai-translation","1.docs\u002F3.ai-translation","i-lucide-languages",{"title":24,"path":25,"stem":26,"icon":27},"AI 回复建议","\u002Fdocs\u002Fai-reply","1.docs\u002F4.ai-reply","i-lucide-message-square-reply",{"title":29,"path":30,"stem":31,"icon":32},"AI 托管规则","\u002Fdocs\u002Fai-agent-rules","1.docs\u002F5.ai-agent-rules","i-lucide-shield-check",{"title":34,"path":35,"stem":36,"icon":37},"常见问题","\u002Fdocs\u002Ffaq","1.docs\u002F6.faq","i-lucide-circle-help",[39,43,47,50,54,60,65,70,75,80,84,88,93,98,103,108,113,117,121,126,131,136,141,144,148,153,158,163,168,173,176,180,185,190,195,200,205,210,215,220,225,230,235,240,245,249,253,258,263],{"id":11,"title":10,"titles":40,"content":41,"level":42},[],"翎影 AI 跨境智能沟通平台的第一版文档占位。",1,{"id":44,"title":10,"titles":45,"content":46,"level":42},"\u002Fdocs\u002Foverview#翎影产品概览",[],"LingYio 规划为面向跨境业务团队的 AI 智能沟通工作台。 第一阶段文档重点应覆盖渠道接入、翻译行为、AI 回复审核、AI 托管规则，以及未来 API 集成方式。",{"id":15,"title":14,"titles":48,"content":49,"level":42},[],"在使用翎影处理 WhatsApp、Facebook 等跨境客户消息前，团队需要准备的账号、权限和协作信息。",{"id":51,"title":14,"titles":52,"content":53,"level":42},"\u002Fdocs\u002Fchannel-setup#渠道接入准备",[],"在正式使用翎影处理跨境客户消息前，建议先完成渠道、账号和团队权限的基础梳理。这样可以减少后续测试和上线时的沟通成本。",{"id":55,"title":56,"titles":57,"content":58,"level":59},"\u002Fdocs\u002Fchannel-setup#适用渠道","适用渠道",[14],"当前优先支持 WhatsApp 和 Facebook 客户沟通场景。后续将根据产品规划陆续开放 Instagram、TikTok 等更多主流软件和社交渠道。 不同渠道的接入方式可能略有差异，但整体思路是一致的：在客户端打开对应软件的网页版或授权页面，通过扫码、邮箱登录或账号授权完成登录；登录完成后，翎影会根据客户发送的消息内容提供翻译、分析和回复辅助。",2,{"id":61,"title":62,"titles":63,"content":64,"level":59},"\u002Fdocs\u002Fchannel-setup#上线前信息","上线前信息",[14],"建议提前整理以下信息： 企业或团队名称。主要客户来源地区。常用沟通语言。需要接入的渠道类型。对应渠道的登录方式，例如扫码登录、邮箱登录或账号授权。是否需要在客户端保持网页版登录状态。客服、销售、管理员等团队角色。是否需要 AI 回复建议。是否允许部分低风险问题进入 AI 托管辅助。",{"id":66,"title":67,"titles":68,"content":69,"level":59},"\u002Fdocs\u002Fchannel-setup#权限建议","权限建议",[14],"渠道账号应由企业或业务负责人统一管理，不建议使用个人临时账号作为长期生产入口。团队成员只获得完成岗位所需的权限，涉及自动回复、托管规则和敏感会话的配置应由管理员确认。",{"id":71,"title":72,"titles":73,"content":74,"level":59},"\u002Fdocs\u002Fchannel-setup#测试流程","测试流程",[14],"上线前建议使用内部测试联系人完成一次完整链路验证： 在客户端打开对应渠道的网页版或授权页面。通过扫码、邮箱或账号授权完成登录。使用内部测试联系人发送外语消息。翎影展示原文、译文、客户分析和回复建议。成员确认后发送回复，或验证后台托管规则是否按预期自动回复。管理员检查记录、权限和托管边界。",{"id":76,"title":77,"titles":78,"content":79,"level":59},"\u002Fdocs\u002Fchannel-setup#注意事项","注意事项",[14],"不同渠道可能存在各自的平台规则、授权要求和消息频率限制。正式上线前，应以实际渠道政策和产品后台提示为准。",{"id":20,"title":81,"titles":82,"content":83,"level":42},"AI 翻译工作方式",[],"了解翎影如何在跨境客户沟通中展示原文、译文、上下文信息和人工确认流程。",{"id":85,"title":81,"titles":86,"content":87,"level":42},"\u002Fdocs\u002Fai-translation#ai-翻译工作方式",[],"AI 翻译是翎影的基础能力之一，但它不是孤立的翻译框。它需要服务于真实客户对话，帮助团队理解客户诉求、减少误解，并让后续回复更准确。",{"id":89,"title":90,"titles":91,"content":92,"level":59},"\u002Fdocs\u002Fai-translation#原文与译文","原文与译文",[81],"跨语言消息应同时保留原文和译文。原文用于复核客户表达，译文用于快速理解。对于金额、地址、型号、时间、合同条款等敏感信息，团队应优先核对原文。",{"id":94,"title":95,"titles":96,"content":97,"level":59},"\u002Fdocs\u002Fai-translation#上下文理解","上下文理解",[81],"客户消息往往依赖前文。翎影的翻译说明应围绕完整会话理解，而不是只翻译单句。遇到省略、指代、口语表达或多轮议价时，上下文会直接影响译文质量。",{"id":99,"title":100,"titles":101,"content":102,"level":59},"\u002Fdocs\u002Fai-translation#业务术语","业务术语",[81],"建议团队维护常见产品名、行业词、规格单位和品牌词。正式产品阶段可以把这些内容沉淀为术语表，减少同一词汇在不同成员之间被翻译成不同表达。",{"id":104,"title":105,"titles":106,"content":107,"level":59},"\u002Fdocs\u002Fai-translation#人工复核","人工复核",[81],"在以下场景中，译文不应直接作为最终判断： 客户提出价格、退款、合同和售后争议。消息中包含地址、账号、发票或其他敏感信息。客户语气强烈，可能存在投诉风险。对话涉及法律、医疗、金融等高风险内容。",{"id":109,"title":110,"titles":111,"content":112,"level":59},"\u002Fdocs\u002Fai-translation#使用建议","使用建议",[81],"把 AI 翻译作为团队沟通效率工具，而不是替代业务判断。对于重要客户和关键交易节点，人工复核仍然是必要环节。",{"id":25,"title":114,"titles":115,"content":116,"level":42},"AI 回复建议流程",[],"使用翎影 AI 回复建议时，如何结合上下文、团队话术和人工审核建立稳定协作流程。",{"id":118,"title":114,"titles":119,"content":120,"level":42},"\u002Fdocs\u002Fai-reply#ai-回复建议流程",[],"AI 回复建议用于帮助业务人员更快起草回复，并保持跨语言表达的一致性。它适合辅助客服、销售和运营团队处理重复问题、产品咨询和初步跟进。",{"id":122,"title":123,"titles":124,"content":125,"level":59},"\u002Fdocs\u002Fai-reply#生成依据","生成依据",[114],"回复建议应结合以下信息： 当前客户消息。上下文聊天记录。客户可能意图。当前沟通阶段。团队已确认的话术和政策。是否需要人工进一步确认。",{"id":127,"title":128,"titles":129,"content":130,"level":59},"\u002Fdocs\u002Fai-reply#回复流程","回复流程",[114],"AI 回复可以按团队风险偏好分为人工确认和自动托管两种模式。默认建议先采用“AI 分析并起草，人工确认后发送”的流程： AI 根据上下文生成候选回复。成员检查事实、价格、语气和承诺边界。必要时调整为更符合品牌语气的表达。点击一键发送，把确认后的回复发送给客户。将高频有效回复沉淀为团队话术。 当团队已经沉淀清晰规则后，可以在后台开启托管配置，让符合规则的会话自动回复。自动回复应始终保留生效时间、上下文数量、风险检测和人工接管等控制项。",{"id":132,"title":133,"titles":134,"content":135,"level":59},"\u002Fdocs\u002Fai-reply#不建议自动发送的内容","不建议自动发送的内容",[114],"以下内容应由人工审核： 价格、折扣、退款和赔偿。交期、库存、合同和发票。投诉、争议、差评和升级工单。涉及个人信息或敏感资料的沟通。",{"id":137,"title":138,"titles":139,"content":140,"level":59},"\u002Fdocs\u002Fai-reply#团队协作","团队协作",[114],"管理员可以把常见问题、禁用表达、产品卖点和售后边界整理成内部规范。AI 回复建议越接近团队真实业务规则，成员越容易把它作为日常工作流的一部分。",{"id":30,"title":29,"titles":142,"content":143,"level":42},[],"设计翎影 AI 托管辅助前，需要明确的自动处理范围、人工接管条件和风险边界。",{"id":145,"title":29,"titles":146,"content":147,"level":42},"\u002Fdocs\u002Fai-agent-rules#ai-托管规则",[],"AI 托管辅助适合处理低风险、高重复、规则清晰的沟通场景。它的目标是提高响应速度，而不是绕过人工负责机制。",{"id":149,"title":150,"titles":151,"content":152,"level":59},"\u002Fdocs\u002Fai-agent-rules#适合托管的场景","适合托管的场景",[29],"以下场景可以优先评估托管辅助： 营业时间、联系方式、基础产品介绍。常见物流状态说明。标准售前问题收集。售后材料初步引导。需要转人工前的信息补全。",{"id":154,"title":155,"titles":156,"content":157,"level":59},"\u002Fdocs\u002Fai-agent-rules#必须人工接管的场景","必须人工接管的场景",[29],"以下场景建议直接进入人工处理： 客户明确投诉或情绪激烈。涉及价格承诺、退款、赔偿和合同。客户要求特殊政策或例外处理。AI 无法判断客户意图。对话包含敏感个人信息。",{"id":159,"title":160,"titles":161,"content":162,"level":59},"\u002Fdocs\u002Fai-agent-rules#规则配置","规则配置",[29],"AI 托管规则需要在商户后台配置。管理员可以按渠道、语言策略、回复模式、生效开始时间、生效结束时间、上下文数量、风险检测和人工接管时间等条件控制自动回复范围。 托管规则建议从保守开始： 只开放低风险问题。明确禁用自动承诺。设置人工接管关键词。保留原文、译文和 AI 决策记录。定期复盘错误案例并调整规则。 当会话超出规则范围，或成员需要直接处理客户时，可以手动接管当前会话。手动接管后，AI 托管应停止自动发送，把后续判断交还给人工。",{"id":164,"title":165,"titles":166,"content":167,"level":59},"\u002Fdocs\u002Fai-agent-rules#上线观察","上线观察",[29],"启用托管辅助后，团队应持续观察回复准确性、客户满意度、人工接管比例和异常会话。早期不建议一次性覆盖所有客户场景。",{"id":169,"title":170,"titles":171,"content":172,"level":59},"\u002Fdocs\u002Fai-agent-rules#责任边界","责任边界",[29],"AI 托管辅助应被设计为团队工作流的一部分。最终业务承诺、客户关系和风险处理仍需要企业团队负责。",{"id":35,"title":34,"titles":174,"content":175,"level":42},[],"围绕翎影产品定位、AI 翻译、AI 回复建议、AI 托管辅助、渠道接入和上线阶段的常见问题。",{"id":177,"title":34,"titles":178,"content":179,"level":42},"\u002Fdocs\u002Ffaq#常见问题",[],"本页整理官网第一版阶段常见的产品问题。后续当服务政策、正式法律文本和真实产品截图确认后，应继续替换为正式答案。",{"id":181,"title":182,"titles":183,"content":184,"level":59},"\u002Fdocs\u002Ffaq#翎影只是翻译工具吗","翎影只是翻译工具吗？",[34],"不是。翻译是翎影的基础能力之一，但产品定位是 AI 驱动的跨境智能沟通与客户服务平台。 翎影的长期方向包括多渠道消息处理、AI 翻译、AI 回复建议、客户意图分析、AI 托管辅助和 AI 工具中心，帮助团队围绕真实客户会话建立完整工作流。",{"id":186,"title":187,"titles":188,"content":189,"level":59},"\u002Fdocs\u002Ffaq#当前重点覆盖哪些沟通渠道","当前重点覆盖哪些沟通渠道？",[34],"当前优先支持 WhatsApp 和 Facebook 客户沟通场景。后续会根据产品节奏陆续开放 Instagram、TikTok 等更多主流软件和社交渠道。 官网表达应区分“当前支持”和“后续规划”，避免把尚未开放的渠道写成已经可用。",{"id":191,"title":192,"titles":193,"content":194,"level":59},"\u002Fdocs\u002Ffaq#各渠道如何接入","各渠道如何接入？",[34],"通常是在客户端打开对应软件的网页版或授权页面，通过扫码、邮箱登录或账号授权完成登录。登录完成后，翎影会围绕客户发送的消息内容提供翻译、客户分析、回复建议和托管辅助。 不同渠道可能有各自的平台规则、授权方式和登录有效期，正式使用时以产品后台提示为准。",{"id":196,"title":197,"titles":198,"content":199,"level":59},"\u002Fdocs\u002Ffaq#ai-翻译会自动发送给客户吗","AI 翻译会自动发送给客户吗？",[34],"AI 翻译的主要作用是帮助团队理解客户原文。是否把翻译后的内容用于回复，需要由团队根据业务场景判断。 涉及金额、合同、退款、地址、账号和投诉等敏感内容时，应保留人工复核。",{"id":201,"title":202,"titles":203,"content":204,"level":59},"\u002Fdocs\u002Ffaq#ai-回复建议可以直接自动发送吗","AI 回复建议可以直接自动发送吗？",[34],"AI 回复支持先生成客户分析和回复草稿，由客服或销售人员确认后一键发送。对于低风险、规则明确的常见问题，也可以在商户后台开启托管配置，让符合条件的会话自动回复。 涉及价格承诺、退款、赔偿、合同、投诉、隐私信息或高价值客户关系时，建议保留人工确认。",{"id":206,"title":207,"titles":208,"content":209,"level":59},"\u002Fdocs\u002Ffaq#ai-次数和-ai-能量如何消耗","AI 次数和 AI 能量如何消耗？",[34],"AI 次数主要用于文本类 AI 能力，例如 AI 翻译、自动回复、建议回复、客户分析和 AI 客服。不同套餐会配置不同的 AI 次数额度，部分高阶套餐可以配置为不限次数。 AI 能量主要用于工具类 AI 能力，例如图片变清晰、场景合成、去水印、生成海报、智能抠图、图片翻译、图片压缩和图片裁剪等。这类能力通常会调用第三方模型或接口，例如通义万相、通义千问、豆包、即梦等，具体消耗会根据后台配置和实际模型成本而变化。 官网当前展示的是基础套餐权益。后续如果某些工具涉及大额模型消耗，可能会按功能、额度或实际消耗另行计费。",{"id":211,"title":212,"titles":213,"content":214,"level":59},"\u002Fdocs\u002Ffaq#什么情况下-ai-托管应该转人工","什么情况下 AI 托管应该转人工？",[34],"AI 托管规则需要在商户后台配置。管理员可以设置平台、语言策略、回复模式、生效开始时间、生效结束时间、上下文数量、风险检测和人工接管时间等条件。 以下场景建议人工接管： 客户明确投诉或表达强烈不满。客户提出退款、赔偿、折扣或特殊政策。对话涉及合同、发票、账号或隐私信息。AI 无法判断客户真实意图。客户连续追问但问题没有解决。客户明确要求人工协助。 转人工不是失败，而是 AI 托管辅助的安全机制。 成员也可以在需要处理客户时手动接管会话。手动接管后，系统应停止自动发送，把后续沟通交给人工处理。",{"id":216,"title":217,"titles":218,"content":219,"level":59},"\u002Fdocs\u002Ffaq#团队上线前需要准备什么","团队上线前需要准备什么？",[34],"建议先准备： 需要接入的渠道。常用沟通语言。高频客户问题。产品术语和标准表达。需要人工审核的敏感场景。允许 AI 辅助处理的低风险问题。 准备越充分，AI 翻译、回复建议和托管辅助越容易稳定融入团队流程。",{"id":221,"title":222,"titles":223,"content":224,"level":59},"\u002Fdocs\u002Ffaq#当前价格页展示的是哪些套餐","当前价格页展示的是哪些套餐？",[34],"当前价格页已经按后台套餐截图整理为免费版、VIP PLUS版、VIP PRO版和 VIP Business版。PLUS 和 PRO 截图中的测试支付价格不对外展示，官网按 99 元和 299 元展示。",{"id":226,"title":227,"titles":228,"content":229,"level":59},"\u002Fdocs\u002Ffaq#官网当前图片为什么是白底占位图","官网当前图片为什么是白底占位图？",[34],"当前产品截图路径已经接入页面，但真实截图还未统一整理。先使用白底占位图是为了让页面结构、尺寸和内容流转先稳定下来。 后续只要按现有路径替换图片，就可以快速完成真实资产接入。",{"id":231,"title":232,"titles":233,"content":234,"level":59},"\u002Fdocs\u002Ffaq#登录和注册页面现在可以使用吗","登录和注册页面现在可以使用吗？",[34],"当前登录和注册页仍是官网阶段占位表单，尚未接入真实产品系统。正式上线前需要确认是否跳转真实后台、注册流程或预约开通页面。",{"id":236,"title":237,"titles":238,"content":239,"level":59},"\u002Fdocs\u002Ffaq#服务条款隐私政策退款和发票信息在哪里","服务条款、隐私政策、退款和发票信息在哪里？",[34],"官网会先保留基础占位说明，用于表达服务边界、数据保护、退款处理和发票开具的基本方向。正式上线前，需要替换为经过业务和法务确认的正式文本，并补齐公司主体信息。",{"id":241,"title":242,"titles":243,"content":244,"level":59},"\u002Fdocs\u002Ffaq#官网内容后续如何维护","官网内容后续如何维护？",[34],"固定营销内容主要放在 app\u002Fconfig\u002F，博客、文档和指南使用 Nuxt Content 管理。新增长文章、帮助文档和 SEO 内容时，优先放入 content\u002F 目录。 内容维护应保持中文、真实、可验证，不要批量生成低质量 SEO 文章。",{"id":6,"title":246,"titles":247,"content":248,"level":42},"翎影文档中心",[],"面向跨境业务团队的翎影产品文档入口，帮助团队理解渠道接入、AI 翻译、回复建议和托管辅助的基础流程。",{"id":250,"title":246,"titles":251,"content":252,"level":42},"\u002Fdocs#翎影文档中心",[],"翎影是一套面向跨境业务团队的 AI 智能沟通平台，第一阶段重点围绕多语言客户消息处理、上下文翻译、AI 回复建议、对话分析和 AI 托管辅助建立稳定的产品说明。 文档中心用于沉淀产品使用流程、团队协作规范和上线前配置要点。当前内容会随着真实产品后台、渠道接入方式和套餐规则逐步完善。",{"id":254,"title":255,"titles":256,"content":257,"level":59},"\u002Fdocs#推荐阅读路径","推荐阅读路径",[246],"先阅读产品概览，理解翎影解决的问题和核心模块。再阅读渠道接入准备，梳理 WhatsApp、Messenger 和团队账号的上线前条件。接着阅读AI 翻译工作方式，确认翻译、原文和上下文的展示边界。然后阅读AI 回复建议流程，建立人工审核和统一话术机制。最后阅读AI 托管规则，决定哪些场景允许自动辅助，哪些场景必须人工接管。",{"id":259,"title":260,"titles":261,"content":262,"level":59},"\u002Fdocs#文档范围","文档范围",[246],"当前文档面向官网第一版，不替代正式产品后台的操作手册。涉及渠道授权、账号权限、消息发送限制和计费额度的内容，后续需要根据真实产品系统继续细化。",{"id":264,"title":265,"titles":266,"content":267,"level":59},"\u002Fdocs#内容维护原则","内容维护原则",[246],"文档内容应保持中文、可维护、可验证。不要加入无法确认的功能承诺，不要把内部开发计划写成已经上线的产品能力。",[269,423,551,684],{"id":270,"title":271,"badge":272,"body":274,"description":413,"extension":414,"meta":415,"navigation":416,"path":417,"readTime":418,"seo":419,"stem":421,"__hash__":422},"guides\u002F4.guides\u002F1.whatsapp-ai-translation-workflow.md","WhatsApp AI 翻译工作流上线清单",{"label":273},"翻译",{"type":275,"value":276,"toc":405},"minimark",[277,281,285,290,293,306,309,313,316,330,333,337,340,354,357,361,364,378,381,385,388,402],[278,279,271],"h1",{"id":280},"whatsapp-ai-翻译工作流上线清单",[282,283,284],"p",{},"AI 翻译上线前，最重要的不是先追求“全自动”，而是让团队在真实客户沟通里稳定理解信息、减少切换、保留上下文。",[286,287,289],"h2",{"id":288},"_1-先确定会话场景","1. 先确定会话场景",[282,291,292],{},"建议先从高频且风险较低的场景开始：",[294,295,296,300,303],"ul",{},[297,298,299],"li",{},"售前询盘：价格、规格、交期、起订量。",[297,301,302],{},"基础客服：物流状态、售后流程、使用说明。",[297,304,305],{},"信息确认：客户语言、目标市场、采购数量、联系方式。",[282,307,308],{},"暂时不要把投诉、合同、付款争议等高风险内容直接交给自动流程处理。",[286,310,312],{"id":311},"_2-准备业务术语","2. 准备业务术语",[282,314,315],{},"翻译质量会受产品词、行业词、缩写和服务规则影响。上线前建议整理：",[294,317,318,321,324,327],{},[297,319,320],{},"产品名称和型号。",[297,322,323],{},"常见规格、单位和包装方式。",[297,325,326],{},"物流、付款、售后相关表达。",[297,328,329],{},"不希望被翻译或改写的品牌词。",[282,331,332],{},"这些内容后续可以进入翎影的术语、规则或知识配置。",[286,334,336],{"id":335},"_3-保留人工复核","3. 保留人工复核",[282,338,339],{},"第一阶段建议采用“AI 翻译 + 人工确认”的方式：",[294,341,342,345,348,351],{},[297,343,344],{},"客户原文必须可见。",[297,346,347],{},"翻译结果必须可见。",[297,349,350],{},"人工回复前可以对照上下文。",[297,352,353],{},"不清楚的表达标记给业务负责人确认。",[282,355,356],{},"这样可以让团队建立信任，也能积累真实问题。",[286,358,360],{"id":359},"_4-记录需要优化的样本","4. 记录需要优化的样本",[282,362,363],{},"上线初期不要只看是否能翻译，还要记录：",[294,365,366,369,372,375],{},[297,367,368],{},"哪些词经常翻错。",[297,370,371],{},"哪些句子容易丢失语气。",[297,373,374],{},"哪些问题需要结合上下文才能理解。",[297,376,377],{},"哪些客户表达经常触发误判。",[282,379,380],{},"这些样本是后续优化 AI 回复、客户分析和 AI 托管 的基础。",[286,382,384],{"id":383},"_5-下一步扩展","5. 下一步扩展",[282,386,387],{},"当翻译流程稳定后，可以逐步加入：",[294,389,390,393,396,399],{},[297,391,392],{},"AI 回复建议。",[297,394,395],{},"客户意图分析。",[297,397,398],{},"会话摘要。",[297,400,401],{},"低风险问题的 AI 托管辅助。",[282,403,404],{},"翎影的目标不是只做翻译，而是围绕跨境客户沟通建立一套可逐步扩展的 AI 工作流。",{"title":406,"searchDepth":59,"depth":59,"links":407},"",[408,409,410,411,412],{"id":288,"depth":59,"text":289},{"id":311,"depth":59,"text":312},{"id":335,"depth":59,"text":336},{"id":359,"depth":59,"text":360},{"id":383,"depth":59,"text":384},"面向跨境团队的 WhatsApp AI 翻译上线前检查清单，帮助先把沟通流程跑顺。","md",{},true,"\u002Fguides\u002Fwhatsapp-ai-translation-workflow","6 分钟阅读",{"title":271,"description":420},"翎影 WhatsApp AI 翻译指南，覆盖场景确认、术语准备、人工复核和后续扩展步骤。","4.guides\u002F1.whatsapp-ai-translation-workflow","WkxHTcBrTMJtdLor2MBJbNUTDPPWJCQ3G69h-ORAJ4s",{"id":424,"title":425,"badge":426,"body":428,"description":543,"extension":414,"meta":544,"navigation":416,"path":545,"readTime":546,"seo":547,"stem":549,"__hash__":550},"guides\u002F4.guides\u002F2.ai-reply-review-process.md","AI 回复建议的人机协作流程",{"label":427},"回复",{"type":275,"value":429,"toc":536},[430,433,436,440,443,457,460,464,467,481,484,488,491,502,505,509,512,526,529,533],[278,431,425],{"id":432},"ai-回复建议的人机协作流程",[282,434,435],{},"AI 回复建议适合帮助团队更快起草内容，但上线初期不应该替代业务人员的最终判断。",[286,437,439],{"id":438},"_1-明确-ai-负责什么","1. 明确 AI 负责什么",[282,441,442],{},"建议把 AI 的职责限定为：",[294,444,445,448,451,454],{},[297,446,447],{},"根据当前消息生成回复草稿。",[297,449,450],{},"总结客户意图和沟通阶段。",[297,452,453],{},"提醒业务人员需要确认的信息。",[297,455,456],{},"给出下一步沟通建议。",[282,458,459],{},"AI 不应该在没有规则的情况下承诺价格、折扣、交期、售后结果或合同条款。",[286,461,463],{"id":462},"_2-人工负责最终发送","2. 人工负责最终发送",[282,465,466],{},"上线初期建议保留人工发送路径：",[294,468,469,472,475,478],{},[297,470,471],{},"AI 输出建议回复。",[297,473,474],{},"业务人员检查数字、条款和语气。",[297,476,477],{},"必要时修改后发送。",[297,479,480],{},"将不合适的回复样本记录下来。",[282,482,483],{},"这能避免因为产品信息、客户背景或商务条件不同导致错误承诺。",[286,485,487],{"id":486},"_3-设置回复边界","3. 设置回复边界",[282,489,490],{},"团队可以先定义几类边界：",[294,492,493,496,499],{},[297,494,495],{},"可以直接建议回复：问候、基础产品说明、资料发送。",[297,497,498],{},"需要人工确认：价格、库存、物流、付款方式。",[297,500,501],{},"必须人工处理：投诉、退款、合同、法律和敏感客户关系。",[282,503,504],{},"边界越清楚，AI 回复建议越容易被团队稳定使用。",[286,506,508],{"id":507},"_4-建立反馈循环","4. 建立反馈循环",[282,510,511],{},"每周可以整理少量真实样本：",[294,513,514,517,520,523],{},[297,515,516],{},"哪些回复可以直接使用。",[297,518,519],{},"哪些回复需要修改。",[297,521,522],{},"哪些回复不应该出现。",[297,524,525],{},"哪些问题缺少产品知识支撑。",[282,527,528],{},"这些反馈可以帮助后续优化提示、术语和知识库。",[286,530,532],{"id":531},"_5-逐步接入-ai-托管","5. 逐步接入 AI 托管",[282,534,535],{},"当某些场景长期稳定后，再考虑让 AI 处理一部分重复问题。自动化范围应该从小开始，并保留人工接管路径。",{"title":406,"searchDepth":59,"depth":59,"links":537},[538,539,540,541,542],{"id":438,"depth":59,"text":439},{"id":462,"depth":59,"text":463},{"id":486,"depth":59,"text":487},{"id":507,"depth":59,"text":508},{"id":531,"depth":59,"text":532},"帮助团队在保留人工判断的前提下使用 AI 回复建议，避免上线初期过度自动化。",{},"\u002Fguides\u002Fai-reply-review-process","5 分钟阅读",{"title":425,"description":548},"翎影 AI 回复建议指南，说明如何设计人工复核、回复边界和团队反馈流程。","4.guides\u002F2.ai-reply-review-process","_5tC6yuZbD7igkTvETABWcUPKW-as7rmTbd5VvlFV3w",{"id":552,"title":553,"badge":554,"body":556,"description":677,"extension":414,"meta":678,"navigation":416,"path":679,"readTime":418,"seo":680,"stem":682,"__hash__":683},"guides\u002F4.guides\u002F3.ai-agent-guardrails.md","AI 托管辅助的边界设计",{"label":555},"托管",{"type":275,"value":557,"toc":670},[558,561,564,568,571,588,591,595,598,615,618,622,625,636,639,643,646,660,663,667],[278,559,553],{"id":560},"ai-托管辅助的边界设计",[282,562,563],{},"AI 托管辅助的价值在于处理重复、明确、低风险的沟通环节，而不是让系统不受限制地代表团队做决定。",[286,565,567],{"id":566},"_1-适合托管的场景","1. 适合托管的场景",[282,569,570],{},"第一阶段可以优先考虑：",[294,572,573,576,579,582,585],{},[297,574,575],{},"常见问题说明。",[297,577,578],{},"基础资料发送。",[297,580,581],{},"订单信息收集。",[297,583,584],{},"营业时间外的初步响应。",[297,586,587],{},"明确规则下的售后流程说明。",[282,589,590],{},"这些场景信息相对稳定，也更容易被规则约束。",[286,592,594],{"id":593},"_2-不适合自动处理的场景","2. 不适合自动处理的场景",[282,596,597],{},"以下场景建议保持人工处理：",[294,599,600,603,606,609,612],{},[297,601,602],{},"价格谈判和折扣审批。",[297,604,605],{},"退款、投诉、纠纷。",[297,607,608],{},"合同、付款、法律条款。",[297,610,611],{},"重要客户或高价值订单。",[297,613,614],{},"AI 无法判断客户真实意图的会话。",[282,616,617],{},"如果系统无法判断，就应该交给人。",[286,619,621],{"id":620},"_3-设计接管规则","3. 设计接管规则",[282,623,624],{},"接管规则可以从三类信号开始：",[294,626,627,630,633],{},[297,628,629],{},"内容信号：客户提到投诉、退款、合同、付款异常。",[297,631,632],{},"价值信号：订单金额、客户等级、长期合作机会。",[297,634,635],{},"不确定信号：AI 多轮无法回答、客户连续追问、语义不明确。",[282,637,638],{},"这些规则可以帮助团队在效率和风险之间取得平衡。",[286,640,642],{"id":641},"_4-记录托管结果","4. 记录托管结果",[282,644,645],{},"AI 托管上线后，需要持续记录：",[294,647,648,651,654,657],{},[297,649,650],{},"成功处理的问题类型。",[297,652,653],{},"被人工接管的问题类型。",[297,655,656],{},"客户不满意或重复追问的会话。",[297,658,659],{},"AI 输出不够准确的原因。",[282,661,662],{},"托管不是一次配置完成，而是持续调优。",[286,664,666],{"id":665},"_5-从辅助开始","5. 从辅助开始",[282,668,669],{},"翎影的 AI 托管 方向应先服务于“辅助”和“边界清晰的自动化”。当团队对场景、规则和产品知识有足够把握后，再逐步扩大自动处理范围。",{"title":406,"searchDepth":59,"depth":59,"links":671},[672,673,674,675,676],{"id":566,"depth":59,"text":567},{"id":593,"depth":59,"text":594},{"id":620,"depth":59,"text":621},{"id":641,"depth":59,"text":642},{"id":665,"depth":59,"text":666},"为跨境客服和销售团队设计 AI 托管边界，减少重复工作，同时保留人工接管。",{},"\u002Fguides\u002Fai-agent-guardrails",{"title":553,"description":681},"翎影 AI 托管指南，介绍自动托管适用场景、禁止场景和人工接管原则。","4.guides\u002F3.ai-agent-guardrails","qB67q6TXJV-fp8rXBc_xuH6hxqL6iudpeZWR25ERvlM",{"id":685,"title":686,"badge":687,"body":689,"description":976,"extension":414,"meta":977,"navigation":416,"path":978,"readTime":979,"seo":980,"stem":982,"__hash__":983},"guides\u002F4.guides\u002F4.launch-readiness-checklist.md","翎影官网上线前检查清单",{"label":688},"上线",{"type":275,"value":690,"toc":966},[691,693,696,700,703,720,724,727,755,758,762,765,782,785,789,792,809,812,816,819,836,839,843,846,869,872,876,879,929,932,936,939,959,962],[278,692,686],{"id":686},[282,694,695],{},"官网第一版已经具备基础页面、内容系统和本地占位资源。正式上线前，建议按下面清单逐项核对，避免因为占位内容、静态 SEO 文件或产品信息不完整影响首轮发布。",[286,697,699],{"id":698},"_1-品牌与基础信息","1. 品牌与基础信息",[282,701,702],{},"上线前先确认所有对外信息一致：",[294,704,705,708,711,714,717],{},[297,706,707],{},"中文品牌名统一为“翎影”。",[297,709,710],{},"英文品牌名统一为“LingYio”。",[297,712,713],{},"网站标题、默认描述和首页主文案无旧名称。",[297,715,716],{},"品牌标志、网站图标、社交分享图和分享信息符合品牌视觉。",[297,718,719],{},"联系邮箱、公司主体、服务地区和表单入口不再使用占位信息。",[286,721,723],{"id":722},"_2-域名与-seo-文件","2. 域名与 SEO 文件",[282,725,726],{},"正式域名确定后，需要检查：",[294,728,729,740,746,749,752],{},[297,730,731,735,736,739],{},[732,733,734],"code",{},"public\u002Fsitemap.xml"," 中所有 ",[732,737,738],{},"https:\u002F\u002Fwww.lingyio.com"," 是否需要替换。",[297,741,742,745],{},[732,743,744],{},"public\u002Frobots.txt"," 中 sitemap 地址是否正确。",[297,747,748],{},"首页 canonical 是否指向最终域名。",[297,750,751],{},"博客、文档、指南的重要页面是否都进入站点地图。",[297,753,754],{},"404 页面和非正式页面是否不会被错误收录。",[282,756,757],{},"如果后续路由继续增加，建议把静态 sitemap 改成自动生成，减少遗漏风险。",[286,759,761],{"id":760},"_3-产品截图与图片资源","3. 产品截图与图片资源",[282,763,764],{},"当前页面已接入白底占位图。上线前需要统一替换为真实资产：",[294,766,767,770,773,776,779],{},[297,768,769],{},"首页产品 UI 展示图。",[297,771,772],{},"产品页收件箱、仪表盘、AI 托管截图。",[297,774,775],{},"功能页翻译、AI 回复、AI 托管、AI 工具截图。",[297,777,778],{},"解决方案页跨境销售、客服、电商团队截图。",[297,780,781],{},"博客封面和作者头像。",[282,783,784],{},"替换时尽量保持原路径和文件名，这样页面代码可以少改动。",[286,786,788],{"id":787},"_4-产品能力与价格信息","4. 产品能力与价格信息",[282,790,791],{},"目前价格页已采用免费版、VIP PLUS版、VIP PRO版和 VIP Business版结构。上线前需要确认：",[294,793,794,797,800,803,806],{},[297,795,796],{},"套餐名是否与后台保持一致。",[297,798,799],{},"金额是否与正式支付价格保持一致。",[297,801,802],{},"额度、席位、消息量或 AI 使用限制是否与后台保持一致。",[297,804,805],{},"是否保留“联系咨询”作为 Business 方案主转化路径。",[297,807,808],{},"登录、注册、试用入口是否跳转真实系统。",[282,810,811],{},"不要把内部规划写成已上线能力。尚未开放的功能可以表达为“规划中”或暂不展示。",[286,813,815],{"id":814},"_5-表单与转化链路","5. 表单与转化链路",[282,817,818],{},"联系页、注册页和登录页是转化关键点，需要确认：",[294,820,821,824,827,830,833],{},[297,822,823],{},"联系表单是否接入真实提交逻辑。",[297,825,826],{},"表单提交失败是否有提示。",[297,828,829],{},"登录入口是否指向真实产品系统。",[297,831,832],{},"注册入口是否指向真实开通流程。",[297,834,835],{},"邮箱、电话或客服联系方式是否可用。",[282,837,838],{},"第一版如果仍保留占位表单，应在上线前明确是否允许展示。",[286,840,842],{"id":841},"_6-内容质量","6. 内容质量",[282,844,845],{},"上线前建议人工阅读以下页面：",[294,847,848,851,854,857,860,863,866],{},[297,849,850],{},"首页。",[297,852,853],{},"产品页。",[297,855,856],{},"功能详情页。",[297,858,859],{},"解决方案详情页。",[297,861,862],{},"价格页。",[297,864,865],{},"博客、文档、指南。",[297,867,868],{},"关于页和联系页。",[282,870,871],{},"重点检查是否有英文模板残留、过度承诺、无法验证的数据、重复标题、错别字和不符合品牌定位的表达。",[286,873,875],{"id":874},"_7-技术验证","7. 技术验证",[282,877,878],{},"上线前至少执行：",[880,881,885],"pre",{"className":882,"code":883,"language":884,"meta":406,"style":406},"language-bash shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","pnpm exec eslint .\npnpm exec nuxt typecheck\npnpm exec nuxt build\n","bash",[732,886,887,905,917],{"__ignoreMap":406},[888,889,891,895,899,902],"span",{"class":890,"line":42},"line",[888,892,894],{"class":893},"sBMFI","pnpm",[888,896,898],{"class":897},"sfazB"," exec",[888,900,901],{"class":897}," eslint",[888,903,904],{"class":897}," .\n",[888,906,907,909,911,914],{"class":890,"line":59},[888,908,894],{"class":893},[888,910,898],{"class":897},[888,912,913],{"class":897}," nuxt",[888,915,916],{"class":897}," typecheck\n",[888,918,920,922,924,926],{"class":890,"line":919},3,[888,921,894],{"class":893},[888,923,898],{"class":897},[888,925,913],{"class":897},[888,927,928],{"class":897}," build\n",[282,930,931],{},"构建通过后，还需要抽测核心路由是否返回 200，并确认浏览器里没有明显资源加载错误。",[286,933,935],{"id":934},"_8-发布后复查","8. 发布后复查",[282,937,938],{},"上线后建议立即检查：",[294,940,941,944,947,950,953,956],{},[297,942,943],{},"首页首屏是否正常渲染。",[297,945,946],{},"站点地图和 robots 文件是否可访问。",[297,948,949],{},"搜索引擎抓取地址是否正确。",[297,951,952],{},"移动端导航是否可用。",[297,954,955],{},"表单和行动按钮是否能完成预期动作。",[297,957,958],{},"页面是否依赖无法访问的远程资源。",[282,960,961],{},"这份清单会随着真实产品后台、正式套餐和生产域名确认继续更新。",[963,964,965],"style",{},"html pre.shiki code .sBMFI, html code.shiki .sBMFI{--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B}html pre.shiki code .sfazB, html code.shiki .sfazB{--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D}html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":406,"searchDepth":59,"depth":59,"links":967},[968,969,970,971,972,973,974,975],{"id":698,"depth":59,"text":699},{"id":722,"depth":59,"text":723},{"id":760,"depth":59,"text":761},{"id":787,"depth":59,"text":788},{"id":814,"depth":59,"text":815},{"id":841,"depth":59,"text":842},{"id":874,"depth":59,"text":875},{"id":934,"depth":59,"text":935},"面向 LingYio \u002F 翎影官网第一版上线前的内容、SEO、资源、性能和产品信息核对清单。",{},"\u002Fguides\u002Flaunch-readiness-checklist","7 分钟阅读",{"title":686,"description":981},"翎影官网上线前检查指南，覆盖域名、SEO、站点地图、联系信息、产品截图、价格内容、表单和构建验证。","4.guides\u002F4.launch-readiness-checklist","ax_Vb5jeA-q8d4p-tk_y4kiFbxli_IeytoYB9iAU1L8",1787887804978]