SMS consent & document-request review
Every public form that collects a phone number, the exact consent language shown, where the consent record is stored, and the items still open.
Test-safe preview. Nothing on this page submits a form, writes a record, or sends a call or text message. No Twilio A2P registration is altered by anything here.
The consent language shown
Version 2026-10-17.2
I agree to receive customer-care and application-related calls and text messages from Clutch Advance only at the phone number I provide, including messages sent using automated technology. Messages may include responses to my inquiry, application-status updates, secure document-upload links, appointment reminders, and follow-up about a request I initiated. Consent is not a condition of approval, funding, or purchase. Message and data rates may apply. Message frequency varies. Reply STOP to opt out and HELP for help. See the Privacy Policy and Terms.
The sentence above is stored verbatim on the record when consent is given, so the audit trail always matches what the applicant read.
Every state of the checkbox
Unchecked by default · never required · links open in the site
Default — unchecked, submit still allowed
Optional — text message consent
Reply STOP to any text to opt out, or reply HELP for help. Consent is optional — you can submit without checking the box, and you can withdraw it at any time.
Checked — consent captured
Optional — text message consent
Reply STOP to any text to opt out, or reply HELP for help. Consent is optional — you can submit without checking the box, and you can withdraw it at any time.
Error styling (unused in normal flow — consent is optional)
Optional — text message consent
Reply STOP to any text to opt out, or reply HELP for help. Consent is optional — you can submit without checking the box, and you can withdraw it at any time.
Example validation styling.
Reply STOP to any text to opt out, or reply HELP for help. Consent is optional — you can submit without checking the box, and you can withdraw it at any time.
Forms updated
7 public forms
| Form | Where the checkbox sits | Recorded source | Stored on |
|---|---|---|---|
| Contact / inquiry form/contact | Consent block directly below the form, above the submit button | contact-form | Interaction (type: contact_form) |
| Apply entry gate (visitors not signed in)/apply | Directly below the phone field, above “Create free account & continue” | apply-entry | Interaction (type: application_start) |
| Loan application wizard (signed in)/apply | “How can we reach you?” step, directly below the phone field | apply-loan-application | Interaction (type: application_start) + LoanApplication |
| Callback request modalSite-wide (header / hero “Call us”) | Directly below the phone number field | callback-modal | Interaction (type: callback_request) |
| Mobile “Did we miss you?” callback barSite-wide on mobile | Directly below the name / phone row | callback-mobile-bar | Interaction (type: callback_request) |
| MCA calculator results gate/mca-calculator | Directly below the phone field, above “Unlock results” | mca-calculator-gate | Interaction (type: calculator_lead) |
| Full MCA application — authorizations step/mca-apply | Last item in the authorizations list, kept separate from the credit, bank-verification and accuracy certifications | mca-application | MerchantCashAdvanceApplication |
Where consent is stored
Same record as the lead or application — no separate or exposed store
- sms_call_consent
- true only if the box was actually checked; recorded on every submission
- consent_timestamp
- UTC time the consent was captured (written only when consent is given)
- consent_text
- the exact consent sentence displayed at that moment
- consent_version
- version tag of that wording, so old consents trace to the language shown
- consent_source
- the form that captured it (see the source column above)
- consent_ip
- submitting IP address, from the request headers
- phone
- the number consented to — already stored on the same record
- page_url
- full page URL, where the record type supports it
Records carrying this audit trail: Interaction, LoanApplication, BrokerApplication and MerchantCashAdvanceApplication. All four keep the admin-only access rules they already had. Bank account numbers, Tax IDs and Social Security numbers are never included in notification emails.
Confirmation states
Reviewed so none implies approval or funding
Contact form
“Request received” — a funding advisor will contact you within one business day.
Loan application
“Application submitted”, plus: “Submitting an application is not an approval, a decision, or a commitment to fund.”
MCA application
“Application submitted”, plus: “Submitting an application is not an approval, a decision, or a commitment to fund.”
Callback modal / mobile bar
“A funding advisor will call you…” / “We’ll call you back shortly.”
Legal pages linked from the checkbox
Linked beside the checkbox copy
- Privacy Policy/privacy-policy
- Terms of Service/info/terms-of-service
- Disclosures/info/disclosures
The Privacy Policy and the Disclosures now describe the message types, the optional nature of consent, and STOP / HELP handling. The Terms of Service carries a matching calls-and-texts section, and the footer shows the opt-out line on every public page.
Open items
Requires attorney review or Twilio console configuration
Attorney review of final consent wording
The language follows the wording you supplied, tightened to name message types and remove the vague “partners” reference. A qualified attorney should confirm it satisfies TCPA, state mini-TCPA rules, and the commercial-financing disclosure requirements in the states you fund in.
Consent is now optional — confirm the sales workflow
Previously every form refused to submit without the box checked. As requested, it is now optional: a lead can arrive with a phone number and no consent (sms_call_consent: false). Those records must not be called or texted until consent is captured another way. This matters most for the two callback widgets — “Call me” and the mobile “Did we miss you?” bar — because a callback request without consent cannot be actioned by phone. Decide how the team should handle them (email-only follow-up, or a re-consent step), and make sure the dialer and any outbound texting tool filter on sms_call_consent before dialing.
Twilio A2P campaign registration
The campaign’s opt-in description, message samples, and help/opt-out language must be updated to match this wording in the Twilio console. Nothing in the app changes A2P registration — this is a console task.
Twilio opt-out and help responses
Confirm the Messaging Service has Advanced Opt-Out enabled so STOP, HELP, and their variants are handled automatically, and that the HELP auto-reply names Clutch Advance and a support number.
Message samples and frequency
The consent says message frequency varies. Before launching, list the actual message types you will send (application status, secure upload links, appointment reminders) as campaign samples so the registered campaign matches what is described.
Secure document-upload link delivery
The consent authorizes texted secure document-upload links. Confirm the upload links are time-limited or tokenized, and that a link is only ever texted to a number that granted consent.
Do-not-call list enforcement
Existing opt-outs live in the DncEntry list. Confirm the dialer and any outbound texting check that list, and that a STOP reply is reflected there.
Marketing consent not added
No separate promotional-consent checkbox was added, because the site does not currently run promotional SMS. If you start sending marketing texts, they need their own opt-in — the customer-care consent captured here does not cover them.
This review documents what the site now does. It is not a legal opinion and does not claim compliance with any particular statute or carrier requirement.