How it fits your setup
No rip-and-replace. The engine sits alongside whatever runs your desk today — your inbox, your phone, your spreadsheet, your property-management software — and everything it touches lands in the same dated evidence log.
Capability map — connections are wired to your actual setup during the production build. This demo runs on synthetic data throughout.
Your inbox stays your inbox
One forwarding address covers portal leads, referencing results and landlord email.
Portal leads from Rightmove, Zoopla and OnTheMarket already arrive as email — so does everything else in lettings. You get one ingest address:
copelands@in.tenancyengine.co.uk(illustrative)
- Day one: forward anything to it by hand — a lead, a reference reply, a landlord thread. It parses, files against the right application, and logs.
- Ten minutes later: a Gmail or Outlook rule auto-forwards portal and provider email. No IT project, no new inbox to check.
- Anything unrecognised waits in a “needs filing” queue for a human — one click to file. Nothing is guessed at, nothing silently dropped.
Sending your own emails? BCC copelands+file@in.tenancyengine.co.uk and the correspondence is on the record — your inbox, our filing.
Watch the parsing work — live
Paste any enquiry email; the real extractor pulls the fields.
This is the same deterministic parser the pipeline uses — plain code, no guesswork with numbers. Paste a lead from your own inbox and watch it extract.
Phone calls become written evidence
Log the call in one line; the engine drafts the confirmation email.
Half of lettings happens on the phone. Every application has a “log offline activity” panel — phone call, paper document, reference taken by phone, branch conversation — each entry timestamped and recorded under the staff member's name.
Then the move that makes a call hold up later: one click drafts a confirmation email — “following our call today, we agreed…” — held for your approval like every other email. The call now exists as a written, dated record, not a memory.
Live in this demo — open any application and try it.
Spreadsheets and your PM software
CSV in at onboarding, CSV out any time. Reapit, Alto, Street, Jupix stay put.
- Onboarding: your lettings book comes in from CSV or spreadsheet — column mapping, a dry-run preview, and a human confirm before anything is created. Every imported row is audited with its source.
- Every day after: your PM software's notification emails flow down the same inbox pipe and land on the right file. Deeper syncs are scoped per agency once we've seen what your package can do.
- No lock-in: one click exports everything — applications, correspondence log, call log, evidence packs. Your data leaves as easily as it arrives.
Paper still happens
Photograph it, attach it, hash it — paper joins the evidence trail.
Payslips handed in at the branch, a signed page, a landlord's note. Photograph or scan it against the application; the file is stored with a cryptographic fingerprint recorded in the evidence log at upload time — so you can show a tribunal the document is byte-identical to the one captured on the day. Anything typed up from paper is logged as a transcription, with the original referenced.
The common thread: every channel — email, phone, spreadsheet, paper — writes to the same chronological evidence log you've seen on every application. Integration here doesn't mean another dashboard; it means the record builds itself from the work you already do.