Auto-sync: 2026-04-17 14:18
This commit is contained in:
51
wiki/sources/event-guest-confirmation.md
Normal file
51
wiki/sources/event-guest-confirmation.md
Normal file
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: "Event Guest Confirmation"
|
||||
type: source
|
||||
tags: [agent-use-case, openclaw, voice-agent, automation]
|
||||
date: 2026-04-17
|
||||
---
|
||||
|
||||
## Source File
|
||||
- [[raw/Agent/usecases/event-guest-confirmation.md]]
|
||||
|
||||
## Summary
|
||||
- 核心主题:AI Agent 自动外呼确认活动宾客出席
|
||||
- 问题域:活动管理、宾客通知、人工外呼效率低
|
||||
- 方法/机制:使用 SuperCall 语音代理逐个呼叫宾客,收集出席状态和特殊需求,汇总生成报告
|
||||
- 结论/价值:替代人工逐一致电确认,大幅提升效率,同时保持高响应率
|
||||
|
||||
## Key Claims
|
||||
- 人工致电 20+ 宾客确认出席效率低,存在电话追踪、记录遗漏问题
|
||||
- 真实电话沟通比短信具有更高响应率
|
||||
- SuperCall 作为独立语音代理,具有安全隔离特性,适合批量外呼场景
|
||||
- 每次通话后记录结果,全部完成后生成汇总报告
|
||||
|
||||
## Key Quotes
|
||||
> "Texting works sometimes, but people ignore messages. A real phone call gets a much higher response rate."
|
||||
> — 文档解释了为何选择电话而非短信通知
|
||||
|
||||
> "The AI persona on the call only has access to the context you provide (the persona name, the goal, and the opening line). It cannot access your gateway agent, your files, your other tools, or anything else."
|
||||
> — SuperCall 安全隔离特性说明
|
||||
|
||||
## Key Concepts
|
||||
- [[Voice Agent]]:具备语音交互能力的 AI 代理
|
||||
- [[Guest Confirmation]]:活动前确认宾客出席状态的工作流
|
||||
- [[Outbound Call]]:主动外呼而非接听来电
|
||||
- [[Persona Isolation]]:每次通话独立上下文,防止信息泄露
|
||||
|
||||
## Key Entities
|
||||
- [[OpenClaw]]:AI Agent 管理工具,用于协调任务执行
|
||||
- [[SuperCall]]:OpenClaw 插件,独立语音代理
|
||||
- [[Twilio]]:电话服务提供商,提供外呼能力
|
||||
- [[OpenAI]]:GPT-4o Realtime 语音 AI 提供商
|
||||
- [[ngrok]]:Webhook 隧道服务,用于外呼回调
|
||||
|
||||
## Connections
|
||||
- [[OpenClaw]] ← uses ← [[SuperCall]]
|
||||
- [[SuperCall]] ← depends_on ← [[Twilio]]
|
||||
- [[SuperCall]] ← depends_on ← [[OpenAI]]
|
||||
- [[SuperCall]] ← depends_on ← [[ngrok]]
|
||||
- [[Event Guest Confirmation]] ← implements ← [[Voice Agent]]
|
||||
|
||||
## Contradictions
|
||||
- (暂无)
|
||||
58
wiki/sources/multi-channel-assistant.md
Normal file
58
wiki/sources/multi-channel-assistant.md
Normal file
@@ -0,0 +1,58 @@
|
||||
---
|
||||
title: Multi-Channel Assistant
|
||||
type: source
|
||||
tags: []
|
||||
date: 2025-04-17
|
||||
---
|
||||
|
||||
## Source File
|
||||
- [[raw/Agent/usecases/multi-channel-assistant.md]]
|
||||
|
||||
## Summary
|
||||
|
||||
核心主题:AI 助手通过多渠道整合实现任务、日程、消息和提醒的统一管理。
|
||||
|
||||
问题域:跨应用工作流繁琐,用户需要在不同工具间切换。
|
||||
|
||||
方法论:通过单一 AI 助手接口,基于主题/工具类型路由请求到对应的外部服务。
|
||||
|
||||
结论:实现效率提升和上下文切换成本降低。
|
||||
|
||||
## Key Claims
|
||||
|
||||
- Multi-Channel Personal Assistant(多渠道助手)通过单一 AI 界面解决应用切换疲劳问题
|
||||
- 基于 Telegram Topic 实现主题隔离和上下文管理
|
||||
- 整合 Slack 用于团队协作和知识库触发
|
||||
- Google Workspace 提供日历、邮件、Drive 任务执行
|
||||
- Todoist 快速捕获待办事项
|
||||
- Asana 项目管理
|
||||
- 自动化提醒(定时任务触发)
|
||||
|
||||
## Key Quotes
|
||||
|
||||
> "Context-switching between apps to manage tasks, schedule events, send messages, and track work is exhausting.
|
||||
|
||||
## Key Concepts
|
||||
|
||||
- [[Multi-Channel Personal Assistant]]
|
||||
- [[Telegram Topic]]
|
||||
- [[Slack Integration]]
|
||||
- [[Google Workspace]]
|
||||
- [[Todoist API]]
|
||||
- [[Asana API]]
|
||||
- Multi-Channel AI Workflow
|
||||
|
||||
## Key Entities
|
||||
|
||||
- Telegram: 核心接口
|
||||
- Slack: 团队协作工具
|
||||
- Google Workspace: 企业工具套件
|
||||
- Todoist: 任务捕获
|
||||
- Asana: 项目管理
|
||||
|
||||
## Connections
|
||||
|
||||
- Telegram ← routes_to → Slack
|
||||
- Telegram ← routes_to → Google Workspace
|
||||
- Telegram ← routes_to → Todoist
|
||||
- Telegram ← routes_to → Asana
|
||||
Reference in New Issue
Block a user