Announcements that land on the right screen
An announcement is a post the organizing team publishes to everyone at the event, delivered as a push notification and kept in a feed inside the app. Because the push is deep-linked, tapping it opens the announcement itself instead of dropping the attendee on the home screen to go looking.
What this looks like in the product
One composer, two delivery times, and a feed that survives an attendee who had notifications switched off.
- Publish or schedule
- Send an announcement immediately or set it to push at a chosen time.
- Deep-linked push
- A notification opens the exact post or thread rather than the app's home screen.
- Announcements feed
- Every announcement stays readable in the app for attendees who had notifications off.
- Live Activity on iOS
- A live event surface driven by the same dispatcher as the push.
- Attendee opt-out
- Push permission is the attendee's, revocable in device settings at any point.
Composing an announcement
- Write the post
- Publish now, or schedule a time
- Delivered as push and to the feed
- Deep link opens the post
- Scheduled queue, editable until it fires
Why the deep link is the feature
A notification that says the keynote has moved to Hall B, and then opens the app's home screen, has moved the problem rather than solved it. The attendee is now standing in a corridor scrolling for the information they were just told existed.
event67 notifications carry a destination. A push about an announcement opens that announcement. A push about a message opens that thread. The gap between reading the alert and having the detail is one tap, which is the difference between an app people trust during an event and one they mute on the first morning.
The second half of the same problem is the attendee who denied notification permission in the first thirty seconds of installing anything. Every announcement stays in the in-app feed, so the information is still reachable by someone who never gets a push at all. Neither channel is the source of truth on its own.
Scheduling, and the discipline it needs
Announcements can be written in advance and set to publish at a time, which is how a two-day conference gets its morning nudge sent at seven-forty rather than by somebody remembering at eight-fifteen. Scheduled announcements sit in a queue in the console and can be edited or removed until they fire.
The discipline part is worth stating because it is where events do damage to themselves. A push is the loudest thing this product can do, and its cost is not measured in dollars. An event that sends nine notifications on day one has an audience that has turned them off by day two, at which point the genuinely urgent room change is delivered to nobody.
- Worth a push
- A room or time change, a delay, a session cancellation, the thing happening in ten minutes that nobody saw coming.
- Worth an announcement without urgency
- Photos of yesterday are up, the feedback form is open, the bar opens at six. Post it; the feed will carry it.
- Not worth sending
- Sponsor promotions dressed as event news. This is the fastest way to teach an audience that your notifications are advertising.
What the organizer controls
- Timing
- Immediate or scheduled, with the queue visible and editable in the console until the moment it fires.
- The destination
- Announcements deep-link to themselves; chat notifications deep-link to the thread, so the routing is not something you configure per send.
- Who can publish
- Announcement publishing is a console capability governed by roles. It does not write an audit record: admin chat and billing are the only actions that do.
- The record
- Announcements remain in the feed for the event rather than disappearing after delivery.
What this will not do
- No SMS and no voice. Push and the in-app feed are the channels; email campaigns are a separate feature with a separate purpose.
- No segmented push to a subset of attendees by track, ticket type or behaviour. An announcement goes to the event.
- No delivery receipt per attendee for push. Push delivery is the operating system's business and it does not report back reliably.
- No automated triggers. Nothing sends itself because an attendee did or did not do something.
- No guarantee an attendee sees it, because notification permission belongs to them and they can revoke it at any point.
The absence of segmentation is the one people ask about most. If you need to reach only the workshop attendees, the practical answer today is an email campaign, which does support targeting, rather than a push.
When this carries the event
Multi-room events where the programme moves. Outdoor and multi-venue events where people are physically spread out. Any event with a session that fills up, a speaker whose flight is late, or a shuttle bus that is not where the printed guide said it would be.
A single-room half-day event does not need push notifications, and sending them anyway is how an organizer teaches an audience to ignore the app before it has done anything useful.
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
Can we schedule an announcement in advance?
Yes. Write it whenever you like and set the time it should publish. It sits in a queue in the console and can be edited or deleted until it fires, which matters because the seven-forty morning nudge is usually written the night before and is usually slightly wrong.
Where does tapping a notification take an attendee?
To the thing the notification is about. An announcement push opens that announcement; a message push opens that thread. It does not drop them on the home screen, which is the behaviour that makes people mute event apps.
Can we send to only some attendees?
Not with push. An announcement goes to the whole event. If you need to reach a subset, use an email campaign, which does support targeting, and accept the different timing that comes with email.
What if an attendee turned off notifications?
They still get everything, just not loudly. Every announcement stays in the in-app feed for the duration of the event, so the information is reachable rather than lost. Push permission is the attendee's and they can withdraw it in device settings whenever they like.
Do notifications cost anything per message?
No. There is no per-message or per-notification charge. The meter is activated attendees: 50 free, $5 each after that, capped at $4,750 for one event.
Keep reading
Features this reaches into
Event types that lean on this
See it in your own event
Your first 50 attendees are free on every event, so the smallest version of this costs nothing to try.