An applicant has found a property they want. Referencing is underway. The file is waiting on one missing item, the landlord wants to know what is happening, and you need to send a chase that sounds helpful rather than sharp.
That is a familiar lettings admin moment. The task looks simple, but the wording matters. A referencing chaser should be factual, calm and clear. It should not sound impatient, make promises, imply an outcome or include unnecessary personal information.
This is where AI can help, if it is used carefully. For a residential lettings administrator, the useful role of AI is not to decide anything about the application. It is to turn confirmed admin notes into a better first draft that you can review before sending.
This guide shows a beginner-friendly workflow for using AI prompts for letting agency admin, specifically polite referencing chaser messages. It is practical drafting guidance, not legal, compliance or referencing advice. Your agency policy, manager guidance and the actual referencing record should always lead the final message.
Quick answer: Lettings administrators can use AI to draft polite referencing chasers by giving it only confirmed, minimal notes, asking for calm wording with clear boundaries, checking that it has not added facts or pressure, and sending only a human-approved version through the agency’s normal process.
- Use placeholders where possible before drafting.
- Tell AI not to add deadlines, promises, legal wording or referencing decisions.
- Review the draft against the CRM record and agency policy.
- Escalate sensitive, unusual or unclear cases to a manager or appropriate internal reviewer.
If you want the shortcut version of this workflow, the Starter Toolkit for Residential Lettings Administrators packages practical prompt structures for routine letting agency admin tasks, including careful first-draft communication support. It is designed for busy UK lettings administrators who want ready-to-use wording frameworks without building every prompt from scratch.
Why referencing chasers are a good fit for careful AI drafting
Referencing chasers are repetitive. You may be asking for a missing document, a clarification, a completed form, an employer response, a landlord reference or another piece of information needed by your agency or referencing process.
They are also sensitive. The message may affect an applicant’s confidence, a landlord’s expectations and the tone of the whole tenancy journey. A chase that is too blunt can sound impatient. A chase that is too vague can create confusion. A chase that says too much can disclose information that did not need to be included.
AI is useful here because it can help with wording. If you already know what is missing, who needs to respond and what the next admin action is, AI can help turn those notes into a short, polite draft for email, SMS-style wording or a CRM note.
The important boundary is that AI is only supporting the draft. The administrator remains responsible for checking the facts, checking the tone, following agency policy and deciding whether the message is suitable to send. AI should not be used to make referencing decisions, interpret results or guess what might happen next.
Think of AI as a tidy-writing assistant for routine tenant and landlord update drafts, not as a referencing adviser.
Start with a missing-information checklist before opening AI
The safest way to use AI for referencing chaser messages is to prepare the facts first. This stops the tool from filling gaps, guessing the position or producing wording that sounds more certain than the file actually is.
Before opening AI, check the CRM, referencing record and any relevant internal notes. Then create a short missing-information checklist.
Referencing chaser preparation checklist
- Applicant name or placeholder: use [Applicant first name] while drafting where possible.
- Property reference or placeholder: use [property address/reference] rather than full details if the address is not needed at draft stage.
- What is actually missing: write the exact missing item or action, such as [missing item] or [information to confirm].
- Who needs to provide it: applicant, guarantor, employer, landlord, referencing provider or internal team member, if confirmed.
- Any agreed deadline or date: only include a date if it is already agreed or recorded. Do not invent urgency.
- Preferred contact channel: reply by email, upload to portal, phone the office or another normal agency route.
- Current CRM status: for example, referencing in progress, awaiting applicant response or update requested.
- Internal approval needed: check whether a negotiator, property manager, senior administrator or manager needs to approve the wording before it goes out.
Privacy note: use placeholders or anonymised details where possible. Do not put unnecessary personal data, identity documents, financial details or sensitive background information into an AI prompt just to draft a simple chaser.
Use a simple prompt structure: role, facts, tone, boundaries and output
A good AI prompt for a referencing chaser does not need to be technical. It just needs to be specific enough to keep the draft controlled.
For this workflow, use five parts: role, facts, tone, boundaries and output.
1. Role
Tell AI what it is helping with. For example, ask it to act as a drafting assistant for a UK letting agency administrator. This frames the task as admin wording, not legal advice or decision-making.
2. Facts
Give only confirmed details from the CRM or referencing record. Do not ask AI to work out what is missing. Do not ask it to decide whether the applicant is likely to pass. If a fact is not confirmed, leave it out or use a placeholder for human completion later.
3. Tone
Tell AI the tone you want. For referencing chasers, useful tone words are polite, calm, clear, factual, helpful and not pushy. You can also ask it to avoid blame, pressure, threats or invented urgency.
4. Boundaries
This is the most important part. Tell AI not to add facts, not to make legal or referencing decisions, not to promise approval or rejection, and not to include compliance wording unless your agency has supplied it.
5. Output
Say what you need: a short email, SMS-style message, landlord update, applicant update or CRM note draft. This keeps the response practical and avoids a long generic explanation.
This structure is useful for any AI toolkit for lettings administrators because it keeps the human in control of the facts and the AI focused on wording only.
Example prompts for common referencing chaser situations
The examples below are prompts, not final customer-facing messages. They use placeholders rather than real personal data. Replace placeholders only after checking the actual CRM or referencing record.
Scenario 1: Applicant missing information
Prompt: You are helping draft a routine referencing chaser for a UK letting agency administrator. Use only the facts below. Do not add deadlines, promises, legal wording or referencing decisions. Write a short, polite email to [Applicant first name]. Facts: property/reference: [property/reference]; missing item: [missing information]; requested action: [what they need to send or confirm]; contact method: [email/upload/reply]; tone: calm, helpful and not pushy. End with a simple thank-you.
Safety note: Confirm the missing item and contact method before sending. Do not include extra applicant details that are not needed for the message.
Scenario 2: Landlord or applicant update while referencing is still in progress
Prompt: Draft a brief update for [landlord/applicant] explaining that referencing is still in progress. Use only these confirmed facts: [current status], [awaiting information from whom, if appropriate], [next admin action]. Do not imply the application is approved or declined. Do not include sensitive details. Keep the wording neutral, polite and suitable for a UK letting agency.
Safety note: Do not disclose unnecessary personal information or speculate about the outcome. Check the final wording against agency policy before sending.
Scenario 3: CRM note after a chase
Prompt: Turn these confirmed notes into a factual CRM note for an internal lettings record. Notes: [date/time], [who was contacted], [method], [what was requested], [any response received], [next follow-up date if already agreed]. Keep it concise and factual. Do not add opinions, assumptions or decisions.
Safety note: The CRM note should record what actually happened, not what AI assumes happened. Check names, dates and next actions carefully before saving.
Optional wording boundary to add to any prompt
If your draft keeps sounding too forceful, add this line: Keep the message polite and practical. Avoid pressure, blame, warnings, invented urgency or any suggestion that the application will be approved or declined.
Review the AI draft before sending
The review step is not optional. Referencing chasers are external communications linked to a person’s application, so the final version should always be checked by a human before it is sent.
Use the AI draft as a starting point, then compare it with the actual record. If the wording does not match the CRM, referencing notes or agency process, change it or start again.
Pre-send review checklist
- Factual accuracy: does the message match the current referencing position?
- No invented deadlines: has AI added a date, timeframe or urgency that was not recorded?
- No promise of approval or rejection: does the message avoid suggesting an outcome?
- No blame: does it avoid making the applicant, landlord or third party sound at fault?
- No unnecessary personal data: does it include only what the recipient needs to understand the request?
- Polite tone: is it calm, clear and helpful rather than impatient?
- Agency policy match: does it follow your office’s normal wording, process and escalation rules?
- No legal or compliance advice: has it avoided giving advice or making definitive statements outside an admin update?
- Correct contact details: is the reply address, upload route, phone number or portal instruction correct?
- Suitable for the channel: is it short enough for SMS, clear enough for email or factual enough for a CRM note?
For sensitive, unusual or unclear cases, escalate the draft to a manager or appropriate internal reviewer. That includes anything involving disputed information, unclear referencing status, potential applicant outcome wording, complaint risk or a situation where you are not sure what your agency would normally say.
Where AI should stop in the referencing process
AI can help draft wording, but it should stop well before any judgement or formal decision. Referencing involves people, records, agency procedures and sometimes compliance-adjacent issues. That means the boundaries need to be clear.
Do not use AI to decide whether an applicant passes referencing. Do not ask it to interpret referencing results, assess affordability, advise on suitability, comment on eligibility, create legal notices, decide right to rent matters, advise on discrimination issues or override your agency’s process.
AI should also not send chasers automatically without review. Even a simple message can cause problems if it goes to the wrong person, includes too much information, uses the wrong tone or suggests an outcome that has not been confirmed.
A useful rule is this: AI may help you write a first draft from confirmed notes, but a trained person should decide what is accurate, appropriate and ready to send.
A reusable 6-step AI workflow for polite referencing chasers
Use this workflow whenever you need to turn confirmed referencing admin notes into a polite first draft.
- Confirm the actual referencing status. Check the CRM, referencing record and any internal notes. Do not rely on memory if the file has moved on.
- List only the missing information or action required. Write down what is missing, who needs to provide it and the correct contact route. If there is no confirmed deadline, do not include one.
- Remove or replace unnecessary personal details. Use placeholders such as [Applicant first name], [property/reference] and [missing item] while drafting. Avoid adding identity, financial or sensitive document details unless they are genuinely needed and permitted by your agency process.
- Prompt AI using role, facts, tone, boundaries and format. Ask for a UK letting agency admin draft. Provide confirmed facts. Specify a calm, polite tone. Tell AI not to add facts, decisions, promises or legal wording. Ask for the format you need, such as email, SMS-style message or CRM note.
- Review the draft against the pre-send checklist. Check accuracy, tone, privacy, channel fit, contact details and agency policy. Remove anything speculative or unnecessary.
- Save a factual CRM note and send only the approved version. Record what actually happened, then send through your agency’s normal process only after the wording has been checked.
This keeps AI in the right place: useful for drafting, but not responsible for the facts, decision or final communication.
