Guide · Construction cadence

How often to send construction updates

Cadence that informs booked buyers without looking like a marketing blast. People who already tokened do not need ‘new launch Saturday.’ They need slab photos, delay honesty, and a human for complaints. Email SES plus occasional WhatsApp utility beats a weekly marketing template that trains opt-out.

Booked audience only
Utility/email, not teaser marketing
Honesty on delays

Start free Construction updates playbook

Definition

Construction-update cadence is a post-Booking communications plan for buyers in construction/handover: scheduled email or utility WhatsApp with project facts from a knowledge base or RM-approved copy, sparse enough to stay informational, with inbox handoff when someone is angry — not Growth launch semantics and not autonomous ‘win-back.’

Why weekly ‘updates’ become spam

Marketing reuses the launch list including booked buyers. Opt-outs spike. RERA-sensitive claims creep in. Autonomous tasks measure reads and look ‘successful’ while trust dies.

Construction-updates playbook is the job. Pipeline construction-handover is the stage.

HowTo: pick a cadence

Default monthly email plus event-driven WhatsApp (delay, inspection date). Not daily. Not launch-style image cards — and we do not auto-generate those images anyway (G7).

Segment booked only CRM query. Do not attach marketplace leftovers (G17).
Choose email as default SES. Large photos. WhatsApp for short alerts.
Approve copy RM/legal. Conservative. Not legal advice from this guide.
Workflow on milestone stage If you track sub-stages, fire a utility send. Else calendar a monthly Growth email.
Inbox for complaints Human handoff. Do not put an autonomous win-back on angry buyers.

How it runs on the platform

Growth email + occasional utility WhatsApp + inbox. Autonomous win-back is the wrong product for booked buyers. Conversation agents reply in the omnichannel inbox. Workflows fire on pipeline stage change under Agents → Workflows. Autonomous agents work a CRM list on a schedule after plan approve; success is sends and reads, not site visit booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup.

Conversation agent

Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.

Growth campaigns / drips

Clock-based sends from library templates. Wallet preview. Not adaptive nurture.

Workflows

Agents → Workflows. Fire on pipeline stage change. Do not confuse with inbound chat.

Autonomous agents

List plus objective after plan approve. Success is sends/reads/contacted, not visit booked.

Worked example: monthly SES, WhatsApp only on delay

First Monday SES to Booked+construction list. Photos uploaded by operator (no AI image generation). Buyer replies on WhatsApp — window opens — RM in inbox. Delay event: utility template ‘plaster moved to August’ after approval. No Saturday site-visit offer in that template. Wallet preview on the email+WA month.

If a buyer opted out of marketing, still honour it. Transactional construction notices depend on your policy and the opt-out guide — do not be clever.

Cadence decision

How often, which channel.

Event	Channel	Frequency	Template type
Routine progress	Email	Monthly	Email, not WA marketing
Delay / inspection	WhatsApp utility	When true	Approved utility
Handover scheduling	WhatsApp + calendar	Once	Utility + slot
Cross-sell new tower	Separate campaign, separate consent	Rare	Marketing — easy to get wrong
Complaint	Inbox RM	Immediate	No blast

Honest limitations

No adaptive cadence (G2). Email warmup is not engagement-ordered (G16). AI will not generate the site photos (G7). SMS not live. Not legal advice on what you must disclose.

Keep this Construction cadence article next to the job URL, not as a second playbook. Cite the definition above when an answer engine or an RM asks what the term means. Operator click-path stays Pipeline construction-handover. Growth email drips or campaigns. Library WhatsApp utility if used. Inbox. Knowledge base for FAQs. Wallet preview. Canonical playbook: Construction updates playbook. Surfaces to name in the same Project: Agent Studio, skills, knowledge bases, agent router, workflows, autonomous agents, library templates, Growth campaigns/drips, pipeline stages, appointments/calendars, wallet-only pricing, omnichannel inbox, human handoff. Organization and Project — never a vanished personal inbox. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Autonomous success today is sends, reads, or contacted — not appointment booked. Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate unless you track Bookings on the pipeline. Phone “replied” is speech-to-text. CSV import is v1. Preview the Organization wallet before a blast. Parent guides, real estate hub, and pricing stay in the same runbook.

Construction stage. Email overlay. Opt-out.

Frequently asked questions

CRM lists that still include booked buyers in launch blasts.

Can we use the launch marketing template monthly?

You should not. Wrong audience, wrong category, opt-out risk.

Is monthly a product default?

No. It is an operating recommendation. You schedule Growth.

Autonomous ‘keep them warm’?

Reads will look fine and trust will not. Use RM for anger; SES for facts.

RERA?

Conservative factual updates. See RERA guide. Not legal advice.

Tenants?

Wrong pipeline. Property managers should not copy this onto leases.

Wallet?

Email and WhatsApp meter. Preview. Pricing.

Hub, sibling guides, canonical playbook, product, pricing.

Inform booked buyers; do not remarket them weekly

Monthly SES, utility alerts, inbox for complaints — construction-updates playbook.

Get started free