Every invite you send becomes someone else's day. Scroll down and follow it onto their phone — the calendar block, the email, the text — in the order they land.
the calendar invite
the moment they register
blocks the time on their calendar, with the join link inside
email nudges
days out, then the night before
up to five per campaign, each on its own lead time
text nudges
hours, then minutes before
short, from your own number
01
the invite lands.
The moment you hit send, it's already sitting on their calendar — no reply, no acceptance step. Their day is blocked before they've even thought about it.
02
a reminder nudges.
A personalized email slips into their inbox right on schedule — warm enough to feel human, never enough to annoy.
03
the final nudge.
A text closes the gap for good, sent exactly when you need it. Three touchpoints, one show-up — and a no-show that never happens.
every touchpoint.one no-show, gone.
your data.your domain.your rules.
To send from your domain, nudgt holds your sending setup and your invitee list. That's a lot to hand over — so here's exactly what we do with it, and what we'll never do.
your own domain, always
Every invite and nudge goes out through a sending domain you verify — no shared mailbox, no shared sending pool. nudgt never touches a password to do it: verification is DNS records you publish yourself, and your domain carries the reputation, never diluted by anyone else’s sends.
vault-encrypted where it counts
There’s no email credential to hold in the first place. Where a credential does exist — your connected SMS provider account — it’s encrypted at rest inside an isolated secrets vault and decrypted only in memory, for the moment a batch actually sends. It never touches a plain database column, and no one — including us — can export it in plaintext.
your list stays yours
Invitee data belongs to your account, not ours. Export it, take it with you, delete it — cancel any time with no lock-in and nothing held hostage.
never sold, never repurposed
Names, emails, and phone numbers exist for one reason: delivering that campaign’s invites and nudges. Nothing is sold, shared, or reused for anything else.
everything elsethat fillsthe room.
The journey above is the headline act. These are the details underneath it — the parts that keep a big send deliverable, editable, and entirely yours.
sends from your own domain
Invites go out through a sending domain you verify — a handful of DNS records, not a password. Your domain, your reputation, never a shared pool. So reminders land in the inbox, not the spam folder.
templates that stick
Save reusable templates for the invite email, the reminder emails, and the SMS nudges — independently, not just the first message. Build each one once, in a full editor, and reuse it on every campaign.
pay for what you send
One flat plan, then simple credits for calendar invites, email, and SMS — metered separately. You only spend on the channels you actually use, never on the ones you don’t.
never trips a spam filter
Big lists go out in steady, capped waves instead of one giant burst — so a large campaign never torches your sender reputation or lands everyone in spam. Reworked sending infrastructure means meaningfully faster delivery at scale, especially on larger lists.
change it after you send
Move the time or the place, and nudgt sends every invitee a fresh invite with the update automatically — no manual re-send, no “please ignore the last invite” follow-up email to write yourself. Decline, and it comes off their calendar entirely — not just marked declined in an inbox.
invites on their own clock
On professional and business, invites can go out on a per-invitee delay instead of all at once — “2 days after they join,” configurable down to 5-minute increments. Built for a rolling audience: a signup form, a CRM import, an ongoing roster. If the delay would land after the event has already started, the invite sends immediately instead of never.
suggested nudges, one click away
nudgt looks at how far out your event is and proposes a tiered reminder schedule automatically — a 2-week-out event gets suggestions at 1 week, 3 days, 1 day, and day-of. Each one is individually approved or dismissed, never applied for you. Running invites on a rolling clock instead? The suggestions shift to recommend relative reminder scheduling instead of fixed countdown tiers.
proof it lands, first
Before a single invite goes out, we push a live test through your own connection and confirm it arrives. A broken setup can never reach your real list.
a zoom link for each person
Every registrant gets their own unique join link, generated automatically at send. No manual sign-in list, no single link getting passed around.
bring yourown smsprovider.
Connect the SMS provider you already use, and we route every text nudge through it — so you keep your own number, your own rates, and your own sender reputation. We never mark up your carrier bill.