Real estate automated marketing works when messages are triggered by things that happen to a property or a person, and fails when it simply sends the same content on a timetable. This article is about trigger design: which events on the levelpartner.ai platform should start a workflow, starting with an opportunity changing pipeline stage when an offer is accepted or a sale completes, what each message should say, and how to limit frequency so an active client is not flooded.
Calendar sends versus event sends
Most offices begin automation with a calendar. A monthly email on the first Tuesday, a quarterly market update, a seasonal campaign in spring. That is useful, and it is not really automation. It is scheduling.
Event-based automation is different. A message goes out because something changed: an offer was accepted, a sale completed, a purchase anniversary arrived, a tenancy is three months from renewal. The reader receives it because it is about them, now. That relevance is why event messages earn replies when calendar messages earn unsubscribes.
The point of view here is simple. Build the event layer first, with a small number of triggers that matter, and keep calendar sends to one or two well-targeted newsletters. For the newsletter side, see newsletter formats for each real estate audience.
The events worth automating, and the trigger for each
Not every event deserves a message. These cover most of the value for a sales and lettings office, and each maps to a trigger the platform already has.
- An offer is accepted or a sale is agreed. Trigger: Pipeline Stage Changed, filtered to that stage. Send the buyer and seller what happens next and who to call.
- A sale or tenancy completes. Trigger: Pipeline Stage Changed to your completion stage, or Opportunity Status Changed to won. Send a thank-you, then a review request a few days later.
- A purchase anniversary or a tenancy renewal date arrives. Trigger: Custom Date Reminder on a date field. Send a short note from the agent who handled it.
- A viewing is booked or attended. Triggers: Customer Booked Appointment and Appointment Status. Confirm the viewing, then ask for feedback the same day.
- A valuation request arrives. Trigger: Form Submitted. Reply within minutes and offer times.
- A valuation was done and the homeowner went quiet. Trigger: Stale Opportunities on the valuation stage. Follow up with what has changed nearby.
Things like "a home sold near a past client" are not single-contact events. Send those as a campaign to a Smart List of homeowners in that area rather than as a trigger.
Each of these depends on accurate data: the stage the opportunity is in, the contact's role and the dates that matter. If the data is wrong, the automation is wrong at scale. Contact roles and fields are covered in organising real estate contacts by role and relationship.
How to build a stage-change trigger
Take the completion trigger as the model, because it is the one most offices miss. The day a sale completes is the day a client is most grateful and most likely to review or refer, and it is usually the day the agent is busiest with the next deal.
- Go to Automation, then Workflows.
- Click Create New Workflow, or open an existing workflow to edit it.
- Click Add New Trigger, search for Pipeline Stage Changed and select it.
- Give the trigger a clear name, such as "Sale completed: thank-you and review".
- Set the filters: In Pipeline set to your sales pipeline and Pipeline Stage set to Completed.
- Define the actions the workflow takes after the stage change.
- Click Save Trigger.
- Confirm all the workflow steps are in place, then click Publish.
- Test by moving a test opportunity into the Completed stage and checking the workflow runs as expected.
The actions here are a thank-you from the named agent the same day, a wait of three days, then the review request. Build the offer-accepted workflow the same way with a different stage filter, and send a plain list of next steps.
Two behaviours matter. The trigger fires on stage moves from the moment it is published, not for deals that moved last month. And if an opportunity moves back to an earlier stage and forward again, the workflow fires again. A sale that falls through and is re-agreed would get a second "congratulations", so check for a tag such as "completion sent" before the first message and set it straight after.
Suppose the office completes around 60 sales a month and, sending review requests by hand, reaches perhaps one client in three, about 20. With the completion trigger, every completed sale would get a thank-you the same day and a review request three days later, so all 60 are asked. If two in five of those asked left a review, that would be 24 reviews a month against 8 under the manual habit. Anniversary notes to 4,000 past clients need only a small response to matter: 30 replies a quarter would be fewer than one in a hundred. These figures are illustrative.
Limits, so automation does not become noise
Event-based marketing has a failure mode. A contact who is selling one home and buying another can qualify for several triggers in one week. Without limits, they receive five messages and stop reading all of them.
The platform runs each trigger independently, so the limits are yours to build. Set three rules before any trigger goes live:
- A quiet rule: contacts with an open opportunity in an active stage are excluded from marketing triggers. Use the trigger's tag filter or an If/Else check at the start of each marketing workflow.
- A frequency rule: each marketing workflow sets a "marketed this week" tag and checks for it first, and a weekly workflow removes it. Transactional messages such as viewing confirmations ignore the rule.
- A priority order: where two triggers can fire on the same day, decide which one wins and add a check for the other's tag.
Letting every agent build their own automations. Within months the office has overlapping workflows, contacts in three at once and nobody able to say what a client received. One person should own the trigger list, the tags and the templates, and agents should request changes rather than build them.
What most articles on automated marketing get wrong
Most advice on real estate automated marketing measures success by volume: how many emails sent, how many drip sequences running, how many contacts enrolled. More looks like better.
It is not. Every automated message spends a little of the reader's attention and a little of your sender reputation. A large volume of low-relevance messages trains readers to ignore you and teaches inbox providers to filter you. The measure that matters is replies and appointments per message sent, broken down by trigger. A trigger that sends thousands of messages and produces no conversations should be switched off, however busy it makes the dashboard look.
Text, email or both
Use email for anything with images, detail or a link to a property page. Use SMS for short, timely messages where the contact has opted in: a new match, a price change, a viewing reminder. Do not send the same message on both channels at once; pick one, and use the other only as a follow-up if there is no response. Consent rules for marketing texts differ between countries, such as the US and the UK, so keep opt-in records per contact and per channel. For text-specific practice, see running SMS marketing for a real estate office.
Say an office sends price-change alerts to 300 buyers who viewed affected homes in a month. Assume email alone gets 40 replies or bookings. Texting the 180 who opted in and emailing the other 120 might get 65. Sending both text and email to the 180 opted-in buyers might lift that to 70, but if it also prompts 25 unsubscribes, five extra responses would cost 25 reachable buyers. The numbers are invented to show the trade-off.
The trade-off
Event-based automation takes longer to set up than a calendar of campaigns. You need clean contact roles, dates and areas, a person who owns the trigger list, and a few weeks of reading replies to tune the wording. If your data is poor, the first month is spent fixing it rather than sending.
What you give up by staying with calendar sends is relevance. Scheduled campaigns are faster to launch and simpler to explain, and they produce steady, modest results. If your office has a large past-client base and flat instructions, the event layer is where the missing listings are. For time-bound pushes that sit alongside it, see email campaign templates with a start and an end.
Measuring each trigger
Review triggers monthly in Reporting, one row per trigger. Track messages sent, replies, appointments booked, opportunities created and unsubscribes. Keep a trigger that produces conversations at a reasonable unsubscribe rate. Rewrite a trigger with low replies. Switch off a trigger whose unsubscribes outnumber its replies. For how AI and automation work across each stage of a transaction, read mapping AI to each stage of a property transaction.
Frequently asked questions
How many automated triggers should an office start with?
Start with three: valuation form replies, the offer-accepted stage change and the completion stage change. Run them for a month, read the replies, and add more only once those three are reliable.
Will automated messages feel impersonal?
Not if they are sent from the agent the client knows, written in that agent's voice and triggered by something relevant to the reader. Impersonal automation comes from generic content and generic senders, not from automation itself.
Can AI write the messages?
AI content can draft each template from your notes, and an AI agent can answer simple replies. A person should approve every template once before it goes live, and check any figure or property detail it includes.
What happens when a contact replies?
The reply should land in a shared inbox, tag the contact and alert the named agent. Automation starts the conversation; a person continues it, usually the same day.