Status Changes → Pick Template → Personalise → Send → Log

Resident Update Blaster

Sends quick scheduled, on-the-way, and completed messages tied to ticket status, so residents stay informed without anyone retyping the same update.

The Problem

Coordinators retype the same status messages all day.

Staff spend time sending manual update texts for every job.

What Changes

Scheduled, on-the-way, completed, sent automatically.

Sends short status messages - scheduled, on-the-way, completed - tied to real ticket status changes. No manual drafting.

Humans stay in control: Your team does the work and owns the templates. The agent sends the status notes. It removes the manual messaging, not the work.

HOW THE AGENT WORKS

TRIGGERLLMAPIDECISIONACTIONWAIT
TRIGGERStatus ChangesA ticket hits a notify milestone
LLMPick TemplateMatch the status to a message
LLMPersonaliseFill in unit, time, vendor details
DECISIONNotify Now?
ACTIONSend UpdateMessage the resident
ACTIONLog TouchRecord on the ticket
The agent doesn't decide the work. It sends the status messages tied to ticket state. Your team controls the templates and the triggers.

HOW TO BUILD IT

Three levels of depth. Pick the one that matches where you are.

For the ops person who needs to understand what's involved and brief their team.

Your TicketsStatus milestones
The AgentWorkflow engine + LLM
Your ResidentsTimely status notes

WHAT YOUR TEAM PROVIDES ONCE

  • Milestone triggers - which statuses send a message
  • Templates - the approved wording per milestone
  • Channels - SMS or email per resident
  • Quiet hours - when not to send
  • Opt-out handling - respecting resident preferences
What happens day-to-day: A ticket moves to scheduled, then on-the-way, then done. The agent sends the matching message each time so the coordinator does not have to. Residents feel informed and the phone rings less.

For the IT person or technical lead who needs to scope the integration.

INQUIRY SOURCES

PMS status events
CMMS
Dispatch tool

WORKFLOW ENGINE (N8N)

Trigger - status change
LLM - Pick template
LLM - Personalise
Branch - notify now?
Send update
Log touch
Respect quiet hours

CONNECTS TO

PMS / CMMSRead: ticket status
SMS / email (Twilio / SMTP)Send updates
Resident directoryRead: channel + opt-out
Ticket logWrite: message history
WITHOUT PMS API

Agent polls a status sheet and sends from templates. The messaging logic still runs.

WITH PMS API

Agent fires on live status events and logs each touch on the ticket. Best experience.

For the person who wants to build this agent step by step. Each node below maps to an n8n workflow node.

TRIGGERNode 1
Trigger - Status Changes
Webhook on ticket status, filtered to notify milestones.
Output: { ticket_id, unit_id, new_status, details }
LLMNode 2
LLM - Pick & Personalise Template
Choose the milestone template and fill in the specifics.
Output: { milestone, message, send }
You produce a resident status update.

Given the status change and TEMPLATES, return:
- milestone: matched milestone or "none"
- message: the filled-in template (plain language)
- send: true only if this milestone notifies residents
Respond ONLY with valid JSON.

TEMPLATES: {templates}
CHANGE: {change}
INPUT
{ "new_status": "tech_en_route", "eta": "20 min", "tech": "Mike" }
OUTPUT
{
  "milestone": "on_the_way",
  "message": "Your maintenance tech Mike is on the way, about 20 minutes out.",
  "send": true
}
DECISIONNode 3
Condition - Notify Now?
IF send and outside quiet hours and not opted out → send. ELSE → hold or skip.
Output: Branch: SEND or HOLD/SKIP
ACTIONNode 4
Send Update
Send on the resident’s channel.
Output: Resident updated.
ACTIONNode 5
Log Touch
Record the message on the ticket.
Output: Touch logged.
MVP vs Advanced — Where To Start
MVP — START HERE
  • Status-poll trigger
  • Fixed templates
  • Single channel
  • No quiet hours
  • Manual log
  • Basic opt-out
ADVANCED — ADD LATER

    Full Video Walkthrough Coming Soon

    From a status change to an automatic update - step by step.

    Register to be notified

    Everything on this page is free to learn.

    When you're ready to build — do it yourself or bring us in.

    OTHER AGENTS IN LEASING & MARKETING

    Collects from every channel, asks what's missing, creates clean tickets
    Translates two-way messages, keeps consistent records
    Drafts standardised notices with required wording in place
    Answers questions, opens requests, routes to the right team

    Frequently asked questions

    Resident Update Blaster is an AI agent that sends status updates tied to ticket milestones, and automatically.
    Coordinators retype the same status messages all day. The Resident Update Blaster addresses this — it sends status updates tied to ticket milestones, and automatically.
    No — your team stays in control. Your team does the work and owns the templates. The agent sends the status notes. It removes the manual messaging, not the work.