Sales Progression for Estate Agents: Chain Chasers With AI

A sales progressor can use AI to keep a chain moving by logging every link and milestone in a tracker, having AI draft a specific chaser the moment a task is overdue, alerting the team to stalled milestones, and escalating by rule. A person reviews each message and makes the phone calls.

The reason it works is simple. Most chains do not collapse because of one disaster. They stall through dozens of small silences: a search not ordered, an enquiry reply sitting in an inbox, a mortgage offer no one has asked about. AI is good at the dull part, which is noticing the silence and drafting the nudge, and poor at the part that matters most, which is judging a relationship. So the machine watches the dates and writes first drafts, and the progressor decides what is sent and when to pick up the phone.

Follow me on Instagram@sagnikteaches

The four parts of the system

1. A chain tracker that records every link, every milestone and every date.
2. Chaser drafts generated from the tracker, specific to the task and the recipient.
3. Milestone alerts that tell the progressor what is overdue today, in priority order.
4. Escalation rules that say who gets called, and when, when the chasers do not work.

Client updates sit on top: short, regular, factual messages to buyers and sellers drawn from the same tracker. Each part below comes with a template you can copy.

Connect on LinkedInSagnik Bhattacharya

Build the chain tracker first

AI cannot chase what you have not recorded. A spreadsheet or your CRM's pipeline view works as long as every link has the same fields. For each property in the chain, capture one row per party and milestone.

Subscribe on YouTube@sagnikteaches

The milestone list is the heart of the tracker. A typical sale runs through: sale agreed and memorandum of sale issued, solicitors instructed on both sides, identity and source-of-funds checks, mortgage application and valuation, searches ordered and received, contract pack issued, enquiries raised and answered, survey results dealt with, mortgage offer received, contracts signed, deposit in place, exchange, and completion. Adapt the list to your market, and add the other links' milestones so you can see where a chain is genuinely waiting.

Setting expected dates

Without expected dates there is no "overdue". Use your own history: from your last 30 completed sales, work out how many working days each milestone usually takes, and add a buffer. If searches normally come back in 10 working days, the expected date is the order date plus 10 working days, and a chaser fires on day 12. Put those defaults in the tracker so the progressor only overrides them when they know something specific, for example a known backlog.

Chaser drafts that get an answer

A good chaser asks one question, names the file, states what is needed, and gives a date. A bad one says "Just checking in on this one". AI is good at following that structure if you give it the tracker row.

Draft a short, polite email from a sales progressor to a solicitor.
Facts (use only these): property ref [REF]; milestone [MILESTONE]; expected by [DATE]; last contact [DATE, METHOD]; blocker [BLOCKER]; chain position [N of M]; target exchange [DATE].
Rules: one clear question; say what we need and by when; mention that the chain is waiting on this only if true; no legal advice; no blame; under 90 words; end with my name and direct line placeholder.
Chaser number [1/2/3]: tone is [friendly / firm / firm and formal].

Illustrative output for a first chaser on a mortgage offer: "Hi [first name], following up on ref 88. We understand the mortgage offer was due last Friday and we are the link between the buyer's chain above and the onward purchase below. Could you let me know today whether the offer has been received, and if not, who at the lender is dealing? We are aiming for exchange by the 28th. Thanks, [your name]." What you would fix: the progressor checks that "we understand the offer was due last Friday" is true, removes the chain remark if the solicitor does not need pressure, and confirms the exchange target is the one the parties agreed.

Three tones, one ladder

Keep three versions of each chaser and move up the ladder only when the previous one fails.

• Chaser 1, friendly. Asks for a status. Assumes the solicitor is busy.
• Chaser 2, firm. References the first message, restates the date and asks for a reply by a stated time.
• Chaser 3, formal and copied. Summarises the history in three lines, states the effect on the chain, copies the right person and ends with a phone call.

Illustrative second chaser: "Hi [first name], I emailed on Monday about the enquiry replies on ref 88 and have not yet heard back. These replies are now the only item between us and exchange. Please could you confirm by 3pm tomorrow when we can expect them? I will call the office at 2pm if I have not heard." Here the AI draft is useful because it keeps the date, the history and the next step together. The call at 2pm is a commitment the progressor must then keep.

What the chaser should not say

Do not let a draft assert that the other party is at fault, predict an exchange date no one has agreed, or give a view on the contents of a contract or search. Add a rule in your prompt and look for those phrases when you review. A progressor's job is to ask and to record, not to adjudicate.

Milestone alerts: what is overdue today

Alerts turn the tracker into a daily list. You need only three rules to begin.

1. Overdue: expected date passed, no actual date. Show it in the morning list.
2. At risk: expected date within two working days, and an upstream milestone is not complete. Show it so you can act before it slips.
3. Chain-critical: any overdue milestone in a chain where another link has already exchanged-ready status, or where a completion date is within 14 days.

Most CRMs and spreadsheets can do this with filters and a daily saved view. Where you want AI in the loop, paste the day's overdue rows, stripped of names, and ask for a ranked list: "Rank these by risk to the chain, give a one-line reason for each, and propose the next action: email, call, or escalate." The model's ranking is a suggestion. The progressor knows which solicitor responds to calls and which to emails.

A morning list, illustrated

Say a progressor is running 38 live sales. The morning view shows 11 overdue items. The AI ranking puts three at the top: a mortgage offer outstanding in a four-link chain with an exchange target in six days; a missing identity document holding up a first-time buyer's solicitor; and enquiry replies from a seller's solicitor, third chase. The progressor starts with two calls, then uses AI drafts for the remaining eight, reviews them in 15 minutes and sends. The chain-critical item gets a call, not an email.

Escalation rules written down

Chasers fail. When they do, the progressor needs a rule, not a mood. A ladder like this works for most agencies.

Write the ladder at the top of the tracker and share it with the team. Tell clients about it at the start: "If I haven't heard from the solicitor within two working days I'll chase, and I'll let you know at each step." Clients who understand the pattern stop sending their own chasers.

Client updates from the same tracker

Buyers and sellers want to know three things: what has happened, what is happening now and what happens next. An AI draft built from the tracker can give them that in four lines. Send it weekly, or when a milestone moves, whichever is sooner.

Write a short update to a seller, friendly and plain, under 100 words.
Facts: [MILESTONES DONE THIS WEEK]; [WHAT WE ARE WAITING FOR AND FROM WHOM]; [NEXT STEP AND DATE]; target exchange [DATE or "not yet agreed"].
Do not promise dates that are not in the facts. Do not criticise any party. End with when I will next update them.

Illustrative output: "Hi [first name], good progress this week: the buyer's mortgage valuation is done and searches are now ordered. We are waiting on the buyer's solicitor for their enquiries, due Thursday. I will call them on Friday if it has not arrived, and update you by end of day. No exchange date is agreed yet; I will confirm once the enquiries are in." What you would fix: check that the valuation really is done and that Thursday is the date the solicitor gave. The "no date agreed" line is deliberately included, because a vague "soon" invites a worse question.

A worked example: a four-link chain

An illustration with invented details. A progressor holds a chain of four: a first-time buyer (link 1) buying from a couple (link 2) who are buying from a family (link 3) who are buying a new flat (link 4). Link 2 is the agency's sale. Target exchange is Friday the 27th.

1. Monday. The morning list shows two overdue items: link 1's mortgage offer (expected last Thursday, chaser 1 sent) and link 3's enquiry replies (expected Friday). The progressor calls link 1's solicitor and is told the lender asked for another payslip. The tracker blocker becomes "awaiting buyer's payslip". An AI draft asks the buyer, through the agency's approved channel, to send it today.
2. Tuesday. Link 3's chaser 2 goes with a 2pm call. The solicitor says replies go out tomorrow. The progressor logs "promised Wed" and sets an alert.
3. Wednesday. Replies arrive. The tracker moves; the AI draft updates the seller of link 2 and the buyer.
4. Thursday. The mortgage offer arrives. Exchange for Friday looks possible, so the progressor sends the chain a short "what's left" list: contracts signed, deposits in place, and confirmation from link 4.
5. Friday. Link 4's deposit is late. The ladder reaches step 4: the manager calls the developer's sales office. Exchange moves to Monday, and every link is told the same message at the same time.

None of this needed AI to be clever. It needed the tracker current, the drafts quick, and a rule for when to pick up the phone. The saving is the time between noticing the silence and sending the right message, which in this example is minutes rather than a morning.

Two more cases: a stalled survey and a silent caseworker

The survey that changed the price

A buyer's survey flags damp in a back bedroom and the buyer's solicitor goes quiet while the buyer decides what to do. The tracker shows "survey received, buyer deciding" for six days. The progressor's alert marks it at risk, because the chain below has a completion target in three weeks. The AI draft to the buyer's agent contact is short and neutral: "Hi [first name], could you let me know whether [buyer] plans to renegotiate or proceed on the current terms? The seller would like to respond this week, and the chain below is waiting on the answer." The progressor does not predict the outcome. The seller gets a separate call that explains the options, and the draft to the seller contains no pressure either way. What this shows is that AI speeds the asking, and the judgement about price remains with the people.

The caseworker who never replies

One solicitor's caseworker answers about a third of emails. The tracker shows chaser count 3 on enquiry replies. Rather than send a fourth email, the progressor follows the ladder: a phone call to the firm's main number, asking for the caseworker's supervisor by name, and a formal chaser copied to that supervisor. The AI draft for the formal version summarises the history in three lines: "Enquiries raised on the 6th; chased on the 11th and the 13th; call made on the 14th. We need replies by Friday so that the chain can keep its exchange date." Listing the dates matters because a supervisor can act on a history in a way they cannot on a general complaint.

A quick sum: what the morning list is worth

Illustrative figures. A progressor with 38 live sales spends two hours a morning reading the pipeline and writing chasers. With the tracker alerts and drafts, the same work takes 45 minutes. That is 75 minutes a day, about six hours a week, which becomes time for calls on the five most critical chains. If that extra call time rescues one sale a month, and one fee on a sale is a figure the agency knows better than any template, the system has paid for itself. If it rescues none, you have still reduced the number of silent files. Measure rather than assume: log time and rescues for two months.

Separating chasers by audience

The same fact needs different wording depending on who reads it. Keep a short set of variants so the AI draft starts with the right voice.

• To the other side's solicitor: brief, specific and professional, referencing the milestone and date. They are busy and handling many files.
• To the buyer or seller: plain language with no jargon, explaining what the delay means for them and what they can do to help, such as returning a form or contacting their lender.
• To another agent in the chain: practical and collaborative, sharing dates and asking for theirs, because you each hold part of the picture.
• To your own manager: a two-line risk summary with the date of the next action.

Put the audience in the prompt as a line, "Recipient: seller, no legal background," and the draft adjusts. For earlier steps in the sales cycle, valuation appointment preparation sets expectations that make chasing easier later.

Keeping client data safe

Chains contain names, addresses, prices, finance details and sometimes health or family circumstances. Before putting any of it into an AI tool, check that the tool is approved by your firm for client data, that training use is switched off, and that you know the retention terms. Use property references or initials in prompts where you can, and keep the full record in your CRM. The buyer and vendor follow-up tutorial covers where to draw that line across the whole customer journey.

Never paste a solicitor's confidential client information into a tool. Your messages ask about progress, so they should not need it. If a solicitor includes sensitive detail in a reply, leave it in your CRM and keep it out of drafts.

Six ways a chaser system goes quiet

• Stale tracker. The AI chases something that was resolved on the phone. Fix: update the tracker before generating chasers, and set a rule that a phone call is logged the same day.
• Chasing the wrong person. The caseworker left and the email went to a dormant mailbox. Fix: keep a second contact for each solicitor.
• Tone drift. Every chaser sounds the same and gets ignored. Fix: vary the opening and cite a specific document each time.
• Ladder skipped. The progressor sends five emails and never calls. Fix: the ladder says "call" at step 2, so make the alert show it.
• Over-promising to clients. A draft implies a date. Fix: the prompt says never to state a date that is not in the facts, and the reviewer checks.
• Chain blindness. You chase your link and ignore the one that is blocking everyone. Fix: show chain position in every row and review the whole chain weekly.

How to tell whether it is working

Pick three measures and review them monthly. The first is average working days from sale agreed to exchange across your sales, since a falling number suggests chases are landing earlier. The second is the fall-through count, tracked by reason, because "no response from solicitor" should shrink. The third is the progressor's time: log how long the morning list and chasers take before and after. If a progressor with 38 sales used to spend two hours drafting and now spends 45 minutes, the time has gone back into calls, which is where deals move.

Check a sample of sent messages every fortnight for accuracy and tone. A short complaint log from solicitors and clients tells you when drafts have become irritating. Over time, keep the chaser wording that gets fast replies and retire the rest.

A five-day setup for one branch

1. Day 1. Build the tracker fields and milestone list, and import your live sales.
2. Day 2. Set expected dates from your last 30 sales and add the overdue filter.
3. Day 3. Save the three chaser prompts and test each on five old cases, comparing with what you sent.
4. Day 4. Write the ladder and share it with the team and the branch manager.
5. Day 5. Run the morning list live and review every draft before sending.

Keep a human on every send for the first month. Then decide, message by message, whether any simple reminder is safe to schedule. For inbound chain calls out of hours, the receptionist call flow tutorial shows how to log them into the same tracker. If you would rather set this up with someone, my AI implementation consultation covers mapping the process and building a version your team can run.

Questions sales progressors ask about using AI

Can AI send chasers automatically?

It can, but start with drafts that a person approves. A sales progressor knows when a solicitor is waiting on a search result and when a nudge would be unwelcome. Automatic sending suits only the simplest reminders, such as a scheduled check on an overdue document, once you have tested the wording for a month.

How often should I chase a solicitor?

Set the interval by milestone, not by habit. A workable pattern is a chase when a task is two working days overdue against its expected date, then a second after another two days with a phone call, then escalation. Tell the client the pattern so nobody feels ignored or hounded.

Is it safe to put chain details into an AI tool?

Only into a tool your firm has approved for client data, with the data terms read. Names, addresses, prices and finance details are personal and commercial information. Use initials or reference numbers in prompts where you can, and keep the full records in your CRM or tracker.

What should I never let AI write?

Anything that states legal advice, promises an exchange or completion date you have not been given, or characterises a solicitor's competence. Drafts should state facts, ask a specific question and set a date. A person reviews every message that goes to a party in the chain.

Further reads

• How Conveyancers Use AI to Cut Admin on Each Transaction — The other side of the chase: the conveyancer's admin.
• How Estate Agents Use AI to Write Property Descriptions — Get properties to offer stage faster with better listings.
• AI for Letting Agents: Handle Tenant Queries Without Extra Staff — A parallel system for lettings queries.
• How to Chase Missing Client Records With AI Before Deadlines — Chasing documents with AI before deadlines.
• Virtual Assistant or AI for a Real Estate Agent: What Goes Where — Decide which chasing tasks go to people and which to AI.
• AI Tools for Estate Agents: A Stack by Job, Valuation to Completion — A stage-by-stage AI stack for a small estate agency: valuation, listing, viewings, offers and progression, with costs and the checks each needs.
• Lease Renewal Letters With AI: Offers, Reminders and Rent Changes — A renewal sequence a leasing team can run with AI: offer letter, reminders and rent-change wording, with a notice check and sign-off before sending.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: general sales progression practice; no vendor pricing is quoted in this tutorial. Check your CRM and AI tool's current data terms before use.