Push notifications that reach users after they’ve left.
Web and mobile push — announcements, re-engagement, and escalation for when a user isn’t in the product, fired by the same triggers as everything else.
Acme
nowYour workspace is waiting — finish in 2 steps
Reaches them off-app → still tied to their plan
Everything you’d expect.
A visual builder for web and mobile push, with audience targeting, scheduling, delivery on the major push services, A/B testing, and per-message stats.
- Web and mobile push from one builder — no separate service to wire up.
- Triggered by live behavior and entitlements, in real time.
- Escalates from in-app and lands in the in-app inbox when enabled.
Replaces: OneSignal · Braze · Airship · Firebase (FCM)
The difference: push fires off the same event stream and entitlements as every other channel, and escalates from an in-app message inside one journey — so you reach a user the moment they’ve left, still tied to their plan and still attributed to the MRR it drives. Not a standalone blaster that knows nothing about your product.
Built for the whole funnel.
Web & mobile push
Reach users on the web and on their device from one composer — announcements, re-engagement, and time-sensitive nudges.
Behavior-triggered targeting
Fire on live behavior and entitlements in real time — “Pro trials who went quiet,” not a stale exported list.
Escalates from in-app
A journey shows an in-app message first, then escalates to push once the user has left the product — one flow, not two tools.
Lands in the inbox
When the owner enables it, a push also lands in the in-app inbox, so nothing is missed while a user was offline.
Delivery, wrapped
Delivery runs on the major push services (APNs/FCM) under the hood — the reach without wiring up and maintaining the pipes.
Attributed to MRR
Because the tap and the subscription live on one record, you see the revenue each push actually drove — not just open rates.
Poily vs a standalone push tool.
| Capability | push tool | Poily |
|---|---|---|
| Web & mobile push | ||
| Behavior-based targeting | ||
| A/B testing & scheduling | ||
| Knows the user’s plan & entitlements | — | |
| Escalates from an in-app message | — | |
| Conversions attributed to MRR | — | |
| One customer record across every channel | — |
Questions, answered.
Web push, mobile push, or both?
Both — send web push and mobile push from the same builder, with delivery handled on the major push services under the hood.
How is this different from OneSignal or Braze?
Those deliver push but don’t know your plans, billing, or the message you just showed in-app. Poily fires push off the same entitlements and event stream, escalates it from an in-app message in one journey, and attributes conversions to MRR.
Can push escalate from an in-app message?
Yes — that’s the point. A journey shows an in-app message while the user is in the product and escalates to push once they’ve left, all on one customer record.
Do I need my own push infrastructure?
No — delivery runs on the major push services (APNs/FCM) under the hood. You get the reach without building or maintaining the pipes.
Is push available on every plan?
Push is part of the Messaging family and is enabled per plan and per tenant — a strong fit for mobile-first and push-capable products.
Related channels
Activation & lifecycle works best alongside these.