Skip to content
Chiho AI
Start for FreeLog in
Telegram Skills
View source
Review tool permissions
crm-automation
OpenClawClaudeCodexHermes Agent

Telegram Proposal and Deck Follow-ups

Find conversations awaiting a reply to a proposal or deck and prepare follow-up tasks.

Example request

Illustrative scenario, not an executed run.

Find these proposal conversations with no reply after the document was sent. Suggest follow-up dates; do not send messages.

Expected result

A list of proposal conversations with their last touch and a suggested task, while messages remain unsent.

Before you start

  1. Connect Telegram and select the personal or team context you intend to use.
  2. Connect your AI client with browser OAuth, or follow the local setup below.
  3. Review the workflow’s tools and target conversations. Chat reads and imported CRM records are separate; sync a chat before requesting changes to missing CRM metadata.

A skill does not schedule itself or grant permissions. Describe whether you want suggestions, a dry run, or an action. Client controls and each tool’s safeguards govern execution.

Flow summary

Parsed from the packaged SKILL.md.

telegram-deck-followup

Use this skill to make sure deck, proposal, and document sends get followed up.

Rules

  • Search for sent-material signals before creating tasks.
  • Check whether the recipient already replied after the send.
  • Use due dates based on user instruction or a default 3 business day follow-up.
  • Tag the chat with Deck Sent or Proposal Sent only when persistence is requested.
  • Do not send follow-up messages directly.

Flow

  1. Search for terms such as "deck", "proposal", "sent over", "attached", or "doc".
  2. Read each matching chat.
  3. Determine whether the latest relevant reply came after the send.
  4. Create follow-up tasks for silent threads.
  5. Optionally add a recurring rule for future deck follow-ups.

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

Required tool permissions

  • telegram.read
  • crm.write
  • automation.rules.write

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.
  • Browser OAuth connections you can review and revoke.
  • Shared team context and tool-specific action safeguards.
  • No local Telegram worker, database, or MCP runtime to operate.
Chiho.ai Telegram CRM workspace
Connect with browser OAuth

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.
Local tgchats command-line workflow
Setup README

Cloud MCP

Required scopes:

  • telegram.read
  • crm.write
  • automation.rules.write

Useful tools:

  • search_messages
  • chat_read
  • tasks_add
  • nudge_generate
  • rules_add

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 chat_read for context and ask for sync/import before persisting follow-up CRM changes.

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 "deck" --limit 50 --json
  • npm run dev -- chat <peer> --limit 50 --json
  • npm run dev -- tasks add <peer> --due <date> --why "Follow up after sent deck" --json
  • npm run dev -- rules add --name "Deck follow-up" --instruction "If a deck or proposal was sent and there is no later reply, create a follow-up task." --followup-days 3 --json

Templates

Formatted preview from the packaged JSON asset.

Deck follow-up task

why

Follow up after sent deck or proposal if there has been no reply.

Examples

Formatted preview from the packaged JSON asset.

Examples 1

prompt

Find chats where I sent a deck and no one replied. Create follow-up tasks for next week.

tools

search_messages
chat_read
tasks_add

Keep building your workflow

Read the related Telegram workflow guide

For unattended jobs, review advanced service-token setup separately.