Review and recover guest texts

Guest texts start with a private draft and a separate recipient enrollment. A saved phone number, email subscription or earlier timeline text is not SMS consent. The household opens its current private invitation or website session, reviews the sender and delivery hours, then sends the displayed enrollment code from that phone. See Guest text preferences for the enrollment steps.

In Guest communications, choose SMS, a configured workspace sender and exact households. Invitations, announcements and event-deadline reminders use the same review process. A reminder includes only guests invited to that event and stops when those guests have answered or the household sends a verified reply.

Review shows every complete rendered text: the sender, guest names, event details, full private invitation URL, reply code and STOP instruction. It also shows the GSM-7 or Unicode encoding, segment count, configured price per segment and maximum cost. Long links, punctuation and emoji can increase the segment count. The recipient's local delivery window can postpone a text; there is no urgent-hours override. Correct warnings before asking the owning workspace administrator to approve the exact review and spending limit.

Changing the recipient, invitation, event, consent or sender holds the old approval. A new price requires another review before approval; an already approved text keeps its frozen quote. Editing a draft does not send a message. Pausing a schedule stops new admission. Resuming does not create a new version of an uncertain attempt.

Sent means the provider accepted the text. Delivered requires a verified provider receipt. Uncertain means the application cannot prove whether the provider accepted the one allowed attempt. The worker never automatically repeats that provider request, even if it stopped immediately after saving its attempt marker. If an original provider message ID is known, Fetch original provider receipt checks that message only. Without an ID, await a signed callback or reconcile with provider support; a fresh copy is not a recovery shortcut. A proven rejection or cancellation before a provider call releases the original spending reservation. An unknown result keeps it reserved.

Replies with the code from the original message can reach that exact current household's private Guest Hub conversation. A reply without a code is routed only when there is one current household context for the phone and sender. A phone shared by two enrolled households is not assigned to whichever message happened most recently. Ambiguous replies remain in an encrypted workspace queue visible only to administrators. Confirm identity through a trusted conversation and ask the guest to include the original reply code. Replies never become a public website or community post, and SMS attachments are not supported.

STOP blocks new texts from that sender to the phone. START does not restore consent or resume old approvals: the recipient must complete a fresh review and phone challenge. SMS has no automatic email fallback. Existing email replies, attachments and email preferences keep their separate channel rules.

This workflow is US-only and depends on a configured, workspace-assigned sender, reviewed segment pricing, an approved usage cap and the final messaging activation checks. Provider registration, real carrier delivery, live STOP handling and billing have not been certified by the local simulator. Local preview receipts do not represent real texts.