The platform · 04
The right message, to the right people, read first.
A message to your guests is written by you, or drafted for you, and shown to you exactly as each guest will receive it — with the names of who it reaches and who it will skip — before a send button exists. Then it sends, by email or by text.
Who it reaches.
You choose the audience in plain words, not a query.
Everyone
Every guest still on the list, and nobody who has left it.
The ones who have not answered
The whole point of a private link: “who has not replied” has an exact answer, so a reminder never reaches the people who already did.
One group
The twelve staying at one hotel. The bride’s side. The Friday dinner. The groups you set on the list are audiences here.
The ones who said yes
Day-of details go to the people who are coming, and to nobody who declined.
Read before it sends.
Shown as the thing itself
Not a summary. The email as it will land, the text as it will read, with a real guest’s name in it.
Who it reaches, and who it skips
The preview counts the audience and names anyone it cannot reach — no number, no consent, opted out, bounced — so “sent to 38” is a figure you can reconcile against your own list.
Then, and only then, a send
The button does not exist until you have seen the preview, and the message that goes is provably the one you read: change a word and it is a new preview.
Now, or at a time
“Send now” sends now. “Schedule” stores a time. Neither is dressed up as something softer.
Once, to each person.
A guest is written to once per message, per channel.
A retried send, a double-clicked button and a re-run job all collapse to one delivery, because each is recorded against the guest before it goes.
Text messages respect the number’s own local hours: a message that would land at three in the morning is held until the window opens, and a hold is not a failure. Guests are not messaged outside waking hours, and not with marketing — only with the running of the event they were invited to.
When a guest writes back.
Without
A reply to a no-reply address. A guest texts “is there parking?” to a number nobody reads. The answer, if it comes, comes from a different thread three days later.
With Evorrah
A guest who texts back is passed to you, and your answer goes back the same way. A guest who replies STOP is stopped — immediately, on that number, across every event it appears in — and only they can undo it.
The one control.
One control stops everything already in flight.
A message scheduled for the morning, a reminder queued for the deadline, a text held for quiet hours: one switch halts all of it, and nothing sends again until you say so.
It exists because the worst thing a messaging system can do is keep going after you have changed your mind. It is the same control that stops a reminder, a chase and a day-of note, because they are all the same kind of thing: words sent in your name.
As delivered.
A guest message as it landed, on four delivered events — a brand launch, a graduation, an engagement party and a charity gala.
Rendered from the file each event ran as — its own guests, dates and colour. Open any one to see it full size.
What it will not do.
Guest communication is where event software most often embarrasses its user. These are standing rules, not settings.
- Send anything in your name that you have not seen
- Message a guest who has opted out, for any reason
- Blast the whole list when a group was meant
- Reach the people who have already replied, when the message was for those who have not
- Send marketing to your guests
- Keep messaging after the event is over
- Send while the whole thing is stopped
Evorrah recommends and drafts. You read, and you send.
The rest of the platform
Three more services,
reading from the same event.
Event Website
A private site carrying your approved invitation, in its colour and its lettering: the schedule, the locations, the answers, the RSVP.
Explore → 06Reminders & Chasing
Late replies followed up for you, counted back from the deadline, only to the guests who have not answered or left something out.
Explore → 07Seating & Tables
The seating plan builds itself from the replies, and re-resolves when someone declines.
Explore →