Agents · Leasing
The Leasing Agent.
An AI agent that answers every inquiry the moment it lands, pre-screens the prospect, books the tour, follows up after and hands the qualified applicant to your team with every message threaded to one guest card.
Multi-channel
One conversation across SMS, email and voice.
A prospect who texts from her personal number, emails from her work address and leaves a voicemail on the way to a tour is one guest card, not three. The Leasing Agent uses phone number, email and conversational signal to link every channel and maintain a single thread.
One thread · Maria G. · prospect
hi! is the 2-bed at 14 Elm still available?
Yes — available May 1. Want to book a tour this week?
Confirmed — Thu Apr 24, 2:00pm. Address + parking instructions inside.
transcript“running late from work — can we push to 3pm? thanks!”
Same guest card. Same context. No re-introduction.
Pre-screening
The right questions, in the right order, with the wrong ones off the table.
Kasai runs a per-community pre-screening script : income ratio, desired move-in, bedroom count, pet policy, intended occupants and whatever custom criteria you define in a tenant-friendly flow. Protected-ground questions (race, religion, disability, family status, etc., per the Ontario Human Rights Code and equivalents in every province) are blocked at the prompt level. Tours only get booked when the prospect qualifies.
Pre-screen · Maria G.
14 Elm · 2-bedAsked & answered
- Move-in dateMay 1
- Bedrooms2-bed
- Income ratio3.2× rent
- Pets1 small dog
- Move-in depositconfirmed
Never asked
- Family statusblocked
- Religionblocked
- Disabilityblocked
- National originblocked
- Marital statusblocked
Per the Ontario Human Rights Code & equivalents — the agent will refuse to ask, even if the prospect volunteers the answer.
Qualified · tour gate unlocked
Calendar
Tours fit around agent availability, travel time and blackout windows.
Tour scheduling is where AI leasing tools usually break. Kasai’s calendar respects the constraints a human scheduler would.
- Per-agent availability — working hours, PTO, coverage assignments.
- Travel time between properties — honors a configurable buffer (default 30 minutes) so the next tour is actually reachable.
- Blackout windows — maintenance visits, community events, anything you mark off.
- After-hours bookings — still works, with your explicit after-hours policy.
This week · agent J. Park
Mon
21
Tue
22
Wed
23
Thu
24
Fri
25
Tour
Tour
lunch
maint.
Tour
Tour ×
Conflict at Tue · lunch
Per-community personas
The voice that matches the asset.
A luxury high-rise and a garden-style community in the same portfolio don’t need the same tone. Kasai runs one of three configurable personas per community.
- Professional — formal, measured, no exclamation marks.
- Cheerful — warm, uses the prospect’s name, restrained enthusiasm.
- Enthusiastic — high-energy, for leasing pushes and newer communities.
Persona
- Professional
- Cheerful
- Enthusiastic
SMS · Maria · prospect
Is the 2-bed still available?
Yes — the 2-bedroom at 14 Elm is available from May 1. Would you like to tour it this week?
Persona: Professional
Proactive follow-up
Silence is a signal.
Lead rot is a discipline problem. Kasai solves it with two automations: a Post-Tour Follow Up that auto-fires within your chosen window and a Proactive Lead Action that nudges qualified prospects who go silent — once, persona-matched, then routed to your team as a Needs Reply task. No spam.
Follow-up timeline · Maria G.
auto · persona-matchedTour completed
Thu 2:45pmAgent: “Liked the natural light, asked about parking.”
Post-Tour Follow Up — auto-fired
Thu 4:45pm · T+2hSMS: “Hope the 2-bed felt right. Want me to send the application link?”
Silence detected
Sat 9:00am · day 2No reply within your 48-hour timeout — Proactive Lead Action queued.
Persona-matched nudge sent
Sat 11:00am · day 2Cheerful tone: “Quick check-in — still thinking about 14 Elm? Happy to answer anything.”
Routed to your team
Mon 9:00am · day 4“Needs Reply” task created for the leasing lead with the full thread attached.
Application handoff
When a prospect is ready, the application arrives complete.
Kasai requests exactly what your policy requires : government ID, proof of income, bank statements, reference letter and credit-check authorization, then validates each file the moment it lands. Name matches the prospect. Dates are fresh. No missing pages, no expired stubs. Anything off triggers a polite, specific follow-up automatically; no human chases paperwork. The full guest card, every screening answer and every verified document arrive on your team’s desk together and your approval rules decide whether Kasai advances the application straight through or routes it to a human approver.
Application · Maria G. · 14 Elm · Unit 2B
complete · auto-bundledRequired documents
5 / 5 verifiedGovernment ID
name match · not expired
Pay stubs
3 most recent · within 60 days
Bank statements
90 days · balance consistent
Reference letter
employer-verified
Equifax authorization
e-signed · timestamped
Each file checked: name match, dates fresh, no missing pages. Anything off → polite, specific follow-up. No human chases paperwork.
Conversation context
Guest card history
47 messages · 3 channels
Pre-screening
5/5 passed · 0 breaches
Tour note
“Liked the natural light, asked about parking.”
Follow-up thread
Replied within 2 hours · persona-matched
Ready for approval · per your auto-advance rule
Auditability
Every message, every decision, in one log.
Every prompt, every reply, every screening question, every approval check — stored against the guest card with a timestamp and a link to the input that produced it. Auditors get a single view that reads like a narrative, with protected-ground guards and PIPEDA-compliant adverse-action notices first-class in the trail.
Guest card · Maria G. · audit log
Export PDFInquiry received
SMS · 7:48pm · matched to existing guest card
Pre-screen prompt
“What's your target move-in date?” · template v3.2
Protected-ground guard fired
blockedprospect mentioned family size — agent ignored, did not store
Pre-screen complete
pass5/5 criteria · 0 breaches · qualified
Tour booked
Thu Apr 24 · 2pm · agent J. Park · calendar conflict-checked
Approval rule fired
auto-advance application if screening clean · matched
PIPEDA notice generated
not triggered — screening passed (notice template v1.4 ready)