Loan Brokers
MCA Lead Qualification Questions: Capture a Complete File Without Pre-Deciding It
A staged merchant-intake checklist for identity, purpose, operating facts, obligations, documents, consent, and specialist handoff.
A commercial-finance first call should capture merchant identity, business basics, requested amount and use, caller-stated revenue and time in business, existing obligations, timing, available documents, consent source, and specialist questions. Those answers create an intake record—not an approval prediction or legal classification.
Separate merchant intake from product and credit decisions
| Layer | Intake may capture | Specialist, funder, or counsel decides |
|---|---|---|
| Identity and request | Business name, contact route, use of funds, requested amount, and caller-stated timing | Verification method, product eligibility, underwriting outcome, and final offer |
| Operating facts | Merchant-stated revenue range, time in business, industry, and existing obligations | Document requirements, verified cash flow, risk treatment, pricing, and approval |
| Product explanation | Approved process language and a neutral description of next steps | Legal classification, disclosures, material terms, reconciliation rights, and contract interpretation |
| Follow-up | Consent source, channel, opt-out status, missing items, and next owner | Permitted outreach, required notices, record retention, and complaint resolution |
Commercial-financing obligations vary by product and jurisdiction. The FTC has applied its authority across providers, brokers, ISOs, marketers, lead generators, servicers, and collectors; California is one example of a state with commercial-financing disclosure requirements. Regulation B also reaches business credit, and covered institutions should review the CFPB's current section 1071 materials. These are issue-spotting sources, not a substitute for legal review. FTC guidance for financing providers and marketers · California commercial-financing disclosure regulations · CFPB Regulation B · CFPB small-business lending rulemaking
Capture the file in four stages
| Stage | Core questions | Boundary |
|---|---|---|
| 1. Identity and request | Legal and trade names, role, entity and state, amount, use, timing, contact | Do not imply intake is an application, approval, or offer unless approved process says so |
| 2. Merchant-stated facts | Time, industry, revenue estimate and period, seasonality, locations, obligations | Mark estimates and sources; do not call them verified |
| 3. Documents and permissions | Existing records, secure route, consent record, missing items | Do not request sensitive files through an unapproved channel |
| 4. Specialist handoff | Questions, uncertainty, product interest, complaint signals, owner, next step | Do not quote cost, predict approval, select product, or interpret contract |
The FTC has challenged deceptive financing claims about amounts, collateral, guarantees, and withdrawals. Intake language should be approved and auditable; Regulation B and state disclosure rules must be mapped rather than inferred from the label MCA. FTC small-business financing guidance · FTC guidance for financing providers and marketers · CFPB Regulation B · California commercial-financing disclosure regulations
Measurement plan
- Required fields completed and corrected after review.
- Estimates preserved with source and period.
- Pricing, approval, complaint, classification, and exception routing.
- Secure-document and consent records attached correctly.
- Files closed with an explicit reason.
Commercial-finance intake forms overlap but are not universal. Define approved core fields and legitimate product, jurisdiction, accommodation, and fact-specific branches; record merchant statements without turning intake into underwriting.
Intake is information capture, not decisioning. Use an approved core with documented product, jurisdiction, accommodation, and fact-specific branches; preserve merchant statements and uncertainty; route verification, product, pricing, and decisions to authorized owners.
The first-call intake sheet
| Question | Why the file needs it |
|---|---|
| Legal business name and entity type | The file starts here — and “I run it under my own name” tells you something about what the submission will need. |
| Monthly revenue, as deposits | Record the merchant-stated revenue or deposit measure, period, source, and uncertainty. The authorized review process determines which measures and documents are relevant. |
| Time in business | Months, not vibes. Many funding programs have minimums, and the answer shapes which funders even see the file. |
| Industry | Funders maintain industry appetites and exclusions. Knowing it’s a trucking company or a restaurant on call one saves a doomed submission. |
| Use of funds | Inventory, payroll, equipment, expansion — this is also where you learn whether an advance is even the right product to broker. |
| Amount seeking | The ask against the revenue tells the specialist whether the conversation is realistic before anyone runs numbers. |
| Open positions | Whether the merchant currently has advances outstanding — how many, and roughly how much remains — changes everything downstream. |
| Timeline | “By Friday” and “sometime this quarter” are different files with different funder lists and different specialist priorities. |
Ask the revenue question like an underwriter reads it
Ask what measure and period the merchant is reporting, record it as merchant-stated, and preserve uncertainty. The assigned review process decides which documents and calculations are required.
Handle the positions question without flinching
Ask about existing obligations neutrally when approved, record what the merchant states, and avoid implying an outcome. The authorized process decides relevance, verification, product fit, and next requests.
Let use of funds do the brokering
Use of funds is an important routing fact, but intake should not select a product or imply suitability. Capture purpose, amount, timing, constraints, and questions for an authorized specialist.
What the first call should never do
- Quote pricing. No factor rates, no cost estimates, no “ballpark” — numbers come from a specialist after the file is reviewed.
- Promise or predict an approval. “Looks great, you’ll definitely get funded” is a sentence that should not exist at intake.
- Make a universal product-classification statement. Use counsel-approved language based on the actual agreement, product design, transaction, and jurisdiction.
- Freelance the question list. Skipping questions for merchants who “sound strong” and piling extras on ones who don’t corrupts both your fairness and your data.
- End with an explicit next step, assigned owner, and the approved document request—if any—rather than assuming a universal stip list or calendar action.
Operational principle: A qualified MCA lead isn’t a merchant who sounds fundable. It’s a merchant whose file has seven answers in it and a specialist call on the calendar.
running the approved sheet on each covered intake, not just the 10 a.m. ones
LumiTalk's audited registry includes code-verified real-time voice, real-time chat, knowledge-base, CRM, agent-management, and agentic-action capabilities. Channel, coverage, language, scheduling, suppression, and destination actions are configuration-specific; verify each operation with a synthetic merchant record, failure test, and audit trail.
Test a synthetic merchant inquiry, opt-out, escalation, destination outage, and recovery path before selecting a deployment.
Explore LumiTalk for business loan brokersContinue through the lending content cluster
Connect this decision to the surrounding service and workflow guides. LumiTalk for business loan brokers · AI intake guide · answering-service scorecard · MCA CRM guide
Scope: This article provides general operational information, not financial, legal, tax, lending, underwriting, or compliance advice. Product classification and duties depend on the agreement, purpose, parties, collateral, solicitation method, jurisdiction, and current law. Use qualified professionals to review the deployed workflow. Existing LumiTalk availability, response-time, language-count, channel, integration-count, scheduling, and named-system action descriptions remain verification-needed until reconciled to the intended configuration; that neutral state is not a finding that a capability is absent.
Quick answers
Frequently asked
What should first-touch intake capture for a commercial-finance inquiry?
Capture identity, business and request details, merchant-stated operating facts, obligations, use of funds, timing, available documents, uncertainty, consent, and the next owner.
What stays with an authorized human or governed decision process?
Keep pricing, product choice, contract classification, exceptions, approval, denial, and legal interpretation within the assigned reviewed workflow. Intake creates and routes a record; it does not make those conclusions merely because it collected the facts.
How should technology or a service be tested?
Use synthetic scenarios that exercise required fields, prohibited questions, escalation, duplicate records, destination outages, recovery, access, retention, and reporting. Preserve the resulting evidence.
What product claims need configuration-specific proof?
Verify the required channel, coverage window, language, response target, scheduling operation, connected-system relationship, supported action, retry behavior, and audit history in the intended deployment.
Evaluate the complete commercial-finance intake workflow
Use synthetic merchant and partner scenarios to verify capture, consent, decision boundaries, escalation, connected-system behavior, recovery, privacy, and reporting in the intended configuration.
