CRM for Loan DSA in India: Track Every File From Lead to Disbursal

A CRM for loan DSA work has to follow each file from the first call to the day the lender releases the money. That means stages for eligibility, documents, login, sanction and disbursal, fields for each loan product, a source for every connector and sub-DSA, and a next follow-up date on every open file. Then the owner reviews file status every morning.

An Excel sheet and a few WhatsApp groups work while the owner can hold every file in their head. They stop working once you have several telecallers, a login team, a dozen connectors and files open with six lenders. Loan brokers who place files with several banks and NBFCs hit the same wall.

Why a CRM for loan DSA work looks different from a sales CRM

A general sales CRM assumes a short path: enquiry, a few calls, a sale. A DSA's path is longer, and most of it happens after the customer says yes. Then come salary slips, bank statements, property papers, a login with the lender, credit queries, a sanction letter and finally the disbursal that earns your payout.

So a CRM for DSA and loan broker offices has to handle a few things a sales CRM often treats as extras:

• The file, not the enquiry. You are paid on disbursal, so stages must run all the way there.
• Different facts per product. A home loan needs property details; a business loan needs turnover and vintage.
• Follow-up on two sides. Telecallers chase customers for documents, and the login team chases lenders for status. Every open file needs a next action and one person who owns it.
• People as a lead source. Connectors, sub-DSAs, builders' sales teams and CAs send files, and many expect a share of your payout.
• Sensitive paperwork. PAN, Aadhaar, bank statements and ITRs pass through the office.

If your files sit in a spreadsheet today, the guide to importing your leads covers moving them across without retyping.

A stage map: lead, eligibility, documents, login, sanction, disbursal

Keep stages to the steps someone actually acts on. In atomcrm.ai, stages are fully customisable and grouped as Not known, Qualified, Disqualified and Other, and a stage can require a next callback date, or an appointment, before a lead can move into it. That one rule does most of the work of keeping files alive.

If one lender declines and you plan to try another, move the file back to Eligible, add the next lender and give it a date. Keep the Disqualified stages for files you have genuinely given up on.

A file holds one pending callback at a time, and a new date replaces the old one. Give the callback to whoever acts next (the telecaller until login, the login team after), and track the other side's chase as a task with a due date in the optional Tasks module.

Use statuses for why a file is stuck. A status is a separate optional label that doesn't change the stage or the reports, so Documents pending plus Property papers pending tells a manager exactly what is missing. Useful ones: Salary slips pending, Bank statement pending, Co-applicant needed, Credit score issue, Lender query open, Customer not responding.

Fields per product: home loan, personal loan, business loan, LAP

Put one dropdown on the lead, Loan type, and show only the fields that product needs. Custom fields can be dropdown, text, number, currency, date, checkbox or multi-select, with conditional rules to show, hide or require them. Every file gets Loan amount required, Employment type, Net monthly income, Existing EMIs, Credit score as told by the customer, and City. Then:

Add file-tracking fields for every product: Lenders logged with (multi-select of your banks and NBFCs), Lender application number, Login date, Sanction amount and date, Disbursal amount and date, Payout rate (number), Payout amount (currency), Connector name and Connector share.

Put Loan type, Loan amount, Net monthly income and Employment type on Quick Update, the one-panel call update, so telecallers fill them during the call. The guide to lead fields and stages shows where each setting lives.

Connectors and sub-DSAs as lead sources

Connector files are easy to lose because they arrive as a WhatsApp forward or a call to the owner's mobile. Create a lead source called Connector referral and a Connector name dropdown listing every connector and sub-DSA. The source lets you compare connectors against ads; the name pulls up one person's files in seconds. A connector with steady volume can get a source of their own, set to bypass the assignment rules and go straight to one telecaller.

Connector leads come in three ways:

1. Typed in by a telecaller. If the customer already has a lead (matched on the last 10 digits of the phone, or on email), the CRM records a re-enquiry on that lead instead of a second one, which helps settle "I sent him first" between two connectors.
2. A weekly sheet imported as CSV, up to 5,000 rows per file, with a phone or email on every row. A CSV import does not check for repeat enquiries, so remove numbers you already have first.
3. A sub-DSA's own web form, posting to its own private webhook URL.

A worked payout example

Say a DSA in Pune closes four files this month. The rates are made up for illustration; real payouts depend on your agreement with each lender and connector.

Total payout is ₹69,000, connector shares are ₹23,250, and the office keeps ₹45,750. The disbursal amount, payout rate, payout amount, connector name and agreed share are all fields on the lead, filled in by your team as each file closes. So when a connector calls asking about their money, you filter Disbursed plus their name and read out the files.

Document collection and customer data protection

Documents are where files stall and where the risk sits.

Send the checklist the moment a file moves to Documents pending. Document chasing usually happens days after the customer last messaged you, outside WhatsApp's 24-hour window, when only a Meta-approved template can be sent. In atomcrm.ai you write templates in the CRM, submit them to Meta and they sync back once approved. For example:

Hi {{1}}, this is {{2}} from {{3}} about your {{4}} application.
To send your file to the bank we still need: {{5}}.
You can reply on this chat with clear photos or PDFs.
If something is not ready yet, reply with a date and we will call you then.

Keep documents on the lead, not on phones. The lead page takes document uploads next to the full call and message history, so the file stays with the office when a telecaller leaves.

Limit who sees what. Set each role's data scope to own leads, team or everything. Mask phone numbers to the last four digits for roles that don't need to call. Every change and export is in the audit trail, logins can require an OTP, and data is stored in India. The security page lists these controls.

The Digital Personal Data Protection Act, 2023 sets out how businesses must handle customers' digital personal data, and your lender agreements may add their own terms on customer documents. Check the current rules and your agreements with your lenders or a professional.

A daily file-status review for DSA owners

Your most valuable file is one that is sanctioned but not disbursed. Say 12 files sit in Sanctioned with sanction amounts adding up to ₹2.4 crore. At a hypothetical average payout of 0.6%, that is ₹1,44,000 waiting on paperwork or a customer who has gone quiet. A 15-minute review each morning keeps it moving:

1. Overdue callbacks. The Overdue tab of the callback queue lists missed follow-ups oldest first, each card showing the last comment. Anything overdue in Sanctioned or Logged in gets reassigned or called by you.
2. Sanctioned, not disbursed. A saved view with Sanction date and lender as columns. For each file: what is blocking disbursal, and when is the next action?
3. Lender queries. Filter Logged in by the status Lender query open. Each one needs a name and a date.
4. Documents pending by status. If Property papers pending keeps growing, the cause may be one builder, not your telecallers.
5. Files with no callback booked. The Assign board shows, stage by stage, leads with no callback booked, for handing out in bulk. Leads that matched no assignment rule stay unassigned and visible on the leads list, so glance at those too.
6. Connector files not yet called. Filter stage New enquiry by the Connector referral source, and include the sources you created for individual connectors. Connectors notice when their leads wait.

Pin the views from steps 2, 3 and 6 to the sidebar. A reminder arrives 15 minutes before each callback is due. Here is how the callback queue works.

Setting up a DSA office in atomcrm.ai

A first-week setup, in the order that saves rework:

1. Stages, statuses and fields from the tables above, with Disbursed as your Converted stage. The Document pickup appointment is created automatically when a lead moves into that stage.
2. Teams and branches, for example secured and unsecured loans, and a branch per office. Automatic assignment runs round robin, weighted, capacity or performance rules with a daily cap per person and a fallback person. Leads that match no rule stay unassigned and visible.
3. Lead sources. Connect Meta lead ads by logging in with Facebook, map form questions such as loan type to your fields, and backfill missed leads for up to 90 days. Add your website eligibility form by webhook.
4. WhatsApp. Connect the inbox through Meta's WhatsApp Cloud API or Gupshup, and add an automation that sends your checklist template when a lead's stage changes to Documents pending.
5. Calls. On Android, the Call Pro app logs every call on the lead with outcome, duration and recording.
6. Reports. Email leads by stage and telecaller performance daily to you and your team leads.

What it does not do matters as much. atomcrm.ai does not connect to bank or NBFC loan portals, so your login team updates stages after checking each portal. It doesn't pull credit bureau reports. There is no automatic dialling, and the only app is Call Pro for Android. If you need any of those built in, it is not the right fit.

See how atomcrm.ai works for loans and insurance teams, and if your office also sells policies, the insurance agents version of this guide.

Frequently asked questions

What is the best CRM for loan DSA in India?

There isn't one right answer for every office. Score each option on the same points: stages that run to disbursal, a required follow-up date on open files, fields that change by loan product, connector tracking, WhatsApp templates, role-based access with masked numbers, and where data is stored. Then run a month of real files through a trial.

Can a DSA CRM connect to bank and NBFC loan portals?

atomcrm.ai does not connect to lender portals. Your login executives check each portal and update the stage and fields themselves. Keep the lender's application number in a text field for quick lookup, and make Logged in require a callback date so every file has a day on which someone checks its status.

How do I track connector and sub-DSA payouts in a CRM?

Record the connector's name and agreed share as fields on the lead, and fill in the disbursal amount and date when the file closes. At month end, filter Disbursed files by connector and you have the list to settle. The CRM keeps the record; the payment itself goes through your usual accounts process.

Is it safe to keep KYC documents in a CRM?

It depends on the controls. Look for data scope by role, masked phone numbers for staff who don't call, a full audit trail, login OTP and clear information on where data is stored. atomcrm.ai stores data in India and isolates each workspace. Check your lender agreements and the Digital Personal Data Protection Act, 2023 for what you may collect and keep.

Next step: run this month's files through a trial

Take the files you have open right now and put them through the stage map above. Start a 14-day trial for ₹5, set it up with your own lead sources, stages and connectors, and see how many files have no next date. Or book a 20-minute demo and bring your stage list and product mix.