Follow-up is the job nobody on a building site has time for, and no one person can read forty site groups a day. At Viya Constructions an AI colleague sits in the Telegram site groups like a site coordinator. It asks about upcoming milestones, payments and missing updates, in the sender's language, inside working hours. It never approves and never pays. The system is shipped. One colleague has been in a supervised pilot in real site groups since 21 October 2026.
[01]What changedViya Constructions
What changes in a site group where the colleague sits. Today, the pilot's groups.
From the system's rules and standard settings.
Follow-up is where site operations leak. A delay reported the same day, with a recovery date, can be acted on. A delay found at the weekly review cannot.
What is live and what is not. The system is shipped: hiring, jobs, Telegram, a memory per site, working hours, caps and approvals. One colleague has worked in real Viya site groups since 21 October 2026, as a supervised pilot. It asks about milestones held in ProjectSignal, follows up payments discussed in the groups and asks for missing morning updates. Jobs for stopped work, short material and the others under "Where it goes next" are designed and not running.
[02]Why this is hardViya Constructions
Viya has more than 40 sites live, each with its own Telegram group of site engineers, project managers, suppliers and crews.
Work stopping, material arriving short, a crew that did not turn up, a milestone at risk, a missing morning update. Each is visible in the site group long before it reaches a dashboard.
A voice note in Manglish (Malayalam in English letters). A photo of a delivery challan, the supplier's delivery note. A scanned PDF. All of it has to be read.
Problems surface at any hour, from people who never open the office software. A reply at 06:41 is a nuisance, so the question has to wait and still get asked.
Left alone, an attentive assistant re-asks, repeats itself and fills the manager's chat. In its first week in real site groups the colleague sent its manager three overlapping messages about one site in 90 minutes. The limits have to be fixed in code, not left to the AI.
[03]How it worksViya Constructions
A manager sets it up in Bleno as they would brief a new coordinator. Always on means it listens at all hours. It speaks only in working hours.
A name, its groups, the job in plain words, the situations that should wake it, its hours and who it reports to. The staff list comes from ProjectSignal.
One typed message runs through the job with every send held. The manager sees what it would have sent, and to whom.
Voice notes, photos and PDFs are turned into text. It is built to understand English, Malayalam, Manglish, Hindi, Tamil and Kannada. A message starts work only when it reports one of the job's situations or answers the colleague.
The drafted text and its recipient are checked against the company's written rules. No clean result, nothing sent, and the manager gets a note.
Hours, recipients, the hourly ceiling, the re-ask count and the site's daily escalation are checked in code. Off hours, the question waits.
No answer after 120 working minutes: one re-ask. Still nothing: one line to the manager, then silence in that group until someone speaks.
Each message carries what a good outcome looks like and a time to check it. At the end of the working day it reviews which follow-ups worked and schedules one more where they did not.
Plinth beam is due Friday. Is the shuttering done today, and when is concreting planned?
Following up: is shuttering complete, and which day is concreting?
Site B: no answer on plinth beam progress since 10:40. One escalation today for this site.
Off hours the colleague listens but sends nothing. The question waits for working hours, goes out once, and is checked on the day the supplier promised. The hold is live. The material job shown is designed.
[04]Connected to ProjectSignalViya Constructions
ProjectSignal data is read fresh on every run and never kept in the colleague's memory.
The colleague cannot create or change a record and produces no documents. Records are still made by people, in ProjectSignal or through the guided workflows.
Writes are designed, not built. The rule is set: a dry run first, confirmed by the sender in the group, then saved as the person who confirmed. Until then the colleague asks and a person records.
[05]Who decides whatViya Constructions
A direct question to the colleague gets an answer, never an action.
A guided workflow stops at a review card. A colleague in many site groups cannot wait for a button before every question, so the approval moves earlier: leadership writes the rules once, and every message is checked against them.
A manager can watch every run in Bleno, stop one, step in, teach it a fact or a rule, and pause or retire it. Any new procedure it proposes waits for a person's approval.
[06]More detailViya Constructions
The AI's instructions carry style. Code carries limits.
Each is a job description. A new job is configuration and a written rule page, not new code.
Designed. None is switched on. Times and thresholds may change.
The rollout is designed too: one colleague per project manager or region, 8 to 12 sites each, with a supervised first week. ProjectSignal is to supply the site-group map, so the right person can be tagged. Rule pages are to be reviewed by the head of projects.
At most one non-urgent message per site per day reaches you, naming the site and the next step.
The ask and the one re-ask happen in the site group. If the site stays silent, the manager gets one line, not a thread.
Every send passes a rules check and fixed caps. People are recognized by account, never by display name.
To start we need a week of real messages from a few site groups, one person it reports to, and thirty minutes a week.
[07]Where this fitsViya Constructions
Send us a week of messages from one site group and tell us who chases today. We will show you what a colleague would ask, and under which limits.