Choose guest text messages for one wedding

Open Text message preferences from your private invitation. The same page is available inside the private invitation opened through the wedding website. Your invitation and saved replies work without text messages.

The page shows the last four digits of the household phone saved by your host. If that number is wrong, ask the host to review it. You cannot enter another number to bypass the saved contact. This workflow currently supports United States numbers only.

Review the choice before receiving a code

Choose your current IANA timezone, such as America/Los_Angeles, and a delivery window within 09:00–20:00 local time. You can narrow that window. There is no urgent-message override. Choose Review text-message enrollment.

Read the wedding name, sender brand, masked phone, delivery hours and notice. It covers operational invitations, RSVP reminders and wedding announcements for this wedding. It does not authorize marketing, other weddings or vendor coordination texts. Message frequency varies, and carrier message and data rates may apply. The review links to privacy and terms information.

Tick the confirmation checkbox, then choose Confirm choice and show phone code. Only then does the page show the sender number and a message in the form WBJOIN XXXX-XXXX-XXXX-XXXX.

Using the saved phone, send that exact message to the displayed number. Open my text app with this code prepares the message in your device’s texting app; you still choose whether to send it. The application sends no automatic verification text.

Return to the page and choose Check current enrollment. Permission becomes active only after a verified provider callback reports that exact code from the expected phone to the expected sender. A code is not evidence of delivery until the callback passes those checks.

A short-lived, specific confirmation

The review and code last at most 15 minutes, bounded by the current invitation or device session. If the phone, invitation access, sender scope, notice or carrier stop state changes, start a fresh review. A website-session challenge cannot be confirmed after that device session is revoked, expires, or loses its current website access. Copying a code into another household’s invitation does not transfer permission.

A lost review or confirmation response can be retried with the same request to recover the saved result. The server retains a code hash and immutable notice evidence, not the readable code. Successful phone confirmation uses the code once. A later copy cannot restore a preference that was withdrawn afterward.

For example, Rowan reviews texts for Cedar and River’s wedding and requests a code. Rowan then stops the pending enrollment before sending the code. The late code cannot activate it. Rowan must review a new choice and confirm a new code.

Stop this wedding’s texts

Choose Stop this wedding’s text messages to withdraw permission. This also works for an issued enrollment that has not yet been verified. Your invitation and RSVP remain available. Messages already accepted by a provider may still arrive; the application cannot retract them.

Earlier queued messages remain stopped. An uncertain earlier provider attempt is kept for receipt recovery and is not blindly retried. A later enrollment never revives that earlier queue: the host must review a new guest message or reminder schedule.

Withdrawal remains available through a current invitation even when the old sender is disabled. The preference history retains recorded code requests, successful confirmations and withdrawals with their times. It does not invent consent for previously saved phone numbers.

Carrier STOP and START

Sending STOP applies to the sender’s phone scope and may affect messages for other weddings using that sender. This private page withdraws only the selected wedding’s permission. Carrier suppression and wedding permission are tracked separately.

If the carrier has stopped the sender, follow its START instructions from your previous text conversation. START alone does not enroll this wedding, clear its local withdrawal or resume queued messages. Return here for a fresh notice review and phone code. A new STOP racing with an older confirmation takes precedence over that older review.

An email opt-in, guest email resubscription, saved phone number or day-of vendor consent does not count as guest SMS permission. Host contact correction cannot create consent. A contact change makes older approval evidence stale and requires a new recipient review and phone confirmation.

What this proof establishes

The invitation is possession-based household access. The signed inbound code demonstrates control of the saved phone at that time. This is not identity verification, and it does not prove that a particular named person owns the household invitation. Keep invitation links and codes private.

No phone number or household list is exposed on the public wedding website. Website entry uses its existing secure private session; the browser is not given the session secret in page data. Public preference pages are excluded from search indexing.

Sending setup and activation

This workflow has been exercised with isolated PostgreSQL and synthetic signed provider callbacks. Live sending and phone registration remain part of coordinated activation: an explicitly workspace-owned sender, trusted callback origin and signing credentials, STOP/START/HELP behavior, sender registration, usage caps, delivery recovery and policy review must be rehearsed together. See SMS sender and delivery setup.

The notice follows the distinction between sender-specific consent and opt-out controls described in Twilio’s Messaging Policy and Advanced Opt-Out documentation. These references do not constitute provider approval or a legal compliance guarantee. Sender registration and the final production wording remain activation review items.