An event app does ten jobs. You need one of them.
Event apps exist for good reasons. If attendees need a searchable agenda, speaker profiles, sessions they can add to a calendar, a floor map, badge scanning and a way to message each other, that is a real product and you should buy one. Event apps such as Whova do not publish public prices. You ask, you describe your event, and you get a quote for that event.
None of that is the job at 11am on the day, when the 2pm breakout has moved to Room B. That job is one sentence, delivered to the phones of the people already in the building. An app bought for a list of features is an expensive way to deliver one sentence, and a good share of your attendees will never have installed it anyway.
A broadcast is the other shape of tool. One message, 160 characters, out to everyone who joined your list, each person receiving it on their own. $5 covers up to 100 attendees. $19 covers up to 500, which is more than most one-day professional seminars, trade association meetings and training days ever put in a room. There is no account to keep and nothing to cancel once the event is over. If your numbers run higher, the pricing for texting 500 people at once holds at the same per-send shape.
The events this suits are the ordinary ones. A one-day trade association meeting. A professional seminar with a credit hour requirement. A training day with two tracks and a shared lunch. A Saturday workshop with 60 people and a single room. In all of those the agenda is already printed on the badge card or the handout, and what the agenda cannot do is change itself at 11am. That is the gap a broadcast fills, and it is the only gap it fills.
Decide by the job, not by the software. If the honest list of what you need is an agenda plus profiles plus networking plus lead capture, buy the app and use it properly. If the honest list is three or four announcements across one or two days, buy the sends and keep the rest of your budget for coffee.
Reach up to 500 attendees for $19 →Where the sign-up link has to go
Nobody joins a text list because it occurred to them. Attendees join because the link was in front of them at a moment when their phone was already in their hand. At a conference there are exactly three of those moments, and the organizers who end up with a usable list use all three rather than picking one.
The first is the registration confirmation email. That is the one email every attendee really opens, because it carries their ticket and the address. Put a line near the top, not buried under the refund policy: day-of updates by text, here is the link, room changes and schedule changes only. Say what it is for in the same breath, because an attendee who expects marketing will not tap it.
The second is a slide in the opening session. Full screen, QR code big enough to scan from the back row, left up for the whole housekeeping talk, and explained out loud by the person holding the microphone. People do scan a code on a screen when someone in front of them says that room changes go out this way. Our guide to the QR code sign-up sheet covers how large to print it and what to write beside it.
The third is printed and in their hands all day: the same QR code on the back of the badge, or on the lanyard insert card that already lists the agenda. This is the one that catches the attendee who skipped the opening remarks and walked in at 10:30. Use one code and one link across all three places, so everything feeds a single list instead of three lists you cannot merge.
One thing not to do: nobody gets added by somebody typing numbers out of the registration spreadsheet. Attendees join by tapping the link or scanning the code themselves, and that is also what creates the record that they agreed to be texted. So the work in the week before the event is not list building, it is making sure the link is in three places where an attendee will meet it. Ask at check-in too if you have a desk and a queue, since a printed card beside the badges costs nothing to put out.
Put a code on the badge and send for $19 →The announcements that actually matter on the day
At a one-day event there are about six things worth a text. The room moved. A speaker is running late. The afternoon start has been pushed. Lunch is somewhere other than the printed hall. The guest WiFi details changed. Something has been closed or canceled. Everything else is noise, and noise is what teaches attendees to ignore the message that does matter.
Total message length is 160 characters, and that includes the automatic prefix with your event name and the closing opt-out line. In practice you are writing about 110 characters of your own, which is more than enough if you lead with the change instead of the apology. Five that fit:
Breakout moved to Room B, second floor. Still a 2pm start. Signs are up by the elevators.
Our 1pm speaker is delayed. The panel runs first and her talk moves to 2:15pm.
Afternoon sessions start at 2pm, 30 minutes later than printed. Coffee is out in the lobby.
Lunch today is in Oak Hall, not the atrium. Doors open at 12:30pm.
Guest WiFi is CONF2026, password harbor26. The registration desk can help if it fails.
Notice what each one does. The new place and the new time sit in the first clause, so an attendee reading the notification preview on a lock screen already has the answer. There is no greeting, no thanks for your patience, no sign-off. If attendees are likely to need to ask something, spend 20 of your characters on a staff cell number inside the text, because replies do not come back to you.
Your event name goes in the prefix, so keep it short and recognizable. A long formal title eats characters that the message needs. Use the name printed on the badge, which is the name attendees will recognize when it lands between messages from their family.
Timing: book the night before, lands at noon
Messages go out at 12pm Eastern on the date you choose, and the earliest date you can choose is tomorrow. So the working pattern for a conference is to set the send up the evening before, dated for the day of the event, with the message landing at midday. You can book up to 30 days ahead, and scheduling a text in advance works the same way here as anywhere else.
Noon suits this better than it first sounds. Most of what goes wrong at a one-day event is known by late morning: the speaker who called from the highway, the double-booked breakout room, the catering van that went to the wrong loading dock. Midday is also when attendees are out of their seats with a coffee in one hand and a phone in the other, so an announcement about the afternoon reaches them before the afternoon starts.
Be clear with yourself about the part this cannot do. A room change discovered at 8:15 on the morning of the event cannot go out through ZestyText that morning. Nothing you book arrives sooner than the next noon. For a change that breaks inside the hour, you use the building: a sign taped to the old room door, a staff member standing at the junction, a word from the stage, and the venue screens if there are any.
Each send is paid for on its own, so choose what earns the noon slot. If two things have changed and both fit inside the character budget, put them in one message rather than paying twice. If the second change is minor, such as a coffee break moving by ten minutes, leave it off and let the room find out from the signs. The announcement people act on is the one that is not surrounded by things they do not need.
On a two-day conference the rhythm is simple. At the end of day one, when you know what moved, book day two. If nothing moved, you have not spent anything, because you only pay when you send. Plan the list early though, because if nobody has joined by the send date, nothing goes out and the payment is not returned.
What this cannot do, plainly
Replies do not reach you. If an attendee texts back to ask which floor Room B is on, you never see it. A reply of STOP removes that person from the list. A reply of HELP triggers an automatic support message. Anything else is recorded by ZestyText and never forwarded to the organizer. This is the single thing to understand before you rely on it, and the reason to put a staff number inside any message that invites a question.
There are no RSVPs and no headcounts. You cannot ask 200 attendees to confirm they are coming to the afternoon workshop and get a number back. No form, no tap to confirm, no tally. If catering needs a count by 11am, you collect it at the registration desk or on a sheet at the door, the way you did before.
There is nothing per person. Every recipient gets the same 160 characters. No individual agendas, no track-specific schedules, no reminder sent only to the people registered for the 3pm session, no name in the greeting. An event app can do all of that because it knows who registered for what. ZestyText knows only that a phone number joined a list, which is also why nobody on the list sees anyone else, since each message is sent one to one.
There are also no images, no PDFs, no floor plans and no slide decks, because this is plain SMS. US numbers only, which matters if you have speakers or delegates visiting from abroad. If you read that list and three of the items are things you genuinely need next month, you need the app, and this page has saved you $19.
The test is worth applying before you book anything. Write down the five things that have to happen at your event. If three of them involve knowing who is in which session, collecting an answer back, or showing an attendee something on a screen, the broadcast is the wrong tool and you should go and get a quote. If four of them are a sentence that needs to reach the whole room by lunchtime, you are in the right place and it costs $19.
What it costs, counted per announcement
Price is per send. $19 covers one announcement to up to 500 attendees. Three announcements across a two-day conference is three sends, so $57. Budget per announcement, not per event. This is the part organizers get wrong when they compare it to a platform, and it is worth saying twice: one payment covers one message to one list.
For a 90 person seminar with a single room change to announce, that is $5. For a 300 person association meeting with two updates on the day, $38. For an 800 person conference, $79 covers up to 2,000 recipients per send. Smaller sessions are cheaper still, with $1 covering up to 25 people, which is the size of a board meeting or a hands-on workshop.
The honest comparison: Text-Em-All runs about $19 a month, or roughly 3 cents a message. If you run a monthly training series and send several updates at each one, that subscription math beats this and you should use it. This suits the organizer who runs two or three events a year and does not want a platform sitting in the budget between them. Four announcements across a year to 500 attendees is $76 here against $228 of monthly fees, and there is more on that in our look at SMS with no monthly fee.
Two details that protect the spend. An AI writer drafts the message on the send page and you approve or edit it before paying, so the character limit is not something you fight. And every message is screened before payment, so a message that would be blocked is never charged for.
Send your day-of update for $19 →This article is informational, not legal advice. Pricing is accurate as of publication and subject to change. All senders must comply with TCPA and 10DLC rules.