PartyGram SMS Consent

Last updated: September 1, 2026

PartyGram is an event invitation and planning platform. Hosts create event pages and invite friends, family members, and other personal contacts. Guests can view event details and RSVP through PartyGram.

This page provides a public, non-interactive reproduction of the optional SMS consent and phone-verification flow shown to a guest after an RSVP is saved. It also provides examples of the event-related messages PartyGram sends.

Open the interactive RSVP and messaging opt-in demo

The following example reproduces the SMS choice presented after an eligible guest saves a Going or Maybe RSVP. No SMS option is preselected. The RSVP is already complete, and selecting “Not now” does not change it.

PartyGram RSVP example

Stay in the loop

Stay in the loop with reminders and important updates for Jordan’s Launch Party.

Public example only: These controls do not submit information or enroll this example number in messaging. In a live event, the phone field is disabled and only shows the number PartyGram will verify. The interactive demo allows reviewers to enter a sample number.
Shown when the exact phone number is not yet verified

Verify your number

We sent a 4-digit code to (555) 123-4567.

1234
Didn't get it? Resend code
Use a different number
The code expires after 10 minutes. A guest receives up to three attempts per issued code and may request one resend. Successful verification confirms the exact number and completes the consent requested by clicking “Get Text Updates”; there is no second consent screen.

If PartyGram already has trusted verification and consent for the exact phone number, text updates remain enabled when that number is invited to another event, including by another host.

How the SMS flow works

  1. Initial invitation: An event host may provide the mobile number of a known friend, family member, or other personal contact so PartyGram can deliver a permitted one-time transactional invitation to that host’s event.
  2. RSVP saved first: The guest submits a Going, Maybe, or Can’t Go RSVP before PartyGram evaluates the optional SMS step. A Can’t Go response proceeds directly to confirmation without showing this opt-in flow.
  3. Optional consent: Eligible Going and Maybe guests may click “Get Text Updates.” Selecting “Not now” leaves the saved RSVP and existing SMS state unchanged.
  4. Exact-number verification: An unverified number must pass the four-digit SMS code step. PartyGram records verification and the pending affirmative consent together only after the correct code is entered.
  5. Verified-number reuse: A guest whose exact number is already verified and opted in remains eligible for event texts when another PartyGram host invites that number.
  6. Cancellation and help: A recipient can text STOP to cancel PartyGram SMS globally or HELP for help. The invitation-specific keyword X mutes future invitations from the host identified by the most recent invitation; it does not replace STOP.

SMS message examples

These examples use the same wording as PartyGram’s current centralized SMS templates. Names, event titles, verification codes, and event URLs are replaced with the applicable values at send time.

Initial invitation or invitation resend

Jordan invited you to Launch Party RSVP at https://partygram.net/e/example Reply X to stop invites from this host

Phone verification

1234 is your PartyGram verification code Didn't request one? Ignore this text

RSVP reminder

Please RSVP for Launch Party when you have a moment: https://partygram.net/e/example

Final RSVP reminder

A final reminder to RSVP for Launch Party: https://partygram.net/e/example

Day-of reminder

Launch Party is today. Review the event details here: https://partygram.net/e/example

Host invitation mute confirmation

You won't receive more PartyGram invitations from Jordan

Hosts may also send event-specific announcements. Announcement wording is written by the event host and is limited to transactional event information.

PartyGram keeps RSVP status separate from permission to receive ongoing event texts. Declining text updates or later opting out does not remove or change the guest’s RSVP.

  • Verified phone: Ongoing consent is tied to the exact verified phone number and applies across PartyGram event hosts. A number supplied only by an event host is not treated as verified or consented unless that exact number already has affirmative PartyGram consent.
  • Consent evidence: PartyGram records the current consent state, when consent was granted or withdrawn, how it was obtained, the consent disclosure shown, and the related event context when applicable.
  • Eligibility checked before every send: Immediately before PartyGram submits an ongoing event message to its messaging provider, it rechecks the verified number, current consent, global suppression, host and event mute preferences, and the event, guest, and message state. This check occurs at delivery time even when a message was scheduled earlier.
  • Provider opt-out synchronization: PartyGram processes signed provider webhook events for STOP and supported re-enrollment and help keywords. A number-wide STOP overrides prior consent and host or event preferences.
  • Suppression before the provider request: If a recipient is no longer eligible, including after STOP, PartyGram skips the delivery before making another outbound messaging request.
  • Consent and delivery auditability: PartyGram records consent changes and provider delivery and inbound events so it can reconcile message status and establish when and how a recipient opted in or out.

The permitted one-time initial invitation follows separate transactional rules and does not establish permission for ongoing event messages.

  1. Guest clicks “Get Text Updates”The guest makes an affirmative request for PartyGram event texts from hosts who invite that number.
  2. Exact phone number verifiedThe verification code confirms control of that number.
  3. Consent recordedPartyGram records the identity, number, time, method, and disclosure.
  4. Eligibility rechecked before each sendOnly a currently eligible recipient is submitted to the messaging provider.
  5. STOP receivedThe number is suppressed before the next outbound provider request.

Messaging disclosures

  • PartyGram does not use this messaging campaign for promotional or advertising SMS.
  • Messages concern event invitations, reminders, announcements, and important event updates.
  • Message frequency varies based on events and host activity.
  • Message and data rates may apply.
  • Text STOP to cancel at any time.
  • Text HELP for help.
  • SMS consent is optional and is not required to RSVP or use PartyGram.

Questions

For help with PartyGram SMS, reply HELP to a PartyGram message or contact:

PartyGram LLC
Email: support@partygram.net