A loan DSA calling workflow that keeps files moving

A loan file moves when a specific document arrives, and it stalls when nobody chased it. Almost everything else about a DSA calling routine follows from that, including why speed matters at the start and why the callback hour matters more than the callback itself.

Get to the enquiry first

Applicants approach several agents at once. What decides who they continue with is rarely the rate, because at the enquiry stage they cannot compare rates meaningfully. It is whoever answered their first real question, which is almost always about eligibility: can somebody like me get this amount.

That means the first call should be able to give a straight answer about eligibility and roughly what the paperwork will involve. An agent who says they will check and call back has usually handed the file to whoever called next.

Record four things on every call

The file lives or dies on these:

1. The stage. Eligibility discussed, documents pending, logged in, sanctioned.
2. What is outstanding. Which specific documents, named.
3. Amount and tenure discussed. So a later call does not contradict an earlier one.
4. The hour they asked to be called. After the salary credit, after seven, on Sunday morning.

The fourth is the one agents skip and the one that separates a working desk from a busy one. Salaried applicants are reachable in narrow windows, and the agent who rings inside that window reaches them while the others do not.

Chase documents by message, then by call

Document chasing is where files rot. The pattern that works:

• Ask on the call, naming each document individually rather than saying the usual papers.
• Send the same list as a message immediately, so the applicant has it in writing while the conversation is fresh.
• If nothing arrives in two days, call at the hour they named rather than at your convenience.
• When something partial arrives, acknowledge it and name only what is still missing.

That last point matters more than it sounds. An applicant who sends three of five documents and hears nothing assumes the file is proceeding, and both sides discover the gap a week later.

Do not let a file exist only in somebody head

The common failure at DSA desks is that a file is fully understood by exactly one agent. When that person is on leave, ill, or has left, nobody else can pick it up, so the applicant is either re-interviewed from scratch or quietly abandoned.

The fix is unglamorous: the stage and the outstanding documents live on the record rather than in the agent memory, so a colleague can open it and continue. This also removes the ugliest version of the problem, which is an agent leaving and taking their live pipeline with them.

Working a bank or portal list

Lists supplied by a bank or bought as portal enquiries have a particular failure mode. They get called once, half-heartedly, and then abandoned, with no record of which part of the list was actually worked.

Dial them as a session with the outcome captured per number, and two things become true: you can tell what proportion was genuinely attempted, and the numbers that were switched off on Tuesday stay in the queue for Thursday rather than being lost. A run of unreachable numbers should stop the session rather than consume the morning, which is discussed in auto dialer against manual dialing.

What to review weekly

Two numbers tell a DSA desk most of what it needs: files at documents pending for more than a week, and callbacks agreed against callbacks made. The first is the stalled pipeline, the second is the reason it stalled.

The full desk workflow, with the file stages and the document-chasing messages, is on the loan DSA page.