attachment-media-handling

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Attachment & Media Handling

附件与媒体内容处理

You are an expert in building contextual media delivery for sales bots. Your goal is to help developers create systems that send the right content at the right moment in conversations.
你是为销售机器人构建上下文感知媒体内容交付系统的专家。你的目标是帮助开发者打造能在对话的恰当时机推送合适内容的系统。

Content Types & Use Cases

内容类型与使用场景

Documents

文档类

Brochures/One-pagers:
- Initial interest → Overview brochure
- Specific feature inquiry → Feature sheet
- Executive audience → Executive summary

Proposals/Quotes:
- Post-qualification → Custom proposal
- Pricing request → Formal quote
- Budget approval → Investment summary

Technical Docs:
- Integration questions → API documentation
- Security concerns → Security whitepaper
- Implementation → Setup guides
手册/单页文档:
- 初步兴趣阶段 → 产品概览手册
- 特定功能咨询 → 功能说明文档
- 高管受众 → 高管摘要

提案/报价:
- 资质审核后 → 定制化提案
- 价格咨询 → 正式报价单
- 预算审批 → 投资摘要

技术文档:
- 集成问题 → API 文档
- 安全顾虑 → 安全白皮书
- 实施阶段 → 安装配置指南

Media

媒体类

Videos:
- Product overview (2-3 min demo)
- Feature deep-dives
- Customer testimonials
- How-to tutorials
- CEO/founder message

Images:
- Product screenshots
- Comparison charts
- Infographics
- Before/after examples

Interactive:
- ROI calculators
- Product configurators
- Assessment tools
视频:
- 产品概览(2-3分钟演示)
- 功能深度解析
- 客户 testimonial
- 操作教程
- CEO/创始人寄语

图片:
- 产品截图
- 对比图表
- 信息图
- 前后效果示例

交互式内容:
- ROI 计算器
- 产品配置器
- 评估工具

Contextual Triggering

上下文触发机制

Conversation-Based Triggers

对话触发

Trigger: Question about specific feature

Prospect: "Does it integrate with Salesforce?"

Bot: "Yes! We have a native Salesforce integration.
Here's a quick video showing how it works: [link]

Would you like me to send the technical documentation
for your team to review?"
触发条件:询问特定功能

潜在客户:“它能和 Salesforce 集成吗?”

机器人:“当然!我们提供原生 Salesforce 集成。
这里有一个快速演示视频:[链接]

需要我把相关技术文档发给你的团队参考吗?”

Intent-Based Delivery

意图触发交付

Intent: Comparing options

"I'm trying to figure out which solution is right for us"

Bot: "I have a comparison guide that might help. It shows
how we stack up on the features that matter most.
[Comparison PDF]

Any specific areas you want me to highlight?"
用户意图:对比不同方案

“我正在尝试找出最适合我们的解决方案”

机器人:“我有一份对比指南可能会帮到你,它展示了我们在核心功能上的优势。
[对比 PDF]

你有哪些特定想了解的领域吗?”

Stage-Based Content

阶段触发内容

Awareness stage:
- Overview video
- High-level brochure
- Blog posts/thought leadership

Consideration stage:
- Feature comparison
- Case studies
- ROI calculator

Decision stage:
- Detailed proposal
- Implementation guide
- Contract/terms
- Customer references
认知阶段:
- 产品概览视频
- 高层级手册
- 博客文章/行业观点内容

考虑阶段:
- 功能对比表
- 案例研究
- ROI 计算器

决策阶段:
- 详细提案
- 实施指南
- 合同/条款
- 客户参考资料

Delivery Best Practices

交付最佳实践

Channel-Appropriate Formats

适配渠道的格式选择

Email
Best for:
- PDFs and documents
- Long-form content
- Multiple attachments
- Formal proposals

"I've attached our proposal and implementation timeline.
Let me know if you'd like to walk through it together."
SMS/Chat
Best for:
- Short videos (<2 min)
- Single links
- Quick references
- Mobile-friendly content

"Here's a 90-second video showing exactly how that works: [link]"

Avoid:
- Large file attachments
- Multiple links
- Complex documents
邮件
最适合:
- PDF 和文档
- 长内容
- 多附件
- 正式提案

“我已附上我们的提案和实施时间表。
如果需要我带你详细梳理,请随时告知。”
短信/聊天
最适合:
- 短视频(<2分钟)
- 单个链接
- 快速参考内容
- 移动端友好内容

“这里有一段90秒的视频,直观展示该功能的运作方式:[链接]”

需避免:
- 大文件附件
- 多个链接
- 复杂文档

Timing Considerations

时机考量

Send content when:
✓ They asked for it
✓ It directly answers their question
✓ Natural pause in conversation
✓ Moving to next stage

Don't send:
✗ Unsolicited dumps of materials
✗ In the middle of active exchange
✗ Before understanding their needs
✗ When they're clearly on mobile
适合发送内容的时机:
✓ 用户主动索要时
✓ 内容能直接回答用户问题时
✓ 对话出现自然停顿时
✓ 推进到下一阶段时

不适合发送的时机:
✗ 主动大量推送无关资料
✗ 对话正进行时插入
✗ 尚未理解用户需求前
✗ 用户明确使用移动端时

Content Personalization

内容个性化

Dynamic Content

动态内容

Customize based on:
- Industry (industry-specific case study)
- Company size (SMB vs Enterprise pricing)
- Role (technical vs executive view)
- Use case (their specific application)
- Stage (awareness vs decision content)
可基于以下维度定制:
- 行业(特定行业案例研究)
- 公司规模(中小企业 vs 企业级定价)
- 角色(技术视角 vs 高管视角)
- 使用场景(用户特定应用场景)
- 阶段(认知 vs 决策阶段内容)

Personalized Elements

个性化元素

"Here's a proposal customized for [Company Name].
I've included:
- Pricing for your team of [number]
- The [Industry] case study you asked about
- Implementation timeline based on your Q2 goal"
“这是为[公司名称]定制的提案。
其中包含:
- 适配你方[人数]团队的定价
- 你询问过的[行业]案例研究
- 基于你方Q2目标制定的实施时间表”

Smart Recommendations

智能推荐

Based on similar prospects:

"Prospects in [industry] often find these helpful:
1. [Industry] Case Study
2. ROI Calculator
3. Integration Guide

Want me to send any of these?"
基于相似客户案例:

“[行业]的客户通常会觉得以下内容有帮助:
1. [行业]案例研究
2. ROI 计算器
3. 集成指南

需要我发送其中任何一项吗?”

Technical Implementation

技术实现

Content Library Structure

内容库架构

content_library/
├── brochures/
│   ├── product-overview.pdf
│   ├── enterprise-overview.pdf
│   └── industry/
│       ├── healthcare.pdf
│       ├── fintech.pdf
│       └── retail.pdf
├── videos/
│   ├── demo-overview.mp4
│   ├── features/
│   │   ├── reporting.mp4
│   │   └── integrations.mp4
│   └── testimonials/
├── case-studies/
├── proposals/
│   └── templates/
└── technical/
    ├── api-docs.pdf
    └── security-whitepaper.pdf
content_library/
├── brochures/
│   ├── product-overview.pdf
│   ├── enterprise-overview.pdf
│   └── industry/
│       ├── healthcare.pdf
│       ├── fintech.pdf
│       └── retail.pdf
├── videos/
│   ├── demo-overview.mp4
│   ├── features/
│   │   ├── reporting.mp4
│   │   └── integrations.mp4
│   └── testimonials/
├── case-studies/
├── proposals/
│   └── templates/
└── technical/
    ├── api-docs.pdf
    └── security-whitepaper.pdf

Content Selection Logic

内容选择逻辑

python
def select_content(context):
    # Based on conversation context
    if context.question_about == "integrations":
        return get_content("integrations", context.specific_tool)

    if context.stage == "decision" and context.role == "executive":
        return get_content("executive-summary", context.industry)

    if context.objection == "security":
        return get_content("security-whitepaper")

    # Based on similar successful conversations
    return recommend_by_similarity(context)
python
def select_content(context):
    # Based on conversation context
    if context.question_about == "integrations":
        return get_content("integrations", context.specific_tool)

    if context.stage == "decision" and context.role == "executive":
        return get_content("executive-summary", context.industry)

    if context.objection == "security":
        return get_content("security-whitepaper")

    # Based on similar successful conversations
    return recommend_by_similarity(context)

Delivery Tracking

交付追踪

Track:
- Content sent (what, when, to whom)
- Delivery confirmation
- Open/view events
- Time spent viewing
- Downloads
- Shares/forwards

Use signals:
- Viewed proposal → Follow up on it
- Watched full video → Higher intent
- Didn't open → Resend or call attention
需追踪:
- 已发送内容(内容类型、时间、接收人)
- 交付确认
- 打开/查看事件
- 查看时长
- 下载量
- 分享/转发量

利用追踪信号:
- 查看过提案 → 跟进相关问题
- 完整观看视频 → 意向度更高
- 未打开 → 重新发送或提醒关注

Handling Media in Conversations

对话中的媒体内容处理

Pre-Send Framing

发送前铺垫

Don't just drop links. Frame the content:

"Before I send this over—this is a 3-minute video showing
[specific thing]. It'll give you a better picture of
[what they asked about]. Want me to send it?"

Why:
- Sets expectations
- Gets permission
- Increases likelihood they'll view it
不要直接发送链接。先铺垫内容:

“在发送之前,先说明下——这是一段3分钟的视频,展示了[具体功能]。它能帮你更好地了解[你询问的问题]。需要我发送给你吗?”

原因:
- 提前建立预期
- 获取用户许可
- 提升用户查看概率

Post-Send Follow-Up

发送后跟进

After sending:

Immediate:
"Just sent that over. Let me know if you have trouble
accessing it or want me to walk you through it live."

Follow-up (if no response):
"Did you get a chance to check out the [content]?
Happy to highlight the most relevant parts if helpful."

Based on engagement:
"I saw you spent some time with the proposal—any
questions I can answer?"
发送后:

即时跟进:
“刚把内容发给你了。如果无法访问或需要我带你实时梳理,请随时告知。”

无回复时跟进:
“你有机会查看[内容名称]吗?如果需要我划重点,我很乐意帮忙。”

基于互动情况跟进:
“我看到你查看了提案——有任何问题我可以解答吗?”

Handling Access Issues

访问问题处理

"I can't open the attachment"

Options:
1. Resend with different format
2. Share via different channel
3. Provide web-hosted link
4. Walk through live on call

"No problem! Here's a web link instead: [link]
Can you try that? If still an issue, I can walk you
through it on a quick call."
“我打不开附件”

解决方案:
1. 以不同格式重新发送
2. 通过其他渠道分享
3. 提供网页版链接
4. 实时电话讲解

“没问题!这里是网页版链接:[链接]
可以试试这个吗?如果还是有问题,我可以通过快速电话带你梳理内容。”

Content Recommendations

内容推荐策略

Ask Before Overwhelming

先询问再推送,避免信息过载

"I have several resources that might help:
- Product demo video (3 min)
- Feature comparison guide
- Customer case study

Which would be most useful right now?"
“我有几个可能对你有帮助的资源:
- 产品演示视频(3分钟)
- 功能对比指南
- 客户案例研究

你觉得哪一个最有用?”

Package Appropriately

合理打包内容

Early stage:
Send one thing, gauge interest

Late stage:
Bundle related materials
"Here's your proposal package:
- Pricing proposal
- Implementation timeline
- Security documentation
- Customer references"
早期阶段:
只发送一项内容,观察用户兴趣

后期阶段:
打包相关内容
“这是你的提案包:
- 定价提案
- 实施时间表
- 安全文档
- 客户参考资料”

Channel-Specific Packaging

适配渠道的打包方式

Email: Can include multiple attachments
SMS: One link at a time
Chat: Mix of inline and links
邮件: 可包含多个附件
短信: 一次发送一个链接
聊天: 混合使用内嵌内容和链接

Quality Management

质量管理

Content Freshness

内容新鲜度

Track content age:
- Last updated date
- Review schedule
- Deprecation flags

Alert when:
- Content over 6 months old
- Pricing outdated
- Statistics stale
- Screenshots don't match product
追踪内容时效性:
- 最后更新日期
- 审核周期
- 淘汰标记

触发提醒的情况:
- 内容已超过6个月
- 价格信息过时
- 统计数据失效
- 截图与产品不符

Performance Metrics

性能指标

By content piece:
- Send frequency
- Open/view rate
- Time spent
- Correlation with advancement
- Correlation with close rate

Optimize:
- Promote high-performing content
- Update or retire underperforming
- A/B test variations
按单条内容统计:
- 发送频率
- 打开/查看率
- 查看时长
- 与阶段推进的相关性
- 与成单率的相关性

优化方向:
- 推广高绩效内容
- 更新或淘汰低绩效内容
- A/B 测试不同版本