SMS opt-in and consent (carrier compliance)

How the double opt-in works before PoolStamp sends any SMS to a customer.

The US carriers require an auditable opt-in for every SMS number PoolStamp texts. PoolStamp records consent before any receipt SMS goes out. This page explains the flow so you can answer customer questions and troubleshoot.

Step 1 — Operator marks the customer as SMS-eligible

When you invite a customer to receive SMS, PoolStamp does not start sending receipt texts yet. The customer stays unconfirmed until they complete the web opt-in form or reply YES to a confirmation text.

Web opt-in path

When you send the opt-in invitation email, the customer opens a signed opt-in URL and sees the consent language:

I agree to receive SMS service notifications from [Business Name] through PoolStamp... Reply STOP to unsubscribe and HELP for help.

They confirm their mobile number, check the consent box, and submit. PoolStamp records the consent text version, source URL, timestamp, and request metadata, then marks the customer confirmed.

Confirmation-text path

If you send a confirmation text instead, PoolStamp sends a one-time message:

Reply YES to confirm you want visit receipts from [Business Name]. Reply STOP to opt out.

The customer texts back YES. Only then is their status flipped to Opted-in and future receipt SMSes flow.

STOP / HELP handling

Any reply of STOP, STOPALL, UNSUBSCRIBE, END, QUIT, or CANCEL immediately opts the customer out and PoolStamp confirms with the carrier-mandated "You have been unsubscribed" message. HELP replies with your business support info. This is handled by PoolStamp — no operator action required.

What breaks it

Auditability

Consent and opt-out events are logged with timestamps, consent text version, source, and message metadata when available. If there is a compliance dispute, contact support for the audit trail.


Receipts & notificationsAll categories
SMS opt-in and consent (carrier compliance) · PoolStamp