How a host confirms permission

This page is for anyone reviewing the SimpleInvite text message program. It shows where consent is collected, what it says, and what happens next.

I know these people and have their permission to get a text invite from me via SimpleInvite. Message and data rates may apply; they can reply STOP any time.

Its default
Unchecked by default. The host must tick it.
Where it appears
On the Send screen of the create flow, directly above the Send now button, and again on the send step of Invite more when texting is turned on for that host.
What it covers
It covers text messages only. It is not combined with an email consent, a terms acceptance, or a marketing sign-up, and there is no other checkbox beside it.
What it gates
Send now stays disabled until it is ticked. A host who does not tick it can still create the event and send by email or share the link themselves — texting is what is withheld, not the product.

The flow, end to end

  1. A host signs up

    A host creates an account with their own email address and accepts the terms of service and the SMS terms.

  2. The host makes an event

    Title, date and time, place, and optionally a photo and a note.

  3. The host adds the people they are inviting

    By typing a name and a mobile number, by pasting a list, by picking from their phone's contacts where the browser allows it, or by pulling in people from a past event. Every one of these is the host entering someone they already know.

  4. The host confirms permission

    On the Send screen, an unchecked box carries the wording above. Send now does nothing until the host ticks it. Ticking it records who ticked it, when, and for which event.

  5. The first message goes out

    The first text a guest receives names the host, says what the event is, gives one link on our own nvite.app domain, says how to reply, and carries the STOP notice.

  6. The guest answers, or does not

    A reply of any kind is recorded as consent to the remaining messages about that event. A guest who never replies receives at most one reminder and nothing else.

  7. STOP ends it everywhere

    STOP, or a plain-English request to stop, suppresses that number for every host on SimpleInvite, immediately and permanently, until the person replies START. The host is shown that the guest opted out and is told to share the link themselves instead.

The screens

Not captured yet. This slot holds the screen described below.

Where the host enters the people they know.That numbers are entered by the host, one event at a time, not uploaded from a purchased list.

Not captured yet. This slot holds the screen described below.

The consent box, unchecked, above Send now.The exact wording, that it is unchecked by default, and that it stands alone.

Not captured yet. This slot holds the screen described below.

Ticked, and only then does Send now work.That sending texts is gated on the host's confirmation.

Not captured yet. This slot holds the screen described below.

The first message a guest receives.Host name, program name, one branded link, how to reply, and the STOP notice.

Not captured yet. This slot holds the screen described below.

STOP, and the one confirmation that follows it.That opting out works and that nothing is sent afterwards.

What a guest receives

Bracketed fields are filled from the host's event. Every link uses our own domain, nvite.app.

First message
[Host] invited you: [Event], [Weekday] [Date] at [Time]. Reply Y or N, or see details: nvite.app/[code] Txt STOP to end
Confirmation
You're in for [Event] on [Weekday]. See you at [Time]. Details: nvite.app/[code]
Reminder
Still thinking it over? [Host]'s [Event] is [Weekday]. Reply Y or N when you know. nvite.app/[code]
Update
[Event] moved to [Weekday] at [Time]. Still coming? Reply Y or N. nvite.app/[code]
HELP
SimpleInvite sends invites from people you know. Reply Y or N to answer, STOP to end. help@simpleinvite.app