Intro Request Triage

Detect and triage Telegram intro requests, then create follow-up tasks or response drafts. Use when the user wants to handle requests for introductions, referrals, investor intros, hiring intros, or partner handoffs.

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-intro-request-triage

Use this skill to process Telegram intro requests without losing context or sending premature replies.

Rules

Identify requester, target, requested reason, urgency, and required consent.
Create a task when an intro needs follow-up.
Use nudge.generate or outbox.preview only for draft/preview behavior.
Never send an intro or disclose contact details without explicit approval.
Tag chats with Intro Request when persistence is requested.

Flow

Use dialogs.list or search.messages to find intro requests.
Use chat.read for context around each request.
Extract requester, target, ask, urgency, and missing information.
Use tasks.add for the next step or tasks.suggest when uncertain.
Optionally create a response preview.
Return grouped requests: ready, needs clarification, blocked, and done.

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
telegram.message.preview when drafting previews

Useful tools:

search.messages
chat.read
tasks.add
tags.set
nudge.generate
outbox.preview

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 intro-request tags or tasks.

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 "intro" --limit 50 --json
npm run dev -- chat <peer> --limit 50 --json
npm run dev -- tasks add <peer> --due <date> --why "<next step>" --json
npm run dev -- nudge <peer> --style concise --json

Templates

Formatted preview from the packaged JSON asset.

Intro clarification

text

Can you share the specific context for the intro and what outcome you are hoping for?

Consent check

text

I can check with them first and only make the intro if they are open to it.

Examples

Formatted preview from the packaged JSON asset.

Examples 1

prompt

Find open intro requests and create follow-up tasks.

tools

search.messages

chat.read

tasks.add