Approved Language Check

Feature Snapshot

Summary:
Approved Language Check is a TrustedForm Verify function that reviews the consent language captured in a lead’s certificate and confirms whether it matches a consent language variant that you have pre‑approved.

Key Benefits:

• Minimizes legal risk by identifying leads using an unapproved consent language
• Automates the verification process so manual review of every lead is not required
• Helps maintain a robust audit trail of consent for regulatory and internal compliance purposes

Typical Use Cases:

• Screening inbound leads automatically to verify that the consent language shown to consumers meets your legal requirements
• Integrating consent language verification with CRM or lead distribution systems via API calls for real‑time decision making
• Using the approved language result as one criterion in multi‑criteria lead validation to reject, flag, or process leads

How the Approved Language Check works

Approved Language Check operates as a component of TrustedForm Verify. When a lead is generated, TrustedForm Certify captures the exact consent language presented on the page. Your organization pre‑configures the Consent Language Manager with a list of approved consent language versions. When a Verify request is made via the Certificate API, TrustedForm automatically extracts the consent language from the certificate and compares it against your approved list. If an exact match or an approved variant (when using wildcards like “{{*}}”) is detected, the check returns a “success” indicator along with a “Language Approved” flag set to true. Otherwise, it flags the lead by returning false so that it can be rejected or further reviewed.

Step‑by‑Step Instructions

1. Configure the Consent Language Manager:
   • Log in to your TrustedForm account and navigate to the Consent Language Manager.
   • Add or update consent language entries with the text approved by your legal/compliance teams.
   • Use wildcards (e.g. “{{*}}”) where dynamic portions of the consent text may vary between leads.

2. Ensure Vendor Integration:
   • Instruct your lead vendors to implement TrustedForm Certify so that every lead includes a certificate URL capturing the consent language shown to the consumer.

3. Perform the Approved Language Check:
   • Perform a Verify request for every lead you process.
   • If a match or acceptable variation is detected, the API response includes a “Language Approved” flag set to true.

4. Interpret the API Response:
   • Reject or flag leads that fail verification
   • Review the consent language that was used and visit your consent language manager to approve/reject it with guidance from your legal/compliance team.

Expected Result:
When a lead is processed, if the consent language shown to the consumer has been pre-approve, the Approved Language Check passes, and the API response returns "Language Approved": true, enabling the system to automatically accept the lead.

Validation & Monitoring (optional)

• Test the Setup:
  • Submit a test lead using a consent language that you have pre‑approved in your Consent Language Manager.
  • Verify that the API response returns "Language Approved": true along with a “success” outcome.

• Where to Monitor?:
  • Monitor the Consent Language Manager section in your TrustedForm account to track newly detected or unreviewed consent language variations.

Best Practices

• Regularly review and update the Consent Language Manager to reflect any changes in legal requirements or common variations encountered in leads.
• Use wildcards strategically within approved language entries to accommodate minor variations without compromising the core consent message.
• Communicate clearly with lead vendors to standardize consent language used for exclusive leads, reducing variability and ensuring consistency.
• Combine the Approved Language Check with other TrustedForm Verify checks (such as font size and contrast ratio checks) for a comprehensive compliance strategy.

Troubleshooting

Frequently Asked Questions (FAQ)

Q: What happens if a new consent language appears that isn’t in my approved list?
A: The Approved Language Check will return “false” for that lead until you review and approve the new language variant in your Consent Language Manager.

Q: Can wildcards be used in approved consent language entries?
A: Yes. Wildcards, represented as “{{*}}”, allow you to cover variable sections of the consent language so that minor text differences do not cause the check to fail.

Q: How do I interpret the API response from the Approved Language Check?
A: Look for the “Language Approved” flag in the response. A true value indicates that at least one approved consent language (or acceptable variant) was detected; a false value suggests the lead should be flagged or rejected.

Q: How can I validate that the Approved Language Check is working as expected?
A: Test leads with known approved consent language and monitor the verification results on the TrustedForm dashboard and within your Consent Language Manager.

Glossary