No approval required

crm-automation

OpenClawClaudeCodexHermes Agent

Follow-up Tasks

Find Telegram chats that need follow-up and create CRM tasks. Use when the user wants a follow-up queue, task suggestions, or reminders based on Telegram conversations.

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

Use tasks.today when the user asks for the current follow-up queue.
Use dialogs.list to find candidate chats.
Use chat.read for chats that need context.
Use tasks.suggest for AI-generated follow-up candidates.
Use tasks.add when the user approves suggestions or gives direct instructions.
Use rules.* 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

Cloud MCP

Required scopes:

telegram.read
crm.write

Tools:

dialogs.list
chat.read
tasks.today
tasks.suggest
tasks.add
tasks.done
rules.*

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

prompt

Show my follow-up tasks due today.

tools

tasks.today

Codex

prompt

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

tools

chat.read

tasks.suggest

Claude Desktop

prompt

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

tools

tasks.add