One messaging channel. Every surface.
Reach users wherever they are — in-app, push, or SMS — from one channel, with progressive native-device reach: in the product, on their device, or on any phone.
In-app
in the product
Push
on their device
SMS
any phone
Everything you’d expect.
A visual builder for in-app messages, push, and SMS, with audience targeting, A/B testing on one shared experiment engine, and per-message stats — three point tools collapsed into one channel.
- Three flavors, one channel: in-app (modals, banners, tooltips, inbox), push, and SMS.
- Progressive reach — escalate in-app → push → SMS in a single journey.
- Real-time, behavior- and entitlement-triggered; attributed to MRR.
Replaces: Intercom · Appcues · Pendo · OneSignal · Braze · Twilio · Attentive
The difference: one journey escalates across surfaces — an in-app banner when they’re in the product, a push when they’ve left, an SMS when a payment fails — each priced to their plan and attributed to the MRR it moves. You replace three stitched-together tools with one channel on one customer record.
One channel, three ways to reach them.
Progressive native-device reach — in the product, on their device, or on any phone — escalated in a single journey.
In-app messaging
Reach users at peak intent — inside the product.
Modals, slide-ins and banners, tooltips and hotspots, and a persistent in-app inbox — fired by live behavior and entitlements. The headline move: a contextual paywall fires the instant a user hits a gate, priced to their plan, one click to upgrade.
- Modals, banners, tooltips/hotspots, and an in-app inbox.
- Contextual paywalls priced to each user’s plan.
- Real-time, behavior- and entitlement-triggered targeting.
Replaces: Intercom (in-app) · Appcues · Pendo · Userpilot · Chameleon
Unlock advanced reports
Available on Pro · $49/mo · priced to your plan
Fires the moment they hit the gate → attributed to MRR
Push notifications
Reach them after they’ve left — same trigger, same loop.
Web and mobile push for re-engagement and escalation when a user isn’t in the product. A journey shows an in-app message first, then escalates to push once they’ve left — and, when the owner enables it, the push also lands in the in-app inbox so nothing is missed. Delivery is wrapped (APNs/FCM), not built.
- Web and mobile push from one builder — delivery wrapped (APNs/FCM).
- Escalates from an in-app message inside one journey.
- A strong fit for mobile-first and push-capable products.
Replaces: OneSignal · Braze · Airship · Firebase (FCM)
Acme
nowYour workspace is waiting — finish in 2 steps
Reaches them off-app → still tied to their plan
SMS
The escalation that follows the money.
Text for the highest-intent moments — led by dunning and failed-payment recovery (“your payment failed, tap to fix”). It fires from the same billing events Poily owns, so a recovery text links straight to the subscription it saves. Bring your own number (10DLC); Poily wraps the carrier and handles consent and opt-out. Premium opt-in.
- Led by failed-payment recovery, tied to recovered MRR.
- Bring your own number (10DLC); consent & opt-out handled.
- Premium opt-in — the top rung of the reach ladder.
Replaces: Twilio (raw) · Attentive · Klaviyo (SMS) · Postscript
Acme: your payment didn’t go through. Tap to update your card and keep Pro — acme.io/fix
SMS · from your number
Recovered
$588MRR
Poily vs a standalone stitched stack.
| Capability | stitched stack | Poily |
|---|---|---|
| In-app messages (modals, banners, tooltips, inbox) | ||
| Web & mobile push | ||
| SMS | ||
| One channel instead of three tools | — | |
| Escalates across surfaces in one journey | — | |
| Knows each user’s plan & entitlements | — | |
| Conversions & recovery attributed to MRR | — | |
| One customer record across every channel | — |
Questions, answered.
What are the three flavors?
In-app messages (modals, banners, tooltips, and an inbox), push notifications (web and mobile), and SMS. One channel, three ways to reach a user — in the product, on their device, or on any phone.
What is “progressive reach”?
A single journey escalates by context: an in-app message while they’re in the product, a push once they’ve left, and an SMS for what truly moves money — like a failed-payment recovery. Email runs alongside as the async baseline.
How is this different from Intercom, OneSignal, or Twilio?
Those are three separate tools that don’t know your plans, billing, or each other. Poily is one messaging channel that fires from the same entitlements and event stream, escalates across surfaces in one journey, and attributes every conversion or recovery to MRR.
Can I show a paywall when someone hits a limit?
Yes — that’s the in-app headline use case. The moment a user hits a gate, a contextual paywall fires, priced to their plan, with a one-click upgrade.
Do all three flavors come on every plan?
In-app is the core; push and SMS are enabled per plan and per tenant, with SMS a premium opt-in (bring your own number). You turn on the surfaces that fit your product.
Related channels
Activation & lifecycle works best alongside these.