Telegram bot
DivitiTasks
Tasks, projects and departments inside Telegram, on a CRM backbone — with morning and evening digests the manager does not have to ask for.
Overview
Task management where the team already is
Teams do not move to a task system; they say they will and then keep using the chat. DivitiTasks accepts that and puts the task system in the chat, on top of a CRM rather than instead of one.
It also turns a thread into a project, which is the moment most work actually starts — somebody describes a job in a message and nobody writes it down.
What it does
- Tasks, projects and departments inside Telegram
- Reports on tasks plus call analytics for the manager
- Turns a chat discussion into a structured project
- Morning task digest and end-of-day summary sent automatically
- Client conversation from Telegram or Wazzup next to the CRM notes
The category
What a task system in a messenger is actually for
Every company that buys a task tracker buys it twice. The first purchase is the licence. The second is the months of asking people to open it, and that second purchase is the one that fails. The work keeps happening in the chat because the chat is where the client writes, where the foreman sends the photo and where the decision gets made at nine in the evening.
DivitiTasks starts from that fact rather than arguing with it. Tasks, projects and departments live inside Telegram, and the data underneath sits on a CRM backbone — EspoCRM with n8n automations — so the records are connected rather than scattered across threads. The manager gets a task digest in the morning and the day's result in the evening without asking anyone for a status.
That is a different product from a tracker with a Telegram notification plugin, and it is worth being precise about the difference, because the price lists below are not comparing the same thing. A plugin pushes a message out of a system people do not open. This puts the system where they already are.
The real cost
What a tracker costs over a year, with the numbers published
Per-seat pricing is the figure vendors lead with. Worked through for a twenty-person team using the prices each vendor publishes on its own pricing page on 3 November 2026, the yearly seat bill looks like this.
- Asana — Starter at $10.99 per user per month billed annually is about $2,638 a year for twenty people; Advanced at $24.99 is about $5,998. Billed monthly the same tiers are $13.49 and $30.49.
- ClickUp — Core at $9 per user per month billed yearly is about $2,160; Business at $17 is about $4,080. The undiscounted prices on the same page are $12 and $25.
- Monday — Basic at $9 per seat is about $2,160; Standard at $12 is about $2,880; Pro at $19 is about $4,560. Monday's CRM is a separate product at $12, $17 and $28 a seat.
- Bitrix24 — priced per organisation rather than per seat: Standard is US$99 a month billed annually and includes fifty users, which is about $1,188 a year however many of those fifty you use. Professional is US$199 and includes a hundred.
Two things in that list matter more than the ranking. The first is Bitrix24's shape: at scale a per-organisation price beats a per-seat one by an order of magnitude, and any honest comparison has to say so. The second is that the AI line is now metered separately almost everywhere — Asana charges $0.50 per prepaid AI request and $0.60 when you pay in arrears, and ClickUp sells credits at $10 per ten thousand. A workflow that leans on automation gets a bill that moves with usage.
DivitiTasks is quoted per deployment rather than per seat, and we are not going to pretend that is automatically cheaper. It is a different shape: a project fee for setting the processes up, then a figure scaled to team size. What it removes from the comparison is the per-seat tax on adding the twenty-first person, which is exactly the tax that stops companies from putting the foreman, the estimator and the driver into the system at all.
Comparison
DivitiTasks against the established trackers
Four tools people actually shortlist against this one, compared on the axes that decide the purchase. Every price here is from the vendor's own pricing page, read on 3 November 2026; where we have no published figure of our own, the cell says so rather than guessing.
| DivitiTasks | Asana | ClickUp | Monday | Bitrix24 | |
|---|---|---|---|---|---|
| Where the team works | Inside Telegram | Web and mobile app | Web and mobile app | Web and mobile app | Web, mobile, own messenger |
| Published price | No — quoted per deployment | Yes | Yes | Yes | Yes |
| Entry paid tier | On request | $10.99 per user / month, annual | $9 per user / month, annual | $9 per seat / month, annual | US$49 per organisation / month, annual, 5 users |
| Mid tier | On request | $24.99 per user / month, annual | $17 per user / month, annual | $12–19 per seat / month, annual | US$99 per organisation / month, annual, 50 users |
| Free tier | No — pilot access instead | Yes, 2 users | Yes | Yes, 2 seats | Yes |
| AI billed separately | No — included in the deployment | Yes, $0.50–0.60 per request | Yes, credits at $10 per 10,000 | Yes, credits bundled per tier | Included per tier |
| Automation ceiling | n8n, no per-tier cap | Per-tier rules | 1,000 / month on Core, 10,000 on Business | Per-tier actions | Per-tier |
| CRM underneath | Yes — EspoCRM | No, integrations | No, integrations | Separate product | Yes |
| Chat thread becomes a project | Yes | No | No | No | No |
| Call analytics for the manager | Yes | No | No | No | Telephony add-on |
| Stage | Pilot, version 1.2 | Mature | Mature | Mature | Mature |
Where we win
What DivitiTasks does better
Four things, and they come from one decision: the interface is the messenger the team already has open.
- Nobody has to be persuaded to log in. The adoption problem that sinks tracker rollouts does not arise, because there is nothing new to open. For a crew of drivers, foremen and estimators this is usually the whole argument.
- A thread turns into a project. Most work starts as someone describing a job in a message that nobody writes down. The bot structures that discussion into a project with tasks and owners at the moment it happens, rather than after the weekly meeting.
- Two digests replace the status round. The morning list and the evening result arrive automatically. Nobody collects statuses, and the manager stops being the integration layer between people who already know the answer.
- Tasks and call analytics sit in one place. Load per person and call quality are in the same report, on a CRM backbone, so the conversation with the client and the note about it are not in two different systems.
The vendor's own estimate of the effect, published on the Russian product page, is up to 80% less time on routine statuses and reports, 15–25% more output per employee and 60% fewer missed deadlines, with payback in one to three months for a team of five or more. Treat those as our estimate rather than a benchmark: they come from our own deployments, not from an independent study, and we would rather label them than dress them up.
Where we lose
What the established tools do better
The honest half of the comparison, and the half most vendor pages leave out.
- Maturity. DivitiTasks is in pilot at version 1.2, with the core working for a limited group of users. Asana, ClickUp, Monday and Bitrix24 have a decade or more of edge cases already found and fixed. If you need something that has survived a thousand companies before yours, that is them, not us.
- Published pricing. They publish, we quote. That is worse for you when you are building a shortlist, and we are not going to argue it is a feature.
- No free tier to try alone. Three of the four let you open an account tonight and form your own opinion by morning. With us the route in is a conversation and pilot access.
- Views and reporting breadth. Gantt charts, portfolio dashboards, workload heat maps, hundreds of integrations and a marketplace of templates — the mature platforms have all of it. A messenger interface is deliberately narrower, and if your work genuinely needs a timeline view with dependencies on a wide screen, that is a real argument against us.
- A single point of dependency. Everything runs through Telegram. If Telegram is blocked, restricted or simply not what your company has standardised on, the product does not degrade gracefully — it stops being the right tool. The established platforms are channel-agnostic by design.
- Compliance paperwork. No public audit reports, no procurement-ready security questionnaire answered in advance, no third-party reviews to read. For a company whose purchasing runs through an information-security review, that is a real obstacle and it is on us to solve it, not on you to overlook.
Why rollouts fail
Why “we will start using the tracker on Monday” does not hold
The pattern is the same everywhere and it has nothing to do with which tracker was chosen. A tool is bought, a template is imported, two enthusiasts fill in their tasks properly for three weeks, and then one urgent job arrives in the chat at eight in the evening and gets done without ever entering the system. After that the tracker is a parallel reality that disagrees with the truth, and the first person who notices stops trusting it.
The second failure is subtler: the system becomes the manager's reporting tool rather than the team's working tool. People fill it in because they are asked to, the data is a day stale, and the manager still rings round to check. At that point the licence is paying for data entry.
Putting the system in the messenger removes the first failure and does nothing about the second. The second is solved by the digests being generated rather than requested, and by the manager agreeing to read them instead of ringing round. That is a habit, not a feature, and if the manager will not give up the status call then no product on this page will help.
The mechanics
Where the work actually starts, and what the bot does with it
A job arrives as a sentence in a group chat. Somebody has to decide what it is, who owns it and when it is due, and in most companies that decision is made verbally and then lost. The chat-to-project step is the one piece of this product that has no equivalent in the trackers above.
- From discussion to structure. A thread becomes a project with tasks and owners, so the context that produced the job stays attached to it.
- From voice to task. Voice messages and plain text are turned into tasks with an owner and a reminder, which matters on sites where typing is the thing nobody will do.
- From CRM to digest. KPI facts — revenue, conversion, overdue items — are pulled from the CRM and sent as a daily summary, which is the thing a morning meeting is usually for.
- From two windows to one. The client conversation from Telegram or Wazzup sits next to the CRM notes, so the history of the deal is in one place rather than reconstructed from memory.
Who should buy what
An honest routing table
We would rather lose a sale than take one that will not work. Four situations, four different answers.
- A team of five to two hundred that lives in Telegram, in construction, manufacturing, an agency or distribution. This is the case DivitiTasks was built for, and the case where the adoption problem is the whole problem.
- A company that already runs on a mature tracker and whose people open it. Stay. You have already paid the expensive part of the price, which is the habit. Adding a messenger layer to a working system buys you very little.
- A team that needs timelines, dependencies and portfolio reporting on a wide screen. Asana or Monday. A messenger is the wrong shape for that work and we will say so before you buy.
- A company of fifty-plus that wants one vendor for CRM, telephony and tasks at a flat organisational price. Bitrix24 is genuinely strong there, and its per-organisation pricing at that headcount is hard to argue with on cost alone.
Rollout
What the three months actually contain
Implementation is a project, not a sign-up, and it runs about three months end to end. Written out so you can hold us to it.
- Weeks one and two — the processes as they are. We sit with the people doing the work and write down how a job currently travels from the client's message to done. This is the part companies want to skip and the part that decides the outcome.
- Weeks three and four — the CRM backbone. EspoCRM is set up around those processes and connected to the channels you already use, Telegram and Wazzup. Integration with an existing CRM is the question to settle before signing, not after.
- Weeks five to eight — the pilot group. A limited circle works in the bot while the rest carry on as before. Tasks, projects, departments and the two digests are live for that group only.
- Weeks nine to twelve — the rest of the team and the analytics. The bot goes to everyone, call analytics and load reporting come on, and the status meeting is removed from the calendar deliberately rather than quietly.
If a vendor tells you a task system lands in a week, they are describing the installation, not the change. The installation is the cheap part.
The pilot
How to run it so the answer means something
A pilot that cannot fail tells you nothing. Four conditions we ask for before starting one.
- Pick the loudest process, not the easiest. The one where jobs currently get lost. An easy process will succeed in any tool and prove nothing.
- Write the success criterion down first. Fewer missed deadlines, or the status call cancelled, or the manager's evening hour returned. One sentence, agreed before the first task is created.
- Include the person who will resist. If the foreman who hates software is not in the pilot, the pilot is measuring the enthusiasts.
- Keep the old way running. Nothing is taken away during the pilot. If the bot is better, people stop using the old way without being told, and that silence is the result you wanted to measure.
Limits
Where this product is the wrong answer
Said plainly, because the alternative is a disappointed customer in month four.
- A company that has standardised on a different messenger. The product is Telegram-first and that is not a configuration flag.
- Work that needs a dependency-aware timeline across dozens of parallel projects on a wide screen.
- Regulated procurement that requires published audit reports and references before a pilot can begin.
- A team of two or three. The payback arithmetic needs five people before it starts to make sense, and below that a shared list is genuinely enough.
- An organisation looking for software it can buy and switch on without changing how it works. This needs the process conversation, and without it the bot becomes another place tasks are typed and ignored.
Due diligence
Questions worth asking any vendor in this category
Including us. If the answers are vague, that is the answer.
- Which CRM is underneath, and what happens to my data if I leave?
- Is the price per seat, per organisation or per deployment, and what does adding the twenty-first person cost?
- Is AI usage metered separately, and what does a heavy month look like on the invoice?
- What is the automation ceiling on the tier I am being quoted?
- Who writes the process down — your team, mine, or nobody?
- What stage is the product at, and how many companies are running it in production right now?
- What does the rollback look like if we stop after the pilot?
The short version
If you only read one section
DivitiTasks puts tasks, projects and departments inside Telegram on a CRM backbone, turns a chat thread into a structured project, and sends the manager a task digest in the morning and the day's result in the evening. It is in pilot at version 1.2, priced per deployment, and takes about three months to put in properly.
Against it: Asana from $10.99 a user a month, ClickUp from $9, Monday from $9 and Bitrix24 from US$49 a month for a whole organisation of five — all published, all mature, all with free tiers you can try tonight. They are better at breadth, reporting views and procurement paperwork. We are better at the one thing that decides whether any of it gets used: the team does not have to go anywhere.
If your people open the tracker you already pay for, keep it. If they say they will and then keep using the chat, that is the problem this product exists for, and the conversation is worth half an hour.
Questions
DivitiTasks, answered.
Why not a proper task tracker?
Because the team opens Telegram and does not open the tracker. A system nobody logs into is worse than a messy one everyone uses. If your people do open the tracker you already pay for, keep it — you have already paid the expensive part of the price, which is the habit.
Is it tied to one CRM?
It runs on a CRM backbone — EspoCRM with n8n automations underneath — so the integration is the part to check before committing. Tell us which CRM you run and we will say plainly whether it fits, before anyone signs anything.
Does the manager still have to chase status?
That is what the two digests are for: the list of tasks in the morning, the result in the evening, without anyone being asked. The catch is that the manager has to agree to read them instead of ringing round. If the status call stays in the calendar, the digests are just more noise.
What stage is the product at, and what does it cost?
Pilot, version 1.2: the core works for a limited group of users. Implementation is a project of about three months — process setup plus CRM integration — and the price is quoted per deployment against team size rather than per seat. We do not publish a price list, which is worse for you when you are shortlisting, and we are not going to call that a feature.
How does this compare on price with Asana or ClickUp?
Read from their own pricing pages on 3 November 2026: Asana Starter is $10.99 per user per month billed annually and Advanced is $24.99; ClickUp Core is $9 and Business $17; Monday Basic is $9, Standard $12, Pro $19. For twenty people that is roughly $2,160 to $6,000 a year in seats alone. Bitrix24 is the outlier worth knowing about: US$99 a month billed annually covers fifty users, about $1,188 a year whatever the headcount. Ours is a project fee plus a figure scaled to the team, so the honest comparison depends on your headcount, not on a per-seat line.
Is the AI billed separately, like everywhere else?
No. On the mature platforms it increasingly is — Asana charges $0.50 per prepaid AI request and $0.60 pay-as-you-go, ClickUp sells credits at $10 per ten thousand — so a month of heavy automation moves the invoice. With us the automation sits in n8n inside the deployment and does not have a per-tier ceiling.
Which companies is this actually for?
Teams of five to two hundred in construction, manufacturing, agencies and distribution, where the manager is drowning in status calls and manual reports and where the crew genuinely lives in Telegram. Below five people a shared list is enough and the payback arithmetic does not work.
When is it the wrong tool?
When your company has standardised on a different messenger; when the work needs a dependency-aware timeline across dozens of projects on a wide screen; when procurement requires published audit reports and customer references before a pilot can start; or when you want software you can switch on without changing how the work travels. In the last case the bot becomes one more place tasks are typed and ignored.
What do the quoted percentages mean?
Up to 80% less time on routine statuses and reports, 15–25% more output per employee, 60% fewer missed deadlines, payback in one to three months from five people up — those are our own figures from our own deployments, published on the Russian product page. They are an estimate by the vendor, not an independent benchmark, and we would rather label them than present them as research.
How do we run a pilot that actually proves something?
Take the loudest process rather than the easiest one, write the success criterion down in one sentence before the first task is created, include the person you expect to resist, and leave the old way running. If the bot is better, people stop using the old way without being told — and that is the result you were trying to measure.
More products
The rest of the portfolio.
DivitiSales
AI for the sales floor: every call reviewed, not a sample
DivitiBuild
Construction management with an AI foreman
DivitiCMS
Your own sales channel, not a marketplace stall
DivitiContent
An editorial pipeline, not a text generator
DivitiLegal
Contract review from your side of the table
DivitiAgro
Grain prices turned into a selling decision
DivitiMentor
A mentor that does not require an appointment
Divitio Minds
A catalogue of practitioners' methods, not a chat with a model
Ready when you are
Which of these fits your operation?
Tell us the process that hurts. We will say which product touches it and which does not.