Automations → A task overdue by 3 days → an alert to the consultant, not the client
A task overdue by 3 days → an alert to the consultant, not the client
Overdue tasks do not disappear, they sink. Once a day, every open task 3 days late surfaces in one message — and whoever owns it sees it before the client asks.

The problem
The task log looks tidy, but between the rows sit tasks a week past due that nobody touched. They surface when the client calls. By then it is not a delay, it is a trust problem.
What happens when it runs
- Schedule: every day 08:30
- Read the task log: status open, due more than 3 days ago
- Aggregate into one list: task · client · days overdue
- A Telegram message to the consultant (or the team group) — not to the client
The tools inside
- Make — the automation engine · Sign up (one month of Core free) →affiliate link
- Google Sheets — log and lists
- Telegram — alerts
Before you start
Three things to have ready before importing, or Make will ask and you will have to leave halfway:
- The task log spreadsheet id
- Days overdue threshold (default 3)
- Chat ID
Sheet templates
The file maps columns by position. Start from exactly these headers, in this order — a column in the wrong place writes a phone number into the email column.
- Task log ·
task | client | due | statusDownload ↓
How to import (2 minutes)
- In Make: Scenarios → Create a new scenario
- At the bottom, the three dots (⋯) → Import Blueprint → choose the file you downloaded
- Click every module with an exclamation mark: choose your connection (Google, Telegram) — Make creates one in a click if you have none
- Replace every value in double curly braces ({{…}}) with your own from the list above
- Run once with a test row in the sheet. Only when it passes — Schedule and ON
The video
Watch on YouTube → · Subscribe to BuilderStack · Telegram channel
What does not work in it
- An overdue task appears every morning until it is closed. That is on purpose — but after a week the message becomes noise. If the same 10 tasks repeat, the problem is not the alert.
- The alert does not distinguish "a day late" from "a month late" beyond the number. Tasks that are truly stuck need a decision, not a reminder.
Affiliate link. If you sign up through it we earn a commission from Make; your price is the same, and the link gives you one month of Core free.
More automations
All automations →
EMAIL → TASKLabelled email → task in the log → reminder
Tag an email with one label and it becomes a task with a due date and an alert. One screen for everything that is waiting.
MORNING DIGESTEvery morning: what is due today → one message
At seven in the morning one Telegram message arrives with every task due today, by client. One screen to open the day, instead of five.
LEAD ALERTLead comes in → logged → alert. No hands.
A form on the client site sends a lead; it is logged and an alert reaches Telegram in seconds. The first automation every consultant sets up.