Which overdue client callbacks need a manager's help?

An overdue promise can cause trouble when everyone assumes someone else is handling it: a vendor update after a price conversation, a buyer callback after a second viewing, an offer response that needed a same-day answer, or a landlord approval holding up the next move.

When reviewing a promised update, check who is waiting, which property or deal it concerns, and when the reply was due. Those details help a manager decide how urgently to intervene.

Branch managers shouldn’t treat every overdue reminder the same way. Some can stay with the original owner. Some should be reassigned quietly. Some need the manager to step in before trust drops.

Find out what the client was promised

The better operating question is, “what did we tell the client would happen by now?”

That wording matters because a reminder can be vague:

• Call Sarah
• Chase feedback
• Update vendor
• Check offer
• Send documents

A promise is sharper:

• Call Sarah by 4pm today with the seller’s answer on access
• Chase viewing feedback from the buyer who said the garden was too small
• Update the vendor before close of business with buyer strength from the weekend viewings
• Confirm whether the buyer’s revised offer has proof of funds attached
• Send the landlord the safety certificate status before the tenant signs

The second list gives a manager enough to decide what to do. The first list just says someone is behind.

An agent’s to-do list becomes hard to prioritise when it drifts away from the client or property. The list may be full, but the manager still can’t see which overdue item affects a live offer, a nervous vendor, a tenant move-in, or a buyer who is likely to walk.

Professional standards point the same way. The Property Ombudsman Codes of Practice are built around clear service, records, communication, and complaint handling. The RICS property agency and management principles also stress accurate and transparent client communication. You don’t need to turn every overdue task into a compliance incident, but you do need a way to spot which silence could become one.

Use 5 triage questions before you chase anyone

Before asking an agent “why has this not been done?”, ask 5 faster questions:

These questions keep a manager out of two bad habits: chasing everything or ignoring everything until the client rings the branch.

The overdue promise triage table

Use this table once a day, ideally before the afternoon gets swallowed by viewings and callbacks. It is simple enough to run from a shared overdue list.

Use the same rule each time:

1. Leave it with the owner when the client has not been exposed to the delay and the owner can still act cleanly.
2. Reassign it when the owner is unavailable, overloaded, or missing context another person can complete.
3. Step in personally when silence could damage trust, negotiation momentum, or complaint position.

Give those cases priority for a manager’s call.

Record the handover when reassigning work

Managers often avoid reassigning overdue work because it feels like a public correction. But in a busy branch, reassignment is just coverage.

Another agent helping is fine. The damage comes when the client hears 3 versions of the same story because the task moved without context.

When you reassign an overdue promise, pass 6 details:

• Client name and role
• Property or deal attached
• Exact promise made
• Last meaningful contact
• Current blocker
• What the next message should achieve

That is enough for a covering agent to make a useful call without pretending to know everything. It also stops the original owner coming back to a blank space later.

Agent workflow software has to do more than display a queue. In AvaroAI, overdue reminders can sit against the contact, listing, viewing, or offer they belong to, so the manager isn’t reading a free-floating task and guessing the risk. The useful part is the context around the reminder: the client promise, owner, due time, and attached matter in the same place.

Role visibility matters too. A manager may need to see that an offer-response promise is overdue without exposing every sensitive note on the negotiation. Give managers enough information to intervene while keeping unrelated sensitive notes restricted.

Do not turn every late promise into a meeting

A daily overdue review should take 10 minutes, not become another standing meeting.

Run it from a filtered list:

• Due before now
• Client-facing
• Attached to a contact, property, viewing, offer, tenancy, or file
• Not marked blocked with a reason
• No confirmed next action

Sort by risk:

1. Offer and negotiation promises
2. Same-day vendor, landlord, buyer, or tenant promises
3. Document blockers holding up public or legal work
4. Viewing feedback promised to a client
5. Routine nurture or internal admin

If a promise has no attached contact or property, don’t spend 5 minutes discussing it. Send it back to the owner with one instruction: link it or close it. A manager can’t sensibly rank a reminder that only says “follow up”.

The Propertymark professional standards section is a useful reminder that agency professionalism also lives in plain daily discipline: communication, records, and responsibility. Overdue promise triage sits right there.

The 10-minute manager routine

Try this tomorrow before the branch gets noisy.

1. Filter overdue work to client-facing promises only.
2. Remove anything with no client, property, or matter attached, and send it back for cleanup.
3. Mark each remaining promise as owner fixes, reassign, or manager steps in.
4. For owner fixes, require a new due time and the next message the client will receive.
5. For reassign, add the 6 handoff details before moving it.
6. For manager steps in, record why: trust risk, offer risk, complaint risk, document blocker, or client already chasing.
7. Review yesterday’s manager-step-in items and close the loop.

After intervening, record the outcome so the original agent and covering colleagues know what happened.

Reminder software should make this routine easy to complete. The manager should not need to ask who owns the promise, which property it relates to, or why the client is waiting. Those answers should already be visible enough to decide the next move.

Related reading

• The client promises agents should record after every conversation
• What agents should flag before managers have to chase
• Client communication fails when the thread has no owner