For Agencies
AI push notifications for agencies running multiple clients
Run push for multiple client apps from one workspace. Per-client tone constraints, per-client frequency caps, per-client provider connections, every notification AI-rewritten on every send.
Growth and lifecycle agencies hit the same wall on push: every client wants their own voice, their own cadence, their own delivery stack, and the agency ends up running campaigns out of half a dozen OneSignal logins, three Firebase consoles and a shared Notion doc that's always out of date. PushPilot is the AI campaign layer agencies have been waiting for, one workspace, one team, one audit log, with a separate push project per client (each with its own FCM or OneSignal connection, its own tone constraints and its own frequency caps). The AI handles voice automatically per client, your team ships campaigns 5–10x faster, and your senior strategists stop spending three days a week typing notification copy.
5–10x
Ship at the speed of your strategists, not the speed of your junior copywriters.
1 workspace
Multiple push projects per organisation, one per client, with separate provider connections and tone rules.
Per-client caps
Frequency caps and audience filters scoped per client, your portfolio doesn't fight itself.
Why push is hard for Agencies teams today
Most push stacks were built to deliver notifications, not to write them. Here's what breaks for teams in this space, and what PushPilot does instead.
Your agency runs push for 12 clients, four are on Firebase, eight on OneSignal, and your team toggles between half a dozen consoles every day.
PushPilot supports multiple push projects per organisation. Each client gets its own FCM or OneSignal connection in its own push project, but lives in the same workspace, same team logins, same audit log, same billing.
Every client expects their own brand voice and you're rewriting copy by hand for each one. Three days a week of strategist time is just typing notifications.
Tone is per-campaign. Configure each client's voice constraints once (words to use, words to avoid, tone, frequency caps), and the AI generates fresh, on-brand notifications on every send for that client. Strategists stop typing, AI handles voice.
Cap collisions: client A's win-back campaign and client B's retention campaign go out the same morning to overlapping audiences and you don't notice until the unsubscribe report.
Frequency caps are scoped per push project (per client). Client A's cap doesn't affect client B, but each client's cap is enforced strictly across every campaign you run for them, win-back, retention, launch, upsell.
Onboarding a new client onto push takes two weeks of engineering hand-offs and your senior team spends most of that time waiting.
Connect a new client's Firebase or OneSignal in 10 minutes (FCM service-account.json or OneSignal App ID + REST API Key, encrypted with Fernet at rest). Authoring the first three campaigns from plain-language descriptions is another hour. Engineering hand-off is a single-page brief.
High-impact use cases
The campaigns that move the metric for your business. Each one ships in minutes, describe it once, the AI writes every send.
Multi-brand campaign management
One workspace, separate push project per client, each with its own provider connection, tone rules and frequency caps. Switch clients in one click.
White-label-friendly setup
Each client's push delivery infrastructure remains theirs (their FCM project, their OneSignal app), the agency configures and operates it from PushPilot. Hand-back is trivial when the engagement ends.
Per-client tone & guardrails
Compliance, brand and frequency rules approved once per client. Junior strategists ship inside the guardrails, senior strategists set them.
Lifecycle templates across clients
Re-use lifecycle patterns (trial activation, win-back, weekly digest) across clients without re-using copy, AI generates fresh per-client and per-send.
Audit-friendly client reporting
Every send is logged with the AI prompt, model version, output and delivery result. Client-facing reports pull from the same source of truth.
Quick scale-up for new clients
New client onboarding is push-provider-connect (10 min), tone-rules-defined (30 min), first three campaigns drafted in plain language (1 hour). Engineering hand-off is a single-page brief.
Example notifications PushPilot writes
Real iOS push notifications, fresh on every send, never repeated, tone-matched to your brand. Watch for the Send 2 rewrites — same campaign, brand-new copy, no marketer at the keyboard.
✨ Three things you haven't tried yet
All take under a minute. The third one is the one most teams skip and regret.
🌅 Twelve minutes before your usual time
You've gone three Mondays in a row. Don't let this be the one that breaks the run.
🔥 Two minutes from 10 in a row
Day 10 is the one that sticks. Most learners who hit it keep going to thirty.
🚀 Season 4 opens at 18:00 your time
Your pass is already loaded. New map, two new heroes, see you on the lobby.
New season opens at 18:00
Pass is loaded, lobby is filling up. Two new heroes and a new map to learn.
🥂 Late checkout is on us through July
Diamond stays this month, automatic 4pm checkout. No request, no email, just there.
☕ Quietly busy morning
Three reads if you've got 8 minutes, one big read, one short, one you'll send to a friend.
Two of the cards above show a Send 2 — that's the AI rewriting the same campaign for the same user a few sends later. No new template, no marketer at 11pm, no recycled subject line.
“We were running push for nine clients out of seven different OneSignal logins and a Firebase console we kept forgetting the password to. Consolidating into PushPilot meant the same team handled twice as many campaigns in half the time, and our senior strategists stopped writing copy in Google Docs at 11pm. The per-client tone rules alone saved us a hire.”
Founder
Lifecycle agency · 9 clients on retainer
Why teams pick PushPilot
Sits on top of Firebase Cloud Messaging or OneSignal. No SDK changes, no migration, no engineering project.
- Multiple push projects per organisation, one per client, each with its own provider connection (FCM or OneSignal), tone rules and frequency caps.
- Layers on top of your clients' existing delivery infrastructure, nothing changes about their FCM or OneSignal stack, hand-back is trivial.
- Tone constraints per campaign let one workspace serve a SaaS client and a wellness client without any cross-contamination of voice.
- Frequency caps are scoped per push project, your portfolio doesn't fight itself for impressions in a shared cap.
- Audit log captures the AI prompt, model version, output and delivery result for every send, so client reports pull from the same source of truth.
- Annual plans save up to 17%. Free plan covers small agencies running push for their first one or two clients.
Frequently asked questions
Can an agency run PushPilot for multiple client apps from one workspace?
Yes. PushPilot supports multiple push projects per organisation. Each client app gets its own push project with its own FCM or OneSignal connection, its own tone constraints, its own frequency caps and its own campaign list, but they share the workspace, the team, the audit log and the billing account. Your strategists switch clients in one click and never log in to a separate console.
How are client credentials kept separate and secure?
Provider credentials (FCM service-account JSON, OneSignal API keys) are encrypted with Fernet (AES-128 in CBC mode with HMAC) at rest, with the encryption key stored separately from the database. Credentials are scoped per push project, so client A's keys never touch client B's data path. PushPilot never logs or returns decrypted credentials.
Can different team members have access to different clients?
Yes, organisation membership and role-based permissions scope what each team member can see and do. A strategist assigned to client A doesn't need to see client B's campaigns or credentials. The full audit log shows who did what for which client.
Does each client need their own PushPilot subscription, or can the agency cover them?
Most agencies pay for one PushPilot subscription on the agency's organisation and run all client push projects from there. Billing, plan limits and quotas are per-organisation. If a client wants to take ownership of their PushPilot subscription at the end of an engagement, the agency can hand the push project (and its connected FCM or OneSignal credentials) to a new organisation.
How fast can an agency onboard a new client onto PushPilot?
Connect the client's FCM or OneSignal in about 10 minutes (the agency or the client's engineer pastes the FCM service-account.json or the OneSignal App ID + REST API Key). Configure the client's tone rules, frequency caps and audience topics in another 30 minutes. Author the first three campaigns from plain-language descriptions in roughly an hour. Most agencies have a new client live and shipping campaigns the same day.
Does the agency keep ownership of the campaign templates and AI prompts?
Yes. Campaign descriptions, tone constraints, audience filters and AI prompts live inside your agency's PushPilot organisation. Per-client tone rules can be templated and re-used as starting points for new client onboarding, so the institutional knowledge your senior strategists build up compounds across the portfolio.
Related solutions & resources
Try it free
Ship your first agencies push campaign in 4 minutes
Connect Firebase or OneSignal, paste the campaign description, watch the AI write your notifications. Free plan, no credit card.