From Tenant Email to Work Order in 60 Seconds: Handling Maintenance Requests in Street

The fastest reliable way to handle a tenant maintenance email is a five-step intake: identify the tenancy, triage the severity, log the job in Street with the tenant's photos and words, queue the landlord's authorisation, and acknowledge the tenant. With the right setup, that first pass is about a minute's work. Street's own Tenant App automates much of this journey already; the craft is applying the same discipline to the reports that still arrive by email.

Key takeaways

• Treat intake as its own job: a logged, triaged, acknowledged request within about a minute of reading the email — a working target, not a statutory rule.
• Street's Tenant App captures reports with photos and deflects some common faults with AI guidance; email reports need the same rigour.
• Damp and mould reports are a special class: Awaab's Law already sets fixed deadlines for social landlords and is due to extend to the private rented sector under the Renters' Rights Act.
• If it is not recorded against the tenancy with dates and times, it effectively did not happen — build the audit trail as you go.

What does the maintenance request journey look like?

Every maintenance issue moves through six stages: tenant report, triage, landlord authorisation, contractor instruction, completion, and record. A work order — the formal instruction to a contractor describing the property, the fault, access arrangements and any cost limit — is the hinge in the middle; Street's public pages refer to these as jobs.

Street's property management module covers the structured version of this well: Tenant App requests appear in the CRM straight away with photos, agents are notified by activity alert and email, landlords approve with one tap in their Landlord App, and compliance checks run before a contractor is assigned. Street also says its AI guides tenants through common faults first, resolving 1 in 5 jobs before they are created.

An emailed report covers the same six stages but starts as unstructured text in an inbox — which is where the discipline below comes in.

Where do the delays really happen?

Rarely with the plumber. The slow parts sit in the office, in four places. First, reading and interpreting: "the boiler's playing up again" must become a fault, a location and a severity before anyone can act. Second, re-keying: copying details and photos from the email into the CRM — the gap a proper Street-to-Outlook connection closes. Third, waiting: landlord authorisation and contractor availability both stall while requests sit unlogged. Fourth, chasing: every unanswered acknowledgement generates a follow-up email.

Delay compounds at intake — so the leverage is in the first minute, not the last mile.

How do you get from tenant email to work order in 60 seconds?

These timings are an illustrative target, assuming tenancy context is at hand rather than hunted for.

1. 0–10 seconds — identify the tenancy. Match the sender to the tenancy and property record in Street, and check for open jobs on the same fault.
2. 10–25 seconds — triage. Grade the report against your urgency bands (table below), flagging anything with a health dimension such as damp and mould.
3. 25–40 seconds — log the job. Create the job against the tenancy in Street, paste the tenant's own words, attach their photos, and note anything material such as access constraints or vulnerability.
4. 40–50 seconds — stage the authorisation. Trigger the landlord approval with the evidence attached — in Street, landlords can approve from their app rather than by phone tag.
5. 50–60 seconds — acknowledge the tenant. Send a short reply confirming what was logged, the urgency band, the next step and who will contact them about access.

Where an Outlook add-in is connected to Street, this collapses further: tools like Lanten read the incoming email, surface the matching tenancy beside it, and draft the acknowledgement plus a staged work order and note for the agent to approve — which is what makes the target realistic at volume.

How urgent is the repair? A triage table

Urgency bands come from tenancy agreements and management contracts rather than statute; the underlying legal duty is to repair within a reasonable time, with landlords' core responsibilities — structure, sanitary fittings, heating and hot water, gas and wiring — set out in government guidance on repairs in private renting. The targets below are common practice, not legal deadlines.

Damp and mould has its own row because the law has moved. Since 27 October 2025, Awaab's Law has required social landlords to investigate and deal with damp, mould and emergency hazards within fixed timeframes, and the government has confirmed it will extend to the private rented sector in a later phase of the Renters' Rights Act (whose first provisions took effect on 1 May 2026). No PRS date is confirmed yet, so treat every damp report as time-critical now.

What should your maintenance audit trail record?

Propertymark's guidance on preparing for Awaab's Law in the PRS frames it as a stopwatch problem: log "day zero" the moment a report lands, then run a timed, risk-led, documented workflow. Applied to any maintenance request, a defensible trail records:

• Receipt: date and time the report arrived and was first read, plus the tenant's original wording and photos.
• Triage: the band assigned, by whom, and why — particularly for anything graded routine.
• Authorisation: the landlord's decision, its date, and any cost limit.
• Instruction: the work order, the contractor and the compliance checks passed — Street runs these checks before assignment and tracks certificates such as gas safety and EICR against expiry.
• Completion: the invoice, any photos of finished work, and the tenant's confirmation.

Keep it all on the tenancy record in Street, not in personal mailboxes — and if you want intake data flowing in automatically, see our guide to the Street Open API.

FAQs

How do letting agents log maintenance requests?

Best practice is to log every report — app, email or phone — against the tenancy record with the date and time, the tenant's description, photos and a triage band. In Street, Tenant App reports create CRM entries automatically; email and phone reports need to be keyed in, or captured through an integration that stages them for approval.

What counts as an emergency repair?

Anything posing an immediate risk to health, safety or the property itself: gas escapes, uncontained water leaks, unsafe electrics, loss of heating or hot water in cold weather, or a property left insecure. Most tenancy agreements define the category explicitly, so check your terms and keep the definition consistent across triage, tenant guidance and your out-of-hours provider.

How quickly must letting agents respond to maintenance requests?

For most private-sector repairs there is currently no single statutory response time — the duty is to repair within a reasonable time, alongside whatever your contracts promise. The exception is Awaab's Law, which already imposes fixed deadlines on social landlords and is due to extend to private landlords; our Awaab's Law guide covers the timescales in detail.

Does Street CRM handle maintenance requests?

Yes. Street's property management module includes tenant reporting with photos, AI fault guidance before a job is created, one-tap landlord approvals, contractor compliance checks and real-time tracking. Confirm current scope with Street, as features evolve.

If you would like tenant emails to arrive with the Street tenancy beside them and a drafted reply and staged work order ready to approve, see Lanten.