How Residents Report Repairs via WhatsApp, SMS and Email using One Platform

Because a resident shouldn't have to tell the same story four times.

Searches for WhatsApp housing association repairs keep climbing. Your residents already live in the app. When a tap starts leaking on a Sunday, they do not want a phone queue that opens on Monday.

Now with WhatsApp, any repair issue reported at 9pm can be triaged and assigned before your contact centre opens. 

Setting it up is more involved than downloading an app. This guide covers what WhatsApp repair reporting actually requires: the Meta approval steps, the messaging rules that catch housing teams out, and the UK data protection position. It also covers the part most rollouts skip, which is what SMS, email and web each do that WhatsApp cannot, and why all four need to land in the same place.

Why are residents asking to report repairs on WhatsApp?

The Regulator of Social Housing's Tenant Satisfaction Measures show that satisfaction with landlords listening to views and acting on them remains one of the lowest-scoring perception measures across the sector, with wide variation between landlords. Residents are not rating the repair. They are rating whether anyone heard them.

WhatsApp closes that gap in a way a phone line cannot. It is asynchronous, so a resident reports at 9pm and reads the reply at 7am. It captures photos and video, which turns a vague description into a diagnosable fault. It shows delivery and read receipts, so residents can see the message landed and if you use it via askporter then it can work in the resident's native language.

What do you need to set up WhatsApp for housing repairs?

For a housing provider, WhatsApp Business app is not the route to take. It has no audit trail, no multi-user access, no integration with your housing management system, and no data processing agreement covering your residents' data. 

What you need is the WhatsApp Business Platform, accessed either directly through Meta's Cloud API or through a Business Solution Provider. Six steps:

1. Verify your organisation in Meta Business Manager. Business verification requires documentation proving your legal entity. Start here, because everything downstream depends on it.
2. Choose a dedicated phone number. It cannot already be registered to a personal WhatsApp or WhatsApp Business app account. Most providers use a new number and publicise it alongside the existing repairs line.
3. Connect through the Cloud API or a Business Solution Provider. A provider handles the technical connection, hosting location, and the data processing agreement. If your residents are in the UK, ask where message data is processed and stored before you sign.
4. Build and submit your message templates. Meta reviews every message you send outside an active conversation. Repair templates such as appointment confirmed, operative on the way and job completed fall under the utility category. Approval is usually quick for verified businesses, but rejections happen and cost you days.
5. Set up opt-in capture and opt-out handling. Every message you send should carry a clear route to stop. Keep a record of when and how each resident opted in.
6. Decide who answers, and how quickly. This is the step most teams underestimate. See the next section.

How does the 24-hour window with WhatsApp Business Platform change repair communications?

When a resident messages you via Whatsapp, a 24-hour customer service window opens. You can reply freely with text, photos, questions, anything. Every new message from the resident resets the clock. Outside it, you can only send a pre-approved template.

So a resident reports damp on Friday evening. Nobody picks it up. By Sunday the window has closed, and your team can no longer ask "can you send a photo of the affected wall?", because that is a free-form message and the window is shut. You are limited to whatever templates you approved in advance.

There is also a date to plan around, and it arrives in weeks rather than months. From 1 October 2026, two things that have been free stop being free. Free-form replies sent inside the 24-hour service window become billable per message. So do utility templates sent inside that window, which is the category your repair updates fall into.

Three details shape what that costs you. Messages residents send to you stay free. The first 1,000 service messages from each business phone number each month stay free. And service messages carry no volume discount, unlike utility and authentication templates, so ten thousand replies cost exactly ten times one thousand. A large landlord gets no scale break on conversation.

The practical effect is that consolidating three short replies into one complete message is now a cost decision as well as a service one. Confirm current rates with your provider before you model anything.

The practical conclusion: WhatsApp repair reporting only works if something answers immediately, at any hour. A channel that opens at 8am and closes at 5pm inherits the same failure as the phone line, with a worse resident expectation attached to it.

What does UK data protection require?

Two regimes apply, and they are often confused.

UK GDPR governs the processing itself. You need a lawful basis, a defined retention period, a record of processing, and a way to honour access and erasure requests covering WhatsApp conversations. Your privacy notice should name WhatsApp as a channel and explain how resident data is handled on it.

PECR governs electronic marketing across every electronic channel, and the ICO has been clear that messaging apps sit within scope alongside SMS and email. This is where the useful distinction lives: a message about a live repair, whether that is an appointment confirmation, an operative en route or a job completed, is service communication under your tenancy relationship, not marketing. A TSM survey invitation or a service campaign is a different matter and needs prior consent, whichever channel carries it.

Getting that line right lets you use the channel properly for repairs without over-restricting yourself, and without accidentally running a marketing programme you have no consent for.

Why WhatsApp alone creates a new problem

Here is the trap. You launch WhatsApp, residents adopt it, and you now run a fifth inbox alongside phone, email, the portal and the out-of-hours service. Nothing is connected. A resident reports a leak on WhatsApp on Monday and chases it by phone on Wednesday, and the advisor who takes that call has no idea the first report exists.

Not every resident wants WhatsApp either, and not every resident can use it. A repairs service that only works well on one channel is a repairs service that works well for some of your residents.

What is each channel actually good for?

Channel choice is usually circumstance, not preference. The same resident will use different channels at different moments, depending on what they are trying to do and what they have to hand.

WhatsApp carries the diagnosis. It handles photos and video, which turns "there's a damp patch" into something an advisor can actually assess. It holds a two-way conversation, so follow-up questions get answered in context. It shows read receipts, so the resident knows the report landed. It works in the resident's own language. This is the strongest channel for a first report of anything complicated. Its limits are the 24-hour window, the need for a smartphone and a data connection, and the fact that the number a resident messages from may not be the number on their tenancy record.

SMS carries the reach. It works on every handset, with no app, no data allowance and no login. It reaches the resident with a basic phone, the resident who has run out of data, and the resident who will never install anything. There is no template approval process and no messaging window. That makes it the most reliable channel for outbound messages that simply have to arrive: appointment confirmations, operative running late, access reminders the day before a visit. What it cannot do is carry a photo or hold a threaded conversation.

Email carries the record. Under Awaab's Law you owe the resident a written summary of your findings within 3 working days of an investigation concluding. That is a document, not a chat message, and email is where documents belong. The same applies to complaint correspondence, survey reports, and anything the resident may need to keep, forward or produce later. Email is poor for urgency and unreliable for open rates, but it is the only one of these channels that produces something the resident holds a copy of.

Web carries the identity. When a resident is signed in to your portal, you already know who they are and which property they are reporting on, before the first word of the report. No verification step, no mismatched phone numbers. It also handles structured intake well: guided questions, photo upload, appointment slots, rent and account alongside repairs. And it is where the resident who searched "report a repair" and clicked your website arrives. The weakness is the forgotten login, which is why it should never be the only route in.

One repair often crosses all four. The resident reports a leak on WhatsApp at 11pm. They get an SMS confirming the appointment, because they are out of data by the weekend. The written summary of the damp investigation goes by email. They rebook the missed slot on the portal. That is four channels and one repair. If there are also four systems, it is four records, and the resident tells the story four times.

A note on emergencies: no digital channel should be the only route for a genuine emergency. Keep the phone line, publicise it, and make sure your digital channels recognise an emergency and route it there.

The question, then, is not which channel to add. It is whether every channel, WhatsApp, SMS, email and web, lands in the same place, creates the same record, and follows the same process. That is what omnichannel resident communications means in housing, and it is the part that most WhatsApp rollouts skip.

How AI-powered triage handles repair reports across channels

That gap between channels is exactly what askporter closes. Rather than adding a fifth inbox, askporter Housing sits underneath WhatsApp, SMS, email and web, so a report on any one of them becomes the same record, triaged the same way, from the moment it lands.

A resident describes the problem in their own words, in their own language. AI-powered triage asks the diagnostic follow-up questions a skilled advisor would ask, requests a photo where one helps, identifies the fault, and allocates it to the right contractor — at 9pm on a Sunday, without waiting for the office to open. At Legal & General, that process achieves 97% successful automatic diagnostic and supplier allocation, across 486,589 assets under management, on every channel a resident chooses to use.

That's also what stops the resident-tells-the-story-four-times problem from earlier. The resident who reports on WhatsApp, confirms by SMS and follows up by phone is one conversation and one record, not four.

The record matters beyond convenience, too. Under Awaab's Law, social landlords in England must investigate and make safe an emergency hazard within 24 hours. For significant damp and mould hazards they must investigate within 10 working days of being notified, give the resident a written summary of the findings within 3 working days of the investigation concluding, and complete safety works within 5 working days of that same point. Phase 2 is expected to extend the same framework to further hazard categories.

Every one of those clocks starts when you are notified, and a notification counts whether it arrives by phone, email, portal or WhatsApp. A conversation sitting in a phone in someone's pocket does not start a clock anyone can evidence. A logged, timestamped, auditable conversation does.

askporter Housing is vendor-agnostic and works alongside your existing housing management system. It handles the resident-facing intake, triage and diagnosis, then passes the completed job into the system you already run. Your system of record does not change, and neither does your asset or tenancy data.

See how askporter Housing handles repair reporting across WhatsApp, SMS, email and web. [Book a demo →]

‍