Landstar Realty Group · Lead Automation

Every five minutes, the system runs the whole playbook.

This page maps every automation working your rental leads — what fires, when it fires, and what makes it stop. All times are Chicago time.

Cycle: every 5 min, around the clock
Texting hours: 7:30 AM – 9:00 PM
Sources: YouGotListings · Apartments.com · Avail
01

The five-minute cycle

One pass runs these nine steps in order. If a step hits an error, it's logged and the rest still run — one problem never stalls the whole machine.

Check replies

Scans Quo for new inbound texts, calls, and voicemails from renters.

Recover appointments

Catches up on any showing texts missed during downtime.

Detect appointments

Reads Kris's confirmation texts and books the calendar.

Send showing reminders

Texts renters their day-before and day-of reminders when due.

Check email replies

Watches Gmail for renters replying to re-engagement emails.

Read new leads

Pulls unread lead emails from the three listing sources.

First texts

Sends the opening two texts to new, clean leads.

Follow-ups

Sends any no-response texts or emails that have come due.

Daily report

Once per morning, emails Kris the full summary.

Only one cycle runs at a time — overlapping runs are locked out, so nothing ever sends twice.

02

Lead intake

New inquiry emails become clean HubSpot contacts — or get flagged for a human when anything is unclear. The system never guesses.

Unread lead emails
YouGotListingslisting inquiries
Apartments.comlead emails
Availinquiry notices
Parsed & matched

Read → match → decide

Pulls the renter's name, phone, email, and the property. Looks them up in HubSpot by phone first, then email. The email is marked read once handled.

One of three outcomes
Clean leadContact created or updated in HubSpot, queued for the first text.
Unclear → reviewTwo possible matches, or a masked email with no phone. Nothing is guessed — Kris gets a review task.
Duplicate → skippedSame inquiry seen before. Recognized and dropped, no double texting.

Combined inquiries smart batching

  • New leads sit in a short 5-minute holding window before the first text.
  • If the same renter inquires about several properties in that window, they merge into one first text listing all the properties — no spam of separate texts.
  • Each extra inquiry restarts the 5-minute clock.
03

The first text

Two fixed messages, sent back to back, from Kris's Quo number.

Sent as Kristian · Quo SMS

Hey {first name}, this is Kristian from Landstar Realty Group. I am reaching out to you about the rental you are interested in at {property}. Msg freq varies. Msg/data rates may apply. Reply STOP to opt out, HELP for help
When are you looking to move in by, how many people will be moving in and do you have any pets?

Who gets it — and who doesn't rules

  • Only clean leads with a valid mobile number. No phone → no text, ever.
  • Only between and . Leads arriving overnight wait for morning.
  • Skipped if the renter is opted out or sitting in review.
  • Right before sending, the system re-checks: if the renter already texted in, or someone already messaged them manually, it stands down.
  • The required STOP notice rides along with the first message.
04

Reply, call & voicemail tracking

Every cycle scans Quo for anything inbound. One reply of any kind shuts the whole follow-up sequence off.

What counts as a response quo

  • Inbound texts — matched to the contact by phone number.
  • Inbound calls and voicemails count too, not just texts.
  • The contact is marked responded in HubSpot right away.
  • All scheduled follow-up texts and emails for that renter stop.

Opt-outs compliance

  • A reply of “STOP” records an opt-out on the contact.
  • Opted-out renters get no further automated texts of any kind — follow-ups and showing reminders included.
  • Opt-outs show up in the daily report.

Email replies

  • Once the email arc starts, Gmail threads are watched for replies every cycle.
  • A renter reply marks them responded and ends the email sequence.
05

The no-response sequence

If a renter goes quiet after the first text, this is the full arc — three texts, then three emails, then done. Silence at any point below means they still haven't responded.

Day 0 · on arrival

First touch — two texts

Intro plus qualifying questions, sent after the 5-minute batching window (within texting hours).

Day 1 ·

Follow-up text

“I'm not sure if you missed my last text. Would you still be interested in checking out {property}?”

Day 2 ·

Final text

“Just following up one last time… Are you still interested? If not, no worries at all.”

Day 3 ·

Email 1 — “Your inquiry about {property}”

Re-asks move-in date, occupants, and pets. States the screening bar: 650+ credit and 3× rent income.

Day 4 ·

Email 2 — short nudge

A brief reply on the same thread. Emails 1 and 2 only go out in the morning — if a send slips past noon, it rolls to the next morning at 8:15.

Day 5 ·

Email 3 — “Still looking for a place?”

Final check-in. After this the sequence completes and the renter is left alone.

Any point

Sequence over

Done — either because the arc finished, or because the renter responded along the way.

What stops the sequence instantly

A text reply · an inbound call · a voicemail · an email reply · a STOP opt-out · the lead being flagged for review or marked as handled manually. Before every single send, the system re-checks all of these one more time.

06

Showings: detection & calendar

Kris books showings by texting the renter as usual. The system reads those outgoing texts and does the bookkeeping.

From text to calendar calendar

  • Kris's outgoing confirmation texts are read for an address, date, and time.
  • All three must be explicit — a vague text is ignored rather than guessed. Same for dates in the past or more than 30 days out.
  • A one-hour Google Calendar event is created: “{Renter} – {Address}”.
  • The renter's name comes from their HubSpot record via the phone number.

Changes & cancellations calendar

  • Kris texts a cancel or reschedule → the event turns red.
  • Kris confirms a new time with the same renter → fresh event created, the old one turns red.
  • Dragging the event to a new time directly on the calendar works too — reminders recalculate automatically.
Blue — renter confirmed
Gray — awaiting confirmation
Red — canceled or rebooked
07

Showing reminders

How much reminding a renter gets depends on how far ahead the showing was booked.

Booked two or more days ahead example: booked Monday, showing Thursday
Mon · booked
Kris books the showingevent created, gray
Tue
quiet
Wed · day before
Reminder text4:30 PM — “reply to confirm”
Thu · showing day
Day-of reminder8 or 11 AM
Showing
Booked for tomorrow example: booked Monday, showing Tuesday
Mon · booked
Kris books the showingevent created, gray
no evening text
Tue · showing day
Day-of reminder8 or 11 AM
Showing
Wed
Thu
Booked same day example: booked Monday morning, showing Monday afternoon
Mon · booked & shown
Kris books the showingevent starts blue — just confirmed
no reminders
Showing
Tue
Wed
Thu

Day-of timing rules

  • Showing before 12:30 PM → reminder at . Later showing → .
  • Always at least one hour before the showing, and never before 7:30 AM.
  • A reminder that misses its window expires — it is never sent late.

If the renter goes quiet alert

  • No reply one hour after the day-of reminder → Kris gets a text.
  • “{Name} hasn't confirmed today's {time} showing at {address} — no reply to the reminders.”
  • Sent no later than 30 minutes before the showing, so there's still time to act.
08

When the renter replies to a reminder

Kris only gets texted when something actually needs attention.

“Confirmed!”
Event turns blue. Kris gets no text — nothing to do.
Cancel / reschedule
Event turns red and Kris gets a text with a preview of what the renter said.
Anything else
Recorded quietly. No text to Kris — but any reply at all cancels the “hasn't confirmed” alert.
They call instead
Counts as a reply. The no-confirmation alert is called off.
09

The daily report

One email to Kris each morning — the first cycle after , exactly once per day.

From Landstar Assistant · To Kris · 7:00 AM
Landstar lead digest — Mon, Jul 21
New leads yesterday
YouGotListings4
Apartments.com2
Avail1
Sends & replies
6 first texts · 3 follow-ups · 2 re-engagement emails
3 replies (2 text, 1 call) · 1 opt-out
2 showings booked · 1 confirmed
Needs your attention
1 lead in review — two possible HubSpot matches for J*** M***
System health
No unresolved errors · last cycle ran 6:55 AM

How it's delivered

  • Exactly once per day — the first cycle after .
  • Covers the previous day plus a 7-day trend of replies and opt-outs.
  • Review items list what's stuck and why, with renter details masked.
  • Warns when the numbers look unusual, so problems surface without anyone checking dashboards.

numbers shown are an example day

10

Safety rails

The rules that hold everything above in check.

Never a guess principle

  • Ambiguous contact match → review task, not a write.
  • Vague showing text → no calendar event, rather than a wrong one.

Quiet hours principle

  • No automated text leaves before or after .
  • Late reminders expire instead of arriving at the wrong time.

Kill switch principle

  • A single switch halts all sending — checked at the start of every cycle and again before every individual send.
  • Errors are logged per step and surface in the daily report — one failure never cascades.