Teaser campaign
A clearer view of the week is coming
Look out for the new planner in the next update.
Workflow
Plan a product launch with AI push campaigns
Turn a product update into scheduled announcements with AI-assisted copy. Set each campaign’s audience, dates, and message goal before activation.
AI copy
Generated from your business context and campaign goal.
Your audience
Firebase topics or OneSignal segments.
Your schedule
Dates, send times, and a campaign timezone you choose.
Use a separate campaign for a teaser, the launch announcement, or a follow-up when each stage needs different facts and timing. These are campaigns you configure, not an automatic event-triggered journey.
FIND THE RIGHT MOMENT
When to use this workflow.
Start with a clear reason to reach your audience.
- A feature or release has a confirmed launch date.
- You have accurate feature details and a destination for readers to explore.
- You want to plan separate messages for selected provider audiences.
FROM SETUP TO SEND
Build it, step by step.
Use this sequence to shape the campaign in your workspace.
- 01
Prepare the audience and provider
Connect your Firebase project or OneSignal app. Confirm devices can receive notifications and belong to the topic or segment you plan to target.
Provider: Firebase or OneSignalAudience: registered topic or provider segment - 02
Write the campaign brief
Add the business context, objective, tone, and accurate facts that should guide the generated messages. Avoid claims that depend on individual data the campaign does not have.
Announce the new weekly planner. Explain that it brings tasks into one view and invite readers to open it. Only describe features that are available. - 03
Choose dates and timing
Set the campaign date window, frequency, send time, and timezone. Check other campaigns aimed at the same audience when deciding how often to send.
Choose the frequency needed for this announcementChoose the launch send time and campaign timezone - 04
Review and activate the draft
Review the campaign details and any preview samples. Activation starts generating actual upcoming notifications in the Scheduled state; a preview is not a queued send.
- 05
Review the upcoming messages
Inspect and edit scheduled copy before its send time. Check notification status and available analytics, then adjust the brief or pause the campaign if needed. Engagement reporting depends on tracking events.
EXAMPLE MESSAGES
A starting point for the words.
These notifications illustrate the workflow. Adapt the content for your own app.
Launch campaign
Your new weekly view is here
Bring your tasks into one place. Open the planner and take a look.
Follow-up campaign
Make the new view your own
Pick a project and try planning it with the weekly view.
THE CAMPAIGN SETTINGS
Keep the plan in view.
- Campaign objective
- Announce the new weekly planner. Explain that it brings tasks into one view and invite readers to open it. Only describe features that are available.
- Push provider
- Your connected Firebase project or OneSignal app
- Audience
- Selected Firebase topics or OneSignal segments maintained by your app or provider
- Frequency
- Choose the frequency needed for this announcement
- Send time
- Choose the launch send time and campaign timezone
- Dates
- A start and end date that match the campaign plan
- Images
- Optional; availability depends on the plan and campaign settings
BEFORE YOU ACTIVATE
Details worth checking.
Consider these cases before the first scheduled send.
Keep each stage accurate
Update the brief if the launch date or feature changes. Pause affected campaigns when needed. PushPilot does not read deployment status or automatically move people between launch stages.
Review facts in generated copy
AI copy can need correction. Check dates, offers, feature names, and tone before the scheduled send, especially when the underlying information changes.
Check overlapping campaigns
A schedule controls this campaign. Consider other campaigns and provider sends reaching the same people; a per-user cap across campaigns is not part of this workflow.
Know what the metrics represent
A successful provider send does not by itself prove a person saw or opened the message. Use available tracking events and your own product data to assess engagement.
Can I use either Firebase or OneSignal?
Yes. Connect the provider your app uses and select its registered topics or segments. Your application must be configured to receive notifications and maintain audience membership.
Does this workflow trigger on each user’s activity?
No. This guide uses scheduled campaigns. Activity-based audience membership must be maintained in your app or provider. Each campaign uses the dates, frequency, and timezone you set.
Do I approve every generated notification?
Active campaigns generate upcoming notifications in the Scheduled state. You can review and edit them before their send time. If a notification is Pending, its Approve action schedules it.
Will every message be unique or improve my open rate?
PushPilot uses your campaign context and recent copy to generate upcoming messages. Review the results for repetition and accuracy. There is no guarantee that each message will be unique or that engagement will improve.
Where can I check limits and image availability?
See the current Pricing page and Settings → Billing in your workspace. Your plan controls notification allowance, active campaigns, and AI image availability.