What should an MVA claimant consent record contain?

An MVA claimant record should connect the person, submitted mobile number, consent event, source page, and case answers in one traceable delivery. Velocity Axis captures every claimant with prior express written consent under the TCPA, attaches a TrustedForm certificate and Jornaya LeadiD token, and requires a six-digit OTP before delivery.

What question should a consent record answer?

The record should let a firm reconstruct how a specific claimant entered the campaign. It needs to identify when the submission occurred, where consent was captured, what language appeared, and which form event produced the delivered record.

That purpose is narrower than a general statement that consent exists. A buyer reviewing one claimant should be able to connect the source evidence with the identity, contact information, and accident record delivered to intake.

Velocity Axis uses four record layers:

The layers do different jobs. Treating any one as a substitute for the others leaves part of the event unrecorded.

What does the TrustedForm certificate contain?

Every delivered claimant record carries a TrustedForm certificate capturing opt-in and the origin event. The Consent and the TCPA Record page identifies four recorded fields:

Together, those fields place the consent event in context. The certificate can show the page, words, time, and session tied to the form instead of leaving the firm with a source label alone.

This matters when intake records move between systems. A name and phone number may appear in a CRM, an email, and a dashboard entry. The certificate travels with the record so the origin event is attached to the same claimant rather than stored as an unsupported campaign-level assertion.

What does the Jornaya LeadiD token add?

The Jornaya LeadiD token identifies the claimant’s form submission. It accompanies the TrustedForm certificate on every delivery and gives the firm another submission-level artifact tied to that event.

The token does not replace the certificate fields. It identifies the submission, while the TrustedForm certificate captures the page, consent language, timestamp, and session replay. Both remain part of the record for Signed Retainer Delivery, Live Transfer, and Claimant Delivery.

Velocity Axis retains both artifacts for five years. The retention period applies across all three formats even though qualification and handoff differ.

What does OTP verify?

Every submitted mobile number must pass a six-digit OTP before delivery. The claimant receives the passcode and completes the check at submission.

OTP establishes control of the submitted mobile number at that moment. It does not independently establish three later or separate facts:

That boundary prevents a common category error. OTP is contact verification at submission. It is not independent case verification and does not promise later reachability.

Signed Retainer Delivery and Live Transfer add live agent confirmation of the number. Claimant Delivery does not include a live qualification call, so the record carries the OTP-verified number and claimant-stated case answers.

How do consent and phone verification fit together?

Consent capture and phone verification are separate events. The consent record documents how the claimant entered the campaign and the language presented. OTP documents completion of the passcode check on the submitted number.

Both attach to the same core record. Under the Exhibit A Field Reference, that record includes:

The delivery format then adds its own evidence. Signed Retainer Delivery includes live-confirmed answers and the firm’s executed representation agreement. Live Transfer includes live confirmation and the routed call. Claimant Delivery carries the submitted answers without a live qualification call.

Does the consent record prove the case facts?

No. The consent record documents origin and opt-in. OTP checks the submitted mobile. Neither verifies injury, treatment, fault, representation status, or insurance coverage.

Under Signed Retainer Delivery and Live Transfer, an agent asks the claimant to confirm the case answers against the order’s criteria. Those answers remain the claimant’s own account. Under Claimant Delivery, the delivered fields are claimant-stated without live confirmation.

Independent verification has a narrower place. When Policy Limit Verification is selected on a Signed Retainer Delivery order, the intake center independently checks the applicable BI or UM/UIM carrier and policy limits and sends supporting insurance records to the firm. That added service does not convert every other case answer into an independently verified fact.

How should a firm audit one delivered record?

Start with the individual claimant rather than a campaign summary. Match the name and contact fields across the receiving system and dashboard, then open the origin artifacts tied to that entry.

The review sequence is mechanical:

1. Confirm the record has its dashboard delivery timestamp.

2. Match the TrustedForm certificate to the same claimant entry.

3. Review the submission time, funnel page, consent language, and session replay.

4. Confirm the Jornaya LeadiD token is present.

5. Confirm the mobile passed six-digit OTP.

6. Separate claimant-stated, live-confirmed, and independently verified fields.

The last step matters because a complete consent record can coexist with a disputed case answer. Origin evidence and eligibility evidence answer different questions. If an Exhibit A criterion failed at delivery, the firm uses the replacement process rather than treating the consent artifact as proof of the case fact.

What happens when an opt-out arrives?

If Velocity Axis receives an opt-out, it forwards the opt-out to the firm within one business day. The firm controls its own communications after delivery.

That division of responsibility belongs in the operating process. The acquisition record establishes how the claimant entered the campaign; later firm communications occur under the firm’s own controls. Forwarding the opt-out gives the firm the information needed to update those controls.

What should a buyer ask a vendor to deliver?

Ask for claimant-level artifacts, their retention period, and the exact fields inside each artifact. A statement that records are compliant is less useful than a sample showing the timestamp, source page, consent language, replay, submission token, and OTP status.

The buyer should also ask whether the same record arrives in the CRM and a separate dashboard copy. A second copy with the delivery timestamp helps reconcile missing or changed fields and establishes when any replacement-request window began.

Finally, ask which facts are claimant-stated, which are confirmed live, and which are independently verified. Those labels keep consent, contact, qualification, and coverage evidence from being blurred into one unsupported claim.

What Velocity Axis does

Velocity Axis attaches a TrustedForm certificate and Jornaya LeadiD token to every delivered claimant record and retains both for five years. Every submitted number completes six-digit OTP before delivery. The exact artifacts, fields, retention rule, and opt-out handling are published in Consent and the TCPA Record and OTP Verification.