OneSignal StrawberryAutomate your push notification review with an AI agent
A companion reads your last twenty sends together, reports what the winners had in common, and drafts the next one without sending it.
Reviewing the last twenty pushes properly means exporting three reports and cross-referencing them by hand, so nobody does it and the sends keep going out on a rhythm.
A companion reads all twenty at once, with their copy, their audience and their delivery and click figures, and tells you what the two winners shared. Then it drafts the next one and stops.
You connect OneSignal once and see exactly what it can reach before you allow it. A push cannot be recalled, so sending waits for you every time.
| Step | OneSignal | Strawberry companion |
|---|---|---|
| Delivery infrastructure and opt-in handling | The product. Not replicable | Reads the delivery data back and says which segments are real |
| Comparing twenty past sends to find the pattern | A chart per message | Reads them together and reports what the winners share |
| Checking whether a segment definition still holds | Visible if you go looking | Audits the definitions against current events |
| Pressing send | One click | Proposes, and waits for you |
What actually happened to the last twenty sends?
A companion pulls each notification with its delivery and click figures, then lines them up next to what they said and who they went to. The two that did well were both sent before 9am and both contained a number. The worst went to a segment of 40,000 that has not been rebuilt since launch.
That is a claim you can act on this week. The dashboard gives you a chart per message; reading twenty together is the part that needed a person and an afternoon.
Segments that stopped meaning what they were named
“New users” was written when onboarding had four steps.
“Engaged” was based on an event your app stopped emitting in March. The segment still has people in it and the sends still go out.
A companion reads every segment definition against the events your product currently emits and reports the ones whose logic references something that no longer happens.
How does a draft push stay a draft?
A companion composes the notification, shows you the segment it targets and the estimated audience size, and stops. You send.
That is the right way round for anything reaching a stranger’s lock screen, and it is what keeps a broken merge token from waking 200,000 people.
- Audience size shown before approval, so a mis-targeted segment gets caught at the review step.
- Copy proposed with the delivery history of similar messages attached.
- No send happens because a model inferred that one was due.
The outside context a dashboard cannot see
A push campaign for a retail app performs differently in a week when a competitor is running a sale. A companion checks the outside world and reads your numbers in the same sitting.
It then closes the loop into everything else you have connected: the summary written into your reporting doc, the anomaly raised as a task. That is generate a weekly metrics digest, filed with your marketing routines.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents