There are many complaints, little time, and it's unclear what to tackle first. The skill consolidates the noise from disputes, tickets, and reviews into the top 3 problems that can actually be fixed, and immediately provides draft replies — you decide what to send, not where to get it all from.
Run the voice-of-the-customer synthesis. Pull feedback signals from all connected sources, identify genuinely solvable topics, and prepare draft replies that the owner will review and send.
Argument breakdown:
--since(default: last 30 days) — start date of the analysis window in the formatГГГГ-ММ-ДД
Step 1 — Collecting feedback signals
Following the skill's workflow customer-pulse:
- Pull disputes and chargebacks from
~~платежей(e.g. YooKassa, Tinkoff Kassa) for the period: reasons, amounts, status. - Pull tickets and notes from
~~crm(e.g. Bitrix24, amoCRM) for the period. - If there are review export files (Yandex Maps, 2GIS, Avito, VK, Otzovik — CSV/Excel) — read and parse them.
- Count the total number of signals per source.
If nothing is connected — ask to export transactions from the bank client to CSV or paste reviews as text.
Step 2 — Identifying topics
Group all signals into recurring topics. For each topic:
- Count how many signals mention it
- Classify: Product quality / Delivery / Payment and invoices / Communication / Mismatch of expectations / Other
- Assess impact: 🔴 High (revenue risk, churn) / 🟡 Medium / 🟢 Low
Step 3 — Top 3 solvable problems
Following the skill's workflow ticket-deflector:
Select the top 3 topics by: frequency × impact. For each:
- Formulate the problem in one sentence
- Explain the root cause (where it is visible)
- Propose a specific operational solution
- Prepare a draft response to the client
Draft response format:
Тема: Re: {тема обращения}
Здравствуйте, {имя}!
Спасибо, что написали. {Признание их ситуации в 1–2 предложениях}.
{Что мы делаем / что произошло / какое решение предлагаем}.
{Следующий шаг или предложение}.
{Подпись}
Step 4 — Summary table
Formulate the conclusion as follows:
Голос клиента — {диапазон дат}
Всего сигналов: {n} ({Споры по платежам: n} | {CRM-обращения: n} | {Отзывы: n})
ТОП-3 РЕШАЕМЫЕ ПРОБЛЕМЫ
1. {Проблема} ({частота}) — {влияние} — Решение: {в одну строку}
2. {Проблема} ({частота}) — {влияние} — Решение: {в одну строку}
3. {Проблема} ({частота}) — {влияние} — Решение: {в одну строку}
Connector failures
Work with what is connected — the team degrades gracefully. If there is no ~~платежей — skip the disputes data and note “Payments are not connected — disputes skipped.” If there is no ~~crm — skip the requests and note this. If not a single source is connected — stop and tell the owner: “Feedback sources are not connected. Connect ~~платежи or ~~crm, or upload a CSV export of reviews.”
Approval gates
- Never send responses automatically. Show drafts to the owner for review only.
- Never close requests in the CRM or resolve payment disputes without the owner's explicit confirmation.
- Never include the client's personal data in the summary — only the first name + the first letter of the last name.
Output
Show the summary table, then each draft response. Ask the owner which drafts they want to send, and wait for explicit confirmation before sending.