Growth & operations12 minute tutorial

Configure consent-based email and text messaging

Activate verified channels safely, record opt-ins, understand automated nurture, and monitor delivery and suppression.

Provider gated

The consent, queue, suppression, and delivery-status controls require provider, sender, worker, school-owner, and end-to-end activation gates.

Before you start

  • Owner access for activation; managers can manage consent and queue approved announcements.
  • A complete school physical mailing address and monitored reply-to email.
  • Platform confirmation that SES/Inngest or Twilio and the school sender are approved.
  • Attorney-reviewed consent language and nurture content for the school’s use.
1

Confirm platform and sender readiness

Open Settings and find Consent-based messaging. Each channel explains its blocker. Email requires the verified SES sender, signed delivery events, unsubscribe signing, background jobs, and the school mailing address. Texting also requires a registered sender assigned to this school.

Provider review can take time. A disabled checkbox is a release gate, not a school error; keep working leads manually until it becomes ready.

Open messaging settings
2

Set the school rules and activate deliberately

The owner reviews the sender name and reply-to address, chooses local quiet-hour start and end, and sets the maximum automated messages per recipient and channel over seven days.

After accepting the compliance terms, enable only the channel you have tested. The global platform kill switch still overrides the school setting.

Watch out: Do not enable messaging to “try it” with customer data. Use a named internal recipient who explicitly agreed to the test.
3

Understand public-form consent

The intro form requires permission for the school to respond directly, then offers separate optional checkboxes for recurring email and automated text messages. A visitor can submit without accepting either automation checkbox.

The exact disclosure, channel, normalized destination, source, time, and evidence hash are retained. An email opt-in never becomes an SMS opt-in, or vice versa.

4

Record consent received another way

Open a lead or member and find Automation consent or Communication consent. An owner or manager may record an opt-in only after entering the exact disclosure used and attesting that the person agreed.

Choose Record opt-out immediately when asked. Never infer consent from a phone number, email, waiver, purchase, or request for one direct reply.

Open leads
5

Let the nurture queue enforce the rules

Every due email or SMS follow-up is checked for school activation, matching opt-in, quiet hours, seven-day cap, provider readiness, and mailing address where required. An ineligible task remains visible for staff and is never silently treated as sent.

Temporary provider failures are retried up to three claims. A successful provider acceptance completes the matching follow-up and adds the contact to the lead timeline.

6

Queue an announcement safely

Posting an announcement always publishes it to the invited web portal. Email and Text queue buttons appear only for activated channels.

The fan-out uses only current member opt-ins whose stored destination still matches the member record. Repeated clicks are idempotent and do not create a duplicate send.

Open Announcements
7

Monitor opt-outs and delivery

One-click email unsubscribe, SMS STOP and START, SES bounce/complaint events, and Twilio status callbacks update the suppression and message records automatically.

If anything looks wrong, the owner disables the school channel. Platform operators can turn off the global channel while leaving queued evidence intact.

Troubleshooting

If something looks wrong

Why is the channel checkbox disabled?

One or more platform gates are incomplete: provider approval, registered sender, background jobs, unsubscribe signing, or the school mailing address. The explanation under the channel identifies the category.

Why was an opted-in person not sent a message?

Check whether the channel is still enabled, the current contact detail matches the consent destination, local quiet hours are active, the seven-day cap was reached, or the provider recorded a bounce, complaint, STOP, or unsubscribe.

Can staff re-enable someone after STOP or unsubscribe?

Only after the person gives a new explicit opt-in using the recorded disclosure. Do not clear suppressions merely to retry a campaign.

Keep going

Reviewed July 27, 2026.