How to Handle Complaints and Disputes in Your CRM
Every estate agency gets complaints. A tenant unhappy with maintenance response time. A landlord disputing a fee. An applicant who feels brushed off. These situations are uncomfortable, but they're unavoidable when you're managing relationships between people with competing interests — and UK agents are legally required to belong to a government-approved redress scheme so that unresolved complaints can be escalated. The Propertymark code of practice sets the standards for how to handle them professionally.
What separates a thriving agency from one that's always in damage-control mode isn't the absence of complaints. It's how you handle them. A complaint acknowledged quickly, investigated thoroughly, and resolved fairly can actually strengthen a client relationship. A complaint ignored or handled inconsistently? That's how you destroy trust.
The difference comes down to one thing: a system. Without it, complaints get lost in email, timelines slip, and nobody remembers what was said to whom. With a CRM, every complaint is logged, tracked, and resolved in a structured, auditable way. That's not just better for your clients — it's your legal protection.
Why Complaints Need a System
In many agencies, complaints are handled the way they've always been: informally. The agent who receives the complaint tries to sort it personally. If they succeed, it's closed. If not, it escalates via verbal handoff and good intentions.
This approach has three built-in failure points. First, there's no record. If the situation resurfaces later or the client contacts a different team member, nobody knows what happened. Second, there's no timeline, so you can't prove you responded quickly (or admit you didn't). Third, there's no pattern analysis. If three tenants have complained about maintenance response times in the last month, you'll never spot the systemic issue because the complaints live in separate people's heads.
This is where 'complaint management' starts to sound like jargon — and it is. What it actually means: a shared complaint record that everyone on your team can see and update. It's less "enterprise-grade system" and more "notes everyone can trust."
The Property Ombudsman's Code of Practice requires a written complaints procedure with defined response times: acknowledgement within three working days, final response within eight weeks. A CRM enforces these timelines automatically. Without one, you're relying on memory and sticky notes.
Set Up a Complaint Workflow
Start simple. Every complaint needs to answer four questions: Who is complaining? What are they complaining about? When did they complain? How urgent is it?
Who is complaining — tenant, landlord, applicant — should link to their contact record in your CRM. This gives you context immediately. You'll see their tenancy history, previous interactions, any other properties they're involved with.
What the complaint is about — capture it in their own words if possible. "Slow maintenance response" is vague. "Reported a burst pipe on Tuesday, heard nothing until Friday, had to chase them" is usable.
When it was received — date, time, channel (phone, email, in person). This matters for your eight-week clock and for spotting patterns later.
Which property it relates to — link it to the relevant record. Complaints about maintenance often cluster around specific properties. Complaints about fees might cluster around specific agents or property types.
Once logged, the complaint moves through four defined stages:
Acknowledgement — within 24 hours, write back. Don't offer a solution yet; just confirm you've received it, assign it a reference number, name the person handling it, and give an expected timeline. This one email cuts complaint frustration in half. People don't mind waiting if they know you've got them.
Investigation — gather evidence. Maintenance logs, communication records, tenancy documents, colleague accounts. A good CRM surfaces all of this without you having to hunt through email folders. If a tenant complained about slow maintenance response, your CRM should show you when the request came in, when it was assigned, when work started, and when it was signed off.
Response — explain what you found. If the complaint is valid, own it and say what you're changing. If it's not, explain why respectfully and provide evidence. Document the response against the complaint record. This creates your audit trail.
Resolution and follow-up — if you promised action (refund, service credit, process change), deliver it. Then follow up a few days later: "Are you satisfied?" This costs almost nothing and shows you care about the outcome, not just closing the ticket.
Escalation and Decision-Making
Some complaints can't be resolved by the person who received them. They need management involvement. Others might involve external bodies — ombudsmen, regulators, legal advisors.
Set up an escalation trigger in your CRM. If a complaint isn't resolved in five working days, it escalates to a manager. If it stays open for ten, it goes to a director. Each escalation is visible in the record, so the person taking over can see the full history without asking questions.
This sounds bureaucratic, but it's actually freeing. The person handling the complaint knows exactly when and to whom they can hand it off. There's no ambiguity, no guilt about "bothering" management — it's the rule.
When you manage landlord relationships or handle maintenance requests, the same logic applies. Clear decision points prevent complaints from languishing and escalate tension while it can still be resolved.
Turn Complaints into Improvement
Here's where most agencies miss the real value. They handle complaints as one-off problems. They should be treated as signals about what's broken in your operation.
If you got four complaints about maintenance response times in March, that's not four isolated incidents. That's a process problem. Maybe you don't have enough maintenance contractors. Maybe the handoff between tenant and contractor is slow. Maybe the CRM isn't routing requests properly. Without analysis, you'll get four more in April.
Most CRMs have basic reporting. Use it. Run a monthly or quarterly report: complaints by category, by property, by team member, by time period. Look for clusters. Bring the team together and ask: "Why are we seeing this pattern? What can we fix?"
A complaint-analysis habit — even just thirty minutes a month — transforms your agency. You stop playing defense (reacting to unhappy clients) and start playing offense (fixing the systems that make clients unhappy in the first place).
When you manage rent collection or track landlord compliance, the same principle works. A pattern of late payments or missing documents isn't a series of individual failures. It's a system gap.
Documentation That Protects You
Here's the practical thing: a complaint that escalates to an ombudsman referral or legal action will be investigated. The investigator's first request is always the same: "Show me the evidence of how you handled this."
Without a system, you'll have scattered emails, incomplete notes, and vague recollections. With a system, you have a complete timeline: complaint logged at 09:47 on [date], acknowledged at 14:23, investigation completed by [date], response sent [date], resolution confirmed [date]. This is not just better — it's often the difference between a decision in your favour and one against you.
The ICO's accountability guidance expects similar audit trails for personal data handling, and complaints often involve personal data. A CRM that records every step is how you prove compliance.
Team training matters here too. Complaints handling is a skill, not an instinct. Role-play scenarios in team meetings. Walk through a tricky complaint: "A tenant says the letting agent misrepresented the property's condition. How do we investigate? What do we say in the response?" The team learns consistency, and less-experienced staff see the standard applied.
When you're onboarding new staff, make complaint handling one of the core workflows you teach. Show them the CRM system, walk them through a sample complaint from receipt to resolution, and explain why the documentation matters.
Frequently Asked Questions
How quickly should I acknowledge a complaint? Aim for within 24 hours, even if you don't have a solution. The Property Ombudsman requires written acknowledgement within three working days, but faster is better for client relations. An immediate response (same day if possible) stops the complainant feeling ignored.
What if the complaint is clearly wrong or unreasonable? Investigate it fairly anyway. Document that you did, and explain your findings respectfully. Even if the complainant was mistaken, the fact that you took them seriously (and can prove you did) matters. Dismissing a complaint out of hand is how you end up in front of an ombudsman.
How long should I spend resolving a complaint? The Property Ombudsman allows eight weeks for a final response. Aim for much faster if possible — two weeks for straightforward complaints, longer for complex ones. The longer a complaint stays open, the more it eats at both your time and the complainant's patience.
Should I refund or offer credit for every valid complaint? Not necessarily. The remedy depends on the harm. A maintenance delay that caused inconvenience might warrant an apology and a small service credit. A miscommunication that cost a client money warrants a refund. Be fair and generous where you've made a mistake; the goodwill often outlasts the cost.
What if the complaint goes to the ombudsman? Continue to follow your process. Gather evidence, document your response, and stay professional. When the ombudsman contacts you, provide the complete audit trail your CRM holds. Ombudsmen respect agencies that handle complaints systematically and transparently.
Do I need a separate complaints management system? No. Your CRM should handle it. A dedicated complaints tool adds complexity and cost. If your CRM can't track complaints, respond to them, escalate them, and report on them, it's not a complete solution for an agency.
How often should I review complaint trends? Monthly is ideal, quarterly at minimum. Look for patterns by category, property, time period, and team member. Discuss findings in team meetings. One complaint is a problem; three similar ones in a month is a signal that your process needs work.
What if a complaint reveals a bigger problem? Good — that's how you improve. If a complaint about maintenance response times reveals that your contractor list is too small, fix it. If complaints about fee disputes reveal that your fee communication is unclear, rewrite it. Individual complaints are data points. Patterns are where improvement lives.
Complaints are not a sign that your agency is broken. They're a sign that your clients care enough to tell you when something is wrong. The agencies that thrive are the ones that handle complaints seriously — logging them, investigating them fairly, responding transparently, and using them to improve.
A CRM like Relentify gives you the workflow infrastructure to do this: structured complaint records, automated escalation, complete audit trails, and reporting that reveals patterns. This integration means that when a complaint arrives, the context is immediately available, and resolution begins without delay.
When you combine a clear process with the right system, complaints stop being things you dread and start being opportunities to demonstrate professionalism and build trust. That's the difference between an agency that survives complaints and one that turns them into competitive advantage.