sales-verint

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Verint Open Platform Help

Verint开放平台帮助

Step 1 — Gather context

步骤1 — 收集上下文

references/learnings.md

exists, read it first for accumulated platform knowledge.

Which area?
- A) Da Vinci AI Bots (Quality Bot, Coaching Bot, Wrap Up Bot, etc.)
- B) Workforce Management (forecasting, scheduling, adherence)
- C) Quality Management (evaluations, scorecards)
- D) CX Analytics / Speech & Text Analytics
- E) Knowledge Automation
- F) IVA / Virtual Assistants
- G) Financial Compliance / Fraud & Security
- H) API / Developer Portal / Integration
- I) Calabrio migration / merger questions
- J) Not sure / general question
Deployment?
- A) Verint Cloud Platform
- B) On-premises / hybrid
- C) Calabrio ONE (now part of Verint)
- D) Not sure
What CCaaS/telephony?
- A) Amazon Connect
- B) Genesys Cloud CX
- C) NICE CXone
- D) Five9
- E) Cisco / Avaya / Mitel (on-prem)
- F) Twilio Flex
- G) Other / multiple

Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.

如果

references/learnings.md

文件存在，请先阅读以获取累积的平台知识。

涉及领域？
- A) Da Vinci AI机器人（Quality Bot、Coaching Bot、Wrap Up Bot等）
- B) 劳动力管理（预测、排班、合规）
- C) 质量管理（评估、评分卡）
- D) CX分析 / 语音与文本分析
- E) 知识自动化
- F) IVA / 虚拟助手
- G) 财务合规 / 欺诈与安全
- H) API / 开发者门户 / 集成
- I) Calabrio迁移 / 合并相关问题
- J) 不确定 / 一般性问题
部署方式？
- A) Verint云平台
- B) 本地部署 / 混合部署
- C) Calabrio ONE（现归属Verint）
- D) 不确定
使用的CCaaS/电话系统？
- A) Amazon Connect
- B) Genesys Cloud CX
- C) NICE CXone
- D) Five9
- E) Cisco / Avaya / Mitel（本地部署）
- F) Twilio Flex
- G) 其他 / 多个

跳过规则：如果用户的提示已包含足够上下文，直接跳至步骤2。

Step 2 — Route or answer directly

步骤2 — 路由或直接回答

Problem domain	Route to
Choosing between WEM/CCaaS vendors	`/sales-ccaas-selection {question}`
QA/coaching tool comparison across vendors	`/sales-coaching {question}`
Connecting Verint to CRM or CCaaS	`/sales-integration {question}`
Genesys Cloud CX-specific questions	`/sales-genesys {question}`
NICE CXone-specific questions	`/sales-nice-cxone {question}`
Talkdesk-specific questions	`/sales-talkdesk {question}`
Calabrio ONE-specific questions	`/sales-calabrio {question}`

If the question is about using Verint itself, continue to Step 3.

问题领域	路由至
在WEM/CCaaS供应商间做选择	`/sales-ccaas-selection {question}`
跨供应商QA/指导工具对比	`/sales-coaching {question}`
将Verint连接至CRM或CCaaS	`/sales-integration {question}`
Genesys Cloud CX专属问题	`/sales-genesys {question}`
NICE CXone专属问题	`/sales-nice-cxone {question}`
Talkdesk专属问题	`/sales-talkdesk {question}`
Calabrio ONE专属问题	`/sales-calabrio {question}`

如果问题是关于Verint平台本身的使用，请继续步骤3。

Step 3 — Verint platform reference

步骤3 — Verint平台参考

Read
references/platform-guide.md
for the full platform reference — Da Vinci AI bots, modules, integrations, API, pricing.

Answer the user's question using only the relevant section. Don't dump the full reference.

**阅读

references/platform-guide.md

**获取完整平台参考——Da Vinci AI机器人、模块、集成、API、定价。

仅使用相关部分回答用户问题，不要提供完整参考内容。

Step 4 — Actionable guidance

步骤4 — 可操作指导

Focus on the user's specific situation.

AI Bot issues: Check which Da Vinci bot applies, verify bot is enabled for the right queues/teams, review training data in Data Hub
WFM issues: Check forecast algorithm settings, shrinkage %, historical data quality, adherence thresholds
Quality Bot issues: Verify scoring rules, interaction scope, form assignment, compliance criteria
Performance issues: Reduce date ranges, filter by team, check concurrent user load, try off-peak hours
API issues: Verify developer portal access, API key permissions, check adaptors vs custom API

If you discover a gotcha, workaround, or tip not covered in

references/learnings.md

, append it there.

聚焦用户具体场景。

AI机器人问题：确认适用的Da Vinci机器人，验证机器人是否为正确队列/团队启用，查看Data Hub中的训练数据
WFM问题：检查预测算法设置、收缩率%、历史数据质量、合规阈值
Quality Bot问题：验证评分规则、交互范围、表单分配、合规标准
性能问题：缩小日期范围、按团队筛选、检查并发用户负载、尝试非高峰时段
API问题：验证开发者门户访问权限、API密钥权限、检查适配器与自定义API的区别

如果发现

references/learnings.md

未涵盖的注意事项、解决方案或技巧，将其添加到该文档中。

Gotchas

注意事项

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.

Steep learning curve — the platform is notoriously complex. Budget 2-4 weeks for admin training. Verint Academy exists but users report needing extensive self-directed learning beyond official materials.
Report latency and inconsistency — reporting tools are outdated and can produce conflicting numbers. Cross-queue analysis often requires running the same report multiple times and reconciling in Excel.
Support resolution times — bugs can take weeks or months to resolve. Document issues thoroughly and escalate via your account manager, not just the ticket queue.
Opaque pricing — no public pricing. Contracts are custom and highly negotiable. Get feature lists in writing during procurement — features promised by sales may not be in your purchased tier.
Calabrio acquisition (Feb 2026) — Verint acquired Calabrio. Existing Calabrio customers continue on Calabrio ONE. Da Vinci AI bots are being expanded to Calabrio customers. If you're on Calabrio, use
```
/sales-calabrio
```
for platform-specific help.
Mobile limitations — mobile experience is limited compared to desktop. Schedule changes and time-off requests work better via desktop.
Data privacy — there have been complaints about call recordings being used for AI training. Review your data processing agreement and opt-out options.

基于研究的最佳实践——请仔细查看，尤其是关于功能限制和集成注意事项的内容，这些信息可能已过时。

学习曲线陡峭——该平台以复杂著称，需预留2-4周的管理员培训时间。Verint Academy虽存在，但用户反馈除官方材料外，还需大量自主学习。
报告延迟与不一致——报告工具较为陈旧，可能产生不一致的数据。跨队列分析通常需要多次运行同一报告并在Excel中核对。
支持解决时长——漏洞可能需要数周或数月才能解决。请详细记录问题，并通过客户经理升级，而非仅提交工单队列。
定价不透明——无公开定价，合同为定制化且极具协商空间。采购时需以书面形式获取功能列表——销售承诺的功能可能不在您购买的套餐层级中。
Calabrio收购（2026年2月）——Verint收购了Calabrio。现有Calabrio客户继续使用Calabrio ONE。Da Vinci AI机器人正扩展至Calabrio客户。如果您使用Calabrio，请使用
```
/sales-calabrio
```
获取平台专属帮助。
移动端限制——与桌面端相比，移动端体验有限。排班变更和休假申请通过桌面端操作效果更佳。
数据隐私——有用户投诉通话录音被用于AI训练。请查看您的数据处理协议及退出选项。

Related skills

Examples

示例

User prompt: "Our Verint Quality Bot is only scoring 40% of interactions — should be 100%." Skill does: Walks through Quality Bot configuration — check scoring rule scope (queue/team filters), verify interactions are being recorded and available before the evaluation trigger fires, review rule syntax for overly narrow matching, check Data Hub data freshness.

User prompt: "We need to connect Verint WFM to our Genesys Cloud CX for real-time adherence." Skill does: Covers BYOT integration — built-in Genesys adaptor, ACD data flow configuration, real-time adherence monitoring setup, and common issues with multi-ACD environments.

User prompt: "Verint reports take 5+ minutes to load and the numbers don't match what we see in the dashboard." Skill does: Addresses known reporting limitations — reduce date range, filter to single team, check data pipeline latency between systems, export to Excel for cross-queue reconciliation.

用户提示："我们的Verint Quality Bot仅对40%的交互进行评分——应该是100%。" 技能操作：引导完成Quality Bot配置——检查评分规则范围（队列/团队筛选器）、验证交互是否已录制且在评估触发前可用、查看规则语法是否过于严格、检查Data Hub的数据新鲜度。

用户提示："我们需要将Verint WFM连接至Genesys Cloud CX以实现实时合规监控。" 技能操作：涵盖BYOT集成——内置Genesys适配器、ACD数据流配置、实时合规监控设置，以及多ACD环境中的常见问题。

用户提示："Verint报告加载需要5分钟以上，且数据与仪表盘显示不一致。" 技能操作：解决已知的报告限制——缩小日期范围、筛选至单个团队、在非高峰时段加载。对于跨队列分析，导出单独报告并在Excel中核对——平台本身不擅长处理跨队列聚合。

Troubleshooting

故障排查

Quality Bot scoring rules not triggering Verify rules are published (not draft), scoped to the correct queues/teams, and that interactions have completed recording before the scoring trigger fires. Check the Data Hub for data freshness — stale data means the bot has nothing to score. If using custom compliance criteria, test the rule against a known interaction to validate matching.

WFM forecast accuracy consistently off Check historical data weighting — Verint may be using outdated patterns. Verify shrinkage percentages, special day handling, and whether recent volume trends are being ingested. If forecasts are off every Monday, check if the system is using weekly vs daily patterns. Adjust the forecast algorithm (short-term vs long-term weighting).

Dashboard/reports slow and inconsistent Large datasets (200+ agents, multi-week views) cause rendering delays. Reduce date range to one week, filter to a single team, and load during off-peak hours. For cross-queue analysis, export individual reports and reconcile in Excel — the platform doesn't handle cross-queue aggregation well natively.

Quality Bot评分规则未触发 验证规则已发布（而非草稿状态）、范围覆盖正确的队列/团队，且交互在评分触发前已完成录制。检查Data Hub的数据新鲜度——数据过时会导致机器人无内容可评分。如果使用自定义合规标准，针对已知交互测试规则以验证匹配效果。

WFM预测准确性持续偏差 检查历史数据权重——Verint可能使用了过时的模式。验证收缩率百分比、特殊日期处理，以及近期业务量趋势是否已被纳入。如果每周一预测都偏差，检查系统是否使用周模式而非日模式。调整预测算法（短期vs长期权重）。

仪表盘/报告缓慢且不一致 大型数据集（200+座席、多周视图）会导致渲染延迟。将日期范围缩小至一周，筛选至单个团队，并在非高峰时段加载。对于跨队列分析，导出单独报告并在Excel中核对——平台本身无法很好地处理跨队列聚合。