PROPERTY & FM · SYSTEM
IN SHORT
The shared inbox read and sorted continuously, routine status questions answered from the live job record, and everything else routed to the right manager with the history attached — always with a route to a person.
The problem
A managing agent's inbox mixes repair reports, complaints, consent requests, arrears queries, service charge disputes, solicitor enquiries and sales packs, and every one of them is urgent to the person who sent it. Most of the volume is people asking what is happening with something already logged — a question the system can answer perfectly, which a human is currently answering badly because they have three hundred others.
How it works
Every message is read and classified. Status questions about an existing job or case are answered from the live record with a real update — what was raised, who is attending, when. Repair reports go into triage. Complaints, consents, legal and arrears matters are routed to the responsible manager with the property record, tenancy or lease and correspondence history attached, so the manager starts with context rather than a search. Anything sensitive, or anything the classifier is unsure about, goes to a person unanswered.
Where the money is
Two things move. Response times fall sharply, because the routine majority stops queueing behind the complicated minority. And complaint volume falls, because most complaints in this sector are not about the repair, they are about the silence before the repair.
What stays with your people
Every complaint, every consent, every arrears conversation, anything involving a vulnerable resident, and anything with a legal or lease consequence. The automation buys your managers the time to do those properly.
What you get
- Every message read and classified within minutes of arrival
- Routine status questions answered from live job data, accurately
- Complaints, consents and legal matters routed to a named person
- Property, tenancy and correspondence history attached on arrival
- Complaint and vulnerability keywords escalated by hard rule
Questions we get asked
- Will it reply to residents on its own?
- Only on the categories you approve, and it says clearly that the update is automatic and how to reach a person. Everything else is prepared for a manager to send, which is still most of the saving.
- How does it handle a complaint?
- By escalating it, not answering it. Complaint indicators are configured as hard rules, and a complaint is routed to the responsible manager immediately with the full history attached and the clock started against your complaints procedure.
- Can it work with our existing portal?
- Yes. Where a portal exists we read from and write to it, so residents keep one place to look and the automation works behind it rather than beside it.
TRUST & CREDENTIALS
How we work, and what stands behind it
This page is maintained by Forth Systems. Everything listed below describes our own team, hosting choices and the technologies we build on — it is a statement of practice, not an independent certification or an endorsement by the vendors named.
UK team & data residency
Who builds it, and where your data sits while they do.
UK-based engineers
Edinburgh-headquartered. Every system is designed, built and supported by our own UK-based engineering team — no offshore delivery pool.
UK / EU hosting by default
Applications and databases are provisioned in UK or EU regions unless you require otherwise, with encryption in transit and at rest.
Human-in-the-loop by design
Every AI system we ship keeps a manual override. Nothing irreversible happens without an operator able to review, edit or stop it.
Audit trails as standard
Automated actions are written as first-class records — who or what did it, when, against which input — so operations stay evidence-ready.
Systems we build on
The platforms our systems run on. These are the technologies we deploy and support — not sponsorships or reseller badges.
OpenAI, Anthropic & Google models
Model-agnostic delivery. We route each workload to the model that fits it on cost, latency and accuracy, and can switch without a rebuild.
Supabase & Postgres
Row-level-security Postgres as the operational spine under every platform we run.
Stripe payments
Payment capture, checkout and reconciliation wired directly into job and permit workflows.
Xero, Sage & HubSpot integrations
Production integrations into the finance and CRM systems UK operators already run, so automation lands where the business keeps its records.
Streetworks & industry credentials
Operational domains we build in daily, with the sector systems we integrate against.
DfT Street Manager integration
The permit chain we built for Kerbco creates and tracks streetworks permit applications against DfT Street Manager and local highway authority processes.
NRSWA-aligned workflows
Permit, reinstatement and traffic-management workflows built to the New Roads and Street Works Act process contractors are inspected against.
Traffic management planning
Roadplan produces signing and guarding layouts for council submission and for the crew installing them on site.
Operator-built, not consultancy-built
Our platforms are built around real operating workflows — including the permit chain we built for our client Kerbco, a Scottish drop kerb contractor.
Insurance certificates, registration numbers and security documentation are available on request — ask the team.
