gladly
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseGladly Skill
Gladly Skill
Manage customer service with Gladly's people-centered support platform.
借助Gladly以人为本的支持平台管理客户服务。
Quick Install
快速安装
bash
curl -sSL https://canifi.com/skills/gladly/install.sh | bashOr manually:
bash
cp -r skills/gladly ~/.canifi/skills/bash
curl -sSL https://canifi.com/skills/gladly/install.sh | bash或者手动安装:
bash
cp -r skills/gladly ~/.canifi/skills/Setup
设置
Configure via canifi-env:
bash
undefined通过canifi-env进行配置:
bash
undefinedFirst, ensure canifi-env is installed:
首先,确保已安装canifi-env:
curl -sSL https://canifi.com/install.sh | bash
curl -sSL https://canifi.com/install.sh | bash
canifi-env set GLADLY_API_TOKEN "your_api_token"
canifi-env set GLADLY_ORGANIZATION "your_organization"
undefinedcanifi-env set GLADLY_API_TOKEN "your_api_token"
canifi-env set GLADLY_ORGANIZATION "your_organization"
undefinedPrivacy & Authentication
隐私与认证
Your credentials, your choice. Canifi LifeOS respects your privacy.
您的凭据,您做主。 Canifi LifeOS尊重您的隐私。
Option 1: Manual Browser Login (Recommended)
选项1:手动浏览器登录(推荐)
If you prefer not to share credentials with Claude Code:
- Complete the Browser Automation Setup using CDP mode
- Login to the service manually in the Playwright-controlled Chrome window
- Claude will use your authenticated session without ever seeing your password
如果您不想与Claude Code共享凭据:
- 使用CDP模式完成浏览器自动化设置
- 在Playwright控制的Chrome窗口中手动登录服务
- Claude将使用您的已认证会话,全程不会获取您的密码
Option 2: Environment Variables
选项2:环境变量
If you're comfortable sharing credentials, you can store them locally:
bash
canifi-env set SERVICE_EMAIL "your-email"
canifi-env set SERVICE_PASSWORD "your-password"Note: Credentials stored in canifi-env are only accessible locally on your machine and are never transmitted.
如果您愿意共享凭据,可以将其存储在本地:
bash
canifi-env set SERVICE_EMAIL "your-email"
canifi-env set SERVICE_PASSWORD "your-password"注意:存储在canifi-env中的凭据仅能在您的本地机器上访问,绝不会被传输。
Capabilities
功能
- Customer Timeline: View complete customer history in single view
- Omnichannel Support: Handle voice, email, chat, SMS, and social
- Task Management: Create and manage follow-up tasks
- Knowledge Management: Access and share help content
- Workforce Management: Manage agent schedules and capacity
- 客户时间线:在单一视图中查看完整的客户历史记录
- 全渠道支持:处理语音、邮件、聊天、短信和社交媒体渠道
- 任务管理:创建并管理跟进任务
- 知识管理:访问并共享帮助内容
- 劳动力管理:管理坐席日程和工作容量
Usage Examples
使用示例
View Customer
查看客户信息
User: "Show me the Gladly timeline for john@customer.com"
Assistant: Returns complete customer interaction history用户:"帮我查看john@customer.com的Gladly时间线"
助手:返回完整的客户交互历史Create Conversation
创建对话
User: "Start a new conversation with customer about order issue"
Assistant: Creates conversation with customer context用户:"启动与客户关于订单问题的新对话"
助手:创建包含客户上下文的对话Add Task
添加任务
User: "Create a follow-up task for the VIP customer inquiry"
Assistant: Creates task linked to conversation用户:"为VIP客户的咨询创建跟进任务"
助手:创建关联对话的任务Search Customers
搜索客户
User: "Find all Gladly customers with VIP status"
Assistant: Searches and returns matching customers用户:"查找所有拥有VIP身份的Gladly客户"
助手:搜索并返回匹配的客户Authentication Flow
认证流程
- Get API token from Gladly admin settings
- Use Basic Auth with token
- Organization-specific endpoints
- SSO available for agents
- 从Gladly管理员设置中获取API令牌
- 使用令牌进行基础认证
- 组织专属的端点
- 坐席可使用单点登录(SSO)
Error Handling
错误处理
| Error | Cause | Solution |
|---|---|---|
| 401 Unauthorized | Invalid token | Verify API token |
| 403 Forbidden | Insufficient permissions | Check admin access |
| 404 Not Found | Customer not found | Verify customer ID |
| 429 Rate Limited | Too many requests | Implement backoff |
| 错误 | 原因 | 解决方案 |
|---|---|---|
| 401 未授权 | 令牌无效 | 验证API令牌 |
| 403 禁止访问 | 权限不足 | 检查管理员权限 |
| 404 未找到 | 客户不存在 | 验证客户ID |
| 429 请求受限 | 请求过于频繁 | 实现退避机制 |
Notes
注意事项
- People-centered, not ticket-centered
- Single customer timeline view
- Voice support built-in
- AI-powered agent assist
- Hero (agent) empowerment focus
- Enterprise-grade platform
- 以人为本,而非以工单为中心
- 单一客户时间线视图
- 内置语音支持
- AI驱动的坐席辅助
- 聚焦赋能坐席(Hero)
- 企业级平台