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

Telegram Follow-up Tasks

Find conversations that need attention and turn agreed next steps into dated CRM tasks.

Example request

Illustrative scenario, not an executed run.

Review my recent customer chats and suggest follow-up tasks. Show me the proposed due dates before creating anything.

Expected result

A proposed task list tied to the relevant conversations, with the commitment, due date, and reason for each follow-up.

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-followup-tasks

Use this skill to turn Telegram conversation context into follow-up tasks.

Rules

  • Prefer task suggestions before creating tasks unless the user already gave exact task details.
  • Keep task why text concise and tied to the conversation.
  • Use due dates that are explicit or easily inferred from the user request.
  • This skill mutates CRM state, not Telegram messages.

Flow

  1. Use tasks_today when the user asks for the current follow-up queue.
  2. Use dialogs_list to find candidate chats.
  3. Use chat_read for chats that need context.
  4. Use tasks_suggest for AI-generated follow-up candidates.
  5. Use tasks_add when the user approves suggestions or gives direct instructions.
  6. Use rules_list, rules_add, and the explicitly approved rule-execution tools when the user wants recurring follow-up behavior.

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

Tools:

  • dialogs_list
  • chat_read
  • tasks_today
  • tasks_suggest
  • tasks_add
  • tasks_done
  • rules_list, rules_add, rules_disable, rules_delete, rules_run, and rules_log

This skill is safe to run before Telegram write scopes are enabled because it only mutates CRM state.

Cloud Telegram reads and CRM metadata are separate. If dialogs_list or chat_read can see a peer but tasks_suggest or other 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 creating CRM 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 or tgchats --json for task flows.

CLI equivalents:

  • tgchats tasks today --json
  • tgchats tasks suggest <peer> --json
  • tgchats tasks add <peer> --due <date> --why <reason> --json

Prefer MCP when available.

Templates

Formatted preview from the packaged JSON asset.

Proposal follow-up task

why

Follow up on the proposal

priority

med

Intro follow-up task

why

Send the promised introduction

priority

high

Examples

Formatted preview from the packaged JSON asset.

OpenClaw

OpenClaw

prompt

Show my follow-up tasks due today.

tools

tasks_today

Codex

Codex

prompt

Suggest follow-up tasks from the last 50 messages with @alice.

tools

chat_read
tasks_suggest

Claude Desktop

Claude Desktop

prompt

Create a high-priority task to send the proposal tomorrow.

tools

tasks_add

Keep building your workflow

Read the related Telegram workflow guide

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