AI and automation
Documents read. Uncertain details reviewed. Decisions kept with your team.
Post-let compliance fails in the gaps: a certificate sitting in an engineer’s sent items, a renewal nobody diarised, a scan filed under the wrong flat. Letify360 automates the collecting, the reading, the matching and the chasing — and deliberately refuses to automate the deciding.
From an engineer’s phone to dated evidence
- Automatic
01A document arrives for review
Send a landlord or an engineer a secure link that expires and can be withdrawn. They drop in a folder of certificates without an account, from a phone if that is what they have. Files can also be imported. Email forwarding requires a configured connection.
- Automatic
02It is checked before it is trusted
Type and size are verified, the file is fingerprinted so the same document is never filed twice, and it is held privately in its original bytes. A scan state is carried openly rather than implied.
- Automatic, with a score
03It is read, and the reading is scored
Issue and expiry dates, certificate references, the engineer's registration and the address are pulled out and matched to a property. A confident read is prepared for filing; a poor one is held back with the reason shown.
- Always a human
04Doubt stops at a person
Nothing becomes proof until someone accepts it. That decision creates the certificate, supersedes the one before it, writes a dated evidence record and moves the property's status on its own.
- Automatic
05The next piece of work opens itself
A nightly sweep raises renewals before they expire, lapsed records, registration deadlines and documents nobody has judged — each into the right queue, with response and resolution times fixed at creation and escalation if they slip.
- Automatic, fully logged
06Delivery is recorded when configured
Delivery states and failures can be recorded. External messages require an active provider configuration; a draft is not a sent message.
Ask Letify360
An assistant that proposes; a person confirms.
It answers from your records
Ask what is expiring this month, which properties are not ready for possession, where the arrears sit, who is on a tenancy. The answer is built from your own data through the permissions of the person signed in.
It proposes; it does not act
Raising a work order, booking an engineer, opening a complaint, drafting a landlord email, creating a tenancy or an agreement — each arrives as a proposal with the exact values it would use.
A named person confirms
On confirmation the real routine runs, with the same checks and the same audit trail as if it had been typed by hand. The whole exchange is kept.
Law is not left to a language model
Notice periods, response times and thresholds are configurable records carrying their source and verification state. Deterministic rules decide; the assistant explains.
Every reader, and its limit
Nine places a model reads for you — and the line each one stops at.
| What it reads | What it pulls out | Where it stops |
|---|---|---|
| Certificates | Issue and expiry dates, certificate reference, engineer registration, the address | A low-confidence read is held for review, never filed |
| Tenancy agreements you already hold | Parties, rent, dates, deposit, terms — to fill the setup answers | Prescribed wording is templated, never generated |
| Identity documents | Name, address, date of birth, document expiry | A person records the right-to-rent check |
| Check-in and check-out photographs | What changed between the pair, with a confidence score | The recoverable figure is arithmetic from published lifespan guidance; you set the final amount |
| Supplier and contractor invoices | Amount, property, work order, what the contractor actually charged | Markup is separated and disclosed by rule, not by judgement |
| Inbound post, email and replies | Subject, urgency and who it belongs to | Routes to a queue; it never closes anything |
| Repair reports from tenants | A first-pass triage and likely trade | Severity can be raised, never lowered; hard stops escalate immediately |
| Your own portfolio, for the briefing and the assistant | The day's real records, cited back to you | Answers only from authorised data through the signed-in person's permissions |
| Rent and deposit advice | Comparables, condition, EPC and income evidence | Suggests with confidence; the deposit cap and the decision are yours |
What no model here is ever allowed to decide
- Lowering a hazard severity
- Deciding possession grounds
- Determining a licence requirement
- Setting a deposit deduction figure
- Passing a right-to-rent check
- Refusing a pet request
- Valuing market rent as fact
- Anything that moves client money
It reads, drafts, ranks, explains and cites. A named person decides, and the decision is stored separately from the suggestion with who, when and why.
Out of hours
Triage that knows when to stop asking questions.
A resident reporting a problem is taken through a short, deterministic set of questions held as editable rules — not generated on the spot. Where the report matches a dangerous condition, troubleshooting stops immediately and the emergency route is given, with an urgent task recorded for review. This does not imply a staffed out-of-hours desk.
- Gas smell
- Carbon monoxide alarm
- Sparking or smoking wiring
- Water near electrics
- Burning smell
Emergency wording and numbers are configurable per agency and are reviewed with you before any live use.
Connections
Tools can read. Only people can commit.
Imported records can support the assistant. CRM and notification connections require configuration and checks before use. Actions affecting real people require confirmation and an audit record.
Each connection states plainly whether it is in test, waiting for credentials, or genuinely configured. Nothing shows as connected because it would look better.