LatchFlowAI Operations for LettingsHere's how we connect to each system: what we use it for, what access we need, and which decisions stay inside your own software.
Every connection is set up against your actual account, permissions, and workflow.
Your property, tenancy, landlord, and branch records.
Anchor property, tenancy, landlord, branch, and activity context to the client-owned record.
Reapit remains authoritative. Scope depends on client permissions and approved API access.
Use Street records and events as context for cross-channel triage, handoffs, and operational proof.
Street remains the record owner; exact scopes depend on client API permissions.
Use Alto portfolio, contact, activity, and workflow context when it is the client-owned agency record.
Alto remains authoritative where it is the active CRM/PMS. Scope depends on available access, exports, and client permissions.
Specialist repair and tenancy-progression tools that keep doing their job.
Coordinate repair intake, job context, contractor handoff, communications, and issue evidence.
Fixflo remains the specialist repair record; connector behavior is agreed during discovery.
Use tenancy progression state to coordinate missing information, renewals, and operational exceptions.
Goodlord keeps progression authority; available data and actions depend on the client setup.
Inbox, messaging, calendar, and phone channels brought into one queue.
Ingest approved shared mailboxes and calendars, draft responses, and attach chronology to cases.
Mailbox access is least-privilege and limited to client-approved accounts and actions.
Capture tenant or contractor messages into the supervised queue with delivery and escalation state.
Consent, template, provider, and retention rules are confirmed before live messaging.
Handle approved call flows, capture transcripts, recover missed calls, and escalate emergencies.
Recording, disclosure, escalation, and fallback policy remain client-approved.
Payment, ledger, and invoice context, used with tight controls.
Surface approved ledger or invoice context for operational exception handling and reconciliation.
No autonomous accounting authority; write actions require explicit scope and approval.
Use approved rent and payment events to drive exception queues, tenant updates, and owner visibility.
PayProp remains the accounting authority; no payment movement is automated by default.
Best for your systems of record, where we can use approved API access.
The connection is built around your repair or progression setup.
Consent, identity matching, delivery, escalation, and fallback are agreed before launch.
Older or finance systems are reviewed before we promise a connection.
Bring your PMS, inbox, repair tool, phone system, finance platform, and the process currently held together by spreadsheets.
