Bring Yardi records or your own customer history into OotlaAI. Yardi activation depends on the client’s licensed interfaces, permissions and configuration.
Use source-aware context for questions and follow-ups. Live SMS, phone and web assistance require approved setup. These scripted examples send nothing.
Illustrative selector only. No organization changes, imports or service connections.
ILLUSTRATIVE ONBOARDING PATH
Yardi-connected path
01
Confirm licensed interfaces
Confirm licensed interfaces and available fields. The client’s exact interfaces are not yet known.
02
Agree access and ownership
Agree permissions. Yardi owns configured property, lease, resident and accounting records.
03
Map, review, then activate
Keep properties and units separate. Test mappings; staff review before activation.
PROPERTY AND CUSTOMER RECORDS
Yardi context, with clear ownership.
Answer questions using authorized records. Agree licensed interfaces, fields, permissions and mappings before activation. Yardi remains authoritative for configured property, lease, resident and accounting records. Properties and units stay separate.
Working simulator available. Live setup awaits documentation, credentials and configuration.
View product exampleRecord mapping, before activationIllustrative
Yardi records Source of configured records
Not connected
Property reference
P-01 → Property identity
Unit reference
U-14 → Separate unit identity
Customer reference
C-08 → Relationship context
Configured lease, resident and accounting records remain authoritative in Yardi.
Invented mapping example. No synchronization or record changes.
GOOGLE CALENDAR
Keep viewings in sync.
Collect preferred times in OotlaAI and sync selected calendars after authorization. A requested time is not a booking; local booking success is separate from Google sync.
API adapter implemented. Live use requires OAuth setup and authorization.
Public example only. No Google event, invitation or booking is created.
ACQUISITION REPORTING
Understand how the inquiry arrived.
See where inquiries began. AI summarizes known attribution only. Google Analytics requires an authorized property, configuration and appropriate consent settings.
Illustrative only. No Analytics tags, visitor counts or conversion claims.
View product example
Acquisition context, not a live reportIllustrative
From discovery to inquiry
Invented acquisition examples
Illustrative acquisition sources and inquiry context
Source
Medium
Next step
Search
Organic
Lead inquiry
Direct visit
None
Viewing question
Partner site
Referral
Staff follow-up
Awaiting configuration
No visitor counts or conversion results are reported.
STANDALONE CUSTOMER HISTORY
Bring the history. Keep the relationship.
Import contacts, properties, separate units and leads from CSV without Yardi. Staff validate rows and review ambiguous contacts before merging. Never merge on name alone.
Staff imports are real. This preview uploads and imports nothing.
Check duplicates, field mapping, access rights and record ownership.
No file is collected and no import runs in this example.
APPLICANT PORTAL
Help people finish what they started.
Applicants save details and private documents through secure access. AI helps explain missing items. Screening requires an approved provider, consent and staff review; AI never decides.
Private portal implemented. This preview collects no documents, consent or applications.
Review the issue, assign the work and agree any visit separately.
Fictional request. Requested access is not a confirmed technician appointment.
EXISTING-PROVIDER PAYMENT HANDOFF
Point residents to their payment provider.
Guide residents to the configured approved provider and explain verified status. That provider handles payments. OotlaAI does not authorize, capture, charge or refund.
Illustrative only. No payment link, verified status or provider action.
