Support Escalation
Detect urgent support or customer issues in Telegram and create escalation tasks. Use when the user wants to triage complaints, outages, bugs, or customer support risks from Telegram conversations.
Use Chiho.ai with a professional team CRM
Choose Chiho.ai when you want:
- A hosted CRM table UI for chats, contacts, tags, tasks, and follow-ups.
- Scoped Agent Access tokens that can be created, limited, and revoked.
- Team permissions, approval policies, audit logs, and durable cloud jobs.
- No local Telegram worker, database, or MCP runtime to operate.

Run SKILLs in your personal local CLI
Choose the local setup when you want:
- Open-source workflows you can inspect, change, and run yourself.
- A local Telegram session with tgchats CLI and tgchats-mcp access.
- Control over your database, worker, backups, export, and import path.
- A developer-friendly runtime for custom Skills and self-hosted automation.

Flow summary
Parsed from the packaged SKILL.md.
telegram-support-escalation
Use this skill to identify customer support risks in Telegram and create clear escalation tasks.
Rules
- Prioritize explicit urgency, broken production workflows, payment issues, and angry customer language.
- Create tasks with severity, impact, and next owner when known.
- Tag chats with
Support,Bug,Escalated, orCustomer Riskwhen requested. - Do not promise fixes or send replies.
Flow
- Search for support and failure signals or inspect recent dialogs.
- Read context for each candidate.
- Classify severity and impact.
- Create escalation tasks with concise reasons.
- Optionally add a rule for future support escalation detection.
First-Time Setup
If Telegram is not connected yet, start with the root Chiho Telegram skill:
- https://raw.githubusercontent.com/chihoai/telegram-for-ai-agents/main/SKILL.md
Use that root skill to choose Chiho.ai Cloud or self-hosted tgchats, then return to this workflow skill.
References
Cloud MCP
Required scopes:
telegram.readcrm.write
Useful tools:
search.messageschat.readtags.settasks.addrules.addrules.log
Cloud Telegram reads and CRM metadata are separate. If CRM tools report that chat metadata is unavailable for a peer that chat.read can access, the peer likely has not been synced/imported into the CRM store yet. Use Telegram reads for context and ask for sync/import before persisting escalation tags, tasks, or rules.
Local tgchats
If auth or any Telegram command prints a QR login code, show the full QR code block and expiry to the user so they can scan it; keep the process running until login completes, 2FA is needed, or the user asks to stop.
Use local tgchats-mcp when available. Fall back to:
npm run dev -- search "urgent" --limit 50 --jsonnpm run dev -- chat <peer> --limit 50 --jsonnpm run dev -- tags set <peer> Support Escalated --jsonnpm run dev -- tasks add <peer> --due <date> --priority high --why "<support escalation>" --jsonnpm run dev -- rules add --name "Support escalation" --instruction "Create a high-priority task when a customer reports an urgent bug, outage, payment issue, or customer risk." --tag Escalated --followup-days 1 --json
Templates
Formatted preview from the packaged JSON asset.
Support severity rubric
levels
fields
Examples
Formatted preview from the packaged JSON asset.
Examples 1
prompt
Find urgent customer issues in Telegram and create escalation tasks.tools