Use case · assigning work

Assign tasks to employees without making them install anything

Most apps for assigning work start by inviting everyone to create an account, usually on a paid seat, and half the team never gets past that. DeloPulse assigns tasks where the team already talks. You mention people in a /task command in the group, and each of them gets a separate line on the card with a deadline and a Done button of their own.

Start assigning in your group

Free, with no sign-up and no per-seat pricing. Works in group chats and one-to-one.

Four ways to hand out a task

All of them produce the same thing: a card with named people on it, each of whom has to answer for their part.

Mention the people who have to do it

Write /task @Malika @Rustam send the July report by tomorrow 18:00 in the group. The bot reads the mentions and the deadline, creates the card and assigns both of them. If you would rather not type in front of everyone, create the same task in the Mini App.

Assign to a group of people you saved once

Shifts and departments change slowly. Save a set of people as an assignee group (“accounting” or “on duty”, say) and hand work to it by name. Everyone in it still reports individually.

Assign to everyone in the chat

For the things that genuinely concern all: a safety briefing, timesheets, a form to sign. The counter on the card shows how many of them are done, so you can tell whether the whole chat has done it or only a handful of people. “Everyone” means every member the bot already knows, so ask colleagues to register first.

Assign one person, with no group involved

A personal assignment lands in a private conversation with that employee. Nobody else sees it, and there is no public overdue notice. The deadline, the reminders and the report work exactly as they do in a group.

What comes back after you assign

Handing work out is the easy part. Below is what you get back afterwards, which is usually what a manager has no way of seeing in a chat.

A counter on the card: 1 / 3 means one of three assignees has reported. It updates in place, so what you see in the chat is the current state and not a snapshot from Monday.
A status for each person: Accepted, in progress, done, or sent back for rework. If one of the three is stuck, their line shows it.
Your decision on the result: If review is on, you accept the work or return it with a comment. The card shows separately that the assignee marked the work done and that you accepted it.
Requests instead of silence: An assignee can ask a question in the task comments or request more time. You answer the question there and approve or decline the new deadline, and the card shows that an extension was requested.
Chasing you do not have to do: The bot writes privately 24 hours, 3 hours and 1 hour before the deadline (for a date-only deadline, on the morning of the previous working day and on the morning of the due day), and only to the people who still owe you something. When you need to push earlier, there is a Remind button, limited to once every four hours per task.
A record you can look back at: Who was assigned and when they reported, and every time the deadline moved. In the Mini App it becomes a list with filters, a calendar and per-period statistics.

Add the bot to a group

The first assignment can go out a minute after the bot joins the group.

Why “everyone, please handle this” produces nothing

Three failures that repeat in every work chat, regardless of the industry.

A task with no name has no owner

A message addressed to the chat is read by everyone as being about somebody else. Naming people costs one keystroke and removes the ambiguity that the message created.

The answer arrives as a message

“Done” typed into a busy chat is gone in an hour. Two weeks later nobody can reconstruct who delivered and who quietly did not.

Somebody has to keep chasing

Remembering who owes what, and when to ask again, is a job in itself. It usually lands on the manager with the least time to spare, which is why it stops happening by Wednesday.

Where it fits and where it does not

A good fit when

you assign work to employees who are already in a Telegram group;
the same task goes to several people and each of them has to answer for their own part;
nobody is going to create accounts, remember passwords or pay for seats;
you need to know who is late before the client tells you.

Look elsewhere if

you need shift scheduling, payroll or an HR system;
you want boards, sprints and burndown charts;
the work is a personal checklist rather than something handed between people.

Frequently asked questions

How does the bot know which employee I mean?

By the @username you mentioned. If that person has never interacted with the bot, the assignment waits for them by username and attaches automatically the first time they appear. The card shows plainly that the link is still pending rather than guessing at a match.

Can two people get the same task without splitting it?

Yes. The task stays one card, and each assignee reports on it separately. That is the difference from a shared to-do item, where one person ticking the box hides what the other two did not do.

Can I set a different deadline for one of the assignees?

Yes. A task can carry a common deadline and personal ones on top of it, which is what sequential work needs. Lateness is judged against the deadline that applies to that person.

What about work that has to be checked before it counts?

Turn on review for the task. The assignee marks it done, you accept the result or send it back with a comment, and the time you spent reviewing is not counted against the assignee in the discipline statistics.

Is it really free?

Yes. Every feature is available at no cost: multiple assignees, reminders, recurring tasks, attachments, the Mini App and the analytics. There is no member limit and no paid tier.

Start with one task

Assign something today and see what comes back

Add DeloPulse to the group where your team already works, hand out one real task with a deadline, and check the card tomorrow morning.

Add the bot to a group