Skip to main content

A2P 10DLC reviewer packet

Account notification SMS consent

This page documents the opt-in and message flow for Porchlight's ACCOUNT_NOTIFICATION campaign. These are operational alerts that a business receives about activity inside its own Porchlight account. The people who opt in are the business's own staff — the organization owner or admin and any internal teammates they add — using their own mobile numbers. There are no consumer, lead, or buyer recipients on this campaign. Opt-in happens inside the authenticated Porchlight web app; because that screen is login-gated, this public page reproduces it exactly so carrier reviewers can see the consent language, the checkbox, and the verification step without an account.

Opt-in summary: who, where, and how consent is collected

Who opts in

The business's own staff. A signed-in organization owner or admin enters the mobile number of an internal recipient (themselves or a teammate at the same business) who should receive operational account alerts. There are no consumer, lead, or buyer recipients on this campaign — every recipient is a first-party user of the business's own Porchlight account.

Where opt-in happens

Inside the authenticated Porchlight web app, on the Settings > Notifications screen (https://app.getporchlight.ai/settings/notifications). Because that screen is login-gated, this public page reproduces it exactly so carrier reviewers can see the consent language and flow without an account.

How consent is collected

Express written consent is captured by a dedicated SMS consent checkbox that is unchecked by default and displays the full disclosure shown below. Checking that box is the opt-in, and the box must be checked before Porchlight will send anything at all. The verification-code step that follows is a separate security check that confirms the staff member controls the phone number — it is not the consent itself. The one-time verification code is the only message sent before verification; no account-notification alerts are sent until the number is verified.

Campaign summary

Use case

ACCOUNT_NOTIFICATION. Porchlight sends operational alerts to an opted-in internal account user or team recipient.

Recipients

Signed-in organization owners, admins, or internal recipients entered by those users in notification settings.

Frequency

Message frequency varies based on account activity and enabled notification settings.

Website opt-in flow

Opt-in happens in the authenticated notification settings screen. The reviewer-accessible evidence for that login-gated screen is this public page: https://www.getporchlight.ai/sms-account-notifications.

  1. Who: A signed-in organization owner or admin of the business opens Settings > Notifications inside the Porchlight web app. Recipients are the business's own staff — never consumers, leads, or buyers.
  2. Where: They enter the internal recipient's mobile number on the form at https://app.getporchlight.ai/settings/notifications. The SMS channel stays disabled until the steps below are complete.
  3. Consent: They check a dedicated SMS consent checkbox that is unchecked by default and contains the full disclosure shown below. Checking this box is the express opt-in for this campaign.
  4. Verify phone ownership: They click Send code; Porchlight texts a one-time code to that number. Entering the code confirms the staff member controls the phone. This is a security step, not the consent.
  5. Activate: Only after the consent box is checked and the code is verified can the SMS channel be enabled. The recipient can reply STOP at any time to opt out, or HELP for help.

Authenticated settings URL: https://app.getporchlight.ai/settings/notifications

Hosted screenshot of the consent form

This interactive form reproduces the login-gated notification settings form, including its gating. The SMS consent checkbox is a separate control that starts unchecked and is the express opt-in. Send code stays disabled until a phone number is entered and the consent box is checked, so the one-time code cannot be requested before consent. The verification-code field only confirms the staff member controls the phone number; it is not the consent.

Send code stays disabled until a phone number is entered and the SMS consent box is checked — the one-time code cannot be sent before consent. The SMS channel toggle then remains disabled until the verification code is confirmed.

Exact opt-in disclosure

I agree to receive automated account notification text messages from Porchlight about lead needs follow-up alerts and booked consult or site-visit alerts for this organization. Message frequency varies based on account activity. Msg & data rates may apply. Reply STOP to opt out, HELP for help. See the Terms and Privacy Policy.

Verification message

Salisbury Saunas: your Porchlight lead alert verification code is 123456. It expires in 15 minutes. Msg & data rates may apply. Reply STOP to opt out, HELP for help.

Keyword handling

Initial opt-in
No keyword opt-in. Initial enrollment happens through the authenticated website form and verification-code step.
Opt out
STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT
Re-subscribe
START, UNSTOP, YES. These only restore a previously verified internal alert recipient after opt-out.
Help
HELP

Representative sample messages

Salisbury Saunas: your Porchlight lead alert verification code is 123456. It expires in 15 minutes. Msg & data rates may apply. Reply STOP to opt out, HELP for help.

Porchlight alert for [business name]: Lead needs follow-up: [lead name] shared contact info and has not booked yet. [project summary]. Open: https://app.getporchlight.ai/leads/[lead-id] Reply STOP to opt out, HELP for help.

Porchlight alert for [business name]: Consult booked: [lead name] booked a consult for [date and time]. [project summary]. Open: https://app.getporchlight.ai/leads/[lead-id] Reply STOP to opt out, HELP for help.