VIP Inbox

Build and maintain a VIP Telegram inbox queue using tags, summaries, and follow-up tasks. Use when the user wants important contacts surfaced before general inbox triage.

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.

Setup README

Flow summary

Parsed from the packaged SKILL.md.

telegram-vip-inbox

Use this skill to surface high-priority Telegram conversations as a VIP queue.

Rules

Prefer existing tags and company links before inferring importance.
Read recent context for chats that may need action.
Use VIP, Needs Follow-up, or domain-specific tags only when requested.
Do not archive, move, or message chats from this skill.

Flow

Use dialogs.list and CRM metadata to identify VIP candidates.
Read recent context for each candidate.
Show due tasks and stale conversations first.
Refresh summaries for important chats with missing context.
Add follow-up tasks or VIP tags when requested.

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.read
crm.write for persisted tags or tasks

Useful tools:

dialogs.list
chat.read
tags.get
tags.set
tasks.today
summary.show

Cloud Telegram reads and CRM metadata are separate. If dialogs.list or chat.read can see a peer but tags.get, summary.show, or other CRM tools report that chat metadata is unavailable, the peer likely has not been synced/imported into the CRM store yet. Continue with Telegram reads and ask for sync/import before persisting VIP metadata.

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 -- inbox --limit 50 --json
npm run dev -- tags ls --json
npm run dev -- tasks today --json
npm run dev -- open <peer> --json
npm run dev -- chat <peer> --limit 30 --json

Templates

Formatted preview from the packaged JSON asset.

VIP inbox tags

Examples

Formatted preview from the packaged JSON asset.

Examples 1

prompt

Show my VIP Telegram inbox and explain who needs attention today.

tools

dialogs.list

tasks.today

chat.read

summary.show