The Site That Runs on WhatsApp: RE061 Construction Vendor AI Agent
Log work orders, check vendor status, and escalate site issues — without digging through WhatsApp chaos.
Audio summary · ~1 min
Audio summary · RE061 Construction Vendors
RE061 — work orders and vendor status without WhatsApp chaos.
It is 7:40 AM at a villa construction site. The plumbing subcontractor arrives at Villa 14, discovers the rough-in does not match the revised drawing, and sends a voice note to the project WhatsApp group. The electrician asks a unrelated question three messages later. The site supervisor is on another call. By 10:00 AM, nobody has logged a formal work order. The plumber waits. The PM finds out at lunch from a frustrated phone call. The delay costs a day.
Every construction project runs on this kind of chaos. One vendor wants a work order. Another needs a drawing clarification. A third reports material stuck at the gate. All of it lands in the same WhatsApp thread — mixed with good morning forwards, labour count photos, and invoice PDFs. Work orders get lost. Status checks become phone-chase loops. Escalations happen too late, without an audit trail.
This is not a communication culture problem alone. It is a routing and capture problem. Developers, project management firms, and facility managers with multi-vendor sites need one standard intake for queries, work orders, and issue reports — with reference IDs, validation, and PM escalation when urgency demands it.
Site reality
The average mid-size residential project coordinates 15–40 active vendors across trades. WhatsApp is the default — but it was never designed to be a work order system.
74% of site coordinators report losing at least one actionable request per week in group chat noise
Intent desks
Query · Work Order · Report Issue — one agent routes to the right workflow without menu hell.
Reference on every ticket
Every logged action returns Ref #RE061-XXXX — searchable by PM, vendor, and site.
Urgency-aware escalation
High-urgency work orders and blocked trades trigger PM notification stubs automatically.
The use case: structured vendor intake on a chaotic site
RE061 · Construction Vendor Coordination is a DestinPQ agent built for developers, PM firms, and facility managers who coordinate multiple trades across active sites. It accepts vendor messages through an embedded portal widget or WhatsApp on a shared business line, detects intent, validates required fields, and returns a reference ID — so nothing actionable disappears into a group chat scroll.
Who it's for: Residential villa developers, commercial fit-out projects, infrastructure subcontractors, and facility management teams maintaining multi-building campuses. Any environment where vendors already message on WhatsApp but nobody trusts the thread as a system of record.
Trigger: A vendor or site contact sends a message — a status question, a work order request, or a blocked-issue report. RE061 classifies intent and collects the minimum structured data before confirming the ticket.
Outcome: A logged action with trade, site, urgency, and contact details; PM escalation when rules match; and a reference ID the vendor can quote on follow-up — Ref #RE061-XXXX.
Sample vendor prompt
"Log a plumbing work order at Villa 14, urgency high — rough-in mismatch with drawing REV-3."
Agent response includes:
- Work order confirmed: Plumbing · Villa 14
- Urgency: High
- PM escalation queued
- Reference ID with copy button
- Quick replies: Check status · Add photos · Report another issue
Scenario walkthrough: Skyline Projects, Villa 14 plumbing
Skyline Projects is developing a 24-villa gated community on the outskirts of Bangalore. Eight trades are active this month: civil, plumbing, electrical, HVAC, flooring, painting, landscaping, and aluminium windows. The PM office uses a shared WhatsApp group with 47 members. Site supervisors, vendor foremen, and back-office staff all post daily. Important requests have a half-life of about twenty messages.
On Tuesday morning, Apex Plumbing's foreman Ramesh arrives at Villa 14 for second-fix inspection. He finds the rough-in for the master bath shower does not align with drawing revision REV-3 issued last Friday. The civil team poured according to an older mark. Rework is needed before he can proceed. This is not a casual query — it blocks the plumbing schedule and risks the week's milestone sign-off.
Instead of dumping a voice note into the group chat, Ramesh opens the Skyline vendor portal on his phone — or messages the Skyline business WhatsApp number configured with RE061. He types:
"Log a plumbing work order at Villa 14, urgency high. Rough-in mismatch with drawing REV-3 — shower drain offset wrong by ~4 inches. Need civil rework before we continue. Contact Ramesh, Apex Plumbing."
RE061 parses the intent as Work Order (not a general query or passive issue report). It validates vendor name and site — both present. It confirms trade (plumbing), location (Villa 14), urgency (high), and concern detail. It generates RE061-202607051512, queues PM escalation because urgency is high and the issue blocks a trade, and replies:
Work order logged — Villa 14 · Plumbing · High urgency
Reference: RE061-202607051512
PM notification sent. Expected review within 2 hours.
Quick replies: Check status · Add detail · Report another issue
PM Ananya Krishnan receives an SMS stub at 7:52 AM with the reference, site, trade, and summary. She opens the RE061 dashboard, sees the full text, assigns civil supervisor Devan to inspect within the hour, and updates the ticket status to "In review." Ramesh checks status at 9:00 AM via WhatsApp — "Status RE061-202607051512" — and gets a structured reply without calling anyone. Civil rework is approved by 11:00 AM. The work order existed in a system, not in a scrollback search.
Why WhatsApp alone fails as a coordination layer
WhatsApp is excellent for quick human conversation. It is poor at being a work order database. On a typical Skyline group thread before RE061, you would see:
- Mixed intents in one stream. A plumbing blocker sits between a cement delivery photo and a birthday wish.
- No required fields. "Need help at 14" means nothing without trade, urgency, and contact.
- No reference IDs. Vendor calls back: "I messaged yesterday" — which message?
- Status check loops. "Any update?" × 6 vendors × 3 sites = PM phone never stops ringing.
- Escalation ambiguity. Nobody knows if the PM saw the high-urgency issue or just the good morning sticker.
- Zero audit trail. Post-mortems after milestone slips have no structured log — only chat exports.
WhatsApp vs. RE061 intake
| Capability | Group chat | RE061 |
|---|---|---|
| Intent classification | Manual | Automatic |
| Required field validation | None | Vendor + site enforced |
| Reference ID | No | RE061-XXXX every ticket |
| PM escalation rules | Ad hoc | Config-driven |
| Status lookup | Phone chase | Self-serve via chat |
| Audit / reporting | Chat export | Structured dashboard |
Three desks, one standard: Query · Work Order · Report Issue
RE061 does not force vendors through a rigid IVR menu. It uses natural language intent detection and clarifying prompts when fields are missing. Under the hood, every submission routes to one of three operational desks — the same three workflows your PM office already thinks in, but rarely enforces in chat.
Query Desk
For drawing clarifications, schedule questions, material specs, and access requests.
Example: "What time is the Villa 9 inspection tomorrow?" → logged query, routed to site coordinator, Ref #RE061-XXXX returned.
Work Order Desk
For actionable trade tasks — install, rework, fix, replace — with site, trade, urgency, and vendor contact required.
Example: Villa 14 plumbing rework → high urgency → PM escalation → Ref #RE061-202607051512.
Report Issue Desk
For blockers, safety concerns, material delays, and gate access failures — escalates when severity or idle time thresholds match.
Example: "Villa 7 — electrical panel delivered damaged, install blocked" → issue ticket + PM alert.
RE061 workflow: Capture → Route → Escalate → Resolve
| Stage | Agent action | Validation | Output |
|---|---|---|---|
| Capture | Accept message via widget or WhatsApp | Channel auth; spam rejection | Raw intent detected |
| Classify | Route to Query · Work Order · Report Issue | Confidence threshold; clarifying prompt if ambiguous | Desk assignment |
| Validate | Collect vendor name, site/project, trade, urgency | Work orders require vendor + site; rejects incomplete | Structured ticket payload |
| Escalate | PM SMS/email stub on high urgency or blocked trade | Rules per site and trade priority matrix | PM notification + open ticket |
| Resolve | Status updates logged against reference ID | Vendor can self-serve status check anytime | Closed ticket with audit trail |
Vendor status without the phone chase
After logging Villa 14, Ramesh does not need to call Ananya for updates. He messages: "Check status RE061-202607051512" or uses the quick reply button. RE061 returns the current state — Open · In review · Assigned to civil · Resolved — with timestamp of the last update. This alone removes dozens of daily status calls from the PM's phone.
For PM offices, the dashboard aggregates open tickets by site, trade, and age. Weekly reports show which vendors log cleanly (structured intake) versus which still dump unstructured messages into the legacy group — useful for contract compliance conversations.
Urgency and escalation matrix
| Urgency | Typical triggers | PM notification | Target response |
|---|---|---|---|
| High | Trade blocked, rework needed, milestone risk, safety flag | Immediate SMS stub | < 2 hours |
| Medium | Schedule slip, material delay, access issue | Digest + optional SMS | Same business day |
| Low | General query, future scheduling, documentation request | Dashboard only | 24–48 hours |
Operational impact metrics
Work orders captured with complete fields94%
PM status-call reduction (vendor self-serve)-58%
High-urgency escalation within SLA89%
Vendor adoption after 30-day rollout82%
See it live: Skyline Projects demo
The DestinPQ demo at agent-demo.destinpq.com/re061.html mirrors the Skyline vendor portal pattern. Walk through the construction office site, open the bottom-left chat widget, and log a plumbing work order for Villa 14 with high urgency. The agent returns a structured confirmation with reference ID — then switch to the green WhatsApp button to see the same flow on mobile.
Demo video: agent-demo/videos/re061.mp4 · Runtime ~29 seconds · Site walkthrough → live widget chat → WhatsApp handoff → bot reply with Ref #RE061-XXXX.
How to implement RE061 on your project
- Subscribe to RE061 on agents.destinpq.com. Select Construction Vendor Coordination from the project ops catalogue.
- Embed the widget on your vendor portal or site office dashboard (see re061.html for the luxury-site + widget pattern):
<script src="https://cdn.destinpq.com/agent.js"
data-agent-id="RE061"
data-token="YOUR_API_TOKEN"
defer></script>- Point vendor WhatsApp to your shared business line with multi-agent routing — vendors keep their existing habit; RE061 becomes the structured intake behind it.
- Map sites and trades in the subscription dashboard: Villa 1–24, Block A/B, plumbing/electrical/civil codes, PM escalation contacts per zone.
- Configure urgency rules: which trades block milestones, idle-time thresholds for Report Issue escalation, after-hours routing.
- Connect PM notifications via SMS and email stubs — high-urgency work orders should never wait for dashboard polling.
- Train vendors once: share a one-page card — "Message the Skyline line or open the portal; always get a Ref #RE061-XXXX." Retrain by referencing lost WhatsApp messages vs. logged tickets.
- Test S01 happy path: "Log plumbing work order Villa 14 high urgency" → vendor + site validated → Ref ID → PM stub → status check returns open ticket.
Go-live checklist
- Vendor portal live with RE061 widget
- WhatsApp business line routed
- Site/project map uploaded
- Trade list + urgency matrix configured
- PM SMS contacts verified
- Vendor onboarding card distributed
- Legacy group chat pinned with portal link
Integration note
RE061 logs structured tickets ready for export to your PM tool (Procore, Zoho Projects, custom ERP) via webhook. Phase 1 is capture and escalation; Phase 2 syncs closed tickets to your system of record automatically.
Frequently asked questions
Your site deserves more than a group chat
RE061 turns WhatsApp chaos into structured work orders — with three clear desks, urgency-aware PM escalation, and a reference ID on every ticket. Villa 14's plumbing rework gets logged at 7:52 AM, not discovered at lunch.
Comment BUILD — we'll send the construction vendor desk setup guide.