Loan Brokers
How to Work Aged MCA Leads: Build the Consent Ledger Before the Cadence
A finite workflow based on provenance, consent, suppression, segmentation, honest messages, and callback handling.
Work an aged lead only after establishing source, consent text, identified seller, covered channels and purposes, permission date, and later suppression. Then use a finite segment-specific plan with honest identity, a clear exit, and a staffed response path.
Separate merchant intake from product and credit decisions
Commercial-financing duties vary by product and jurisdiction. FTC authority reaches providers and marketers; Regulation B reaches business credit; state disclosure rules may apply. Use qualified product-specific review. FTC financing guidance · CFPB Regulation B · California disclosure regulations
The consent ledger comes before segmentation
| Field | Why | Block when |
|---|---|---|
| Source and context | Shows what person saw | Only contact data exists |
| Consent text | Defines seller, purpose, channel, technology | Exact text and time unavailable |
| Identity and owner | Prevents undefined multi-brand permission | Contacting entity outside permission |
| Suppression | Combines entity, campaign, vendor, channel | Any stop unresolved |
| Transfer history | Shows recipients and controls | Recipients or deletion duties unclear |
| Campaign basis | Connects permission to method | Counsel has not approved scope |
Measurement plan
- Accepted, quarantined, and rejected records
- Opt-out propagation across vendors
- Response, intake, review, and funded outcomes by segment
- Complaint, wrong-party, duplicate, and stale rates
- Callback and handoff completion
An aged lead is a prior inquiry whose current contactability cannot be inferred from age or a vendor label. Establish provenance, exact disclosure and consent, identified seller, covered purpose and channels, transfer history, and suppression before outreach.
Rule zero: only work lists you can defend
- Documented consent: work leads where the merchant provided their contact information and agreed to be contacted about funding — and where you can show it. If a list vendor can’t produce the consent trail, that tells you what you’re buying.
- Honor every applicable opt-out and suppression rule across the relevant entity, purpose, and channel. Use counsel-approved retention and re-permission rules and propagate the stop state to vendors before further outreach.
- Respect calling and texting rules: telemarketing regulations around automated outreach are strict and actively enforced in this industry. Time-of-day limits, identification, and channel consent aren’t optional garnish.
- Lead with identity and an exit: each covered interaction says who you are, why you’re reaching out — they inquired with us about funding — and how to make it stop.
None of this is just compliance hygiene. Merchants who get hammered by funding robocalls reward the one shop that shows up like a professional.
Segment by why the file stalled
A flat re-dial of the whole list is how aged campaigns die. The lead’s history tells you the message:
| Segment | What likely changed | The re-engagement angle |
|---|---|---|
| Funded elsewhere | That advance may be substantially remitted by now — a possible renewal-timing window | A check-in about how the funding worked out and what’s next, not a pitch against their funder |
| Went quiet mid-process | The urgent need passed, or gathering stips felt like homework | Make resuming effortless: the file’s still open, here’s the one thing needed to move |
| Didn’t fit at the time | More months in business, stronger deposits, a position paid down | An honest “worth another look?” — circumstances change and the door’s open |
| Seasonal industries | The season that drove the original inquiry is coming back around | Reach out ahead of the buy — inventory, staffing, equipment prep |
A cadence that respects the merchant and the math
- Open on the channel they gave you — a short, identified message referencing their original inquiry, with a clear opt-out. No wall of urgency, no countdown clocks.
- Space the touches in days and weeks, not hours. Two or three attempts across a couple of weeks, then rest the record for a segment-appropriate interval.
- Rotate the substance, not just the timestamp: a process note, a product-fit thought (equipment financing or factoring may suit them better now), a season-ahead check-in.
- Kill on signal: an opt-out ends everything permanently; sustained silence retires the record. A list worked forever is a complaint generator, not a pipeline.
- Log each covered interaction in the CRM — channel, message, response — so the next campaign starts smarter and the consent trail stays intact.
Operational principle: Compare aged-lead segments using consent quality, response, complaints, complete intake, reviewed files, and funded outcomes; do not assume timing or tone guarantees reactivation.
The step everyone skips: answering the callback
A reactivation response may arrive outside a staffed window. Measure callback and reply timing, coverage, complete intake, opt-out handling, and ownership so the response path is designed from evidence.
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 brokersThe bottom line
Use only records that pass consent and suppression review, apply a finite counsel-approved cadence, identify sender and purpose, provide the required exit, and retire records under approved rules. Do not assume prior acquisition cost makes a record valuable.
Do not treat an aged or B2B label as permission. Review the exact call, text, and email workflow, preserve consent and suppression evidence, and apply counsel-approved federal and state rules. FTC telemarketing guidance · FTC CAN-SPAM guide · FCC consent-revocation order
Continue through the lending content cluster
Connect this workflow to the applicable service and related decision guides. LumiTalk for business loan brokers · MCA response measurement · merchant intake checklist · loan-broker answering-service scorecard
Scope: General operational information only—not financial, legal, lending, underwriting, or compliance advice. Duties depend on the actual product, agreement, purpose, parties, channel, jurisdiction, and current law.
Quick answers
Frequently asked
What makes an aged lead eligible for review?
Require source provenance, exact consent and disclosure, timestamp, identified seller, covered channels and purpose, transfer history, and current suppression state before outreach.
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.
