public data.held to ahigher bar.
A public hearing notice sent from a shared marketing domain gets treated like marketing — filtered, ignored, or flagged. For an agency, the sender identity isn't a technical detail, it's the whole reason residents trust the notice enough to open it.
what changes.
Public hearings, policy briefings, citizen notifications — this is exactly where "your own SMTP, your own domain, nothing sold or repurposed" stops being a nice-to-have and starts being the whole reason an agency can use the platform at all.
a day inthe life.
how it worksfor public notices.
- 1
Every notice sends from the agency's own verified domain, never a shared platform address.
- 2
A reminder follows ahead of the hearing or briefing, timed to when residents are actually deciding whether to attend.
- 3
Nothing about a resident's data is sold or repurposed — the sending identity and the recipient list stay the agency's own.
worthasking.
does nudgt replace our notification or records system?
No — it doesn't replace your notification or records system. It takes your registered resident list and sends the calendar invite and reminder from your agency's own verified domain, never a shared one.
what if a resident still doesn't show up?
A reminder closes the gap between registering and remembering — it doesn't guarantee attendance. What it does is remove the single biggest reason people miss things they meant to attend: it stopped being in front of them.
is this only for public hearings?
No — public hearings and citizen notifications are one of the places it gets used most, not the limit of what it works for. The same calendar-invite-plus-nudge-sequence mechanic applies anywhere someone needs to show up to something they said yes to.
alsocommon.
public notices rarely happen in isolation — these get run the same way.
ready tofill theroom?
Sign up now, no credit card required — you're in immediately. Try it on your next public notice campaign, at a founding rate that stays yours for good.