Skip to content

Product

From conversation to structured work.

Tydy reads your work chats in Telegram and keeps projects, tasks and their history up to date, with a person making the final call.

Telegram ingestion

Tydy listens where the work is discussed

Connect the groups, forum topics and personal Business chats you choose. Everything else in your Telegram stays out.

  • Groups and forum topics, each kept separate
  • Personal chats via Telegram Business, only the ones you add
  • Text, screenshots, documents and voice notes
TydyChats

Context engine

Several messages, one meaning

Tydy reads a batch of messages as one request and decides: is this new work, or a change to a task that already exists?

  • Messages from one person are read together, not one by one
  • Open tasks and similar ones are checked before anything is created
  • A follow-up hours later updates the same task
TydyCRM · board

Chats

Every work conversation in one inbox

The team reads Telegram inside Tydy: which chat, which topic, what is unread and which task each message belongs to.

  • Groups, topics and Business DMs side by side
  • Unread counts per chat and topic
  • Linked task on every relevant message
  • Reply to Telegram or leave an internal note
TydyChats

Task Conversation

The whole story lives next to the task

The task keeps its conversation: what the client wrote, what the team replied, what AI changed. In order.

  • Telegram messages and replies from the web
  • Screenshots, documents and voice with transcripts
  • AI actions and status changes as events
  • Internal notes the client never sees
TydyCRM-91

AI Inbox

Uncertain changes wait for you

When Tydy is not sure enough, the change becomes a proposal. Try it: accept, edit or ignore, then undo.

  • Every proposal shows its source message
  • Confidence decides what applies automatically and what waits
  • Applied actions can be undone
TydyAI Inbox

AI Inbox

3 to review
  • CRM-91

    Add label Bug

    Marina: “The Pay button doesn’t work on mobile”

    94%
  • CRM-91

    Move to Review

    Alex: “Fixed, please check”

    91%
  • CRM-104

    Set due date Friday

    Zahar: “Needed by Friday”

    62%
Demo: nothing is sent anywhere

Kanban

The board stays current

Tasks live in projects and columns with priorities, labels, assignees and due dates. The board reflects the conversation instead of lagging behind it.

  • Your own columns per project
  • Labels, priorities, assignees and due dates
  • AI can move a card when policy allows
TydyCRM · board

Files & voice

Files don’t get lost in the chat

Screenshots, documents and voice notes are attached to the task they belong to, with a link back to the message they came from.

  • Screenshots understood by AI (plan permitting)
  • Voice notes transcribed
  • Every file keeps its source message
TydyFiles

Deadlines in Telegram

The bot reminds you before the client has to ask

When a task has a due date and an assignee, Tydy messages the assignee in Telegram: a day before, an hour before, and once when it is overdue. Complete the task or move the date right from the message.

  • A day before, an hour before, or both: everyone picks their own
  • Buttons in the message: complete, +1 day, tomorrow, next week
  • One overdue message, no hourly nagging
  • Optional quiet hours: the bot stays silent at night and reminders arrive in the morning

Reminders go to the task's main assignee. Included on every plan, Free too. Link your Telegram account to get them.

One message in the morning instead of ten overnight

Turn on the morning digest in the bot and get one message at 09:00 or a time you choose: due today, overdue, waiting for review and newly assigned. If there is nothing, the bot stays quiet.

TelegramTydy · bot
17:00

Deadlines in the app

TydyCalendar

Calendar: every due date in the month

Tasks on a month grid by due date, overdue ones in red. Filter by project and assignee. Drag a task to another day and the due date moves, keeping its time.

TydyReports

Reports: where deadlines slip

How many tasks are overdue right now, in which projects and with whom, and which one has waited longest. Only projects you can see are counted, and access to reports is set by role.

Permissions & roles

Everyone sees what they should

Workspace roles, private projects and custom roles decide who sees a project, who may write to Telegram and who reviews AI proposals.

  • Owner, Admin, Member, Viewer and Guest roles
  • Private projects visible only to their members
  • Custom roles for specific rights, e.g. sending to Telegram
  • Every change is checked on the server
Technical note

For MCP, effective access is the intersection of granted scopes, live role permissions (RBAC) and plan access. Tokens are stored hashed and revoke immediately.

TydyRoles

MCP

AI agents get context, not your password

Cursor, Claude and other MCP clients connect to one workspace. They see and do only what the token’s scopes and your role allow.

  • Tasks, chats, files and AI Inbox as tools
  • Scopes you choose, bound to one workspace
  • A revoked token stops working immediately
MCP for developers
TydyMCP

Stop losing work in chats

Connect Telegram, watch tasks appear, and keep the final call.

Pricing