Update nexus: fix conflicts and sync local changes
This commit is contained in:
@@ -1,46 +1,46 @@
|
||||
---
|
||||
title: "Report Distribution Agent"
|
||||
type: source
|
||||
tags: []
|
||||
date: 2026-04-25
|
||||
---
|
||||
|
||||
## Source File
|
||||
- [[raw/Agent/agency-agents/specialized/report-distribution-agent.md]]
|
||||
|
||||
## Summary(用中文描述)
|
||||
- 核心主题:销售报告自动分发 AI Agent,专为 STGCRM 系统设计
|
||||
- 问题域:企业销售团队需要按时、按区域将合并报告精准送达对应业务员和管理层
|
||||
- 方法/机制:基于区域参数路由 + SMTP 邮件发送 + 全程分发日志审计
|
||||
- 结论/价值:实现 99%+ 定时送达率,零错误区域分发,完全可追溯的分发历史
|
||||
|
||||
## Key Claims(用中文描述)
|
||||
- Report Distribution Agent 通过区域路由确保每个业务员仅接收其负责区域的数据
|
||||
- 管理员和经理接收公司级汇总报告,而非区域明细
|
||||
- 每次分发尝试均记录状态(sent/failed)和时间戳,支撑合规审计
|
||||
- 每日报告于工作日 8:00 AM 发送,每周汇总于周一 7:00 AM 发送
|
||||
- 发送失败时记录错误并继续分发,不中断其他接收者
|
||||
|
||||
## Key Quotes
|
||||
> "You are the Report Distribution Agent — a reliable communications coordinator who ensures the right reports reach the right people at the right time." — Agent 身份定义
|
||||
> "Territory-based routing: reps only receive reports for their assigned territory" — 核心路由规则
|
||||
> "Graceful failures: log errors per recipient, continue distributing to others" — 容错设计
|
||||
|
||||
## Key Concepts
|
||||
- [[Territory Routing]]:基于销售区域参数进行路由分发,每个业务员仅接收其分配区域的数据报告
|
||||
- [[SMTP Transport]]:通过 SMTP 协议传输 HTML 格式邮件报告的底层技术机制
|
||||
- [[Audit Trail]]:分发日志记录,含接收人、区域、状态、时间戳,支持合规查询
|
||||
- [[Scheduled Distribution]]:定时任务触发机制(工作日 8:00 AM / 周一 7:00 AM),支持手动按需分发
|
||||
|
||||
## Key Entities
|
||||
- [[Data Consolidation Agent]]:为 Report Distribution Agent 提供区域报告和公司汇总报告的数据来源
|
||||
- [[STGCRM]]:该 Agent 所服务的企业 CRM 系统品牌,提供区域分配数据和邮件路由规则
|
||||
|
||||
## Connections
|
||||
- [[Data Consolidation Agent]] ← feeds_data ← [[Report Distribution Agent]]
|
||||
- [[Report Distribution Agent]] ← distributes_to ← [[Sales Representative]]
|
||||
- [[Report Distribution Agent]] ← audit_trail ← [[Compliance System]]
|
||||
|
||||
## Contradictions
|
||||
- 与 [[Sales Data Extraction Agent]]:Sales Data Extraction Agent 负责原始销售数据提取,Report Distribution Agent 负责报告分发;两者在数据管道中为上下游关系,不存在冲突
|
||||
|
||||
---
|
||||
title: "Report Distribution Agent"
|
||||
type: source
|
||||
tags: []
|
||||
date: 2026-04-25
|
||||
---
|
||||
|
||||
## Source File
|
||||
- [[raw/Agent/agency-agents/specialized/report-distribution-agent.md]]
|
||||
|
||||
## Summary(用中文描述)
|
||||
- 核心主题:销售报告自动分发 AI Agent,专为 STGCRM 系统设计
|
||||
- 问题域:企业销售团队需要按时、按区域将合并报告精准送达对应业务员和管理层
|
||||
- 方法/机制:基于区域参数路由 + SMTP 邮件发送 + 全程分发日志审计
|
||||
- 结论/价值:实现 99%+ 定时送达率,零错误区域分发,完全可追溯的分发历史
|
||||
|
||||
## Key Claims(用中文描述)
|
||||
- Report Distribution Agent 通过区域路由确保每个业务员仅接收其负责区域的数据
|
||||
- 管理员和经理接收公司级汇总报告,而非区域明细
|
||||
- 每次分发尝试均记录状态(sent/failed)和时间戳,支撑合规审计
|
||||
- 每日报告于工作日 8:00 AM 发送,每周汇总于周一 7:00 AM 发送
|
||||
- 发送失败时记录错误并继续分发,不中断其他接收者
|
||||
|
||||
## Key Quotes
|
||||
> "You are the Report Distribution Agent — a reliable communications coordinator who ensures the right reports reach the right people at the right time." — Agent 身份定义
|
||||
> "Territory-based routing: reps only receive reports for their assigned territory" — 核心路由规则
|
||||
> "Graceful failures: log errors per recipient, continue distributing to others" — 容错设计
|
||||
|
||||
## Key Concepts
|
||||
- [[Territory Routing]]:基于销售区域参数进行路由分发,每个业务员仅接收其分配区域的数据报告
|
||||
- [[SMTP Transport]]:通过 SMTP 协议传输 HTML 格式邮件报告的底层技术机制
|
||||
- [[Audit Trail]]:分发日志记录,含接收人、区域、状态、时间戳,支持合规查询
|
||||
- [[Scheduled Distribution]]:定时任务触发机制(工作日 8:00 AM / 周一 7:00 AM),支持手动按需分发
|
||||
|
||||
## Key Entities
|
||||
- [[Data Consolidation Agent]]:为 Report Distribution Agent 提供区域报告和公司汇总报告的数据来源
|
||||
- [[STGCRM]]:该 Agent 所服务的企业 CRM 系统品牌,提供区域分配数据和邮件路由规则
|
||||
|
||||
## Connections
|
||||
- [[Data Consolidation Agent]] ← feeds_data ← [[Report Distribution Agent]]
|
||||
- [[Report Distribution Agent]] ← distributes_to ← [[Sales Representative]]
|
||||
- [[Report Distribution Agent]] ← audit_trail ← [[Compliance System]]
|
||||
|
||||
## Contradictions
|
||||
- 与 [[Sales Data Extraction Agent]]:Sales Data Extraction Agent 负责原始销售数据提取,Report Distribution Agent 负责报告分发;两者在数据管道中为上下游关系,不存在冲突
|
||||
|
||||
|
||||
Reference in New Issue
Block a user