SMS opt-in proof

Last updated: August 2, 2026

This page shows how consent to receive a text message is obtained and recorded in DLRPos. It supports our toll-free verification and is the artifact referenced by our SMS Terms & Conditions.

How consent is obtained

Consent is verbal, asked for as its own separate question, after the work is finished and a balance is ready to pay. It is never part of a repair order, an invoice, or any other agreement, and it is never a condition of any purchase or service. A customer who declines is offered the emailed link, a printed link, or payment at the counter.

The dealership employee asks, in these words or an approved equivalent:

"Would you like me to text you a secure link so you can pay from your phone? You'll get one text from us with the link. Message and data rates may apply, and you can reply STOP at any time to opt out. If you'd rather not, I can email it to you, print it, or take payment here — it makes no difference to your service."

How the platform enforces it

Only after the customer agrees does the employee record the consent. Until they do, DLRPos will not send anything — the control is required, and the send is blocked both in the interface and on the server, so it cannot be bypassed by calling the API directly.

The DLRPos Send Text panel with the consent attestation unticked and the Send Payment Text button greyed out and disabled. — **Before consent is recorded.** The attestation is unticked and *Send Payment Text* is disabled — no message can be sent. The panel also shows the opt-out disclosure that DLRPos appends to every outbound text automatically: "Reply STOP to opt out, HELP for help. Msg & data rates may apply." Employees cannot edit or remove it.

The same panel with the consent attestation ticked and the Send Payment Text button now enabled. — **After consent is recorded.** The attestation reads: "The customer agreed to receive a one-time payment link by text at this number, and was told they can reply STOP to opt out." Only now does *Send Payment Text* become available. The note beneath it — "Required. We record who confirmed this and when" — tells the employee that their attestation is logged against their name.

What is recorded

For every payment link sent by text, DLRPos stores:

Record	Purpose
Mobile number	The number the customer gave and agreed to be texted at
Consent flag	That the attestation was made
Attesting employee	Which user recorded the consent
Timestamp (UTC)	When it was recorded
Dealership	Which business obtained the consent
Transaction	The specific balance the message relates to

Any individual message can therefore be traced back to the consent that authorized it, and to the employee who recorded it. The attestation is bound to the number it was given for: editing the phone number clears it, so a consent can never carry over to a different number or customer.

Frequency and opt-out

One message per transaction — a payment request produces a single text. There are no recurring messages, campaigns, or reminders. A receipt is sent only if the customer asks for one after paying. Replying STOP (or STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT) stops all further messages immediately; HELP returns support contact details.

Full details are in our SMS Terms & Conditions and Privacy Policy. Mobile opt-in data and consent are never sold or shared with third parties.

Note on the screenshots

Both images are from the DLRPos application. The customer details shown ("Pat Sample", a 555 number, repair order 48219) are fictional test data — no real customer information appears on this page.