Fixed quote after a free call

Tenant maintenance request automation for letting agents and property managers

Repair requests arrive by phone, text, email and portal, often without photos or access details. We build a workflow that collects every tenant maintenance request in one tracker with photos, flags emergencies to a person straight away, briefs your approved contractor, asks the landlord to approve spend above an agreed limit and keeps the tenant updated until the job is closed. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why tenant repairs swamp letting teams

Maintenance is where tenants judge a letting agent or property manager, and where most staff time disappears. A dripping tap, a boiler failure in winter and a smell of gas all arrive in the same inbox, and the urgent ones must never wait behind the routine ones.

Each job needs the same facts: what is wrong, photos, access, who pays and whether the landlord has approved the cost. Chasing those by phone means jobs stall, tenants chase, landlords ask why, and nobody has a clean record when there is a dispute.

In England, Awaab's Law now sets deadlines for social landlords: emergency hazards must be investigated and made safe within 24 hours, so response records matter more than ever.

What we build

What our tenant maintenance request automation includes

One maintenance request form

A mobile-friendly tenant maintenance request form with photos, access times and pets, linked from texts, emails and your website.

Emergency first

Words such as gas, smell of burning, no heat, flooding or electrics trigger the agency's emergency instructions and a staff alert, not a queue.

Contractor briefing

Job details, photos and access sent to the approved contractor, with a link to accept and propose a time.

Landlord approval

Quotes above the agreed limit go to the landlord for one-tap approval before work starts.

Tenant updates

Status texts when a contractor is booked, on the way and done, with a short satisfaction check.

Tracker and audit trail

Every request, message, photo, approval and invoice in one maintenance request tracker, synced to your property management system where possible.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Request logged

    The tenant reports a repair with photos and access details.

  2. 02 Automated

    Urgency sorted

    Emergency words go straight to a person with the agency's safety instructions.

  3. 03 Automated

    Contractor briefed

    Routine jobs go to the approved contractor with everything they need.

  4. 04 Negotiator or PM review

    PM approves

    The property manager checks the job, cost and landlord approval.

  5. 05 Agent or broker decides

    Safety and spend decisions

    Whether a property is safe and who pays are decided by the property manager and landlord.

How it behaves

How repair triage behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the tenant sees

  • One simple form with photo upload
  • Emergency instructions straight away when needed
  • Texts when a contractor is booked and when the job is done

What the property manager sees

  • Emergencies flagged at once
  • A tracker of every open job and its status
  • Landlord approvals and contractor replies in one place

What the automation does

  • Logs every request with time and photos
  • Briefs contractors and asks landlords for approval
  • Keeps tenants updated and records everything

Edge cases and fallbacks

Tenant reports by phone
Staff log it in the same form so it joins the tracker.
Contractor does not accept within the agreed time
The next approved contractor is offered and the PM is told.
Landlord does not reply
Reminders follow, then the PM decides, within your management agreement.
Emergency reported out of hours
The on-call number and instructions are sent, and the on-call person is alerted.
Workflow or SMS outage
The form still records requests and the on-call alert falls back to email.

Architecture

Tenant maintenance request triage at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Tenant Form, text, email n8n workflow Log and sort Urgency check Emergency words Property manager Emergencies, spend Contractor Accept and book Landlord Approves cost PM system Job and audit log
  • Input
  • Logic and services
  • AI step
  • People
  • Output
  • Data

How it flows

  1. 1 The tenant reports a repair with photos through one form, text or email.
  2. 2 The workflow logs it and checks for emergency words; emergencies go to a person at once.
  3. 3 Routine jobs are sent to the approved contractor, and costs above the limit go to the landlord.
  4. 4 The job, messages, approvals and invoice are recorded in the property management system.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Tenant maintenance requests & repair triage project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    How repairs are reported today, emergency process, contractor list, spend limits and PM system.

  2. 02

    Design

    2 to 3 days

    Request form, emergency words and wording, contractor flow, approval rules and tenant updates.

  3. 03

    Build

    1 to 2 weeks

    Form, n8n workflow, urgency check, contractor and landlord links, tracker sync.

  4. 04

    Shadow run

    About 1 week

    Requests are logged and sorted while staff still dispatch by hand and compare.

  5. 05

    Launch

    1 to 2 days

    Send the new form to tenants and walk staff and contractors through it.

  6. 06

    Support

    Ongoing

    Contractor changes, new categories and monitoring.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Buildium Open API or your PM system's integration route Fixflo where already in use Twilio SMS A form tool with photo upload Claude or OpenAI for urgency sorting

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Emergency process, contractor flow and approval rules.

    $200 – $400

  • Build

    Form, urgency check, contractor and landlord links, tenant updates.

    $500 – $1,300

  • Integrations

    PM system, repairs platform and messaging.

    $150 – $400

  • Testing and shadow run

    QA and a side-by-side run with manual dispatch.

    $100 – $250

  • Launch and training

    Tenant roll-out and contractor walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. If you already use a repairs platform such as Fixflo, we connect around it rather than replace it. Messaging and n8n are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • Form tool and AI usage: The form provider's plan and pay-per-use model fees for urgency sorting.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

England: Awaab's Law for social landlords

Since 27 October 2025 social landlords in England must investigate and make emergency hazards safe within 24 hours of becoming aware of them. Request timestamps and actions are logged for that reason.

Source: www.gov.uk

UK: gas emergencies go to people

Suspected gas leaks follow the agency's safety instructions and the national emergency number; the workflow never decides whether an appliance is safe.

Source: www.hse.gov.uk

EU and UK: tenant photos are personal data

Photos inside a home can show people and belongings, so storage is limited to the job record and contracted processors.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Tenant maintenance request questions questions, answered.

Address and unit, what is wrong, where, photos or a short video, access times, pets and whether anyone vulnerable lives there. Our form asks only that, so tenants finish it on a phone in a minute.

Emergency words trigger your emergency instructions and an immediate alert to the on-call person. The workflow never tells a tenant a situation is safe.

Landlords get a one-tap approval for quotes above the limit you agree with them. Below the limit, the property manager approves. Nothing above the limit is booked without a yes.

No. If you use Fixflo, Buildium, AppFolio or similar, we connect around it and automate the gaps, such as contractor chasing or landlord approvals.

Yes. They get a secure link per job to accept, propose a time, upload photos and mark it complete.

Time to first response, time to make safe for emergencies, time to complete routine jobs, landlord approval time and tenant satisfaction checks.

Free 20-minute call

Want this for your estate & letting agent?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call