Phone enquiries

Callback requests: closing the loop within the hour

Who owns the callback queue, how fast each request type should be returned, when to escalate and how to log outcomes, for estate and letting agencies.

Ava research teamPublished 7 min read

On this page
  1. Where callbacks go missing
  2. One queue, one owner per shift
  3. Targets and escalation by request type
  4. Taking a message for a colleague
  5. Making the queue visible
  6. Requests that arrive after closing
  7. When the caller does not answer
  8. Logging outcomes that mean something
  9. Example: a lost valuation, and the fix
  10. Measuring the loop
  11. Frequently asked questions
  12. References

Key takeaways

  • Every callback request goes into one queue with a named owner per shift; requests in personal notebooks or inboxes get lost.
  • Set targets by request type: valuations and complaints first, then landlords, buyers and tenants, with escalation when a target is missed.
  • A callback is closed only when the caller has been reached or three attempts have been made and logged.
  • A quarter of recent sellers expect a reply within an hour[1], so the one-hour target is a customer standard, not an internal nicety.

Where callbacks go missing

Callback requests arrive from everywhere: voicemails, website forms, messages taken by a colleague, answering services, portal enquiries and 'can you ask Sarah to ring me' at the front desk. In many branches each route lands somewhere different: a sticky note, a personal email, a shared inbox, a negotiator's mobile. Requests fall through the gaps between them.

The cost is high because callback requests are usually from people who have already tried once. In a YouGov survey for Zoopla, 26% of recent sellers expected a response from an agent within one hour and 67% within four hours[1]. Someone who asked for a callback and waited a day has often called another agent in the meantime.

Recent sellers who expect an agent to reply within one hourYouGov for Zoopla, 1,000 people who sold a home in the past five years
Recent sellers who expect an agent to reply within one hourDonut chart. Expect a reply within one hour: 26%.Expect a reply within one hour: 26%26%
  • Expect a reply within one hour 26%

Source: Zoopla, 2025[1]

Show the data
ItemValue
Expect a reply within one hour26%

It also shows up in complaints. Poor, unclear or delayed communication across all stages was listed first among the top issues in Property Ombudsman lettings disputes in 2025[2], and the government's reform consultation noted that consumers often face months without updates once a sale is progressing[3]. A missed callback is often the first small failure in a longer story.

One queue, one owner per shift

The fix is structural: every callback request, from every route, goes into one queue, and one named person owns that queue for each shift. The owner does not have to make every call. Their job is to make sure each request is assigned, returned within target and closed with an outcome.

  1. Capture

    Every request becomes a task in the CRM or shared queue with the caller's name, number, reason, the time received and the target time. Colleagues who take a message at the desk add it straight away, not at the end of the day.

  2. Assign

    The queue owner assigns each request to the right person: the negotiator for the property, the valuer, the lettings manager or the property manager. If that person is unavailable within the target, the owner assigns someone else or makes the call.

  3. Call

    The assignee returns the call, refers to the request so the caller does not repeat themselves, and resolves it or agrees a next step.

  4. Log and close

    The assignee records the outcome against the contact and closes the task. If the caller was not reached, they log the attempt and the next try time.

  5. Check

    At the end of the shift, the owner reviews any open requests and hands them over by name to the next owner.

Targets and escalation by request type

Example callback targets and escalation rules for a branch; set your own and review them quarterly.
Request typeTarget returnEscalate ifEscalate to
Valuation or market appraisal30 minutesNot assigned within 15 minutesBranch manager
Complaint or unhappy client1 hourNot returned within 1 hourBranch manager
Landlord enquiry1 hourNot returned within 1 hourLettings manager
Buyer or tenant enquiry1 hourNot returned within 2 hoursQueue owner reassigns
Sale progress updateSame dayNot returned by end of daySales progressor or manager
Tenant repairPer repair urgency tierAny urgent repair not actioned within the hourProperty manager

Valuations come first because they are scarce. RICS contributors reported in September 2026 that the number of market appraisals remained below the level of twelve months earlier[4]. A valuation callback returned the next morning may find that another agent has already booked the appointment.

Complaints sit near the top for a different reason. A complaint answered within the hour is often resolved on that call; one left overnight tends to arrive in writing.

Taking a message for a colleague

Many callback requests start when a caller asks for a specific person who is out. The message taken at that moment decides whether the callback goes well. A half-written note saying 'Mr Jones rang' forces the colleague to start from scratch, and the caller has to explain everything again.

  • Caller's full name and the number they want to be called on, read back to check.
  • The property or file they are calling about.
  • What they want, in a sentence: 'wants to reduce the asking price', 'asking whether the offer was accepted'.
  • How urgent it is to them, and any time they cannot take calls.
  • What you told them: 'I said Sarah would call by 3pm.'

Then tell the caller exactly what will happen, using a time you know the queue can meet. If the person they asked for is away all day, say so and offer someone else rather than promising a call that cannot happen.

Making the queue visible

A callback queue that only the owner can see tends to grow quietly. Put the open requests somewhere the whole team can see them: a CRM dashboard on a screen in the office, a shared list in the team chat, or a short summary at the morning huddle. Seeing the count of open requests, and the oldest one, prompts colleagues to pick them up between appointments. It also makes it obvious when the queue owner needs help, for example on a Saturday when most of the team is out on viewings.

Requests that arrive after closing

Web forms, voicemails and answering service messages left overnight should already be in the queue when the branch opens. The opening shift owner works through them first, oldest and most valuable first, before booking appointments for the morning. Promise after-hours callers a specific morning time, such as by 10am, and keep it. If you use evening cover, make sure it adds requests to the same queue with the same details, so the morning team is not piecing together messages from different places.

When the caller does not answer

Many callbacks reach voicemail. Agree a fixed attempt pattern so requests are not closed too early or left open forever.

  1. First attempt within target. If no answer, leave a short voicemail and send a text with a direct number and the time of the next attempt.
  2. Second attempt at a different time of day, for example early evening if the first was mid-morning.
  3. Third attempt the next working day, followed by an email summarising what you can help with and how to reach you.
  4. Close the task with the outcome 'not reached, three attempts' and the dates. Leave the contact open for any future call.

For lettings, where Propertymark letting branches averaged 121 new tenant registrations each in August 2026[5], a fixed pattern also protects negotiators' time: three logged attempts is enough, and the applicant can always call back.

Logging outcomes that mean something

An outcome should tell the next person what happened and what happens next. Use a short list of codes and a one-line note.

  • Resolved on call: question answered, nothing further needed.
  • Appointment booked: viewing or valuation in the diary, with date.
  • Next step agreed: what, who and when, for example 'send brochure today, call Friday'.
  • Passed to colleague: who, and that they have accepted it.
  • Not reached: number of attempts and dates.

Avoid closing a task with 'called' and nothing else. If a client later says nobody rang back, a clear log settles it in seconds.

Example: a lost valuation, and the fix

Example. A fictional homeowner fills in the 'request a callback' form on a Thursday at 11am, asking about selling. The form goes to the branch email inbox, which is checked mainly by the manager, who is out valuing until 3pm. A negotiator sees it at 3.30pm and calls; the homeowner says another agent rang within twenty minutes and is coming on Saturday.

Example. The branch routes all forms, voicemails and messages into a single CRM queue, names a queue owner each shift and sets a 30-minute target for valuation requests with an alert to the manager's phone. Over the next month, every valuation callback is made within 30 minutes during opening hours, and the branch books two appraisals it would previously have lost. The greeting on the branch voicemail is updated to match the new promise; see voicemail greetings.

Measuring the loop

Track four numbers each week: callback requests received, median time to first attempt, the share returned within target by request type, and the share closed with a meaningful outcome. Look at the slowest tenth of requests as well as the median. Review the escalations: if the manager receives many, the targets or the staffing are wrong.

Some callbacks need specific handling. Valuation callers asking for a figure are covered in answering 'how much is my house worth?' calls. Repair callbacks should follow the intake in tenant repair reporting. And lettings callbacks about rent need care under the new rules; see phone enquiries about rent.

Frequently asked questions

How quickly should an estate agent return a callback request?

Within an hour for most requests during opening hours, and within 30 minutes for valuations. A quarter of recent sellers expect a reply within an hour[1].

Who should own callback requests?

One named queue owner per shift, who assigns each request, makes sure it is returned within target and hands open requests to the next owner.

How many times should we try to reach a caller?

Three attempts at different times, with a voicemail and text after the first and an email after the third, then close with a logged outcome.

What should be logged after a callback?

The outcome code, a one-line note on what was agreed and the next step with a date, or the number and dates of attempts if the caller was not reached.

References

  1. Zoopla (2025). Sellers want a more personalised communication approach from agents, but needs vary finds new Zoopla study (opens in a new tab) ↑

  2. The Property Ombudsman (2025). Annual Review 2025 (opens in a new tab) ↑

  3. Ministry of Housing, Communities and Local Government (GOV.UK) (2025). Home buying and selling reform (consultation) (opens in a new tab) ↑

  4. Royal Institution of Chartered Surveyors (RICS) (2026). UK Residential Market Survey, September 2026 (opens in a new tab) ↑

  5. Propertymark (2026). Housing Insight Report: August 2026 (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo