sales-live-chat

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Live Chat & Chatbot for Sales

销售用在线聊天与聊天机器人

Help the user with live chat and chatbot — from tool selection and widget setup through chatbot flow design, agent routing, visitor tracking, and chat-to-lead conversion. This skill is tool-agnostic but includes platform-specific guidance for Brevo Conversations, Drift (Salesloft), Intercom, HubSpot, Crisp, LiveChat, Zendesk, Tidio, Freshdesk, and ZoomInfo Chat.

为用户提供在线聊天和聊天机器人相关帮助——从工具选型、组件设置，到聊天机器人流程设计、坐席路由、访客追踪、聊天转线索转化全流程覆盖。本技能不绑定特定工具，但包含Brevo Conversations、Drift (Salesloft)、Intercom、HubSpot、Crisp、LiveChat、Zendesk、Tidio、Freshdesk、ZoomInfo Chat等平台的专属指导。

Step 1 — Gather context

步骤1：收集上下文信息

Ask the user:

What do you need help with?
- A) Tool selection — choosing a live chat platform
- B) Widget setup — installing and configuring the chat widget
- C) Chatbot flows — building automated conversation flows
- D) Agent routing — assigning chats to the right team members
- E) Proactive messaging — triggering chat based on visitor behavior
- F) Chat-to-lead conversion — capturing leads from conversations
- G) Analytics — measuring chat performance and ROI
- H) Integration — connecting chat to CRM, helpdesk, or other tools
- I) Something else — describe it
What's your primary use case?
- A) Sales — qualifying leads, booking demos, answering buyer questions
- B) Support — resolving customer issues
- C) Both sales and support
- D) Self-service — chatbot only, no live agents
What tool are you using (or considering)?
- A) Brevo Conversations
- B) Drift (Salesloft)
- C) Intercom
- D) HubSpot
- E) Crisp
- F) LiveChat
- G) Zendesk Chat
- H) Tidio
- I) Freshdesk / Freshchat
- J) Not decided yet
- K) Other

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end.

询问用户以下问题：

你需要哪方面的帮助？
- A) 工具选型——选择在线聊天平台
- B) 组件设置——安装并配置聊天组件
- C) 聊天机器人流程——搭建自动化对话流程
- D) 坐席路由——将聊天分配给合适的团队成员
- E) 主动消息——根据访客行为触发聊天
- F) 聊天转线索转化——从对话中获取销售线索
- G) 数据分析——衡量聊天性能和ROI
- H) 集成对接——将聊天工具与CRM、服务台或其他工具打通
- I) 其他需求——请描述
你的核心使用场景是什么？
- A) 销售——线索定级、预约演示、解答买家问题
- B) 客户支持——解决客户问题
- C) 同时覆盖销售和客户支持
- D) 自助服务——仅使用聊天机器人，无人工坐席
你正在使用（或考虑使用）什么工具？
- A) Brevo Conversations
- B) Drift (Salesloft)
- C) Intercom
- D) HubSpot
- E) Crisp
- F) LiveChat
- G) Zendesk Chat
- H) Tidio
- I) Freshdesk / Freshchat
- J) 尚未决定
- K) 其他工具

如果用户的需求已经提供了大部分上下文信息，可以直接跳转到对应步骤。 优先基于合理假设（需明确说明）给出你能提供的最优解答，最后仅补充1-2个最关键的澄清问题即可。

Step 2 — Strategy and approach

步骤2：策略与落地方法

When to use live chat for sales

销售场景下使用在线聊天的最佳时机

Live chat converts best when:

High-intent pages — pricing, demo request, comparison pages
Complex products — B2B SaaS, enterprise software, custom solutions
Time-sensitive decisions — trial users, cart abandonment, upgrade moments
Account-based selling — identified target accounts visiting your site

在线聊天在以下场景转化效果最优：

高意向页面——定价页、演示申请页、产品对比页
复杂产品——B2B SaaS、企业级软件、定制化解决方案
时间敏感决策——试用用户、购物车遗弃、升级节点
基于客户的销售（ABS）——已识别的目标客户访问你的站点

Chat-to-lead conversion framework

聊天转线索转化框架

Identify — track visitor identity (email, company via reverse IP, UTM source)
Qualify — chatbot asks qualifying questions before routing to agent (budget, timeline, role)
Route — send qualified leads to the right rep (by territory, deal size, product line)
Convert — book a meeting directly from chat (calendar integration)
Capture — push lead data to CRM automatically

识别——追踪访客身份（邮箱、反向IP匹配的公司信息、UTM来源）
定级——聊天机器人在转人工坐席前询问定级问题（预算、 timeline、角色）
路由——将合格线索分配给合适的销售代表（按区域、交易规模、产品线划分）
转化——直接在聊天中预约会议（日历集成）
归集——自动将线索数据同步到CRM

Chatbot flow design principles

聊天机器人流程设计原则

Start with a greeting that matches the page context — "Looking at our pricing?" not "Hi, how can I help?"
Use buttons, not open text — guide the conversation with multiple-choice options
Qualify in 2-3 questions max — don't interrogate visitors
Always offer a human option — "Talk to a person" should be available at every step
Set expectations — if agents are offline, say so and offer email/callback
Personalize when possible — use visitor name, company, or page context

使用匹配页面上下文的问候语——比如“正在查看我们的定价方案？”而不是通用的“您好，请问有什么可以帮您？”
使用按钮而非开放式提问——用选择题选项引导对话流程
最多设置2-3个定级问题——不要过度询问访客造成反感
始终提供转人工选项——每个步骤都要保留“联系人工客服”的入口
明确告知预期——如果坐席离线，要明确说明并提供邮箱/回呼选项
尽可能个性化——使用访客的姓名、公司信息或页面上下文定制内容

Tool selection framework

工具选型框架

Factor	Brevo	Drift	Intercom	HubSpot	Crisp	LiveChat
Best for	All-in-one marketing + chat	Enterprise sales chat	Product-led growth	HubSpot ecosystem	SMB budget	Support-focused
Pricing	Included in Brevo plans	$$$ (enterprise)	$$$	Free (basic) to $$$	Free to $$	$$
Chatbot	Basic automation	AI + playbooks	AI + custom bots	Basic to advanced	Basic bot	Basic bot
CRM integration	Built-in CRM	Salesforce, HubSpot	Own CRM	Native	Zapier	Zapier, native
AI features	Aura AI agent	AI chatbot, Bionic	Fin AI agent	AI assistant	AI bot	AI assist
Meeting booking	No native	Yes	Yes	Yes (HubSpot meetings)	No native	No native

选型维度	Brevo	Drift	Intercom	HubSpot	Crisp	LiveChat
最佳适用场景	一体化营销+聊天	企业级销售聊天	产品驱动增长	HubSpot生态用户	中小微预算团队	侧重支持场景
定价水平	包含在Brevo套餐内	$$$（企业级）	$$$	免费（基础版）到$$$	免费到$$	$$
聊天机器人能力	基础自动化	AI+剧本模板	AI+自定义机器人	基础到高级	基础机器人	基础机器人
CRM集成	内置CRM	Salesforce、HubSpot	自有CRM	原生集成	Zapier集成	Zapier、原生集成
AI功能	Aura AI Agent	AI聊天机器人、Bionic	Fin AI Agent	AI助手	AI机器人	AI辅助
会议预约能力	无原生功能	支持	支持	支持（HubSpot meetings）	无原生功能	无原生功能

Step 3 — Platform-specific guidance

步骤3：特定平台专属指导

In Brevo

Brevo平台

Product: Brevo Conversations — live chat + chatbot included in all Brevo plans
Widget: Install JavaScript snippet on your website
Chatbot: Automated messages triggered by page URL, time on page, visitor behavior
Agent management: Set online/offline status, assign visitors to groups
API: REST API for sending messages, managing automated messages, visitor assignment
Strength: Included free with Brevo — no separate chat tool needed. Chat contacts sync to Brevo contact database automatically. Good for teams already using Brevo for email/CRM.
Limitation: Less sophisticated chatbot flows than Drift or Intercom. No native meeting booking from chat.
Platform skill:
```
/sales-brevo
```

产品：Brevo Conversations——所有Brevo套餐都包含在线聊天+聊天机器人功能
组件：在你的网站上安装JavaScript代码片段即可
聊天机器人：可通过页面URL、页面停留时长、访客行为触发自动消息
坐席管理：设置在线/离线状态，将访客分配到不同分组
API：REST API支持发送消息、管理自动消息、分配访客
优势：Brevo套餐免费包含——无需额外采购聊天工具，聊天联系人会自动同步到Brevo联系人数据库，适合已经使用Brevo做邮件/CRM的团队
局限性：聊天机器人流程不如Drift或Intercom复杂，没有原生的聊天内会议预约功能
平台专属技能：
```
/sales-brevo
```

In Drift (Salesloft)

Drift (Salesloft)平台

Product: Drift is now part of Salesloft — enterprise conversational sales platform
Playbooks: Visual chatbot builder with qualification logic, routing, and meeting booking
AI: Drift AI chatbot handles conversations when agents are offline
Revenue routing: Route chats based on account data, deal size, territory
Strength: Best for enterprise B2B sales with complex routing needs. Deep Salesforce integration.
Limitation: Expensive — enterprise pricing only. Overkill for SMB.
Platform skill:
```
/sales-salesloft
```

产品：Drift现在属于Salesloft——企业级对话式销售平台
剧本模板：可视化聊天机器人搭建器，支持定级逻辑、路由、会议预约
AI能力：Drift AI聊天机器人可在坐席离线时处理对话
营收路由：可基于客户数据、交易规模、区域分配聊天
优势：最适合有复杂路由需求的企业级B2B销售场景，与Salesforce深度集成
局限性：价格昂贵——仅提供企业级定价，对中小微企业来说功能过剩
平台专属技能：
```
/sales-salesloft
```

In Intercom

Intercom平台

Product: Customer messaging platform with chat, bots, help center
Fin AI: AI agent that resolves support questions and qualifies leads
Custom bots: Visual bot builder with conditional logic, API calls, and app integrations
Product Tours: Guide users through your product from chat
Strength: Best for product-led growth — combines support, sales, and onboarding in one tool. Strong for SaaS companies.
Limitation: Pricing scales with contacts/conversations — can get expensive.

产品：客户消息平台，包含聊天、机器人、帮助中心功能
Fin AI：AI Agent可解决支持问题并完成线索定级
自定义机器人：可视化机器人搭建器，支持条件逻辑、API调用、应用集成
产品引导：可通过聊天引导用户使用产品功能
优势：最适合产品驱动增长场景——在一个工具中整合了支持、销售、用户引导功能，非常适合SaaS公司
局限性：定价随联系人/对话量增长——成本可能会很高

In HubSpot

HubSpot平台

Product: Live chat and chatbots built into HubSpot CRM
Chatflows: Chatbot builder with branching logic, integrated with HubSpot CRM
Meeting booking: Native calendar integration — book meetings directly from chat
Free tier: Basic live chat included in HubSpot Free
Strength: Best if you're already in the HubSpot ecosystem. Seamless CRM integration.
Limitation: Advanced chatbot features require paid plans.

产品：在线聊天和聊天机器人内置在HubSpot CRM中
聊天流：聊天机器人搭建器支持分支逻辑，与HubSpot CRM深度集成
会议预约：原生日历集成——可直接在聊天中预约会议
免费 tier：HubSpot免费版包含基础在线聊天功能
优势：如果你已经在使用HubSpot生态是最优选择，CRM集成无缝
局限性：高级聊天机器人功能需要付费套餐

In Crisp

Crisp平台

Product: Affordable multi-channel messaging (chat, email, SMS, WhatsApp)
Free tier: 2 agents, basic chat
Strength: Best value for SMBs — generous free tier, clean UI, multi-channel inbox.
Limitation: Less sophisticated automation and AI than enterprise tools.

产品：高性价比多渠道消息工具（聊天、邮件、SMS、WhatsApp）
免费 tier：支持2个坐席，基础聊天功能
优势：对中小微企业性价比最高——免费套餐额度充足，界面简洁，多渠道收件箱
局限性：自动化和AI能力不如企业级工具复杂

In GetResponse

GetResponse平台

GetResponse includes a basic live chat widget as part of its all-in-one marketing platform:

Chat widget: Embed on GetResponse landing pages or external websites. Captures visitor info for your contact list.
Automated greetings: Configure welcome messages triggered by page visit or time on page.
Contact capture: Chat conversations auto-create contacts in your GetResponse lists with conversation history.
Availability hours: Set online/offline status with appropriate messaging.
Available on all paid plans: No additional cost — included in Starter, Marketer, Creator, and MAX.
Limitation: Basic functionality compared to dedicated tools (Drift, Intercom, Crisp). No chatbot flow builder, no AI-powered responses, no advanced routing rules, no native meeting booking. Best for simple lead capture — use a dedicated chat tool for complex sales chat workflows.
Best for: GetResponse users who want basic website chat without adding another tool. Good for landing pages and simple lead qualification.
Platform skill:
```
/sales-getresponse
```

GetResponse的一体化营销平台包含基础在线聊天组件：

聊天组件：可嵌入GetResponse落地页或外部网站，自动获取访客信息存入你的联系人列表
自动问候：可配置基于页面访问或停留时长触发的欢迎消息
联系人归集：聊天对话会自动在GetResponse列表中创建联系人并附带对话历史
可用时长设置：设置在线/离线状态并匹配对应消息
所有付费套餐都可用：无额外费用——包含在Starter、Marketer、Creator和MAX套餐中
局限性：和专用工具（Drift、Intercom、Crisp）相比功能基础，没有聊天机器人流程搭建器、无AI回复、无高级路由规则、无原生会议预约，适合简单的线索获取场景——复杂销售聊天工作流建议使用专用聊天工具
最佳适用场景：不想额外增加工具，只需要基础网站聊天功能的GetResponse用户，适合落地页和简单线索定级场景
平台专属技能：
```
/sales-getresponse
```

In ZoomInfo (Chat)

ZoomInfo (Chat)平台

Visitor identification — ZoomInfo Chat identifies anonymous visitors using WebSights (IP-to-company matching) and enriches them with firmographic data before the conversation starts
Smart routing — route conversations to the right sales rep based on account ownership, territory, or firmographic criteria. High-value accounts get human reps; others get bot.
Chatbot — automated conversations triggered by visitor firmographics (e.g., show different bot flows for enterprise vs SMB visitors)
Meeting booking — let qualified visitors book meetings directly from chat, synced to rep calendars
Data enrichment — even if a visitor doesn't chat, WebSights captures their company info for follow-up
Integration — chat transcripts and visitor data sync to Salesforce, HubSpot, and ZoomInfo CRM records
Advantage — ZoomInfo Chat knows WHO is visiting (company, size, industry) before the chat starts, enabling personalized experiences. Most chat tools only see anonymous visitors until they self-identify.

访客识别——ZoomInfo Chat通过WebSights（IP转公司匹配）识别匿名访客，在对话开始前就补充完整公司属性数据
智能路由——可基于客户归属、区域、公司属性将对话分配给合适的销售代表，高价值客户对接人工坐席，其他客户对接机器人
聊天机器人——可基于访客公司属性触发自动对话（比如给企业客户和中小微客户展示不同的机器人流程）
会议预约——让合格访客直接在聊天中预约会议，同步到销售代表日历
数据补全——即使访客没有发起聊天，WebSights也会捕获其公司信息用于后续跟进
集成能力——聊天记录和访客数据同步到Salesforce、HubSpot和ZoomInfo CRM记录
优势：ZoomInfo Chat在聊天开始前就知道访客身份（公司、规模、行业），可提供个性化体验，大多数聊天工具只能看到匿名访客，直到访客主动提供信息

In SendPulse

SendPulse平台

SendPulse offers a full-featured live chat solution as part of its multi-channel marketing platform:

Website chat widget: Customizable appearance and colors to match your brand. Pre-chat form captures visitor details before the conversation starts.
Unified inbox: Conversations from Telegram, Facebook, WhatsApp, Instagram, Viber, and your website chat all appear in a single panel — agents never have to switch between apps.
Bot-to-human handoff: SendPulse chatbots can handle initial qualification and transfer to a live agent seamlessly when the visitor needs human help.
Canned responses: Pre-written quick replies for common questions — speeds up agent response time.
Visitor info panel: Agents see pages viewed, location, and device info alongside the conversation for better context.
Business hours: Configure online/offline hours. When agents are unavailable, an offline form collects messages for follow-up.
Mobile app: Agents can respond from iOS or Android — useful for small teams without a dedicated support desk.
Free plan: Live chat is included on SendPulse's free plan, making it accessible for startups and solopreneurs.
Best for: Teams already using SendPulse for email or chatbots who want unified multi-channel conversations without adding a separate chat tool.
Platform skill:
```
/sales-sendpulse
```

SendPulse的多渠道营销平台提供功能完整的在线聊天解决方案：

网站聊天组件：外观和颜色可自定义匹配品牌，预聊天表单可在对话开始前获取访客信息
统一收件箱：来自Telegram、Facebook、WhatsApp、Instagram、Viber和网站聊天的对话都展示在同一个面板中——坐席无需切换应用
机器人转人工：SendPulse聊天机器人可处理初始定级，当访客需要人工帮助时无缝转接给人工坐席
预设回复：常见问题的预制快速回复——加快坐席响应速度
访客信息面板：坐席可在对话旁查看访客浏览的页面、地理位置、设备信息，获取更多上下文
营业时间设置：配置在线/离线时长，坐席不可用时通过离线表单收集消息用于后续跟进
移动端应用：坐席可通过iOS或Android端回复消息——适合没有专属服务台的小团队
免费套餐：SendPulse免费套餐包含在线聊天功能，创业公司和个体经营者都可使用
最佳适用场景：已经在使用SendPulse做邮件或聊天机器人，不想额外增加工具就需要统一多渠道对话能力的团队
平台专属技能：
```
/sales-sendpulse
```

In LiveChat / Zendesk / Tidio / Freshdesk

LiveChat / Zendesk / Tidio / Freshdesk平台

LiveChat: Support-focused with ticketing integration. Good for support teams.
Zendesk Chat: Part of Zendesk Suite — best if you're already on Zendesk for support.
Tidio: Affordable with AI chatbot (Lyro). Good for e-commerce.
Freshdesk/Freshchat: Part of Freshworks — good for support-first teams with sales needs.

LiveChat：侧重支持场景，集成工单系统，适合支持团队
Zendesk Chat：属于Zendesk套件——如果你已经在使用Zendesk做支持是最优选择
Tidio：高性价比，自带AI聊天机器人（Lyro），适合电商场景
Freshdesk/Freshchat：属于Freshworks套件——适合以支持为核心、同时有销售需求的团队

Step 4 — Actionable guidance

步骤4：可落地指导

Implementation checklist

落地检查清单

Install widget — add JavaScript snippet to your website (usually 1 line in
```
<head>
```
)
Brand it — match colors, logo, welcome message to your site
Set business hours — configure online/offline hours with appropriate messaging
Build qualification bot — create a 2-3 question flow for when agents are busy/offline
Set up routing — assign chats by page, visitor segment, or round-robin
Connect CRM — push qualified leads to your CRM automatically
Add to high-intent pages — pricing, demo, trial, comparison pages
Train agents — response templates, qualification criteria, escalation paths
Measure — track chat volume, response time, conversion rate, CSAT

安装组件——将JavaScript代码片段添加到你的网站（通常是
```
<head>
```
中的一行代码）
品牌定制——调整颜色、logo、欢迎消息匹配你的站点风格
设置营业时间——配置在线/离线时长并匹配对应提示消息
搭建定级机器人——创建2-3个问题的流程，用于坐席忙碌/离线时接待访客
配置路由规则——按页面、访客分组或轮询分配聊天
打通CRM——自动将合格线索同步到你的CRM
部署到高意向页面——定价页、演示页、试用页、对比页
培训坐席——统一回复模板、定级标准、升级路径
数据衡量——追踪聊天量、响应时间、转化率、CSAT

Key metrics

核心指标

Metric	Benchmark	What it tells you
Chat-to-lead rate	10-30%	How well chat qualifies visitors
First response time	< 30 seconds	Agent availability and speed
Resolution time	< 5 minutes (sales)	Efficiency of conversations
CSAT	> 85%	Quality of chat interactions
Meeting booked rate	5-15% of chats	Chat-to-pipeline conversion

指标	基准值	代表含义
聊天转线索率	10-30%	聊天对访客的定级效果
首次响应时间	< 30秒	坐席可用性和响应速度
解决时长	< 5分钟（销售场景）	对话效率
CSAT	> 85%	聊天交互质量
会议预约率	占聊天量的5-15%	聊天转销售管道的转化效果

Gotchas

注意事项

Don't pop up chat on every page — aggressive chat popups annoy visitors. Target high-intent pages only (pricing, demo, trial). Use passive widget on other pages.
Don't build a 10-question chatbot — long qualification flows have high drop-off. 2-3 questions max before routing to a human or offering to book a meeting.
Don't forget offline hours — if no agents are online and no chatbot is configured, visitors see a dead chat widget. Always have an offline message or email capture form.
Don't ignore mobile — chat widgets can obscure content on mobile. Test the experience on small screens and consider hiding or minimizing the widget on mobile.
Don't skip CRM integration — chat leads that don't get pushed to CRM get forgotten. Always connect chat to your lead management system.

不要在每个页面都弹出聊天窗口——过于激进的聊天弹窗会惹恼访客，仅在高意向页面（定价、演示、试用）使用主动弹窗，其他页面使用被动组件
不要设计10个问题的聊天机器人流程——过长的定级流程流失率很高，最多2-3个问题，之后要么转人工要么提供会议预约选项
不要忽略离线场景——如果没有坐席在线也没有配置聊天机器人，访客会看到无法使用的聊天组件，始终要设置离线消息或邮箱收集表单
不要忽略移动端体验——聊天组件可能会遮挡移动端的内容，要在小屏幕上测试体验，考虑在移动端隐藏或最小化组件
不要跳过CRM集成——不同步到CRM的聊天线索很容易被遗忘，始终要将聊天工具和你的线索管理系统打通

Related skills

Examples

示例

Example 1: Setting up sales chat on pricing page

示例1：在定价页搭建销售聊天

User says: "I want to add live chat on our pricing page to catch buyers who are comparing plans" Skill does: Recommends proactive chat trigger (15 seconds on pricing page), qualification bot (company size, use case, timeline), routing to AE, and CRM push. Provides implementation steps for the user's chosen platform. Result: Chat widget on pricing page with qualification flow, agent routing, and CRM integration

用户需求：“我想在我们的定价页添加在线聊天，获取正在对比方案的买家” 技能输出：推荐主动聊天触发规则（在定价页停留15秒触发）、定级机器人（公司规模、使用场景、 timeline）、路由给客户成功经理、同步到CRM，提供用户所选平台的落地步骤结果：定价页的聊天组件具备定级流程、坐席路由、CRM集成能力

Example 2: Building a lead qualification chatbot

示例2：搭建线索定级聊天机器人

User says: "We need a chatbot that qualifies visitors and books demos when our team is offline" Skill does: Designs a 3-step bot flow (greeting → 2 qualifying questions → meeting booking or email capture). Covers offline handling, calendar integration, and fallback paths. Result: Chatbot flow that qualifies and books meetings 24/7

用户需求：“我们需要一个聊天机器人，在团队离线时完成访客定级并预约演示” 技能输出：设计3步机器人流程（问候→2个定级问题→预约会议或收集邮箱），覆盖离线处理、日历集成、 fallback路径结果：聊天机器人流程可7*24小时完成定级和会议预约

Example 3: Choosing a chat tool

示例3：选择聊天工具

User says: "We're a 10-person SaaS company using HubSpot CRM. Should we use HubSpot chat or Intercom?" Skill does: Compares HubSpot native chat (free, CRM-integrated, basic bot) vs Intercom (more powerful bot, product tours, but expensive). Recommends HubSpot chat to start, upgrade to Intercom if they outgrow it. Result: Clear recommendation with reasoning and migration path

用户需求：“我们是10人的SaaS公司，正在使用HubSpot CRM，应该用HubSpot chat还是Intercom？” 技能输出：对比HubSpot原生聊天（免费、CRM集成、基础机器人）和Intercom（更强大的机器人、产品引导、但价格高），推荐先使用HubSpot chat，功能不够用再升级到Intercom 结果：清晰的推荐，附带理由和迁移路径

Troubleshooting

故障排查

Chat widget not appearing

聊天组件不显示

Symptom: Widget doesn't show up on the website after installation Cause: JavaScript snippet not loaded, ad blockers, content security policy, or conditional display rules Solution: 1) Check browser console for JS errors. 2) Verify the snippet is in

<head>

<body>

. 3) Test in incognito mode (ad blockers). 4) Check CSP headers allow the chat provider's domain. 5) Review display rules — the widget may be hidden on certain pages.

症状：安装后网站上没有出现聊天组件原因：JavaScript代码片段未加载、广告拦截器拦截、内容安全策略限制、条件展示规则配置错误 解决方案：1) 检查浏览器控制台的JS错误；2) 确认代码片段已添加到

<head>

或

<body>

中；3) 在无痕模式下测试（排除广告拦截器影响）；4) 检查CSP头是否允许聊天服务商的域名；5) 检查展示规则——组件可能在特定页面被隐藏

Low chat engagement

聊天参与度低

Symptom: Widget is live but very few visitors start conversations Cause: Widget is too passive, on wrong pages, or proactive messages aren't compelling Solution: 1) Add proactive messages on high-intent pages (pricing, demo). 2) Make the greeting contextual to the page. 3) Use a chatbot to initiate with a question, not just "Hi!" 4) Test button placement and color contrast.

症状：组件正常运行，但很少有访客发起对话原因：组件过于被动、部署页面不对、主动消息没有吸引力 解决方案：1) 在高意向页面（定价、演示）添加主动消息；2) 使用和页面上下文匹配的问候语；3) 用聊天机器人主动抛出问题，而不是只说“您好！”；4) 测试按钮位置和颜色对比度

Chat leads not reaching CRM

聊天线索没有同步到CRM

Symptom: Conversations happen but leads don't appear in CRM Cause: Integration not configured, mapping incorrect, or webhook failures Solution: 1) Verify CRM integration is active in chat tool settings. 2) Check field mapping (email, name, company → CRM fields). 3) Test with a known lead and trace through both systems. 4) Check webhook/API logs for errors.

症状：有对话产生，但CRM中没有出现对应线索原因：集成未配置、字段映射错误、webhook失败 解决方案：1) 确认聊天工具设置中CRM集成已激活；2) 检查字段映射（邮箱、姓名、公司→CRM字段）；3) 用已知测试线索跑通全流程校验两个系统的数据；4) 检查webhook/API日志中的错误