The short answer
Consent that holds up names the specific company that will call, says calls and texts may be made using automated technology, is agreed to by an affirmative act that is not a pre-ticked box, and is captured with a record of what the merchant saw. The element most often missing is the first: a disclosure that says "our partners" without naming who names nobody, and consent to an unnamed party is the weakest kind there is.
Consent is not a checkbox, it is a record. The question a court asks is not whether the merchant agreed to something but whether you can show what they saw, when, and that they took a deliberate action on it. Almost every consent problem is a record problem wearing a wording costume.
| Element | Weak version | What holds |
|---|---|---|
| Who may call | "Us and our marketing partners" | The calling company named, or a linked list |
| What may happen | Silent on automation | Calls and texts, including automated technology |
| How it was given | Pre-ticked box, or consent bundled into terms | An unticked box or a submit action tied to visible text |
| What was captured | A flag in a database | Timestamp, IP, page URL, and the disclosure text as shown |
Why the named-party element is the one that matters
A merchant who agreed to hear from "trusted funding partners" has agreed to hear from nobody in particular. When the call comes from a name they have never seen, the consent has to carry the weight of a party the merchant could not have identified — and that is the argument plaintiff-side firms build cases on.
This is also the practical difference between an exclusive lead and an aggregated one. A lead generated on a page that names one buyer can name that buyer in the disclosure. A lead sold to five brokers cannot, which is why aggregated consent language is always vague — the vagueness is structural, not sloppy. Exclusivity makes naming the buyer possible, not automatic: ours does not, and it is quoted below.
What the disclosure on our exclusive leads does
- Is shown on the application at the point of submission.
- Authorizes the funding brand, “us” in the text, to contact the merchant about business-financing options.
- Does not name the broker who receives the lead, and does not mention calls, texts or automated technology.
- Is agreed to by submitting the application, which is an affirmative act.
- Is captured on a third-party TrustedForm certificate with the timestamp, IP address, page URL and browser, and the disclosure exactly as the merchant saw it.
The last one is the part vendors skip. Disclosure text changes; the record has to hold the version the merchant actually saw, not the version on the page today. If a vendor cannot produce the historic text, they cannot prove what was agreed.
Set against the table above, our disclosure is agreed to by an affirmative act and captured with a record of what the merchant saw. It names the funding brand rather than the broker who calls, and it says “contact” without mentioning calls, texts or automated technology. What that means for the way your floor dials is a question for your own counsel, with a certificate in front of them rather than this page.
What consent does not do
It does not survive a revocation you did not record. A merchant who says "stop calling me" has revoked, in any reasonable form, on any channel — and continuing after that is the fact pattern that turns a nuisance into a claim. Suppression has to be immediate and it has to be across every channel, not just the one they said it on.