No approval required

crm-automation

OpenClawClaudeCodexHermes Agent

Lead Qualification

Qualify Telegram conversations as sales or partnership leads and create CRM tags, company links, tasks, and summaries. Use when the user wants to score inbound chats, identify promising leads, or triage Marketing and BD opportunities.

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-lead-qualification

Use this skill to turn Telegram conversation context into a qualified CRM lead record.

Rules

Read enough recent context before making a qualification.
Prefer AI suggestions for tags, company, and tasks before persisting.
Use explicit lead-stage tags such as Lead, Qualified, Partner, Customer, or Investor.
Keep the qualification reason concise and tied to conversation evidence.
Do not send Telegram messages.

Flow

Use dialogs.list to find candidate chats when no peer is specified.
Use chat.read to inspect recent context.
Use tags.suggest, company.suggest, and tasks.suggest.
Use summary.refresh when the chat lacks current context.
Apply tags, company links, and tasks only when requested or when policy allows automatic CRM writes.
Return the qualification, evidence, next action, and any persisted changes.

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

Useful tools:

dialogs.list
chat.read
tags.suggest
company.suggest
tasks.suggest
tags.set
company.link
tasks.add
summary.refresh

Cloud Telegram reads and CRM metadata are separate. If dialogs.list or chat.read can see a peer but CRM tools report that chat metadata is unavailable, 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 lead tags, company links, tasks, or summaries.

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 -- chat <peer> --limit 50 --json
npm run dev -- tags suggest <peer> --json
npm run dev -- company suggest <peer> --json
npm run dev -- tasks suggest <peer> --json
add --apply only when the user approves CRM writes.

Templates

Formatted preview from the packaged JSON asset.

Lead stage tags

Examples

Formatted preview from the packaged JSON asset.

Examples 1

prompt

Qualify my recent inbound Telegram leads and show the top follow-ups.

tools

dialogs.list

chat.read

tags.suggest

company.suggest

tasks.suggest

Examples 2

prompt

Qualify @alice as a lead and apply the CRM updates if the evidence is strong.

tools

chat.read

tags.suggest

company.suggest

tasks.suggest

tags.set

company.link

tasks.add