CB AI Ops 长沙若邻网络科技有限公司 Changsha Ruolin Network Technology Co., Ltd.

跨境售后邮件执行层 · 私有化部署 + BYOK Cross-border support execution layer · Private deployment + BYOK

把跨境客服从“盯收件箱救火”切到“审核发送闭环” Move support teams from inbox firefighting to a review-send operating loop

不是通用AI邮件助手，而是给 2-10 人客服团队上的私有化执行层：先拦垃圾和空白邮件，再做分诊、草稿、审核发送、日报和告警。先用 1 个邮箱试点，再按ROI扩容。 Not a generic AI mail bot, but a private execution layer for 2-10 person support teams: remove spam and blanks first, then triage, draft, review-send, digest, and alert. Start with one mailbox, then scale by ROI.

微信/电话咨询 WeChat / Call Now 查看案例结果 See Case Results
1-3天联调d setup 7天验收d validation BYOK 一次性交付 + 月维护One-time delivery + monthly maintenance

试点成效方向

Pilot Impact Direction

先看漏回、积压、噪音下降，再谈扩容与自动发送比例 Reduce misses, backlog, and noise first, then scale automation

典型验收观察项 Typical Acceptance Signals

低价值重复动作 Low-value repetitive work 上线前Before 100% 上线后After 45-65%
待处理积压 Pending backlog 上线前 高Before high 上线后 降After reduced
老板可视化 Manager visibility 上线前 弱Before low 上线后 日报化After digest-driven

说明：以上是常见趋势，不是对所有客户的固定承诺。

Note: these are common trends, not fixed promises for every team.

Before and after support operation comparison chart

核心能力

Core Capabilities

不是分完邮件就结束，而是让团队稳定按闭环执行 Not just triage, but a repeatable daily loop

邮件分诊与噪音剥离 Email Triage + Noise Isolation

自动识别物流、退款、投诉、产品咨询、地址变更等分类；垃圾、空白、测试邮件先分流，减少AI消耗和人工噪音。

Classifies shipping, refund, complaint, product, and address requests while routing spam, blank, and test emails away before they consume AI or agent time.

AI草稿与补充项提示 AI Draft + Missing Info Prompt

生成英文回复草稿与缺失信息清单，让客服从“找模板、重写邮件”改成“补判断、做审核”。

Builds English drafts plus missing-info prompts so agents move from template hunting and rewriting to judgment and review.

审核发送闭环 Review & Send Loop

群消息直达审核页，可发送（SMTP）或标记已处理，把“收件箱作业”切成“审核发送作业”。

Group messages open the review page for SMTP send or handled marking, shifting work from inbox digging to review-send operations.

老板日报与处理结构 Daily Digest + Processing Mix

每天汇总新增、待处理、已发送、垃圾占比和高紧急样本，让老板看到结构变化，而不是只看群消息刷屏。

Summarizes new, pending, sent, spam ratio, and high-urgency samples so managers see structural change instead of just chat noise.

静默故障告警 Silent-Failure Alerts

超过阈值无新分诊时自动提醒，帮助快速排查 IMAP、模型限流或执行链路异常。

Alerts on prolonged triage inactivity so IMAP issues, model throttling, or broken execution chains get caught early.

私有化交付，不是演示流程 Operational Delivery, Not a Demo

客户自持模型Key，台账、日报、告警和边界说明一起交付，重点是让客户敢上线、敢验收。

Clients keep their own model keys, while ledger, digest, alerts, and scope boundaries ship together so the system can actually go live and be accepted.

落地流程

Delivery Workflow

5步走完从咨询到稳定运行 From discovery to stable operation in 5 steps

01

需求诊断Discovery

确认邮件量、客服班次、部署条件和优先目标。

Clarify email volume, staffing shifts, deployment constraints, and target outcomes.

02

试点联调Pilot Setup

先接1个邮箱+1个群，跑通端到端流程。

Start with 1 mailbox + 1 group and complete end-to-end integration.

03

灰度运行Controlled Rollout

先人工审核，再按风险逐步开放自动发送。

Manual-first review, then progressive auto-send by risk level.

04

7天验收7-Day Validation

看新增、待处理、发送结构和垃圾拦截占比。

Validate by new/pending/sent mix and spam interception ratio.

05

扩容升级Scale Up

多邮箱、多客服和二期API对接按ROI扩展。

Expand to multi-mailbox/multi-agent and phase-2 APIs based on ROI.

真实案例（脱敏）

Real Cases (Redacted)

看真实联调结果，不拿教程演示冒充交付系统 Real integration results, not tutorial demos

案例A｜验收联调

Case A | Acceptance Pilot

3封常见售后邮件验证3 Typical Support Emails

物流查询、退款、产品咨询三类邮件均成功分诊并推送，最快约22秒触达。

Shipping/refund/product emails were triaged and pushed successfully, fastest at around 22s.

3/322s-1m

案例B｜混合灰度

Case B | Mixed Gray Test

10封混合邮件连续测试10 Mixed Emails Sequentially

正常咨询、广告、空白邮件均有处理结果，垃圾邮件分流生效并减少AI调用。

Normal, spam, and blank emails all produced outcomes; spam routing reduced AI calls.

10/10Spam Split

案例C｜稳定性保障

Case C | Stability Control

日报 + 心跳告警协同Digest + Heartbeat Alert

日报准时触发；长时间无新分诊时自动告警，便于及时排查IMAP或模型异常。

Digest triggers on schedule; heartbeat alert detects long triage idle windows for fast troubleshooting.

09:00 DigestAuto Alert

说明：实际效果受邮件结构、团队执行、网络条件和客服流程纪律影响。 Note: outcomes vary by email structure, team execution, network conditions, and process discipline.

交付套餐

Service Plans

先用 1 个邮箱试点，不急着上重平台 Start with one mailbox first instead of forcing a heavy platform rollout

引流试点版

Pilot Starter

¥4,999

1邮箱 + 1群 + 主流程，先把“收件箱模式”切到“审核发送模式”。

1 mailbox + 1 group + core flow to move from inbox work to review-send work.

标准成交版

Standard Delivery

¥7,999

1-2邮箱，含分群路由、规则调优和更完整的日报告警口径。

1-2 mailboxes with routing, rule tuning, and fuller digest-alert operations.

增长协作版

Scale Team

¥12,999

多客服场景，支持灰度自动发送、周复盘和更清晰的人头ROI评估。

Built for multi-agent teams with controlled auto-send, weekly review, and clearer headcount ROI evaluation.

费用口径：试点价/标准交付为一次性交付费；维护费按月收取。最终报价按邮箱数量、部署方式和API范围确认。 Billing model: Pilot and Standard are one-time delivery fees; maintenance is monthly. Final quote depends on mailbox count, deployment mode, and API scope.

业务术语与交付边界

Business Terms & Delivery Scope

展开查看，减少售前重复沟通成本 Expand for quick scope alignment before consultation

这不是完整工单平台This Is Not a Full Ticketing Platform

当前更适合仍以邮箱处理售后的团队，先落地“分诊 - 审核发送 - 日报告警”主链路；如需全渠道统一收件箱、知识库、CRM/ERP深度联动，通常属于二期或更大平台项目。

This fits teams still handling support through email and needing the triage-review-send-digest-alert backbone first. Full omnichannel inbox, knowledge base, or deep CRM/ERP coupling is usually a phase-two or larger platform project.

一次性交付费（项目费）One-time Delivery Fee

试点版/标准版按“项目”收取一次性费用，不按年收费。报价会随邮箱数量和流程复杂度变化。

Pilot and standard plans are charged per project, not annually. Quote varies by mailbox count and workflow complexity.

月维护费Monthly Maintenance

维护费按月收取，覆盖告警、备份、小改动、版本升级等持续运维项。首批签约可赠送12个月基础维护（具体以合同条款为准）。

Maintenance is charged monthly and covers alerts, backup, minor adjustments, and version updates. Early-batch clients may receive up to 12 months of baseline maintenance subject to contract terms.

默认审核策略Default Review Policy

默认“人工审核后发送”，避免误发风险。自动发送仅建议在低风险场景灰度开启。

Default mode is review-before-send to reduce risk. Auto-send should be enabled gradually for low-risk tickets only.

上线前置条件Go-live Prerequisites

需提供可用邮箱授权、部署机器和群通知通道；如需远程审核入口，需客户IT提供可达地址。建议环境：4核8G以上、Windows 10+/Linux；如使用境外模型/API，需具备稳定的跨境网络访问能力。

Requires mailbox auth, deployment machine, and group notification channel. Remote review access depends on client IT network setup. Recommended baseline: 4 vCPU + 8 GB RAM and Windows 10+/Linux. If overseas model/API endpoints are used, stable cross-border network reachability is required.

验收口径Acceptance Criteria

验收看“分诊可用性、推送时效、处理结构变化、日报告警稳定性”，不承诺固定收益数字。

Acceptance focuses on triage usability, notification speed, processing mix changes, and digest/alert stability.

超范围项Out-of-Scope Items

客户VPN/网络建设、深度ERP/API改造、额外系统集成通常属于增购项。

Client VPN/network buildout, deep ERP/API refactoring, and extra system integrations are usually add-on scope.

联系我们

Contact

建议优先微信或电话，沟通更快 WeChat or phone is recommended for fastest response

电话Phone 17773101098
QQ 262772898（点击加好友） (Add on QQ)
邮箱Email licheng527@qq.com
地址Address 长沙市天心区雀园路创谷产业园 Chuanggu Industrial Park, Queyuan Rd, Tianxin District, Changsha

首次沟通建议提供：日均邮件量、客服人数、计划上线时间。

For first call, share: daily email volume, support team size, and target go-live date.

交付边界：我们负责应用部署与联调，不负责客户VPN/网络建设。

Scope boundary: we deliver app deployment/integration, not client VPN/network infrastructure.

电话咨询Call QQ 微信沟通WeChat