TGH Tech
Case study · Workflow 12 of 20 · Run the sites · In pilot

An AI colleague sits in the site groups and follows up. It asks once, re-asks once, then tells its manager once.

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.

Client
Viya Constructions
Department
Site execution, project management, leadership
Starts from
Messages, voice notes, photos and PDFs in the Telegram site groups
Gives you
A question in the group, one re-ask, at most one non-urgent escalation per site per day
Connected to
ProjectSignal, reads only
Status
In pilot. Shipped. One colleague in real site groups since 21 October 2026

[01]What changedViya Constructions

The follow-up gets asked in the group. The manager hears about a site at most once a day, unless it is urgent.

What changes in a site group where the colleague sits. Today, the pilot's groups.

Before

Scroll, remember, phone.

  • Managers learn at 09:00 which sites have not filed. Nobody asks the site
  • Promises and decisions sit buried in long site group threads
  • Leadership reads raw updates from many groups, or nothing at all
  • Project managers chase answers by phone
Now

Ask in the group. Ask again once. Report once.

  • Every message is read, voice notes, photos and PDFs included
  • The question is asked in the group, in working hours, in the sender's language
  • No answer in 120 working minutes: one re-ask, then one line to the manager
  • One non-urgent escalation per site per day, with the site and the next step
  • 1
    non-urgent escalation per site per day
  • 120 min
    of working time before the one re-ask
  • 40
    messages an hour, the standard ceiling
  • 5
    refused sends stop a run

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

The problem is in the chat long before it is on a report. And the chat is voice notes, photos and three languages.

Viya has more than 40 sites live, each with its own Telegram group of site engineers, project managers, suppliers and crews.

  1. 01

    The chat knows first

    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.

  2. 02

    Site chat is not typed English

    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.

  3. 03

    Sites talk at all hours

    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.

  4. 04

    A helper that nags is resented

    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

Hired like a coordinator: a job, a manager, hours and limits.

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.

  1. 01A manager sets up

    Hire it and brief it

    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.

  2. 02A manager confirms

    Test it before it speaks

    One typed message runs through the job with every send held. The manager sees what it would have sent, and to whom.

  3. 03The AI reads

    Listen, and decide whether it matters

    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.

  4. 04Written rules decide

    Check the exact message

    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.

  5. 05Fixed logic

    Send only inside the limits

    Hours, recipients, the hourly ceiling, the re-ask count and the site's daily escalation are checked in code. Off hours, the question waits.

  6. 06Fixed logic

    Follow up once, then report

    No answer after 120 working minutes: one re-ask. Still nothing: one line to the manager, then silence in that group until someone speaks.

  7. 07The colleague

    Check back

    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.

Site B group · a milestone question
AI colleague · 10:40

Plinth beam is due Friday. Is the shuttering done today, and when is concreting planned?

AI colleague · 12:40, the one re-ask

Following up: is shuttering complete, and which day is concreting?

AI colleague to its manager · later that day

Site B: no answer on plinth beam progress since 10:40. One escalation today for this site.

Illustrative. Made-up site, times and wording. Shuttering is formwork.

A 06:40 photo becomes one question at 09:00.

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.

Site C group · steel arrives short
06:40 · Site engineerPhoto of the delivery challan. "12mm vannu, but kuravanu" (12 mm came, but short)Queued
09:00 · AI colleague"12mm ethra bars short aanu? Supplier delivery date paranjo?" (How many bars short? Did the supplier give a date?)Sent
09:14 · Site engineer"40 bars short. Supplier says Thursday."Noted
Thursday · Check-backBars received? If not, one re-ask, then one line to the manager.Due
Illustrative. The designed material follow-up job, under today's live limits. Made-up site and quantities.

[04]Connected to ProjectSignalViya Constructions

It reads ProjectSignal. Today it writes nothing to it. Its work is in the chat, where the site already answers.

  1. Reads

    From ProjectSignal

    • The staff list, with roles
    • Each site's upcoming milestones
    • For the designed jobs: site snapshot, open issues, readiness
  2. Does

    What the colleague does

    • Listens in the site groups it is assigned
    • Asks the responsible person, in the group
    • Re-asks once, then reports once
    • Keeps a separate memory per site
  3. Writes

    To ProjectSignal

    • Nothing today. Its output is questions, replies and escalations in the chat

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.

  1. Milestone plan import
  2. ProjectSignal milestones
  3. AI colleague asks
  4. Manager hears once

[05]Who decides whatViya Constructions

The AI reads. Written rules and fixed limits decide. People answer, and people act.

StepDone by
Reading messages, voice notes, photos and PDFsThe AI
Whether a message reports one of the job's situationsThe AI, against situations written in plain words
Whether a message may be sentA check of the exact text and recipient against the company's written rules
When it goes, how often and to whomFixed logic: hours, re-ask count, daily escalation, hourly ceiling, recipients
The cause, the recovery date, the answerThe site engineer or project manager, in the group
What to do about itThe manager the colleague reports to
Approving, paying, contacting a homeownerPeople only

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 rules it follows

Every limit, written down.

The AI's instructions carry style. Code carries limits.

RuleWhat it does
Rules checkBefore every send, the exact text and recipient are checked against the company's written rules. What goes out must match what was checked, character for character
RecipientsOnly the job's own site groups and the people named to receive its updates
Working hoursDefault Monday to Saturday, 09:00 to 19:00. Outside them a question waits, unless the manager has allowed urgent ones
Re-askOnce, after 120 working minutes. Then one line to the manager, and nothing more to that group until someone there speaks
EscalationOne non-urgent message to the manager per site per day, with everything for that site in it. A second is refused. Only a safety risk or work stopping within hours passes as urgent
Clarifying questionsOne per person per day
Hourly ceiling40 messages an hour in the standard setup, across all its jobs
RefusalsFive refused sends stop the run
LanguageReplies in the sender's language. Malayalam is written as Manglish unless Malayalam script is chosen
Uncertain readingMalayalam script read from a photo is marked uncertain. An unclear quantity, date or amount is asked about, not guessed
Rules check unavailableThe colleague pauses and tells its manager
NeverApproves, pays, or contacts a homeowner
Where it goes next

Follow-up jobs designed for it. None is running yet.

Each is a job description. A new job is configuration and a written rule page, not new code.

Designed jobWhenWhat it does
Missing site update10:00 and 19:30Asks the site group once, in English and Malayalam. An hour later the project manager gets one list of sites still missing. Never on Sundays or holidays
Labor shortfall11:30Asks the cause (contractor short, rain, material, other) and a recovery date. Checks next morning whether the crew is back. Only for gaps above 20 percent
Delay and stoppageWhen work stopsAsks cause and recovery date once. One summary to leadership at 18:00. Safety items go at once
Material follow-upMaterial short, late or wrong; 18:30 dailyChases the supplier until the material reaches site, reading the site snapshot from ProjectSignal
Site group digest19:00Tells the project manager what was asked, promised and left open in each group
Weekly readinessThursday and Friday, 10:00Reads each site's readiness for the coming week and reports the gaps

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.

What it means for you

Three readers, and four signs it is your problem too.

  1. For owners

    One message per site, not a stream

    At most one non-urgent message per site per day reaches you, naming the site and the next step.

  2. For operations heads

    The first chase happens in the group

    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.

  3. For your technical person

    Limits in code, access read-only

    Every send passes a rules check and fixed caps. People are recognized by account, never by display name.

  • Your project managers start the day scrolling site groups
  • A missing daily update is noticed, but nobody asks the site
  • Shortfalls and stoppages are mentioned in chat without a cause or a date
  • Leadership phones managers for status

To start we need a week of real messages from a few site groups, one person it reports to, and thirty minutes a week.

Which question in your site groups goes unasked when everyone is busy?

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.