📦 Client — 客户管理

# 客户 客户不只是付了钱的顾客。客户是一段需要被理解、管理并持续交付的持续关系。大多数客户问题并非始于投诉那一刻，而是更早：期望错位、糟糕的 onboarding、沟通模糊、范围不清、跟进迟缓、隐藏决策者，或从未被主动管理的关系。本技能帮助构建更健壮的客户体系，让关系在实践中而非理论上奏效。 ## 触发条件 当用户需要以下情况时启用本技能： - 引入新客户 - 改善客户关系 - 管理客户沟通 - 定义期望、范围与边界 - 降低流失、困惑或摩擦 - 提升交付、交接或客户管理 - 准备面向客户的流程、文档或话术 - 识别客户关系成败的关键因素 也适用于用户说出如下话语： - “帮我管理这个客户” - “如何 onboard 客户” - “我的客户关系很乱” - “如何更好地设定期望” - “如何留住客户” - “新客户该发什么” - “如何应对难搞客户” ## 核心原则 健康的客户关系依赖“先清晰，后复杂”。客户很少无缘无故变得难搞，更多是因为关系建立在从未被明确的假设之上：成功意味着什么、谁来做决策、沟通如何运作、包含什么、不包含什么、变更如何处理、出现问题时怎么办。优秀的客户管理通过减少模糊来建立信任。 ## 本技能能做什么 帮助： - 定义客户关系顺畅运行所需条件 - 优化 onboarding、沟通与交付体系 - 澄清范围、责任与期望 - 在问题爆发前识别客户管理风险 - 构建面向客户的文档、工作流与触点 - 提升留存、信任与长期账户质量 - 将临时服务转变为更稳定的客户系统 ## 默认输出 根据请求，输出以下一项或多项： 1. 客户 onboarding 计划 开启关系时的结构化流程。 2. 客户沟通框架 更新、反馈与下一步的规则、节奏与模板。 3. 客户成功地图 展示目标、期望、里程碑与风险点的关系模型。 4. 范围与边界框架 定义包含、排除、变更控制与升级的结构。 5. 客户风险审计 诊断潜在摩擦、误解或流失威胁。 6. 留存与增长计划 维护信任、扩展价值、深化长期关系的系统。 ## 响应规则 回应时： - 识别客户关系类型 - 定义双方的成功含义 - 区分销售承诺与交付现实 - 厘清范围、时间与沟通 - 及早暴露风险 - 区分关系问题与流程问题 - 明确责任归属 - 优先清晰、信任与可用性，而非表面复杂 ## 客户生命周期 ~~~python CLIENT_LIFECYCLE = { "stage_1_pre_close": { "purpose": "Ensure the relationship is sold honestly and clearly", "focus": [ "expectation setting", "fit assessment", "decision-maker mapping", "scope clarity", "risk signals before close" ] }, "stage_2_onboarding": { "purpose": "Start the relationship with alignment and momentum", "focus": [ "intake", "goals", "roles", "timeline", "deliverables", "communication norms" ] }, "stage_3_active_delivery": { "purpose": "Deliver value while keeping expectations aligned", "focus": [ "updates", "feedback loops", "change handling", "issue resolution", "progress visibility" ] }, "stage_4_stabilization": { "purpose": "Move from reactive execution to a steady working rhythm", "focus": [ "relationship trust", "predictability", "repeatability", "reduced confusion", "review cadences" ] }, "stage_5_retention_growth": { "purpose": "Preserve and expand a valuable relationship", "focus": [ "renewal readiness", "new opportunities", "expansion", "risk prevention", "long-term fit" ] } } ~~~ ## 客户关系架构 ~~~python CLIENT_ARCHITECTURE = { "core_elements": { "outcome": "What the client is actually trying to achieve", "scope": "What is and is not included", "timeline": "When key milestones happen", "communication": "How updates, questions, and decisions are handled", "ownership": "Who is responsible for what", "success_measure": "How both sides know things are going well", "change_management": "How revisions, additions, and surprises are handled" }, "guiding_questions": [ "Why did this client hire us", "What do they think they bought", "What do we think we are delivering", "Who influences satisfaction and renewal", "What would make this relationship fail", "What is unclear right now that may become expensive later" ] } ~~~ ## 客户 Onboarding 框架 ~~~python CLIENT_ONBOARDING = { "step_1_alignment": { "purpose": "Confirm goals, scope, and expectations", "outputs": [ "desired outcome", "success criteria", "constraints", "key contacts", "timeline assumptions" ] }, "step_2_information_gathering": { "purpose": "Collect what is needed to start well", "outputs": [ "intake information", "documents", "access", "history", "preferences", "known risks" ] }, "step_3_working_model": { "purpose": "Define how the relationship will operate", "outputs": [ "meeting cadence", "communication channel", "approval process", "feedback mechanism", "escalation path" ] }, "step_4_first_value": { "purpose": "Create early confidence through visible progress", "outputs": [ "quick win", "first milestone", "clear next step", "evidence of momentum" ] } } ~~~ ## 常见客户失败模式 ~~~python CLIENT_FAILURE_PATTERNS = { "patterns": [ "Scope was never truly understood", "The buyer and day-to-day stakeholder wanted different things", "Communication rhythm was too vague", "The client did not understand what was required from them", "Problems were noticed late and discussed vaguely", "Too much was customized informally", "No one tracked satisfaction until renewal time", "The provider focused on output while the client cared about outcome" ], "responses": [ "Re-clarify goals and success criteria", "Create explicit status and decision checkpoints", "Define boundaries and change process", "Map stakeholders and priorities", "Review risk signals earlier and more often", "Translate delivery into client-visible value" ] } ~~~ ## 客户沟通逻辑 ~~~python CLIENT_COMMUNICATION = { "principles": [ "Silence creates anxiety faster than bad news", "Clients tolerate problems better than ambiguity", "Updates should answer: what happened, what matters, what is next", "Tone should match confidence without hiding reality", "Escalation is better than drift" ], "cadence_examples": { "high_touch_service": "Weekly updates plus milestone reviews", "project_based_work": "Milestone-based updates with decision checkpoints", "advisory_relationship": "Regular strategic reviews plus as-needed support" } } ~~~ ## 客户输出格式 ### 客户摘要 - 客户类型： - 期望成果： - 当前阶段： - 主要期望： - 范围与边界： - 沟通模式： - 风险或摩擦点： - 推荐改进： - 推荐下一步： ## 边界 本技能帮助设计和优化客户关系体系、沟通、onboarding 与交付结构。不可替代法律、财务、人力、合规或合同建议。针对受监管或高风险合作，请根据用户所在司法辖区、行业要求及正式协议调整输出。 ## 交付前质量检查 - [ ] 客户类型与关系背景已明确 - [ ] 成功已从客户视角定义 - [ ] 范围、时间与沟通已明确 - [ ] 角色与责任已清晰 - [ ] 风险或摩擦点已识别 - [ ] 建议提升清晰度、信任或留存 - [ ] 输出以具体下一步作结