Estate Agent Complaints Handling: AI-Drafted Replies and a Log

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Estate Agent Complaints Handling: AI-Drafted Replies and a Log.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Estate Agent Complaints Handling: AI-Drafted Replies and a Log.

An estate agency can use AI to draft the acknowledgement, the investigation chronology and the final reply, as long as a named person checks every fact, sends it and records each stage in a log. The log, not the AI, is what satisfies your redress scheme: dates received, acknowledged, investigated and answered.

The common failure is not a bad draft. It is a perfect-sounding reply that quietly admits fault, promises compensation or misstates what the file says, sent by someone who never opened the file. Everything below is built to stop that, using a three-stage routine and a log you can show a scheme adjudicator.

Follow me on Instagram@sagnikteaches

Why a complaint is a record first and a letter second

When an unhappy landlord or buyer escalates to the redress scheme, the adjudicator does not read your reply for elegance. They look at what you did and when: did you acknowledge it, did you look into it, did you give a reasoned answer, and did you tell the person where to go next. The letter is evidence of those steps, and the log is the index to the evidence.

Connect on LinkedInSagnik Bhattacharya

That is why the log sits at the centre of the routine below. Generic complaint-policy templates tell you to "respond promptly". They rarely give you the fields to record, the cut-off dates to watch or the wording boundaries that keep a reply honest without conceding liability on the principal's behalf. For the wider picture of getting a firm ready for AI in regulated work, see the AI readiness checklist for professional firms.

Subscribe on YouTube@sagnikteaches

The timings your redress scheme cares about

Two outer limits matter most. The consumer guidance from The Property Ombudsman (TPO) says a complainant can bring a complaint to it once the agency has sent its final viewpoint letter, or eight weeks after complaining if the agency has not resolved it. The complainant then has 12 months from receiving the final response to refer it. Those are the dates an adjudicator checks first.

The ombudsman's guidance for member businesses fills in the inside of that window. Acknowledge the complaint within three working days and say a written response will follow within 15 working days. If the complainant is still unhappy, offer a review by someone who had no part in the matter, finished within a further 15 working days. The whole in-house process should take no longer than eight weeks from the date you receive the complaint in writing, and it ends with a final viewpoint letter. A verbal complaint should be noted with its date and time and then put in writing, by the complainant or by you.

If you belong to the Property Redress Scheme or another scheme, read its own terms of reference: the stages are similar, but the numbers and wording are the scheme's, and its code is the authority, not this page. Whatever timescales apply, write them into your complaints procedure and use the log to prove you met them. A missed target is awkward; a missed target you never recorded is worse.

StageWhat happensWho does itTPO guide timingWhat the log records
1. AcknowledgeConfirm receipt, name the handler, say what happens next and whenAI drafts, office manager sendsWithin 3 working daysDate received, date acknowledged, handler
2. InvestigateGather the file, speak to the negotiator, build a dated chronologyHuman gathers, AI structuresInside the 15-day reply windowEvidence list, people spoken to, dates
3. ReplyA reasoned answer, an outcome, and how to ask for a reviewAI drafts, director approvesWithin 15 working daysOutcome, date sent, approver
4. Review, if still unhappyA colleague with no part in the matter re-checks and sends the final viewpoint letterSenior person not involved; AI drafts from their findingsA further 15 working days; all within 8 weeksReview date, reviewer, final letter date, referral wording included
The Complete Excel Course with AI Integration thumbnail

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Set up the log before you draft anything

A spreadsheet is enough for a small agency. One row per complaint, one tab for the live ones and one for closed. The fields are the whole point, so agree them first and add columns only when you can say who will fill them in.

  • Reference: a simple sequence such as C-2026-014.
  • Branch or department: sales, lettings or property management.
  • Date received and channel: email, phone, post, review site or in person.
  • Complainant and property: name and address, kept in this tab only.
  • Nature of complaint: one short category plus a one-line summary in the complainant's words.
  • Handler and reviewer: two different people wherever possible.
  • Acknowledged on: date and a link to the sent message.
  • Evidence reviewed: a list, with file locations.
  • Acknowledge-by and reply-by dates: three and 15 working days from receipt if you follow the ombudsman's guide, worked out by a working-day formula rather than by hand.
  • Eight-week date: calculated from the date the complaint arrived in writing, so the sheet flags it for you.
  • Review requested on, and reviewer: blank unless the complainant asks for a second look.
  • Outcome: upheld, partly upheld, not upheld or resolved informally.
  • Remedy offered: apology, correction, refund or goodwill payment, with who authorised it.
  • Final response sent on: date, plus whether the scheme referral information was included.
  • Lessons and changes made: what the firm will do differently.

Add a conditional-format rule on the eight-week date so that any open row within ten days turns amber. That one formula does more for compliance than any AI feature. If you are importing an old complaints list from several places, the tutorial on cleaning messy data shows how to tidy it first.

Stage one: an acknowledgement that promises only what you can do

Acknowledgements are where AI earns its keep, because they are quick, repetitive and need a calm tone. The risk is a draft that apologises for things you have not yet investigated. Give the tool the rules, the facts you know and a ban on opinions.

You are drafting an acknowledgement for a letting agency's complaints handler.
Rules:
- Thank the person for raising the matter. Do not say we are sorry for any specific event.
- Do not state or imply that we were at fault or that we will pay compensation.
- Confirm: the date we received the complaint, the name of the handler, and that we will send a full written reply by [date].
- Say that if they remain unhappy after our final reply, we will tell them how to take it to our redress scheme.
- Plain, warm, everyday English. Under 150 words. No jargon.
Facts: complaint received [date] by email from [first name] about [one-line summary]. Handler is [name], reviewer is [name].
Do not add any facts not listed above.

A realistic output is a short, courteous note: it thanks the complainant, names the handler, gives the reply date and says nothing about blame. If the draft says "we are sorry the property was not as described", delete the sentence. That is an admission about a fact nobody has checked. A neutral line such as "I am sorry to hear you are unhappy and I will look into this properly" is honest and concedes nothing.

Worked example: a lettings complaint about a deposit

Say a four-person lettings agency receives an email from a former tenant. The tenant says a cleaning charge of $180 was taken from the deposit, that the check-out photos do not support it and that nobody replied to two earlier messages. The office manager logs it as C-2026-021, received on a Monday, and the sheet works out the eight-week date. The acknowledgement goes out on Tuesday, well inside the three-working-day guide, drafted from the prompt above, checked by the office manager and sent from the shared complaints mailbox.

The log row now shows received Monday, acknowledged Tuesday, a handler and a different reviewer, and a promised reply date ten working days out. Nothing has been decided. That is the point: stage one proves you responded, not that you were right.

Stage two: investigate with the file, and use AI only to structure it

The investigation is a human task. Someone opens the tenancy file and reads the inventory, the check-in and check-out reports, the messages and the invoices. The AI helps once you have the facts in front of you: it can turn a heap of notes into a dated chronology and spot gaps.

Paste only what the chronology needs: dates, the nature of each event and who was involved. Remove phone numbers, bank details and anything the draft does not need. On a business plan where content is not used for training by default, that is reasonable practice; on a free consumer plan, do not paste complaint details at all.

Build a dated chronology from these notes. Output a table with columns: date, event, source document, who was involved.
After the table, list (1) any dates where two sources disagree, (2) any gaps longer than 7 days with no recorded contact, (3) any claim by the complainant that the notes do not confirm or contradict.
Use only the notes below. If something is not stated, write "not recorded". Do not guess or fill gaps.
Notes: [paste]

On the deposit complaint, the output might show: check-out on the 14th, report uploaded on the 16th, deductions proposed on the 20th, tenant's first message on the 21st, and no reply until the 29th. Under "gaps" it flags eight days of silence. Under "claims not confirmed" it lists the tenant's statement that the photos show clean skirting boards, because the notes never mention the photos. Those two flags tell the human where to look next.

What the AI gets wrong at this stage

Three failures show up in practice. It smooths over a disagreement between sources by choosing one, so keep the "dates where sources disagree" instruction. It invents a plausible date when a note is vague, so insist on "not recorded". And it can read a negotiator's casual note as a confirmed fact. Treat the chronology as a map, then open the underlying documents for every entry you will rely on in the reply.

Speak to the people involved and note what they said in the evidence column. A reply that says "I have spoken to the property manager and reviewed the check-out report and the inventory" is only honest if that happened.

Stage three: the reply, with an outcome and the next step

A good final reply has five parts: a summary of what the complainant said, what you looked at, what you found, what you will do about it, and where they can go if they disagree. AI drafts this well when you give it the findings and the decision, not when you ask it to decide.

Draft a final response letter for a letting agency complaint.
Structure: 1) what [first name] told us, in two sentences; 2) what we reviewed (list below); 3) our findings, one short paragraph per point; 4) the outcome and any action we will take; 5) if they remain unhappy, how to ask for a review by [senior colleague not involved], and that after the review we will send our final viewpoint letter explaining how to refer the matter to [redress scheme name].
Tone: courteous, plain, no legal language, no defensiveness. Short sentences.
Decision already made by the director: [e.g. partly upheld: the cleaning deduction is reduced because the check-out photos do not support the full amount].
Do not offer any remedy, compensation or admission beyond the decision stated.
Reviewed: [list]. Findings: [bullet points].

The final line of that prompt is the guardrail. Many drafts try to be generous on the firm's behalf with phrases such as "we will of course make this right". Strip them out. Remedies are decisions for the person with authority, and in many agencies that is the director or the landlord client, not the complaints handler.

A filled-in reply paragraph

Here is the findings paragraph an AI might return for the deposit case, labelled illustrative. "The check-out report dated the 16th records the oven and the bathroom as needing a deep clean, and the photographs attached to that report support this. It does not support the charge for the skirting boards, which appear clean in the images. We have therefore reduced the deduction to cover the oven and bathroom only and will return the difference within five working days." The handler checks every date and item against the report, and the director approves the refund before it goes out. If the director would rather phone first, the log notes that too.

The fixed closing paragraph for a final viewpoint letter

If the former tenant replies that a partial refund is not enough, the complaint moves to stage four. A senior colleague who had no part in the tenancy re-reads the file, the chronology and the first reply, and decides whether the outcome stands. AI can draft the letter from the reviewer's findings with the same reply prompt, but the closing paragraph should be fixed text that the handler pastes in, never generated, so it cannot drift:

This letter is our final viewpoint and completes our in-house complaints procedure. If you remain dissatisfied, you can refer your complaint to [redress scheme name], [postal address, email and website]. You can do this within 12 months of receiving this letter. [Any further wording your scheme's code requires.]

The ombudsman's business guidance says the final letter should tell the complainant the in-house procedure is complete, give the scheme's contact details and website, and state the 12-month referral window. Check your own scheme's code for anything extra. In the log, record the date the letter was sent and the reviewer's name. A typical slip at this stage is an AI draft that rewrites the closing paragraph into "you may wish to contact an ombudsman", which names no scheme and no time limit and so does not do the job.

Tone rules that keep replies honest

Put these in a short style sheet and paste it into every prompt, or save it in a ChatGPT or Claude Project, or a Gemini Gem, so you do not retype it. Google is replacing Gems with skills: personal accounts switch in November 2026, Workspace business accounts in March 2027.

  • Acknowledge the experience, not the fault: "I understand this has been frustrating" rather than "we got this wrong".
  • State facts with dates and sources: "the check-out report is dated the 16th" beats "as per our records".
  • No admissions of liability on behalf of the principal, landlord or vendor without their written agreement. Where the complaint involves a landlord client, tell them before you reply.
  • No blame on colleagues, contractors or the complainant. Describe what happened, not who failed.
  • Never promise compensation, a repeat visit or a changed process unless the decision-maker has approved it.
  • Offer a named person to contact, not a mailbox.

Before and after: a defensive line fixed

A first draft written under pressure: "As clearly stated in your tenancy agreement, the deposit deductions were entirely reasonable and your allegations are unfounded." Rewritten with the style sheet: "I have reviewed the tenancy agreement and the check-out report. The agreement allows deductions for cleaning where the property is returned in a worse condition than at check-in. The report supports part of the amount, and I explain which part below." The second version is firmer on facts and softer in tone.

Complaints that need extra care

Some complaints should not run through the standard route unchanged.

  • Complaints about the principal or a director. The person complained about must not draft, review or sign. Log the handover.
  • Allegations of discrimination, fraud or safety risks. Stop drafting, tell the principal and take professional advice before replying.
  • Vulnerable complainants. Keep the language simpler, offer a call and consider whether a letter alone is enough.
  • Claims already with a solicitor. Do not send an AI-drafted reply; pass it to your adviser.
  • Complaints about a third party's work, such as a contractor or a mortgage broker. Say what you can verify and who they should speak to about the rest.

A mistake and how it showed up

Imagine a sales branch asks AI to reply to a vendor who says a buyer's offer was not passed on. The draft says "we always pass on every offer immediately". The negotiator's notes show a three-day delay on one offer. The sentence is false, and the vendor's own evidence would have contradicted it. The fix is a rule in the prompt, "do not use 'always', 'never' or 'immediately' unless the notes say so", plus the human check against the file. Absolute words are the commonest source of an inaccurate reply.

A short handling checklist to pin beside the log

Print this for whoever handles each complaint.

  1. Log it the day it arrives, including verbal complaints and public reviews that name the firm.
  2. Send the acknowledgement within the time your procedure promises (three working days under the ombudsman's guide).
  3. Assign a handler and a different reviewer.
  4. Collect the file: agreements, inventories, reports, messages, invoices, call notes.
  5. Build the chronology; open the source for every fact you will rely on.
  6. Decide the outcome with someone who has authority to decide it.
  7. Draft the reply; check each date, amount and name against the file.
  8. If they stay unhappy, arrange a review by someone not involved, and send the final viewpoint letter within eight weeks of the written complaint.
  9. Include the fixed redress scheme paragraph your code requires.
  10. Send, record the date and store the sent copy with the file.
  11. Record lessons, then review the log monthly for patterns.

Using the log to find patterns, not only to defend the firm

Once a quarter, export the log and ask AI to group complaints by category and branch. Give it only the category, branch, outcome and lessons columns, with no names or addresses. A summary might show that six of nine complaints in the quarter were about silence after a viewing or a repair request, which points to the follow-up process, not the people. The buyer and vendor follow-up tutorial covers fixing that cause, and the tenant queries tutorial does the same for lettings.

Treat the output as a prompt for a conversation at the team meeting. The AI can count and cluster; it cannot know that two complaints were really one repeated problem with one landlord. You can.

Privacy and what the AI is allowed to see

Complaints contain personal data, and sometimes financial and health details. Decide, in writing, what may go into an AI tool. A workable rule for a small agency: only business-plan tools where the provider does not train on your content by default; no bank details, dates of birth or identity documents; "[first name]" instead of full names where the draft does not need them; and never the complainant's full inbox thread. If you are unsure whether a tool meets this, ask the vendor for their data-processing terms and keep their answer on file.

Tell staff the rule and test it. Ask a colleague to draft a mock complaint reply and see whether they paste in anything they should not have. Fixing that in a trial costs nothing.

How to check the routine worked

After a month or two, pull five closed complaints and test each against the log. Can you show the received date, acknowledgement date, reviewer, outcome, reply date and the scheme wording? Was every acknowledgement inside three working days and every first reply inside 15? Did anything reach the eight-week mark without a final response? Was any reply later contradicted by the file? If a row has a blank field, that is where the routine leaks, and the fix is usually a mandatory column, not another tool.

Also compare time spent. Note how long the acknowledgement, chronology and reply took before and after. Savings are typically in the typing and formatting; the decision time stays. If a reply still takes the same time, look at whether the handler is rewriting the AI's tone from scratch, which means the style sheet needs tightening.

If you would rather map this with someone, that is what my AI implementation consultation covers: finding the steps worth automating, adding AI to the tools you already use and handing over something your team can run.

Questions agents ask before putting complaints through AI

Can I paste a complainant's email into ChatGPT or Claude?

Only on a business plan where your content is not used for training by default, and only after removing details the draft does not need, such as phone numbers and bank details. Check your data-protection policy first. The safest habit is to paste the facts you have verified, not the whole inbox thread.

Should the log record the AI draft as well as the sent reply?

Keep the sent reply, because that is what the complainant received. Keep the draft only if your firm's retention policy says drafts are records. Always log who reviewed and approved the reply, and when, because that shows a person took responsibility for what was said.

What if the complaint is about the principal or a director?

Take it out of the normal routine. The person complained about should not draft, review or sign the reply. Pass it to another director or an outside adviser and log that you did, with the date, so the file shows the conflict was handled.

Does AI make the reply faster or just different?

Faster for the first draft and the chronology, which are the slow parts. The investigation, the decision and the sign-off still take human time. Expect to save the typing and tidying, not the thinking.

Further reads

Sources: The Property Ombudsman's consumer page on how its service works and its business guidance on handling complaints (both checked November 2026), and the Property Redress Scheme's own site; your own scheme's code of practice and terms of reference remain the authority.

Want your complaints routine mapped properly?

On a 1:1 call we can walk through how complaints reach your office today, where AI can draft safely, and what your log needs to record.

Book a 1:1 call with me