Workflow
Run a product launch with AI push notifications
A staged push-notification workflow for launching a new feature or version of your app — pre-announce, day-of-launch, post-launch reinforcement — with fresh AI-written copy on every send.
If you're a product manager or founder shipping a real feature this week, this is the workflow that takes the launch from 'we built something' to 'our users actually noticed and used it.' You set up three staged campaigns (T−2 days teaser, T+0 announcement, T+3 days nudge for users who didn't open). Each campaign gets fresh AI-generated copy and a matching image, so the same user doesn't see the same line twice across the three sends.
3 stages
Pre-launch teaser, announcement, post-launch nudge
1 hour setup
From describing the feature to first scheduled send
AI images
Each notification gets a generated image, no designer
When to use this workflow
If any of these match your situation, this is the right workflow to start with:
- You're shipping a real new feature, version, or product within the next two weeks.
- You want a coordinated 3-touch launch sequence — not just one 'we shipped it' send that gets buried.
- You don't have a marketing team to write three different angles for the same launch by hand.
- You want each of the three notifications to use a different angle (excitement, walkthrough, results) without you brain-storming hooks.
- You'd like the launch notifications to include a generated image (without a designer) so they actually stand out in the lock screen.
How it works, step by step
Plain-language walkthrough, exactly how you'd set this up inside PushPilot. No jargon, no hand-waving.
Pick the launch date and write a one-paragraph brief
Before any campaign setup, write 3–4 sentences answering: what is the feature, who is it for, what one user problem does it remove, and what's the tone (playful / serious / technical). This brief becomes the campaign description fed to the AI for all three stages — so it's worth taking 15 minutes to make it good.
Concrete settings
- Example brief: 'We just launched dark mode for our reading app. The audience is night-time readers and people on commutes. The problem we removed: eye strain and battery drain in low light. Tone: warm, slightly poetic, never marketing-speak.'
Create the T−2 day teaser campaign
Two days before launch, send a short teaser to your full active-user audience. The goal is curiosity, not explanation. The AI writes a single short notification per send — keep it text-only, no image yet. This is the campaign where the AI's voice matters most: a vague-but-intriguing teaser is harder to write by hand than a launch announcement.
Concrete settings
- Audience: all active users (last_active <= 14 days)
- Send time: 6pm user local time (peak engagement window)
- Tone override in description: 'mysterious, single-line teaser, no specifics'
- Generate images: false
Create the T+0 launch announcement campaign
Day-of-launch notification. This one gets the AI-generated image because it has to stand out. The AI uses your brief to write a notification that names the feature, hints at the user benefit, and includes a clear call-to-action. Send to the same active-user audience as the teaser; users who saw the teaser will recognize this as the payoff.
Concrete settings
- Audience: same as teaser (active users last 14 days)
- Send time: 9am user local time (capture morning attention)
- Tone override: 'celebratory but specific — name the feature, name the user benefit'
- Generate images: true (include AI-generated image matching the feature)
Create the T+3 day post-launch nudge campaign
Three days after launch, send a follow-up to the subset of users who saw the launch announcement but did NOT open the app afterward. This is your second chance — and it shouldn't repeat the announcement message. Describe this campaign as 'walkthrough angle' so the AI writes it as 'here's how to actually use the new thing' rather than re-announcing.
Concrete settings
- Audience filter: received T+0 announcement AND last_active < that date
- Send time: 11am user local time (mid-morning, work-context)
- Tone override: 'practical walkthrough — describe one concrete thing they can do with the new feature'
- Generate images: true (different image from T+0)
Watch the funnel, not individual sends
The metric that matters for a launch isn't open rate per send — it's the percentage of active users who eventually opened the app and used the new feature in the first 7 days. Inside PushPilot's analytics dashboard, look at the combined reach of all three sends, deduplicated. That's your real launch number.
Example notifications PushPilot generates
These are the kind of messages the AI writes for this workflow. Each notification is fresh on every send — you never repeat the same line.
Your app
Something new — Thursday morning
We've been working on this for a while. Two-day heads-up.
Your app
Pencil it in: Thursday at 9
If you've ever wished the app did one specific thing — open it Thursday.
Your app
Dark mode is live
Settings → Appearance. Or just open the app at night and we'll suggest it.
Your app
It shipped — and it's a big one
Open the app to see the new look. Three taps to enable, free for everyone.
Your app
30 seconds with the new feature
If you haven't tried dark mode yet — open Settings, tap Appearance, pick 'Auto.'
Your app
The thing we shipped on Thursday — here's how to use it
One screenshot, one tap. We walked you through the setup inside the app.
Recommended configuration
These are the exact settings we recommend for this workflow. You can change any of them later.
Edge cases & honest gotchas
Things people miss the first time they set this up. Worth a two-minute read before you go live.
Don't combine launch with promotional sends
If you also run a daily-deal or sale notification on launch day, your launch message will compete with it for attention in the lock screen and lose. Pause promotional campaigns during the 5-day launch window. The launch needs the channel to itself.
Time the T+0 send carefully if you have global users
Timezone-aware delivery is great for engagement campaigns, but for a real product launch you sometimes want everyone to hear about it within the same 24 hours (so your community discussion happens together). For T+0 specifically, consider using a single fixed UTC time instead of per-user local time. PushPilot supports both.
The T+3 nudge must NOT repeat the T+0 message
If you reuse the same campaign description for T+3, the AI will generate a re-announcement and the user will pattern-match 'oh I already saw this' and ignore it. Override the tone for T+3 explicitly to 'practical walkthrough — describe one concrete thing they can do' to force a different angle. This is the most common workflow mistake we see.
AI-generated images take 8–12 seconds to produce
If you're scheduling a same-day launch, factor this in. The AI generates a fresh image at send-time per send, which means a campaign sending to 100k users will produce 100k images. PushPilot batches and caches sensibly, but the very first send in a new campaign can take a minute longer to start than a text-only campaign. Schedule the T+0 send 5 minutes before your target time to be safe.
Frequently asked questions
How do I run a product launch push notification campaign?
The reliable workflow is three staged campaigns: a teaser two days before launch, the main announcement on launch day, and a walkthrough nudge three days later for users who didn't open the app. Each stage uses a different tone and angle — the AI generates fresh copy for each send so users who see all three notifications never see repeated language. Setup takes about an hour inside PushPilot once your campaign brief is written.
What should a product launch push notification say?
It depends on the stage. The teaser (T−2 days) should create curiosity without specifics — a single short line. The announcement (T+0) should name the feature, name the user benefit, and include an AI-generated image so it stands out in the lock screen. The follow-up nudge (T+3) should describe one concrete thing the user can do with the new feature — never re-announce. PushPilot's AI writes all three for you from a single one-paragraph brief.
When is the best time to send a product launch notification?
For a global product launch, 9am user local time on the day of launch typically works best — captures morning attention without competing with social media's evening peak. Send the teaser two days before at 6pm local (peak engagement window) and the post-launch walkthrough at 11am local (mid-morning when people have a moment to actually try the feature). PushPilot handles all of this timezone-aware automatically.
Should every launch notification include an image?
Not the teaser. A vague-but-intriguing teaser works better as text-only — adding an image gives away too much. The launch announcement (T+0) and walkthrough (T+3) should both include AI-generated images because they have to compete for attention against everything else in the lock screen on launch day. PushPilot generates fresh images for every send via Vertex AI, so you don't need a designer in the loop.
Can I use one campaign instead of three staged campaigns?
You can, but the launch will underperform compared to a staged workflow. A single 'we just shipped X' notification reaches everyone once. A staged workflow reaches the same audience three times with three different angles, captures users who missed the first send, and gives the launch a sense of arc. The whole point of automating push notifications is that running 3 campaigns isn't more work than 1.
How do I make sure users don't get the same notification twice during a launch?
Two mechanisms. First, PushPilot's AI generates fresh copy on every single send, so even if a user is in multiple campaigns, the wording is never repeated. Second, the T+3 nudge campaign filters out users who already opened the app after the T+0 announcement — so you only re-engage users who didn't see or didn't act on the launch message. Frequency caps inside the campaign settings prevent more than 3 launch-related sends per user across the 5-day window.
Does this workflow work with Firebase Cloud Messaging or OneSignal?
Both — and they're both first-class. Upload your Firebase service-account.json OR paste your OneSignal App ID + REST key, and the same 3-stage launch workflow ships notifications either way, with no SDK changes. For a launch specifically, the choice doesn't matter much: launches are short (5-day window), so the per-event reporting loop OneSignal provides isn't critical the way it is for daily/win-back campaigns. For daily and win-back workflows we recommend OneSignal because it reports open events back; for launches use whichever you're already on.
Related workflows & resources
Try it free
Set this workflow up in 4 minutes
Connect Firebase or OneSignal, paste the campaign description, watch the AI write your notifications. Free plan — no credit card.