On this page
Borrower calls arrive all day, and each one seems urgent to the person making it. A processor who answers every call keeps borrowers happy but never finishes a condition review. A processor who never answers creates a different problem, because borrowers then call the loan officer or the branch manager. A defined call-back window gives the team a middle path that is honest, visible, and easy to staff.
Define the window before the phone rings
A call-back window is a published period when the team returns borrower calls, paired with a first response outside that period. The first response can be a short text or email that acknowledges the request and states when a person will call. This combination tells the borrower they were heard without forcing the processor to abandon the file in front of them. The window also gives the borrower a predictable time to plan around.
Choose a window that matches borrower availability rather than staff preference. Many mortgage borrowers can answer a call during lunch or after standard work hours, while processors need quiet time for document review. A window from eleven to twelve and another from three to five often covers both needs. The exact hours matter less than keeping them stable from week to week.
Publish the window in the borrower portal, the document request emails, and the voicemail greeting. When the expectation is visible, a returned call feels on time instead of late. The team should also state the target for acknowledging a new request, such as one business hour during the workday. A borrower who knows the target is less likely to call a second channel for reassurance.
Protect one block of processing time
The call-back window only works if another block of the day is protected from calls. Treat that block like a meeting with the file, and let voicemail and approved messages handle the interruptions. A processor who protects ninety minutes in the morning can often clear the document review that would otherwise spill into the evening. Record the exception so the protected block can be reviewed later.
Protection should be visible to the whole team, including loan officers and branch staff. Put the block on the shared calendar and route non-urgent calls to the call-back queue during that time. If a loan officer needs an exception, require a specific reason and a new time for the interrupted work. Exceptions that are not recorded become the new normal within a month.
Not every call can wait. Define the small set of urgent situations that justify an interruption, such as a closing scheduled within a few hours or a wire issue. Give the team a written rule for those cases and a named person who can make the call. The rest of the calls go to the queue, where they receive a promised return time.
Record the promise, not just the call
Every borrower contact should end with a recorded promise. The note names what the borrower needs, what the team will do, and when the team will respond. A note that only says left voicemail cannot support a later review or a handoff. The promise is the part that the next person can act on.
Use one field for the promised date and time, and another for the next action. Keep the language factual and avoid conclusions the team cannot support. If the borrower asks about approval or pricing, the note should record the question and route it to the licensed person who can answer. The borrower communication support workflow separates administrative updates from lending decisions for that reason.
When a call is returned, update the note with the outcome and the new promise if one exists. Close the item only when the borrower's question is answered or the work has moved to a named owner. A queue of open promises gives the team a reliable view of who is waiting and for how long. It also shows whether the window is realistic for the current call volume.
Staff the window with a rotation
One person should not own every call-back. Build a rotation that pairs a primary caller with a backup, and publish the rotation a week ahead. The primary handles the queue during the window, while the backup covers the protected block if an urgent call arrives. This keeps the process running when someone is sick or on leave.
The rotation should match skill to call type. A specialist who is still learning the file process can handle document reminders and appointment confirmations, while a senior processor handles questions about conditions or timelines. Give the junior caller a short list of questions to route rather than allowing an improvised answer. The loan processing support team can define that list during onboarding.
Track the number of calls offered, returned, and left unresolved at the end of each window. A high return rate with a low resolution rate suggests the caller lacks information or authority. A low return rate suggests the window is too short or the queue is not being worked. Review the counts weekly and adjust the rotation before the backlog becomes a complaint.
Handle the borrower who cannot wait
Some borrowers cannot take a call during the published window because of work, caregiving, or time zone. Offer one alternative that does not reopen the whole day, such as a scheduled evening slot twice a week. The alternative should be finite and visible, not an open invitation to call anytime. A predictable evening slot is easier to staff than a promise to call whenever the borrower is free.
For borrowers who prefer text or email, keep the same promise structure. The channel changes, but the commitment to a response time does not. Record the channel in the note so the next person knows where the conversation lives. The Federal Trade Commission's consumer advice on mortgage payments is a useful reference for plain-language borrower guidance, though the team should always follow its own approved scripts.
When a borrower misses a scheduled call, do not chase indefinitely. Send one message that offers a new time and explains that the file will continue on its current schedule. Record the attempt and move the item to a follow-up queue with a due date. Chasing without a limit consumes the same protected time the window was meant to defend.
Review the window every month
A call-back window is a service promise, so it needs a monthly review. Compare the promised response time with the actual return time and look for the days when the queue broke down. Ask the callers which questions they could not answer and which calls should have gone to a different owner. The answers usually point to a missing script or a routing gap.
Adjust the window when the evidence supports a change. If most borrowers answer between four and six, moving the afternoon window later may improve contact rates without adding staff. If the protected block keeps getting interrupted, the exception rule may be too loose. Make one change at a time so the team can see what improved.
Write the current window, the response target, and the urgent exceptions in one page. Give the page to every new caller and review it at the start of each rotation. A simple document that the team actually reads is more useful than a detailed policy that lives in a folder. The goal is a borrower experience that feels responsive and a processing day that still has room for the file.