Guides
How to Build a Post-Tour Leasing Follow-Up Workflow with Thoughtly
Build a CRM-triggered Thoughtly workflow that follows up after completed apartment tours, routes the right next step, and measures rental applications through units leased.
Guides
Build a CRM-triggered Thoughtly workflow that follows up after completed apartment tours, routes the right next step, and measures rental applications through units leased.
Last updated
A completed apartment tour is not a cold lead and it is not another speed-to-lead event. The prospective renter has already raised a hand, visited a community, and spent time with the leasing team. The next useful question is narrower: what should happen now so a real application can move forward, or the journey can close cleanly?
A post-tour leasing follow-up workflowWorkflowAn automated, multi-step process — usually triggered by an event (form fill, new lead) and orchestrating one or more voice / SMS / email actions. should start only after the system of recordSystem of recordThe authoritative system where customer, lead, policy, loan, appointment, or account data is stored and updated. confirms that the tour occurred. Thoughtly can then carry the community and tour context into an approved voice, SMS, or email follow-upEmail follow-upEmail follow-up is the process of sending timely, context-aware replies or reminders that keep an inbound lead moving toward qualification, scheduling, or handoff., capture the prospect's next-step intent, send an official rental-application link when appropriate, and route questions that need a person.
The conversion unit is not calls placed. It is rental applications started and submitted, followed by units leased. That is the standard that keeps the workflow attached to property-management revenue instead of turning it into generic messaging automation.
To build post-tour leasing follow-up with Thoughtly, triggerTriggerThe event or condition that starts an automated workflow, such as a new lead, missed call, CRM status change, calendar booking, or completed call. an Automation from a verified completed-tour event in your CRMCRMThe system of record for leads, contacts, deals, and activity. Thoughtly reads from and writes to your CRM continuously., PMS, scheduler, or integration layer. Filter out opt-outs, duplicates, already-submitted applications, and stale property records. Pass only the current community, tour, prospect, owner, and permission fields into the call. Then use a compact agent flow to classify the next step: ready to apply, needs approved information, wants another tour, needs a leasing specialist, is no longer moving, or wants communication to stop.
Thoughtly's Automation triggers support incoming webhooks, CRM events, schedules, and post-call hooks. Its Automation actions and steps can branch, call a contact, send SMS or email, write dispositions and attributes, schedule a follow-up, and send data back through CRM or webhookWebhookAn event-based integration that sends data from one system to another when something happens, such as a form submission, booked appointment, or completed call. actions. The system of record should still own tour status, rental-application status, screening, and lease execution.
The existing leasing inquiry speed-to-lead guide owns the path from a new inbound inquiry to a booked tour. The leasing re-engagement guide covers a paused search, changed inventory, a canceled tour, or a missed tour. This guide begins after the tour status is completed and the next conversion event is a rental application.
That start state changes the build. You do not need to rediscover which property the person asked about or pretend this is a first conversation. You do need an authoritative tour record, the latest property facts, a clear application path, a human owner, and a terminal state for prospects who are not moving forward.
| Workflow state | Required context | Thoughtly action | Structured output | Human boundary |
|---|---|---|---|---|
| Completed tour, eligible | Contact ID, community, tour time, permission state | Call Contact with per-call metadata | Attempt ID and current journey state | No screening or approval judgment |
| Ready to apply | Official application URL and current unit context | Send SMS or email link | Link sent and application next step | PMS or application system owns submission |
| Needs approved information | Question topic and verified property source | Answer from approved knowledge or create a task | Question category and resolution state | Pricing exceptions and policy questions go to staff |
| Wants another visit | Community, tour type, timezone, verified availability | Check times and schedule only an available slot | Second-tour status and appointment ID | Accommodation requests go to trained staff |
| Needs a leasing specialist | Summary, property, urgency, assigned owner | Transfer or create a priority task | Handoff result and owner | Human handles concessions, screening, and exceptions |
| Not moving forward | Neutral reason category and preferred channel | Write disposition and stop this path | Closed-lost or future-timing state | Do not infer a reason |
| Opt-out or wrong party | Channel and stop signal | End and update suppression state | Suppression timestamp and source | No further automated follow-up |
Write the entry rule in plain language. A useful version is: enter post-tour follow-up when a known inbound leasing inquiry has a completed tour, no rental application has been started or submitted, no later tour or active follow-up already exists, the property context is current, and the record remains eligible for the approved channel.
Write the exclusions beside it. Suppress a record when the tour was canceled or marked no-show, the person opted out, the phone or email belongs to someone else, an application already exists, the unit or community data is stale, a complaint or accommodation request is unresolved, or another workflow owns the next action. If the source event cannot explain why the person is eligible, the workflow should not guess.
Choose one state vocabulary across systems. For example:
A small, stable vocabulary is easier to test and report than free-form notes such as "seemed interested." The notes can add nuance; the structured state should decide what happens next.
The cleanest pattern is an Incoming Webhook fired by the CRM, PMS, scheduler, or integration layer when the tour status becomes completed. Include a unique event ID. Thoughtly's trigger documentation recommends planning for idempotency because external systems can retry events. Store or check that event ID so the same tour cannot create two calls.
If the completed-tour status is available through a native CRM event, use that event instead. If the source system cannot emit a reliable event, a narrow recurring schedule can query records that entered the completed state since the last run. Do not turn a loose daily sweep into an excuse to call every old prospect.
Before the call step, add Conditions that verify the current state. Check the tour status again, confirm no application has appeared since the original event, confirm the record is not suppressed, and require the minimum routing fields. This protects the workflow from racing a human leasing specialist or a delayed PMS update.
Use metadata for call-specific context and attributes for persistent contact facts. Tour ID, community ID, units or floor plans shown, tour timestamp, application URL, source event ID, and assigned leasing specialist usually belong in per-call metadata. Durable preferences or the latest approved journey state can be written as contact attributes when they are needed across future conversations.
A practical per-call payload might include:
Keep tokenized application URLs short-lived and inside the systems that need them. Do not place Social Security numbers, bank details, identity documents, screening results, or a full application payload into metadata, attributes, prompts, or call notes.
The opener should identify the property manager or community, reference the completed visit, and explain the purpose without pretending the agent conducted the tour. Then ask one broad but bounded question: whether the person would like the application link, has a property question, wants another visit, needs a leasing specialist, or is no longer considering the community.
Use variables to capture only the fields that drive the next step. Useful examples are next_step_intent, application_link_requested, second_tour_requested, question_category, human_help_needed, preferred_channel, and stop_requested. Extraction instructions should return an empty value when the answer is unclear rather than inventing one.
Use open-ended interpretation only to understand ordinary intent. Use deterministic rule-based routing for stop requests, missing permissions, action results, and other critical paths. Thoughtly's outcomes documentation recommends rule-based outcomes for precision and compliance-sensitive logic, with a final Else path so an unclear reply does not strand the conversation.
Confirm that the prospect wants the official application link, then use Send SMS or Send Email if that channel is approved. Record that the link was sent, but do not claim the application is complete. The application system remains the source of truth for started, submitted, screened, approved, denied, and withdrawn states.
Answer only from current, approved property information. Good topics include published amenities, office hours, tour options, application-process steps, and factual availability when a live source supports it. If price, fees, concessions, unit availability, or policy cannot be verified at that moment, create a task or transfer rather than improvising.
Use a scheduling action only against verified availability. Thoughtly's scheduling guide recommends checking available times, presenting a short set of real slots, confirming the selected time, and routing booking failures to a fallbackFallbackA safe backup path used when the caller says something unexpected, an integration fails, or the agent cannot confidently complete the intended step.. Store the new appointment ID so the completed-tour event cannot keep reopening the old workflow.
Transfer or create a priority task with the community, tour, question category, captured intent, and contact result. A useful handoff saves the prospect from repeating the visit history. A bloated transcriptTranscriptThe text record of a voice conversation, used for review, training, compliance audit, and search. dump does not.
Capture a neutral, optional reason category such as timing, location, price range, unit mismatch, already leased elsewhere, or prefers no reason. Do not probe for or infer protected characteristics. Close this workflow and let the property team's approved future-contact policy determine whether any later lifecycle state is allowed.
Use the On Call Completed trigger for post-call automation. The trigger exposes outcomes, captured variables, action flags, transfer data, voicemail state, and call telemetry that can be parsed with Conditions before writing to the CRM, PMS, spreadsheet, or BI layer.
At minimum, write back:
Treat write-back failure as an operating exception. The call may have succeeded while the system of record still looks untouched. Send a failure notification or create a review queue, and make retries idempotent so a repaired integration does not send another application link.
The Fair Housing Act protects people from discrimination in renting and other housing-related activity. A post-tour agent should use consistent entry rules and scripts, give equal access to approved property information and the application path, and route accommodation or policy questions to trained staff.
Keep the agent outside tenant screening. It should not predict whether someone will qualify, interpret a screening report, recommend an approval or denial, negotiate a deposit, improvise an eligibilityEligibilityThe fit criteria that determine whether a prospect can move forward, such as service area, insurance coverage, loan type, location, age, or program requirements. rule, or discourage an application. Those are different decisions with different owners.
A completed tour establishes prior engagement; it does not erase communication rules. The FCC's AI-voice declaratory ruling confirms that AI-generated voices fall within the TCPATCPAUS federal law governing telemarketing calls and SMS. Thoughtly enforces consent capture, time-of-day windows, and DNC scrubbing automatically.'s artificial or prerecorded voice restrictions. Have counsel review the actual channel, consent, identification, timing, and opt-outOpt-outA recipient’s request to stop receiving calls or messages. Compliant systems must capture opt-outs and suppress future outreach where required. design, including state and local requirements. Honor stop requests immediately.
Thoughtly's testing guide separates fast text testing in Test Agent from real voice checks with Call Me. Test the trigger and action payloads in Draft mode first, then run the conversation paths with internal records and numbers.
A useful launch suite includes:
Inspect the structured output after every test. The happy pathHappy pathThe ideal conversation flow where every input matches expectations and the agent reaches the intended outcome with no detours. matters, but duplicate suppression, failure recovery, and stop behavior are what keep the workflow from becoming expensive theater.
Build reporting from the completed-tour cohort forward. Useful operating metrics include eligible completed tours, contact attempts, contacts reached, application links requested, links sent, second tours booked, and human handoffs. The business funnel should then follow rental applications started, applications submitted, and units leased.
Compare results by community, lead sourceLead sourceThe channel, campaign, marketplace, referral partner, or form that generated a lead. Lead source often determines routing, compliance rules, and follow-up cadence., tour type, and workflow version. Use a pre-launch baseline or a valid holdout when the operation can support one; the existing conversion-lift measurement guide explains why activity alone does not establish incremental impact.
A high contact rateContact rateThe percentage of inbound leads your team actually reaches by phone. Most B2C teams hover around 25%; Thoughtly typically delivers 90%+. with few submitted applications may point to stale property information, a broken application path, or poor handoff timing. Many links sent with few applications started may mean the link or mobile experience is the bottleneck. The purpose of structured write-back is to find the constraint, not merely decorate a dashboard.
Thoughtly is the communication and workflow layer between a verified leasing event and the next measurable action. Automations accept the event, filter it, attach context, call or message the contact, branch on results, and return structured outcomes. Agent Builder controls the conversation, variables, actions, outcomes, transfer, and end states.
The PMS, CRM, scheduler, and application platform keep their own jobs. They remain authoritative for tour completion, current property data, application state, screening, leasing ownership, and lease execution. This division is deliberate: fluent conversation should not outrun the systems that know what is true.
Thoughtly's work with Nomad demonstrates the broader property-management fit: high inbound volume, HubSpot integration, fast response, follow-up texts, and measurement tied to properties activated and units leased. This guide does not claim that Nomad uses this exact post-tour workflow; the case study supports the platform and vertical context, not an invented deployment detail.
No, not when it is a narrowly governed continuation of a known inbound leasing inquiry and completed tour. The workflow should still verify channel permission, suppression, identity, timing, and applicable law before contact. Prior engagement is context, not a blank check.
Trigger only after the source of truth marks the tour completed and after any deliberate waiting rule the property team approves. Re-check that no application, later tour, opt-out, or human-owned task has appeared before calling. There is no universal delay that fits every portfolio.
This workflow should not. It can explain approved process steps, send the official application link, capture ordinary next-step intent, and connect the person to staff. The application system should collect sensitive data and own submission, screening, approval, denial, and notices.
Yes, when the property team provides an approved scheduling path with current availability. The agent should offer only returned slots, confirm the timezone and tour type, write the new appointment back, and use a human fallback when booking fails or an accommodation is requested.
Record the attempt and follow the property's approved retry and channel policy. An eligible SMS or email can continue the same conversation, but the workflow should stop when suppression, timing, or maximum-attempt rules say stop. Do not turn one completed tour into an endless cadenceCadenceA cadence is the planned sequence of calls, texts, emails, delays, and retries used to follow up with a lead until they answer, opt out, book, or become inactive..
Start with applications started and submitted from the eligible completed-tour cohort, then follow units leased. Contact rate, links sent, and handoffs are diagnostic metrics. They help explain the funnel but do not replace the revenue result.
A post-tour workflow earns its place when it preserves context and reduces ambiguity. The property system says the tour happened. Thoughtly asks what the prospect needs next, takes the approved action, and returns a structured result. Humans keep the housing decisions and exceptions that deserve judgment.
The practical standard is simple: every eligible completed tour gets a timely, accurate next step; every stop signal is respected; every application stays in the right system; and the operation can trace the journey from tour to rental application to unit leased.