Plyrium follows CTIA / TCR / A2P 10DLC consent rules across every form where we collect a phone number. This page documents exactly how, where, and what each recipient sees before they ever receive a text.
This exact checkbox is required before any user can complete signup or booking. Submit buttons stay disabled until it's checked.
↑ This is a static preview. The live forms render this same block; submit buttons stay disabled until the box is checked.
Each element appears inline in the consent block above.
Three distinct surfaces, one per recipient class.
Recipients: contractors creating a Plyrium account. Use cases: two-factor authentication, account verification, billing notifications. Consent block appears at the bottom of the signup form; the "Create account" button is disabled until checked.
Recipients: homeowners booking a service appointment with a Plyrium contractor. Use cases: appointment reminders, "tech on the way" alerts, AI lead-response conversations, quote/invoice links. Consent block appears on the contact step (after picking a service, address, and time slot); the "Confirm booking" button is disabled until checked.
Reviewer note: this is one contractor's instance of the booking widget (PlumbDemoPro, a plumbing company in Tucson AZ - used as our public demo). Every contractor on Plyrium gets their own widget URL at /widget/{client_id}; all instances render the same consent checkbox + 8 disclosure elements. To navigate: click "Continue" → enter any U.S. address (e.g. "123 Main St, Tucson, AZ, 85710") → pick a slot → land on the contact step where the consent block sits above the "Confirm booking" button.
Recipients: homeowners who phone the contractor's business number directly. The AI receptionist (e.g. "Hannah" at PlumbDemoPro, "Jessica" at Plyrium) qualifies the call, captures the caller's phone number, and books an appointment verbally. Calls are recorded with two-party-consent disclosure where state law requires it (Cal. Penal Code § 632, etc. - see Privacy Policy Section 8). Per-call consent records are written server-side with the call ID, recipient phone, and timestamp; available for carrier audit on request.
Our full Privacy Policy is at /privacy. Section 3.1 (titled "SMS Opt-In Data and Consent") opens with the carrier-required clause:
"All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties. ... SMS opt-in data is never sold, shared with marketing affiliates, or transferred to any party other than the carriers and SMS infrastructure providers (Quo / OpenPhone) required to deliver the message itself."
Each consent capture is logged to our internal events table with the form URL, recipient phone, and timestamp. If a carrier requests proof of opt-in for a specific phone number, we can produce the matching record on demand.
Opt-out keywords (STOP, END, QUIT, UNSUBSCRIBE, CANCEL - case-insensitive) are honored immediately and propagated across all message templates from the same sender.
Questions on this program? privacy@plyrium.com