1. What is customer retention software?
Customer retention software is technology that helps a business increase repeat engagement, repeat purchases, renewals or customer relationships, through capabilities such as loyalty, lifecycle communication, segmentation, automation, customer data management and reactivation. It is an umbrella term rather than a product category. No single vendor delivers all of those capabilities well, and the platforms that compete for the search term are frequently complements rather than alternatives.
Search for "customer retention software" and you will be shown a points engine for Shopify stores, an enterprise journey orchestration platform, a CRM, a data infrastructure product and a digital stamp card tool — on the same results page, ranked as though they were competing for the same purchase. They are not. The reason the category is confusing is that retention is an outcome and software is a tool, and an outcome can be produced by several unrelated mechanisms.
Customer retention software
Technology that helps a business increase the rate at which existing customers return, purchase again, renew, or maintain an active relationship. In practice the term spans seven distinct software categories — loyalty, lifecycle marketing, CRM, customer data platforms, customer engagement platforms, win-back and churn-deflection tooling, and wallet-based engagement — each of which addresses a different part of the retention problem.
What retention software can help a business do
Across the whole landscape, retention software supports ten jobs. Almost no platform does more than four of them properly, which is why the list is worth reading as a menu rather than a specification.
- Identify customers — recognise a returning person at all, which for a cash or walk-in business is often the entire problem
- Segment customers — group them by recency, frequency, value, tier, product affinity or lifecycle stage
- Automate communication — trigger messages from events rather than from someone remembering
- Reward repeat behaviour — points, stamps, tiers, referrals, member pricing, perks
- Recover inactive customers — detect a lapse and act on it before it becomes permanent
- Manage a loyalty programme — the administrative reality of balances, expiry, redemptions and fraud
- Personalise campaigns — content that differs by customer, not a merge field in a blast
- Measure retention — cohort retention, repeat purchase rate, churn, frequency
- Increase engagement — give the customer a reason to interact between purchases
- Understand customer lifetime value — connect retention work to money rather than to opens and clicks
Retention is an outcome. Software is a tool.
This distinction sounds pedantic and it is the single most expensive thing buyers get wrong. Retention is a result: more customers coming back more often, for longer. Software is one of several inputs that can produce it — alongside product quality, pricing, service, convenience and staff behaviour, none of which any platform can fix.
The practical consequence is that you cannot evaluate retention software against "does it improve retention?" — every vendor will say yes and none of them can prove it for your business. You can only evaluate it against a mechanism: does this tool change the specific customer behaviour I have identified as my problem? A brand losing customers after the first purchase and a gym losing members who stopped attending have different problems, and the correct software differs accordingly — even though both would describe themselves as having a retention problem.
Before looking at any tool, answer this: if your retention rate improved next quarter, what would customers have done differently? If the answer is "come back a fourth time instead of stopping at three," you have a frequency problem and probably need an incentive. If it is "opened the renewal email," you have a communication problem. If it is "not cancelled at the cancel screen," you have a deflection problem. If it is "not left because the product disappointed them," no software on this page will help, and buying one will cost you a year.
- Customer retention software is an umbrella over seven distinct categories, not one product type.
- Ten capabilities span the landscape; individual platforms typically deliver three or four.
- Retention is an outcome; software is one input. Evaluate tools on mechanism, not on the outcome.
2. What should customer retention software do?
Retention software should do at least one of four jobs well: give customers a reason to return, reach them at the right moment, tell you who is slipping away, or intervene at the point of leaving. Underneath those four jobs sit fourteen capabilities — customer data, segmentation, personalisation, loyalty, rewards, lifecycle automation, win-back, reactivation, messaging, wallet engagement, analytics, reporting, integrations and testing. The feature matrix below maps each capability to the retention use case it serves and the software category that usually owns it, so you can see immediately whether one platform can cover your requirements or whether you are buying two.
Most feature comparisons fail because they list capabilities without saying which retention job each one performs. A segmentation engine and a points engine are both "features," but one tells you who to talk to and the other gives them a reason to listen. The matrix below is built the other way round: capability first, then the retention use case it actually serves, then the category of software that normally owns it.
Fourteen capabilities, each mapped to what it does, the retention use case it serves, and the software category that typically owns it. Use it in two directions: read down the capability column to write a requirements list, or read across from a use case to find out which category you should be shortlisting. Cite or adapt with attribution.
| Capability | What it does | Retention use case | Typical software category |
|---|---|---|---|
| Customer data | Collects and unifies customer records from web, app, point of sale and back office into one profile | Knowing that today's buyer is the same person who bought in March | CDP · CRM · lifecycle platform |
| Segmentation | Groups customers by recency, frequency, value, tier, product or lifecycle stage | Targeting lapsed, at-risk, new and VIP customers separately | Lifecycle platform · CDP · engagement platform |
| Personalisation | Varies content, offer or timing per customer | Making a return offer relevant enough to act on | Lifecycle platform · engagement platform |
| Loyalty | Runs the programme mechanic — points, stamps, tiers, membership | Giving customers a structured reason to come back | Loyalty software · wallet engagement |
| Rewards | Issues, tracks, expires and redeems the reward itself | Converting accumulated behaviour into a return visit | Loyalty software · POS loyalty |
| Lifecycle automation | Triggers journeys from behavioural events | Post-purchase, replenishment, renewal and onboarding sequences | Lifecycle platform · engagement platform |
| Win-back | Detects a lapse against a defined cycle and messages accordingly | Recovering customers before they are permanently gone | Lifecycle platform (as a flow, not a product) |
| Reactivation | Re-engages dormant contacts with a stronger, time-boxed offer | Bringing back a long-dormant list segment | Lifecycle platform · loyalty platform with RFM |
| Messaging | Actually delivers email, SMS, push, WhatsApp or in-app messages | Every campaign you plan depends on this existing somewhere | Lifecycle platform · engagement platform · ESP |
| Wallet engagement | Issues Apple Wallet and Google Wallet passes and updates them after issue | A persistent branded touchpoint with no app to install | Wallet engagement platform |
| Analytics | Measures retention rate, repeat purchase rate, cohorts, frequency, CLV | Knowing whether retention actually improved | CDP · lifecycle platform · BI |
| Reporting | Presents programme performance to people who did not build it | Justifying the spend and diagnosing what stopped working | All categories, at very different depths |
| Integrations | Connects the retention stack to commerce, POS, support and data systems | Making loyalty state visible to the tool that sends the message | All categories — the most common point of failure |
| Testing | A/B and holdout testing of offers, timing and creative | Proving the programme caused the behaviour rather than coinciding with it | Lifecycle platform · engagement platform |
Integrations. The most common failure in a retention stack is not a missing feature — it is that the loyalty state lives in one system and the messages are sent from another, and the two do not talk. If your points balance sits in a loyalty app and your email platform cannot read it, then "your reward is ready" is not a campaign you can run, however clearly both vendors listed the capability. Ask for the specific data fields that sync, in which direction, and how often, before you buy either tool.
The four jobs, underneath the fourteen capabilities
Compress the matrix and every retention platform is doing at least one of four things. Naming yours narrows the field faster than any feature list.
- Give the customer a reason to return. An incentive, a balance, a status, a stored value, a perk. Owned by loyalty and wallet platforms.
- Reach the customer at the right moment. A triggered message tied to a behaviour. Owned by lifecycle and engagement platforms.
- Tell you who is slipping away. Recency and frequency analysis, cohort retention, at-risk scoring. Owned by CDPs, analytics and RFM-capable loyalty tools.
- Intervene at the point of leaving. A cancel-flow offer, a failed-payment retry, a renewal save. Owned by churn-deflection tooling, and only relevant if you have a subscription.
- Fourteen capabilities, four underlying jobs — name the job before comparing features.
- Loyalty owns the incentive; lifecycle owns the timing; CDPs own the data; deflection owns the exit.
- Integration between loyalty state and messaging is where most stacks quietly fail.
3. The main types of customer retention software
There are seven categories: loyalty software, lifecycle marketing platforms, CRM platforms, customer data platforms, customer engagement platforms, win-back and churn-deflection tooling, and wallet-based engagement. Each solves a different retention problem, and the fastest way to identify yours is to ask which of the four jobs from Section 2 you need done — give a reason to return, reach at the right moment, see who is slipping away, or intervene at the exit. Categories are not interchangeable: a loyalty platform will not run a behavioural journey, and a lifecycle platform will not issue a reward.
Seven categories grouped by the retention job each performs, with verified example vendors under each. Find your job in the left column of the map and the categories that serve it are on the same row. Cite or adapt with attribution.
1. Loyalty software
What it is. Software that runs the incentive mechanic of a retention programme and holds the member data behind it. Points, stamps, tiers, referrals, membership, reward issuance, balance tracking, expiry and redemption.
Best for: repeat purchases, rewards, points, stamps, membership, customer loyalty.
What it does not do. This is the part vendors underplay. Most ecommerce loyalty platforms do not send campaigns. Smile.io's own help documentation is explicit that you need to connect an email marketing app — and its segment guides are titled "create a segment within Klaviyo" and "create segments in Mailchimp," meaning the segments are built in the messaging tool from Smile's loyalty data, not in Smile. Smile itself sends only nine transactional notification emails. LoyaltyLion sends three by its developer documentation, or five by its help centre, which adds points-expiry and referral emails. Stamped sends none at all — it passes order data to Klaviyo, Attentive or Postscript. So a loyalty platform is normally half a retention stack, and the other half is a bill you have not yet budgeted for.
Where it fits: the incentive layer. Buy it when the behaviour you want to change is frequency, and when a structured reward would plausibly change it.
2. Lifecycle marketing platforms
What it is. Software that triggers automated journeys from behavioural events and delivers messages across channels. Klaviyo is the archetype for consumer ecommerce; it now describes itself as an "autonomous B2C CRM" and an AI marketing and service platform rather than an email tool.
Best for: automated customer journeys, email, SMS, behavioural messaging, lifecycle campaigns, post-purchase and win-back flows.
What it does not do. Klaviyo has no native loyalty engine. Its own guidance on loyalty software defines the category as products that "help your brand create loyalty programs while centralizing points, tiers, rewards, and engagement data" — and then lists the third-party platforms Klaviyo integrates with to provide it, rather than a Klaviyo feature. If you need points, you are buying two products.
Where it fits: the timing layer. Buy it when you know what you want to say and the problem is saying it at the right moment, to the right subset, without anyone remembering to press send.
3. CRM platforms
What it is. Systems of record for customers, accounts and the interactions around them, with workflow on top. HubSpot and Salesforce are the reference examples.
Best for: customer relationship management, sales and customer records, relationship workflows, account health, renewals with a human owner.
What it does not do. A CRM is built for retention that a person drives. HubSpot's retention machinery sits in Service Hub — customer success workspace, health scores, NPS and CSAT surveys, help desk — while Marketing Hub's own stated purpose is to "attract, convert, and engage high-intent visitors," which is acquisition. Neither hub has a native loyalty engine.
Where it fits: the relationship layer. Buy it when retention means renewals and named accounts, not purchase frequency across thousands of anonymous consumers.
4. Customer data platforms
What it is. Infrastructure that collects customer data across sources, resolves identities into unified profiles, and activates audiences into downstream tools. Twilio Segment is the reference product; Salesforce's equivalent is now called Data 360, having been renamed from Data Cloud.
Best for: customer data unification, identity resolution, segmentation, audience activation.
What it does not do. It does not retain anyone. Segment's engagement module natively supports three channels — SMS, email and WhatsApp — and everything else is activation into other tools. A CDP makes retention possible downstream; it performs none of it itself.
Where it fits: the data layer, and usually the third purchase rather than the first. Buy it when you have a working retention programme that is being held back because the data is fragmented — not before.
5. Customer engagement platforms
What it is. Cross-channel orchestration at scale, typically for app-first consumer brands. Braze describes itself as a customer engagement platform powering "customer-centric interactions between consumers and brands in real-time"; Insider One positions as an "Agentic Customer Engagement Platform" and acquired Bluecore in May 2026 to strengthen its data layer.
Best for: multi-channel engagement, messaging, segmentation, automation, real-time decisioning across large audiences.
What it does not do. Neither has a native loyalty engine — Braze lists loyalty as a partner category, naming vendors such as Talon.One and Open Loyalty — and neither publishes pricing. Braze states plainly that it does not believe in a one-size-fits-all rate card; Insider One has no pricing page at all.
Where it fits: the timing layer at enterprise scale. Buy it when message volume, channel count and real-time decisioning genuinely exceed what a lifecycle platform can carry — and when you have the team to operate it.
6. Win-back and reactivation tooling
What it is. Two different things wearing one name, and separating them is the single most useful thing in this section.
For business-to-consumer retention, win-back is a feature, not a category. No credible vendor sells a standalone B2C "win-back platform." Klaviyo documents its winback flow as a series of messages to customers who previously engaged but have not interacted for a defined period, triggered off a Placed Order metric, and files it under lifecycle flows. Loyalty platforms with RFM analysis do the same thing from the other direction — Boomerangme automatically sorts customers into segments including "Sleeping," "At risk" and "Needs attention," and fires messaging on the transition.
For subscription businesses, churn deflection is a genuine standalone category. Churnkey, Churn Buster, Raaft and Paddle Retain intercept a discrete event — a clicked cancel button or a declined card — and respond in the moment with an offer, a pause, or an adaptive payment retry. Churnkey publishes a Starter tier at $250 per month billed yearly for businesses under $5,000 monthly churn volume; Raaft publishes a free tier, $79 per month for 100 sessions and $299 per month for unlimited. Chargebee Retention is no longer a standalone product — it is now part of Chargebee Growth — and Paddle Retain is included with Paddle Billing at no extra cost rather than sold separately.
Best for: lapsed customers, churn prevention, reactivation — but check which of the two problems you have first. These tools cannot substitute for each other: a cancellation-deflection tool has no way to detect a retail customer who simply stopped coming.
7. Wallet-based customer engagement
What it is. Retention delivered through a pass saved in Apple Wallet or Google Wallet — a loyalty card, membership card, coupon or reward card — which the business updates after issue. Enrolment is a QR scan or a save link: no app, no account, no download by either party.
Best for: digital loyalty cards, membership cards, coupons, rewards, and a persistent branded touchpoint for businesses whose customers visit in person.
What it does not do. It is not a general-purpose messaging channel, and Section 10 sets out precisely what Apple and Google document. It is also the category with the widest gap between marketing claims and verified capability — several loyalty vendors advertise a "digital loyalty card" that is a web page, not a wallet pass.
Where it fits: the incentive layer and a persistent presence layer, for businesses that would otherwise have no way to reach a customer between visits.
Three of the seven — loyalty, wallet and deflection — change what the customer experiences. Two — lifecycle and engagement — change when you speak to them. Two — CDP and CRM — change what you can see. Buyers get into trouble by shopping in the third group when their problem is in the first. Data clarity feels like progress and rarely produces a returning customer on its own.
- Seven categories, four jobs — loyalty and wallet own the incentive, lifecycle and engagement own the timing, CDP and CRM own visibility, deflection owns the exit.
- Most ecommerce loyalty platforms cannot send campaigns; most lifecycle platforms cannot issue rewards.
- B2C win-back is a flow inside a lifecycle tool; subscription churn deflection is a real, separate product category.
4. Loyalty software vs customer retention software
Loyalty software is one category inside the customer retention software landscape, not a synonym for it. Loyalty software runs the incentive — points, stamps, tiers, rewards, referrals — and holds member data. Customer retention software is the umbrella that also covers lifecycle marketing, CRM, customer data platforms, engagement platforms, win-back tooling and wallet engagement. Every loyalty platform is retention software; most retention software is not loyalty software; and critically, not every retention platform provides loyalty, and not every loyalty platform provides lifecycle marketing. That double gap is why so many stacks need two vendors.
The terms are used interchangeably in marketing copy and they should not be. The confusion has a direct cost: a business that buys "retention software" expecting a points programme and receives a journey builder has bought the wrong half of its stack, and will discover this three weeks into implementation.
The matrix below is the clearest way to see it. Read the rows as capabilities and the columns as categories, and note how few cells are filled in any single column.
Twelve capabilities against the five categories most often confused with one another. Native means the category typically ships the capability itself. Integration means the capability is normally reached by connecting a second vendor. This is the table to screenshot before a vendor call.
| Capability | Loyalty software | Lifecycle platform | CRM | CDP | Wallet engagement |
|---|---|---|---|---|---|
| Points, stamps & tiers | Native | No | No | No | Native |
| Reward issuance & redemption | Native | No | No | No | Native |
| Referrals | Native | Integration | No | No | Varies |
| Behavioural journeys | Rarely | Native | Partial | Partial | Basic triggers |
| Email & SMS sending | Transactional only | Native | Partial / gated | Limited channels | Usually not |
| Advanced segmentation | Often gated or absent | Native | Account-shaped | Native — strongest | Tag / tier level |
| Identity resolution | No | Partial | Partial | Native | No |
| Account & relationship workflow | No | No | Native | No | No |
| Win-back detection | Only with RFM | Native (as a flow) | Manual | Native (as an audience) | Varies — verify |
| Persistent on-device presence | No | No | No | No | Native — the whole point |
| Works without a website or app | POS-tied ones do | No | Partial | No | Yes |
| Retention analytics | Programme-level | Cohort & revenue | Account health | Native | Install, visit, campaign |
Not every retention platform provides loyalty. Klaviyo, Braze, HubSpot, Twilio Segment and Insider One have no native points-and-tiers engine between them — every one of them reaches loyalty through a partner or marketplace app. Not every loyalty platform provides full lifecycle marketing. Smile.io, LoyaltyLion and Stamped all depend on a separate messaging platform to run campaigns, and Yotpo stopped sending email and SMS itself after deprecating those products at the end of 2025. Salesforce is the notable exception with a genuine first-party loyalty engine — at $20,000 per organisation per month to start.
When you need both, and when you do not
- You need both when the retention mechanic is an incentive and the programme depends on triggered messaging: an ecommerce brand running points plus post-purchase and win-back flows. Budget for two subscriptions and one integration.
- You need loyalty only when the customer relationship is in-person and high-frequency, and the card itself carries the message: a coffee shop, a salon, a gym. The stamp count on the card does the work a campaign would otherwise do.
- You need lifecycle only when your product has a natural repurchase rhythm and no incentive is required to trigger it: consumables, replenishment, subscriptions. A reminder beats a discount, and costs less.
- You need neither when the churn cause is product, price or service. Diagnose before you buy; software applied to a service problem produces a well-automated exit.
- Loyalty software is a subset of retention software, not a synonym.
- Five major retention platforms have no native loyalty engine; four major loyalty platforms cannot send campaigns.
- Ecommerce brands usually need both categories. In-person businesses often need only one.
5. Customer retention software comparison
Fourteen platforms are compared below, chosen because each genuinely serves customer-retention buying intent — not because they are famous. The headline findings: five of the best-known retention platforms have no native loyalty engine at all; four of the best-known loyalty platforms cannot send a marketing campaign without a second vendor; wallet support is claimed far more often than it is verifiable; and published pricing ranges from $0 to $45,000 per organisation per month, which is why any "average cost of retention software" figure is meaningless. Every capability below was checked against the vendor's own documentation or pricing page in August 2026. Where a claim could not be verified from an official source, it says so rather than guessing.
How platforms were selected — and what was excluded
A vendor is included here only if it satisfies three tests: it is currently positioned by its own marketing as serving retention, loyalty, lifecycle or churn; it owns at least one of the four retention jobs from Section 2 natively rather than through a partner; and its capabilities and commercial model can be verified from its own published material. That produced fourteen platforms for the main comparison in Table 3, across all seven categories. Six further vendors — PassKit, Loopy Loyalty and Boomerangme in the wallet category, and Churn Buster, Raaft and Paddle Retain in churn deflection — passed the same verification but are compared in the sections where they are relevant rather than in the master table: wallet capability in Table 7, pricing in Table 11 and Section 14. That keeps Table 3 readable without hiding anything; every vendor named anywhere in this guide was verified to the same standard.
Several well-known names were deliberately excluded, and the reasons are as informative as the inclusions:
- Bloomreach now leads with "The AI Platform for Personalization" — it has repositioned toward personalisation and agentic commerce rather than retention.
- Emarsys no longer exists under that name; emarsys.com states that SAP Emarsys is now SAP Engagement Cloud. Citing "Emarsys" in a 2026 comparison would be citing a defunct brand.
- Standalone B2C "win-back software" vendors were searched for and not found. Everything ranking for the term was agency content marketing, not software. Section 3 explains why.
- Chargebee Retention is no longer a standalone product; it is now part of Chargebee Growth.
PushNotice publishes this guide and PushNotice appears in the comparison. It is included because wallet-based engagement is a real category that a retention buyer should evaluate, and excluding our own product from our own comparison table would be less honest, not more. It is described using the same verification standard as every other row, its limitations are listed in the same column as everyone else's, and Section 6 names five use cases where a different platform is the better answer. Section 16 gives the full treatment, including six things PushNotice does not do.
Fourteen platforms across seven categories, on ten dimensions. Capabilities verified against official vendor documentation and pricing pages, August 2026. "Not verified" means exactly that — the vendor does not publish it and we did not find it, so we did not assume it. Cite or adapt with attribution.
Table 3 is wide — scroll it horizontally, or print the page for the full grid.
| Platform | Primary retention approach | Best for | Loyalty | Lifecycle automation | Segmentation | Wallet support | Integrations | Pricing approach | Main limitation |
|---|---|---|---|---|---|---|---|---|---|
| Klaviyo | Behavioural lifecycle messaging off ecommerce events | Shopify and DTC brands needing post-purchase and win-back flows | None native — integrates third-party loyalty apps | Strong — flows, campaigns, AI agents | Strong, real-time | None native | Deep Shopify; marketplace apps | Active profile tiers + separate messaging credits + metered add-ons | No loyalty engine and no wallet; modular add-ons make the real bill hard to predict |
| Braze | Real-time cross-channel journey orchestration | App-first consumer brands at mid-market and enterprise scale | None native — partner category | Journey orchestration plus AI decisioning across email, push, in-app, SMS, RCS and WhatsApp | 100+ out-of-the-box filters | Partner only — PassKit named in Braze's own docs | 170+ turnkey partner integrations; Shopify named | Quote only — edition + monthly active users + action credits | No published pricing at all; assumes an app with the SDK installed |
| HubSpot | Service-led account retention and health scoring | B2B and services businesses with named accounts | None native — marketplace apps | Workflows around lifecycle stages, not purchase behaviour | Lists on the CRM object model | None native (Apple Pay at checkout is not a wallet pass) | Large app marketplace; 100+ Data Sync | Seats + marketing contacts; mandatory onboarding fees at Pro and Enterprise | Retention features split across two paid Hubs; SMS needs Pro plus an add-on and is US/Canada only |
| Salesforce | Assembled from separate clouds — loyalty, marketing, data, service | Enterprises that need a first-party loyalty engine at scale | Native — Loyalty Management (points, tiers, vouchers, referrals) | Journey orchestration in Marketing Cloud Next | Via Data 360 | Google Wallet native to Loyalty Management; Apple Wallet not verified | Deep across the Salesforce estate; AppExchange | Per org per month, billed annually, plus consumption credits | Loyalty Management starts at $20,000/org/month; Data 360 cost is unpublished |
| Twilio Segment | Data unification and audience activation | Teams whose retention is blocked by fragmented customer data | None | Engage journeys, three native channels | Native identity resolution, computed traits and audience building | No wallet channel | 550+ destinations; 700+ integrations advertised | Monthly tracked users; Connections from $0 / $120 — full CDP unpublished | Retains nobody on its own; MTU billing counts anonymous visitors |
| Insider One | Native CDP plus agentic cross-channel orchestration | Enterprise marketing teams running many channels | Not verified — no loyalty engine documented | Strong | Native CDP-backed | No wallet channel in its published list | Unlimited APIs and integrations in the platform fee | Quote only — monthly active users; no pricing page exists | Demo-gated enterprise motion; no loyalty and no in-store retention mechanic |
| Smile.io | Points, referrals and VIP tiers for Shopify stores | Small to mid-market Shopify and BigCommerce brands | Native — the whole product | Nine transactional emails only; no campaigns | None native — its docs tell you to use an email app | None ("Smile Wallet" was a consumer app, closed Oct 2024) | Klaviyo, Mailchimp, Omnisend, Gorgias, Recharge and more | Monthly order bands: Free / $15 / $79 / $199 monthly; $999 on annual billing; Enterprise quoted | Loyalty engine only — no segmentation, no campaigns, no SMS; Shopify and BigCommerce only |
| Yotpo Loyalty | Points, VIP tiers and referrals across several commerce platforms | Mid-market and enterprise ecommerce beyond Shopify | Native | None — Yotpo deprecated its own Email and SMS at the end of 2025 | Smart segments from the Premium tier only | Via partners (Novel; Passcreator by Fobi) — not native | Shopify, BigCommerce, Adobe Commerce, Salesforce B2C, Klaviyo, Attentive | Free; Pro from $199/mo incl. 500 orders then per-order overage; Premium and Enterprise quoted | VIP tiers and segmentation both sit behind unpublished Premium pricing; no messaging of its own |
| LoyaltyLion | Points, tiers and challenges with a genuine wallet pass | Shopify mid-market brands wanting loyalty plus a wallet card | Native | Three native emails; real flows run through Klaviyo | Analytics strong; native segment builder not verified | Native Apple and Google Wallet with device auto-detection — paid add-on | Klaviyo, Attentive, Omnisend, Shopify POS; headless API | Free for ≤400 orders/mo; Classic $199/mo incl. 500 orders; Advanced and Plus quoted | Two of four plans are quote-only, VIP tiers start at the quote-only Advanced plan, and the wallet add-on rate is unpublished |
| Marsello | Loyalty tied to POS and ecommerce data, activated through Marsello's own email and SMS | Omnichannel retail and hospitality, especially multi-site | Native | Native, but metered — prebuilt loyalty emails on all plans; marketing email and SMS are separately priced add-ons; conditional splits and segmented audiences on Accelerate | RFM on the entry plan; custom segments on Accelerate | Native Apple and Google Wallet passes on all plans | Lightspeed, Clover, Cin7, Heartland, Shopify, WooCommerce, BigCommerce, Ecwid | Per site: NZ$100 and NZ$200/mo (from US$60 / US$120) plus usage add-ons | Per-site pricing plus separately billed contacts and SMS credits makes multi-location cost hard to model; no free plan |
| Square Loyalty | Visit- and spend-based rewards inside the Square POS | Brick-and-mortar SMBs already processing on Square | Native | Automatic transactional texts; campaigns need Square Marketing | Not verified inside Loyalty itself | Apple Wallet pass native; Google Wallet not verified | Square only — POS, Online, Invoices, Marketing, Loyalty API | Included from Square Plus at $49/mo per location ($149 Premium) | Total lock-in to Square; no reach beyond it and no way to take the programme elsewhere |
| Stamped | Reviews, loyalty and replenishment-timing intelligence | Mid-market DTC brands buying two or three products together | Native | Timing intelligence ("Plays") but no sending — uses Klaviyo, Attentive or Postscript | Native smart segmentation | Not verified | Klaviyo, Attentive, Postscript, Gorgias, Shopify; 50+ | Per product on its own rate card: Reviews $199, Loyalty $299, Lifecycle $499; bundle from $798/mo. Cheaper self-serve Reviews tiers (from $23/mo) are sold via its Shopify App listing | Highest loyalty-only entry price here, and you still pay a separate platform to send anything |
| Churnkey | Cancellation deflection and failed-payment recovery | Subscription businesses losing customers at the cancel screen | Not applicable | Not applicable — intervenes at one moment | Cancellation-reason and adaptive-offer logic | Not applicable | Subscription billing stacks | Starter $250/mo billed yearly under $5k monthly churn volume; higher tiers quoted | Only relevant with a subscription; cannot detect a retail customer who simply stops coming |
| PushNotice (ours) | A branded wallet pass as a persistent, app-free customer touchpoint | Local and repeat-visit businesses with no app, no developer and no POS dependency | Native — stamp cards, membership, VIP reward cards, coupons | Manual and scheduled campaigns; no journey builder | Tag and loyalty-tier filters (Pro plan) | Native Apple and Google Wallet passes on every plan | No third-party integrations published | Audience-size tiers: Free / $29 / $79 per month, Agency quoted; no per-message fee | Wallet only — no email, SMS, CRM, CDP or POS; no published integrations and no journey builder |
What the table shows that a listicle would not
Klaviyo, Braze, HubSpot, Twilio Segment and Insider One — five of the most recommended "retention platforms" anywhere — have no native loyalty engine between them. Every one reaches points, tiers and rewards through a partner or marketplace app. Klaviyo's own article on loyalty software defines the category as products that "help your brand create loyalty programs while centralizing points, tiers, rewards, and engagement data" — and then recommends the third-party platforms it integrates with, rather than a Klaviyo feature. Braze's documentation files both mobile wallet and loyalty as partner categories, naming Talon.One and Open Loyalty among the loyalty partners and PassKit for wallet. If your retention problem needs an incentive, none of these five is a complete answer on its own.
Smile.io, LoyaltyLion, Yotpo and Stamped all sell loyalty and none of them can run your retention campaigns. Smile sends nine transactional emails and its own documentation says you will need an email marketing app — with the segments built inside Klaviyo or Mailchimp from Smile's loyalty data rather than inside Smile. LoyaltyLion sends three by its developer documentation and five by its help centre, which adds points-expiry and referral emails; we note both rather than picking one. Stamped sends none — it passes order data to Klaviyo, Attentive or Postscript. Yotpo deprecated its own Email and SMS products, with full decommissioning at the end of 2025, and directed customers to Attentive or Omnisend. The realistic ecommerce budget is two subscriptions, not one.
This is the claim most often flattened into a yes/no column, and it should not be. Verified for this guide: native and included (Marsello — Apple and Google Wallet passes on every plan, per its own pricing page and two help-centre articles). Native but separately priced (LoyaltyLion — "Loyalty Pass is a paid add-on… Pricing is based on the number of active pass installs," with the rate unpublished). Partner-delivered (Yotpo, via Novel or Passcreator by Fobi — a second vendor contract). Single platform only (Square — Apple Wallet confirmed on Square's own product page and April 2025 announcement; Google Wallet not found on any official Square page). Absent despite loyalty-card language (Smile.io, Stamped). Note especially that "Smile Wallet" was a discontinued consumer app closed in October 2024, not Apple Wallet support — any comparison citing it is wrong.
Braze states it does not believe in a one-size-fits-all rate card and publishes nothing. Insider One has no pricing page — /pricing returns a 404 — and confirms only that pricing is based on monthly active users. Salesforce's Data 360 is consumption-priced with no published figures, which means a total cost of ownership for a full Salesforce retention stack cannot be calculated from public information even though the Loyalty Management and Marketing Cloud list prices are published. Budget for a procurement cycle, not a checkout page.
Three things changed recently enough that any article written before mid-2026 is likely to be wrong. Salesforce Marketing Cloud is now branded Agentforce Marketing, and Data Cloud is now Data 360. Klaviyo now describes itself as an "autonomous B2C CRM", not an email and SMS platform, having added Customer Hub, Helpdesk, Customer Agent and Reviews. Segment.com now redirects to Twilio, and Segment is sold as Twilio Segment. If a comparison you are reading still uses the old names, treat its capability claims as equally stale.
A note on the one product in this table that does not belong to a category
Churnkey is included because subscription businesses searching for retention software are a real and distinct audience, and because they are otherwise served entirely by tools that cannot help them. If your customers leave by clicking cancel, no loyalty programme, wallet pass or lifecycle flow reaches them at the moment that matters — the intervention has to happen inside the cancellation flow. Conversely, if your customers leave by quietly not coming back, a deflection tool has nothing to intercept. It is the clearest example in this guide of two products that both call themselves retention software and cannot substitute for each other in either direction.
- Five major retention platforms have no native loyalty; four major loyalty platforms cannot send campaigns.
- Wallet support comes in five distinct forms — native and included, native but extra, partner-delivered, one platform only, or absent.
- Braze, Insider One and Salesforce Data 360 publish no usable price, so a like-for-like cost comparison across the category is impossible.
- Recent rebrands mean pre-2026 comparisons are describing products that have changed names and capabilities.
6. Best customer retention software by use case
There is no defensible universal number one, because the platforms are not competing for the same purchase. By use case: loyalty programmes — Smile.io for small Shopify stores, LoyaltyLion or Yotpo for mid-market ecommerce, Marsello for omnichannel retail, Salesforce Loyalty Management at enterprise scale. Lifecycle automation — Klaviyo for ecommerce, Braze for app-first brands at scale. Ecommerce retention — Klaviyo plus a loyalty platform, not either alone. Enterprise engagement — Braze or Insider One. Small business — Smile.io free tier, Square Loyalty if already on Square, or a wallet platform if neither applies. Win-back — a lifecycle flow for ecommerce, Churnkey for subscriptions. Wallet-based retention — Marsello for POS-integrated retail, PassKit for developer-led builds, PushNotice or Loopy Loyalty for small businesses without either. DTC — Klaviyo plus LoyaltyLion or Yotpo, plus deflection if you sell subscriptions.
Every recommendation below states who should not use it, because that is the half of a recommendation that saves money. A ranked list without disqualifiers is a list of vendors who paid for placement somewhere.
Eight retention use cases, each with the platform that fits, the reason, and the specific buyer who should look elsewhere. No overall ranking is given, because none is defensible.
| Use case | Strongest fit | Why it fits | Who should use it | Who should not | Main strength | Main limitation |
|---|---|---|---|---|---|---|
| Loyalty programmes | Smile.io (small) · LoyaltyLion or Yotpo (mid-market) · Marsello (omnichannel) · Salesforce Loyalty Management (enterprise) | These are the platforms where points, tiers and rewards are the product rather than an add-on | Businesses whose retention problem is purchase frequency and where a structured incentive would plausibly change it | Anyone who needs the loyalty tool to also run campaigns — none of the first three can | Mature programme mechanics: earning rules, tiers, expiry, redemption, fraud controls | All except Marsello depend on a separate messaging platform |
| Lifecycle automation | Klaviyo (ecommerce) · Braze (app-first, at scale) | Both are built around behavioural triggers and multi-channel journeys as the core product | Brands with enough purchase and browse data for triggers to be meaningful | Businesses with no digital purchase signal — a walk-in salon has nothing to trigger from | Timing: the right message fired by an event rather than a calendar | Neither issues a reward; the incentive is a second vendor |
| Ecommerce retention | Klaviyo plus a loyalty platform | The two halves — message timing and incentive — sit in different products, and both are needed | Shopify and BigCommerce brands past their first few hundred orders a month | Stores with too little order volume to justify two subscriptions; start with one | Post-purchase, replenishment and win-back flows enriched with loyalty state | Two bills, one integration, and a dependency on loyalty data syncing correctly |
| Enterprise engagement | Braze · Insider One | Real-time orchestration across many channels and very large audiences, with decisioning on top | Enterprises with an app, an engineering team and message volume that breaks smaller tools | Anyone without a procurement process — neither publishes a price or offers self-serve | Scale, channel breadth and real-time decisioning | No native loyalty in either; both assume digital-first customers |
| Small businesses | Smile.io free tier · Square Loyalty (if on Square) · a wallet platform (if neither) | Each launches without a developer and has a real entry point below $50 a month | Single-location and small multi-location businesses, and small online stores | Businesses that need lifecycle automation on day one — that is a bigger purchase | Time to launch, and predictable cost | Capability ceilings arrive quickly as the programme matures |
| Win-back campaigns | A lifecycle flow (ecommerce) · Churnkey (subscriptions) | The two problems are structurally different: silent lapse versus an explicit cancellation event | Ecommerce brands with a definable purchase cycle; subscription businesses losing people at cancel | Anyone buying a "win-back platform" for B2C — no such standalone product was found to exist | Ecommerce: recency-based targeting. Subscription: intervention at the exact moment of leaving | Neither works for the other's problem, in either direction |
| Wallet-based retention | Marsello (POS-integrated) · PassKit (developer-led) · PushNotice or Loopy Loyalty (small business) | These have verified Apple and Google Wallet pass issuance as a first-class capability, not a partner add-on | Businesses whose customers visit in person and who have no app and no intention of building one | Pure-online businesses whose customers would never use the card in a physical context | A persistent branded object on the phone, enrolled in seconds with no download | Wallet messaging is bounded by Apple's and Google's rules — see Section 10 |
| DTC brands | Klaviyo + LoyaltyLion or Yotpo · add Churnkey if you sell subscriptions | Covers the three DTC retention moments: first-to-second purchase, VIP status, and subscription cancellation | DTC brands with repeat-purchase potential and enough margin for an incentive | Single-purchase or very high-consideration products where repeat purchase is not realistic | Segment-level personalisation with loyalty status feeding the messaging | The stack costs more than most first-time buyers expect; VIP tiers are often quote-only |
Best for loyalty programmes
Why it fits. Loyalty platforms are the only category where earning rules, tiers, expiry, redemption and fraud handling are engineered as the core product rather than bolted on. Smile.io covers points, referrals and VIP tiers for Shopify and BigCommerce, with a genuine free plan up to 200 monthly orders. LoyaltyLion and Yotpo serve mid-market ecommerce, both with a real entry point of $199 per month. Marsello is the strongest fit where the programme spans a point of sale and an online store. Salesforce Loyalty Management is the only enterprise option here with a first-party engine — points, tiers, custom reward currencies, non-transactional rewards and referrals — at a published $20,000 per organisation per month to start.
Who should not. Anyone expecting the loyalty tool to also run their retention campaigns. Smile's own documentation is explicit that you connect an email marketing app and build the segments there, from Smile's loyalty data — and neither Smile nor Stamped sends marketing messages at all.
Best for lifecycle automation
Why it fits. Klaviyo is built around behavioural triggers on ecommerce events and rebuilt its flows engine in August 2026; its documented winback flow is the reference implementation of lapsed-customer messaging. Braze is the equivalent at enterprise scale, with journey orchestration and AI decisioning across email, push, in-app, SMS, RCS and WhatsApp.
Who should not. Businesses with no digital purchase signal. Behavioural automation needs behaviour to be recorded somewhere; a business whose transactions happen at a counter and never reach a system has nothing to trigger from until it fixes that first.
Best for ecommerce retention
Why it fits. Ecommerce retention needs both halves, and the market has settled on the split: lifecycle platform for the message, loyalty platform for the incentive. This is not a failure of the tools — it is how the category is structured, and pretending otherwise leads to a half-built programme.
Who should not. A store doing under a few hundred orders a month should buy one tool, not two, and should almost certainly buy the messaging one first: a discount programme with no way to tell anyone about it is worse than a well-timed email with no discount attached.
Best for enterprise customer engagement
Why it fits. At genuine enterprise scale — millions of users, a dozen channels, real-time decisioning — the constraint stops being features and becomes throughput and governance. Braze and Insider One are built for that. Their commercial models differ, though: Insider One publishes an all-inclusive platform fee covering unlimited channels, integrations and APIs, while Braze includes every channel in all four editions but meters volume through Action Credits alongside monthly active users.
Who should not. Anyone who wants to know what it costs before a sales conversation, and any organisation without an app, since a large share of the differentiated value in both platforms assumes one. Enterprise software is not automatically better retention software — it is better at scale, governance and orchestration, all of which are overhead if you do not have those problems.
Best for small businesses
Why it fits. The binding constraints for a small business are time, not features: no developer, no one to run campaigns, and no tolerance for a cost that scales unpredictably. Smile.io's free tier, Square's included loyalty at $49 per location per month, and wallet platforms starting between $25 and $29 per month all clear that bar. A wallet-based option is often the right answer specifically when the business has neither Shopify nor Square — it does not require a commerce platform or a point of sale to exist.
Who should not. A small business that genuinely needs behavioural journeys on day one. That is a real requirement for some subscription and services businesses, and it means a bigger purchase than any of the above.
Best for win-back campaigns
Why it fits. Ecommerce win-back is a targeting problem: define the normal purchase cycle, find everyone past it, and message them before the relationship goes cold. That is a flow inside a lifecycle platform, and Klaviyo documents it as exactly that. Subscription win-back is an interception problem: the customer has told you they are leaving and you have one screen to respond. Churnkey, Churn Buster, Raaft and Paddle Retain exist for that screen.
Who should not. Anyone shopping for standalone B2C "win-back software." We looked; the search results are agency content, not vendors. Buying into that framing means paying for a feature you already have.
Best for wallet-based retention
Why it fits. Three quite different buyers land here. A retailer with a point of sale wants the wallet card tied to transaction data — Marsello. A team with developers wants pass infrastructure and an API — PassKit, which publishes a full rate card from $39.50 per month plus per-pass volume pricing. A small business with neither wants a card it can launch this week — Loopy Loyalty from $25 per month, or PushNotice with a free tier and paid plans from $29.
Who should not. A business whose customers will never hold the card in a physical context. A wallet pass earns its place by being visible when the customer opens their wallet; if there is no counter, no door and no barcode moment, the pass has nothing to do between campaigns and a web-based programme will serve you better.
Best for DTC brands
Why it fits. DTC retention has three distinct pressure points and they need different tools: getting the second purchase (lifecycle flows), rewarding the top decile (loyalty tiers), and holding subscribers at cancellation (deflection). Stamped is worth a look for brands that want replenishment timing intelligence bundled with reviews and loyalty, at $798 per month for the three-product bundle — but note that it still relies on Klaviyo, Attentive or Postscript to send.
Who should not. Brands selling something people genuinely buy once. Retention software applied to a single-purchase product produces a well-instrumented flat line; referral and reactivation of the customer's network is the better investment there.
- No universal number one exists; the strongest platform depends entirely on the use case.
- Ecommerce and DTC realistically need two products; in-person businesses often need one.
- Every recommendation here comes with a disqualifier — read those first.
7. How to choose customer retention software
Work through thirteen steps in order, and note that the first three happen before you look at a single vendor. Define the retention problem, identify the customer behaviour you want to change, and choose the required retention mechanism — those three decide your category, and the category decision constrains everything that comes after it. Then evaluate data requirements, segmentation, automation, loyalty capability, communication channels, wallet support where relevant, integrations and analytics, calculate total cost, and finish with a real test on real customers. Buyers who start at step four end up comparing prices between products that solve different problems.
Step 1 — Define your retention problem
Write one sentence with a number in it. "Only 22% of first-time buyers place a second order." "Members stop attending around week seven and cancel at month four." "Half our reviews are five stars and we still see the same faces twice a year." If you cannot write that sentence, you do not yet have a software problem — you have a measurement problem, and Section 13 comes first.
Step 2 — Identify the customer behaviour you want to change
Convert the problem into a behaviour with a subject and a verb: customers do not return after their first purchase; members stop attending before they cancel; subscribers cancel rather than pause. Behaviour is what software can act on. "Improve loyalty" is not a behaviour.
Step 3 — Choose the required retention mechanism
Four mechanisms, from Section 2, and this single choice selects your category:
- An incentive — the customer needs a reason. Loyalty or wallet.
- A message at the right moment — the customer needs a prompt. Lifecycle or engagement.
- Visibility — you cannot see who is lapsing. CDP, analytics, or an RFM-capable loyalty tool.
- An intervention at the exit — the customer is actively leaving. Churn deflection.
Step 4 — Determine your customer-data requirements
Ask what the platform needs to know about a customer to do its job, and whether you actually have that data. A lifecycle platform needs purchase events. A loyalty platform needs identity at the moment of transaction — which for a cash business is the hard part, not the software. A CDP needs sources worth unifying. If your transaction data never reaches a system, fix that before buying anything that depends on it.
Step 5 — Evaluate segmentation
Test one segment specifically: "customers who have not purchased or visited in N days." That is the win-back segment and it is the most valuable one in retention. Not every platform can express it — Loopy Loyalty's documented filters cover stamps earned, rewards earned and rewards redeemed, with no recency filter documented, which means the lapsed segment is not natively addressable there. Ask every vendor to build that segment live in the demo.
Step 6 — Evaluate automation
Distinguish four tiers, because vendors use one word for all of them: manual send, scheduled send, event-triggered, and conditional journey with branching. Marsello's entry plan is basic email-only automation, with conditional splits and segmented audiences reserved for the higher tier; Boomerangme documents triggered auto-push plus RFM segment transitions, without publishing the full trigger list. Neither is a journey builder, and neither claims to be — but a feature grid saying "automation" hides the difference.
Step 7 — Evaluate loyalty capabilities
If you need loyalty, get the specific mechanic demonstrated: points versus stamps, tiers and thresholds, expiry rules, multi-location, staff scanning, and what happens on a refund. Check the tier gating too — VIP tiers are a $199-per-month feature at Smile.io, and a quote-only feature at both Yotpo and LoyaltyLion.
Step 8 — Evaluate communication channels
List the channels you will actually use and confirm each is included rather than adjacent. HubSpot's SMS requires Marketing Hub Professional plus a paid add-on and is limited to the United States and Canada on long code. Yotpo no longer sends email or SMS at all. Square Loyalty sends transactional texts automatically, but campaigns need Square Marketing, which is a different product.
Step 9 — Evaluate wallet support where relevant
Ask three questions and accept nothing softer: Apple Wallet, Google Wallet, or both? Native, or through a partner we would contract separately? Included in the plan, or priced separately — and at what rate? Section 5's Finding 3 shows why: five materially different answers all get written as "wallet support" on a comparison page.
Step 10 — Evaluate integrations
Name your systems and ask for the specific fields that sync, in which direction, and how often. The failure mode to design against is loyalty state living in one product and messaging in another with no reliable bridge — at which point "your reward is ready" is not a campaign you can run.
Step 11 — Evaluate analytics
Ask whether the platform reports outcomes or only activity. Enrolments, sends and redemptions are activity. Repeat purchase rate, cohort retention and revenue per customer are outcomes. A tool that only reports activity will make a failing programme look busy.
Step 12 — Calculate total cost
Model the subscription at three times your current customer count, then add implementation, integration, migration, messaging fees, design and staff time. Section 14 covers this properly. Watch for the structures that surprise people: per-site pricing (Marsello), per-active-pass add-ons (LoyaltyLion), per-order overage (Yotpo), monthly tracked users counted from anonymous visitors (Segment), and mandatory onboarding fees of $1,500 to $7,000 (HubSpot Professional and Enterprise).
Step 13 — Run a real customer test
Before signing anything annual: enrol yourself and a colleague as real customers, on an iPhone and an Android phone. Earn a reward. Trigger the lapse condition. Receive the message. Redeem at the counter or the checkout. Twenty minutes of this teaches you more than any demo, and it is where the gap between a feature grid and a working programme becomes visible.
Thirty checks in six groups. Print it, take it into demos, and ask for the documentation page behind every yes. If you cannot answer the first five, you are not ready to shortlist. Cite or adapt with attribution.
Group 1 — Problem definition (before any vendor)
- We can state our retention problem in one sentence containing a number
- We know the specific customer behaviour we want to change
- We know which of the four mechanisms would change it — incentive, message, visibility or intervention
- We know which of the seven categories that mechanism lives in
- We have ruled out that this is a product, price or service problem rather than a software one
Group 2 — Data and identity
- We can identify a returning customer at the moment of purchase or visit
- The data the platform needs already exists in a system we control
- We know where customer records live today and whether they are duplicated
- Consent capture and opt-out handling are covered for every channel we will use
- We can export our own customer data without asking support
Group 3 — Capability
- The vendor built our specific "not purchased in N days" segment live in the demo
- We know which of the four automation tiers the plan we are quoted actually includes
- The exact loyalty mechanic we need was demonstrated, including refunds and expiry
- Every channel we plan to use is included in our tier, not an add-on or a different product
- Wallet support was answered as Apple, Google, native or partner, included or extra
- Personalisation goes beyond a first-name merge field
- Frequency capping and quiet hours exist and apply across campaigns, not within one
Group 4 — Integration
- Our commerce platform, point of sale or booking system is named as a supported integration
- We know the specific fields that sync, in which direction, and how often
- Loyalty state is readable by whatever tool sends our messages
- An API exists and its documentation is readable before purchase
- We know what breaks if we later change point of sale or commerce platform
Group 5 — Measurement
- The platform reports outcome metrics, not only activity metrics
- We can see retention by cohort, not just totals
- We have chosen the one metric this purchase will be judged on, before buying
- A holdout or control group is possible, so we can attribute the change
Group 6 — Commercial
- We have modelled the cost at three times our current customer count
- We know every metered line: contacts, messages, orders, sites, seats, passes, credits
- Implementation, onboarding and migration fees are quoted in writing
- Someone on our team has completed a full customer journey on a real phone before signing
- Steps 1 to 3 select your category and matter more than any vendor comparison.
- Make every vendor build your lapsed-customer segment live — many cannot.
- Model cost at three times your current size, including every metered line.
8. Customer retention software by business size
Business size changes which problem is binding, not which software is "better." A small business is constrained by time and identification — it often cannot tell a returning customer from a new one. A growing business is constrained by manual effort. A mid-market business is constrained by fragmented data across channels. An enterprise is constrained by governance, scale and integration. Enterprise software is not automatically better retention software; it is better at enterprise problems, and every one of those capabilities is pure overhead to a business that does not have them.
| Stage | Binding constraint | Typical needs | Required features | Potential complexity | Recommended approach |
|---|---|---|---|---|---|
| Small business | Cannot identify returning customers at all; nobody has time to run campaigns | A programme that launches this week and runs itself | Fast enrolment, a visible mechanic, basic analytics, predictable price, no developer | Low — one tool, one workflow | One tool. A free or sub-$50 loyalty or wallet programme. Resist buying anything with the word "platform" in it |
| Growing business | The programme works but is run manually and does not scale past the owner | Automation of the moments that currently depend on someone remembering | Event triggers, real segmentation, a second channel, exportable data | Moderate — first integration appears here | Add automation to the working programme. Do not replace it — the migration cost is the hidden expense of this stage |
| Mid-market | Customer data is fragmented across store, site, support and point of sale | One view of the customer, and messaging that reflects it | Unified profiles, cross-channel journeys, cohort analytics, loyalty state syncing into messaging | Significant — this is where two-vendor stacks are normal | Lifecycle platform plus loyalty platform, integrated properly. Consider a CDP only if data really is the blocker |
| Enterprise | Scale, governance, compliance and integration with existing systems | Orchestration across many channels, markets, brands and teams | Identity resolution, real-time decisioning, permissioning, experimentation, audit | High — multi-quarter implementation is normal | Engagement platform plus a first-party loyalty engine plus a data layer. Expect a procurement cycle and unpublished pricing |
Buying up a stage. A growing business that buys a mid-market stack acquires an implementation project instead of a retention programme, and typically spends two quarters configuring something that replaces a working manual process with a half-configured automated one. The cost is rarely the licence — it is the six months in which nothing improved. Buy for the constraint you have now, and treat the next stage as a migration you will pay for later with a bigger budget and a clearer requirement.
It is better at governance, permissioning, multi-brand and multi-market complexity, real-time decisioning across very large audiences, and integrating with systems that already exist. It is not better at giving a coffee shop a reason for customers to come back on a Tuesday. Those capabilities are answers to problems of scale, and paying for answers to problems you do not have is the most reliable way to make retention software look like a bad investment.
- Size determines the binding constraint: identification, then manual effort, then data fragmentation, then governance.
- Buying one stage above your constraint buys an implementation project, not a retention programme.
- Enterprise capability is not general superiority — it is scale-specific, and overhead below that scale.
9. Customer retention software for ecommerce and DTC brands
Ecommerce retention is not one problem — it is seven, each occurring at a different point in the customer relationship, and each answered by a different capability. First purchase needs onboarding. Second purchase needs a prompt and often an incentive. Repeat purchase needs a mechanic. A lapsed customer needs recency detection. A VIP needs recognition. A churn-risk subscriber needs intervention. A renewal needs a reminder. The technology map below assigns a software category to each stage, which is the fastest way to see whether your current stack has a hole in it.
Seven lifecycle stages, each with the retention problem, the capability that solves it, the software category that owns that capability, and the metric that tells you whether it worked. Use it as a gap analysis on your current stack.
| Lifecycle stage | The retention problem | Capability required | Software category | Example platforms | Metric that proves it |
|---|---|---|---|---|---|
| First purchase | The buyer has no relationship yet and no reason to expect a second visit | Post-purchase onboarding; setting expectations; enrolment into the programme | Lifecycle platform | Klaviyo | Programme enrolment rate among first-time buyers |
| Second purchase | The steepest drop-off in ecommerce, and usually a timing failure rather than a pricing one | Behavioural trigger at the right interval, optionally with an incentive | Lifecycle platform, plus loyalty | Klaviyo + Smile.io or LoyaltyLion | First-to-second purchase conversion rate |
| Repeat purchase | Nothing accumulates, so there is no compounding reason to keep choosing you | A programme mechanic the customer can see progressing | Loyalty or wallet engagement | Smile.io · LoyaltyLion · Marsello · a wallet pass | Purchase frequency and repeat purchase rate |
| VIP customer | Your best customers get the same treatment as everyone else | Tiers, thresholds, recognition and genuine privileges | Loyalty software (tier-capable) | LoyaltyLion · Yotpo Premium · Salesforce Loyalty Management | Retention and share of revenue in the top decile |
| Churn risk | A customer is slowing down and nothing detects it | Recency and frequency scoring; at-risk audiences | Lifecycle platform · CDP · RFM-capable loyalty | Klaviyo · Twilio Segment · Marsello RFM | Size of the at-risk segment over time |
| Lapsed customer | Past the normal purchase cycle, and getting further away every week | A recency-defined segment and a time-boxed offer | Lifecycle platform (win-back flow) | Klaviyo winback flow | Reactivation rate within 30 and 90 days |
| Subscription renewal | The customer reaches an explicit decision point and clicks cancel | Deflection at the cancel screen; adaptive payment retry | Churn-deflection tooling | Churnkey · Churn Buster · Raaft · Paddle Retain | Save rate at cancellation; involuntary churn recovered |
Stage two. For most ecommerce brands the first-to-second purchase conversion is both the biggest leak and the cheapest to address, because the customer is still warm and you already have their contact details and their consent. Fix the timing first — send the right prompt at the right interval — and only add an incentive if timing alone does not move it. Reaching for the discount first permanently teaches your customers to wait for one.
DTC brands frequently buy loyalty before they have a repeat-purchase reason to be loyal to. If the product is genuinely bought once every two years, points will not change that, and the programme will simply discount the customers who were coming back anyway. The better retention investments for genuinely low-frequency products are referral, community and post-purchase experience — not a points balance the customer will never accumulate.
- Ecommerce retention is seven problems at seven stages, not one problem.
- The largest and cheapest win is usually first-to-second purchase, and it is a timing problem first.
- Map your current stack against the seven stages; the hole is usually at at-risk detection or lapsed win-back.
10. Where wallet marketing fits into customer retention
Wallet-based engagement is an additional layer in the retention stack, not a replacement for any existing one. The conventional stack is CRM plus email plus SMS plus loyalty plus advertising plus analytics. Wallet adds something none of those provide: a persistent, branded object on the customer's phone that carries state — stamps, points, tier, expiry, a barcode — and that they see without you sending anything. It does not replace your CRM, CDP, email platform, SMS provider, native app or point of sale, and any vendor telling you otherwise is overselling. What it replaces, at best, is the paper card and the plastic one.
What wallet-based engagement actually is
The customer saves a pass — a digital loyalty card, membership card, coupon or reward card — into Apple Wallet or Google Wallet, both of which are already on the phone. Enrolment is a QR scan or a tapped link: no download, no account, typically a few seconds at a counter or a checkout. The business can then change what that pass says, and each platform surfaces some of those changes to the customer.
The strategic value is not the message. It is that the card is working between campaigns. A customer opens their wallet to pay for something unrelated and sees they are two stamps from a reward. Nothing was sent, no permission was consumed, no cost was incurred. Every other channel in the stack only exists at the moment you use it.
What Apple and Google actually document — and where the exaggeration happens
This is where the category earns its reputation for overclaiming, so it is worth being exact. The two platforms work differently and the difference matters commercially.
Apple documents a pass update web service: the device registers the pass with your server and provides a push token, your server sends a push notification when pass data changes, and "The user's device receives the notification and queries your server for updated passes." Critically, that push uses "an empty JSON dictionary for the payload" — it carries no text and cannot. Visible alert text comes from the pass itself: a field's changeMessage, a format string containing %@ which the field's new value replaces, and Apple states "You need to provide a value for the system to show a change notification." So on Apple you cannot send arbitrary marketing text to a pass. You change a field, and the alert is a consequence of that change. Apple's lock-screen relevance — date and location — is separate and, in Apple's archived Wallet guidance, passive: "It doesn't present alerts or post notifications." A pass may have at most ten relevant locations.
Google supports something Apple does not. A message added to a pass with messageType set to TEXT_AND_NOTIFY "Renders the message as text on the card details screen and as an Android notification," and field updates can trigger notifications when notifyPreference is set to notify on update. The limits are documented and strict: a maximum of three messages that trigger a push notification in a 24-hour period, a maximum of three notifying updates in the same window, a QuotaExceededException beyond that, and an explicit statement that "Google may throttle your push notification delivery quota if it deems you are spamming your users." Users must have notifications enabled for their passes. Google's geofence notifications went generally available in October 2025, with up to ten merchant locations per class and per object, a Google-set radius and a dwell requirement, and they require the user to have granted precise, always-on location access to the Google Wallet app.
"Apple Wallet lets you send push notifications like an app." No — the payload is empty and the alert comes from a changed field. "Send a message to your Apple Wallet pass holders." Not supported as a free-form message. "Apple sends a notification when a customer is near your store." Apple relevance is passive lock-screen surfacing; Google's geofence push is a real notification, and attributing Google's capability to Apple is the most common error in this category. "Unlimited wallet push." Google caps at three notifying messages per 24 hours. "No permissions needed, so it always reaches the customer." Google requires OS notification permission plus a per-pass user toggle. And the subtly wrong one: both platforms use the phrase "push notification" to mean structurally different things — on Apple it is a silent update trigger, on Google it is a user-visible notification.
Which retention platforms actually have verified wallet capability
Table 7 is the wallet-specific view, because "wallet support" in a general comparison hides too much. Only platforms where the capability could be verified from official documentation appear as supported.
| Platform | Apple Wallet | Google Wallet | Native or partner | Included or extra | Notes |
|---|---|---|---|---|---|
| Marsello | Yes | Yes | Native | Included on all plans | Proximity notifications are in closed beta, require the Accelerate plan, and custom messages are Apple-only |
| LoyaltyLion | Yes | Yes | Native, with device auto-detection | Paid add-on, priced by active pass installs — rate not published | Points, tier and rewards update on the pass; lock-screen notifications on earn, expiry and near-store |
| PassKit | Yes | Yes | Native — it is the whole product | Platform fee from $39.50/mo plus per-pass volume | Developer-oriented; no native segmentation or journey builder; multi-use passes billed on live-record high-water mark |
| Loopy Loyalty | Yes | Yes | Native | Included — $25 / $69 / $95 per month | Stamp cards only; documented filters cover stamps and rewards with no recency filter; beacon messages are Apple-only |
| Boomerangme | Yes | Yes | Native | Included — from $199/mo | Automatic RFM segments including "Sleeping" and "At risk"; geo-push is iOS-only with a fixed radius and no frequency cap |
| PushNotice (ours) | Yes | Yes | Native | Included on every plan, free tier upward | Stamp, membership, VIP reward and coupon passes; tag and tier filtering; no email or SMS sending |
| Square Loyalty | Yes | Not verified | Native | Included with Square Plus | Apple Wallet pass confirmed on Square's own product page; no Google Wallet support found on any official Square page |
| Salesforce Loyalty Management | Not verified | Yes | Native integration | Within Loyalty Management licensing | Membership ID, tier and point balance on the pass; vouchers auto-link, up to 50 per pass |
| Yotpo Loyalty | Via partner | Via partner | Partner — Novel, or Passcreator by Fobi | Separate vendor contract | Yotpo's marketing describes wallet support; the delivery is a second vendor |
| Braze | Partner only | Partner only | Partner — PassKit named in Braze's docs | Separate vendor contract | Braze files mobile wallet under partner additional channels |
| Klaviyo · HubSpot · Smile.io · Stamped · Twilio Segment · Insider One | No native support found | No native support found | — | — | "Smile Wallet" was a consumer app closed in October 2024, not Apple Wallet support. HubSpot's Apple Pay support is checkout payment, not a wallet pass |
Wallet is a strong additional layer and a weak only layer for most ecommerce brands — there is no counter moment, no barcode, no door. It is a strong primary layer for businesses whose customers show up in person and who have no other way to reach them between visits, because for those businesses the alternative is not a worse channel, it is no channel. Judge it on that basis rather than against app push, which it is not competing with.
- Wallet touches the incentive and communication layers and contributes nothing to the data layer.
- Apple's pass push carries an empty payload; visible text comes from a changed field's change message.
- Google supports real developer-authored messages, capped at three notifying messages per 24 hours.
- Six platforms have verified native support on both wallets; several well-known ones have none.
11. Customer retention software without a mobile app
Almost all retention software already works without an app — email, SMS, web and loyalty platforms have never required one. The only thing a native app uniquely provides is app push notifications and in-app experiences. The genuine question is what gives you a persistent presence on the customer's phone without asking them to install anything, and the answer is a wallet pass. But a wallet pass is not equivalent to app push, and the comparison below says exactly where each option wins and loses rather than flattening them together.
Building an app in order to retain customers is one of the most expensive mistakes available to a small or mid-sized business. The build cost is visible; the permanent maintenance cost — two platforms, OS updates, store accounts, releases, support — is not, and it does not stop when you stop adding features. Meanwhile the customer has to find, download and keep an application for a business they visit twice a month.
| Dimension | Native app | Wallet pass | Web (site / PWA) | SMS | |
|---|---|---|---|---|---|
| Customer friction | Highest — find, download, open, allow | Lowest — scan or tap, seconds | Permission prompt, or an install for a PWA | Low — a number and consent | Low — an address and consent |
| Installation | App store download | None — the wallet is pre-installed | None for the browser; install for a PWA | None | None |
| Reach | Only people who installed and kept it | Only people who saved the pass — but the save is cheap | Only browsers that granted permission, per device | Near-universal | Near-universal |
| Persistence | Icon stays until deleted | A visible card in the wallet | Nothing visible between messages | Nothing after it is read | Buried after it is read |
| Branding | Full — icon and interface | Full-colour branded card | Only while they are on the site | A sender name | Template branding in a crowded inbox |
| Communication control | Complete — content, timing, richness | Bounded by Apple and Google rules; free-form text on Google only | Full control within browser rules | Full control | Full control |
| Loyalty suitability | Strong, if they keep the app | Strongest — the card carries the state | Account-based only | No state | No state |
| Automation | Whatever you build | Triggers and schedules, vendor-dependent | Mature vendor tooling | Mature | Most mature of all |
| Cost structure | Build plus permanent maintenance | Subscription, no per-message fee | Subscription, no per-message fee | Per message, forever | Subscription by list size |
| Best use case | Daily-use products where the app is the experience | Loyalty, membership, offers and in-person repeat visits | Web-native businesses with real repeat traffic | Urgent and transactional messages | Considered offers, receipts, long-form |
A wallet pass is not equivalent to native app push. App push lets you send any message, any time, with rich content and full control. Wallet messaging is bounded by rules Apple and Google set: on Apple the alert is a side effect of a changed field, and on Google it is a real message capped at three notifying sends per 24 hours. What wallet wins on is not messaging power — it is enrolment cost and persistence. Choosing it because it is "app push without the app" is choosing it for the one thing it is not.
One persistent channel plus one universal channel. The persistent channel — a wallet pass, or web push for a web-native business — carries the ongoing relationship: the card, the balance, the status, the recurring nudge. The universal channel — email, or SMS for genuinely urgent messages — carries everything that must arrive whether or not the customer ever enrolled: receipts, confirmations, changes. Businesses that make one channel do both jobs over-send on the persistent one and lose it.
- Most retention software never needed an app; only app push and in-app experiences do.
- A wallet pass buys persistence and near-zero enrolment friction, not messaging control.
- Pair one persistent channel with one universal channel; do not ask either to do both jobs.
12. Customer retention automation examples
Eleven automations cover most of the retention value available to most businesses, and the first four cover most of the first four. Welcome, first-to-second purchase, reward earned, reward reminder, lapsed, win-back, VIP, membership renewal, birthday, post-purchase and re-engagement. Each is defined below by trigger, audience, message, channel, goal and KPI. These are illustrative templates, not tested campaigns — no open rates, redemption rates, uplift figures or benchmarks are claimed for any of them anywhere in this guide.
The pattern worth noticing across the table is that ten of the eleven trigger on something the customer did or did not do, rather than on a date in a marketing calendar. That is the difference between a retention programme and a newsletter with extra steps. Build them in the order given: the first four are the ones you can run indefinitely without writing anything new.
| Automation | Trigger | Audience | Message (illustrative) | Channel | Goal | KPI |
|---|---|---|---|---|---|---|
| Welcome | Programme enrolment or first purchase | New members only | What the programme does, how to earn, what happens next | Email · the card itself | Make the first use obvious | First redemption or second visit within 30 days |
| First-to-second purchase | Days since first order reaches a defined interval with no second order | One-time buyers only | A prompt tied to what they bought, not a generic discount | Email · SMS | Convert a buyer into a customer | First-to-second purchase conversion rate |
| Reward earned | Points, stamps or spend threshold reached | The individual who reached it | "Your reward is ready" plus exactly how to claim it | Wallet pass update · email | Convert earning into a visit | Reward claim rate |
| Reward reminder | Reward earned, N days elapsed, still unredeemed | Earners who have not claimed | A reminder with no new offer attached | Wallet update · email | Recover an earned but unused reward | Late claim rate |
| Lapsed (early) | No purchase or visit for 1.5× the normal cycle | Previously active customers only | Acknowledge the gap; give one clear reason to return | Email · wallet update | Intervene before the habit breaks | Return rate within 30 days |
| Win-back | Well past the normal cycle — 2× or more | Dormant customers, excluding recent recipients | A stronger, explicitly time-boxed offer | Email · SMS where consented | Recover a customer before they are gone | Reactivation rate at 30 and 90 days |
| VIP | Spend, frequency or tier threshold crossed | Top segment only | Recognition and a real privilege — early access beats a bigger discount | Wallet tier update · email | Protect the customers who matter most | Retention and revenue share of the top decile |
| Membership renewal | Fixed period before expiry | Members approaching renewal | Renewal date, what is included, one action | Wallet membership card · email | Prevent passive lapse | Renewal rate |
| Birthday | Known date, sent in advance | Members with a date on file | A specific gift, not a percentage off everything | Wallet offer · email | Create a dated reason to visit | Redemptions per 100 birthdays |
| Post-purchase | Order delivered or service completed | Recent buyers | Usage, care, what to expect, how to get help | Reduce regret and returns; set up the repeat | Return rate and support contact rate | |
| Re-engagement | Scheduled, segmented by state | Everyone except recently active and recently messaged | Timely and specific; never "we miss you" | Email · wallet campaign | Concentrate demand into a window | Campaign-period visits or orders |
Reward-state messaging only works if the system that knows the reward state can reach the system that sends the message. If stamps live in a loyalty app and campaigns go out from an email platform with no sync, "your reward is ready" is not a campaign you can run — see Section 7, step 10. Lapsed and win-back automations require recency segmentation, and not every platform has it: Loopy Loyalty's documented filters cover stamps earned, rewards earned and rewards redeemed, with no recency filter documented. Confirm both before you design a programme around them.
Build welcome, reward earned, lapsed and renewal first — those four cover the moments when a customer is most likely to either start or stop, and they run indefinitely without new copy. Add VIP and birthday once they are stable. Leave seasonal re-engagement until last; it is the most enjoyable to write and the least load-bearing. The rule: set a frequency cap across all campaigns, not within each one. Eleven automations firing independently is how a customer receives four messages in a week and deletes the pass.
- Ten of eleven automations trigger on customer behaviour, not on your calendar.
- Welcome, reward earned, lapsed and renewal deliver most of the value — build those first.
- Verify reward-state sync and recency segmentation before designing around them.
13. How to measure customer retention software ROI
Judge retention software on four outcome metrics — customer retention rate, repeat purchase rate, purchase or visit frequency, and customer lifetime value — and use programme metrics only to diagnose why an outcome moved. Enrolments, sends, opens and redemptions measure whether the tool is being used, not whether retention improved, and a failing programme can look extremely busy on those numbers. Not every metric applies to every business: a subscription company should lead with churn and renewal rate; a coffee shop should lead with visit frequency and has no meaningful average order value story.
Twelve metrics in three tiers. Tier 1 tells you whether retention improved. Tier 2 tells you why. Tier 3 tells you whether the software is being used. Judge the purchase on Tier 1 only, and never report Tier 3 as if it were Tier 1.
| Tier | Metric | How to compute it | What it tells you | Where it misleads |
|---|---|---|---|---|
| 1 · Outcome | Customer retention rate | Customers at end of period, minus those acquired during it, divided by customers at start | The headline: are you keeping people | Meaningless without a defined period matched to your purchase cycle |
| 1 · Outcome | Repeat purchase rate | Customers with more than one purchase, divided by all customers in the period | Whether buyers become customers | Rises automatically as a cohort ages — always compare like-aged cohorts |
| 1 · Outcome | Purchase / visit frequency | Orders or visits divided by unique customers in the period | The metric loyalty programmes are actually built to move | A few heavy users can hide a collapsing middle — check the distribution |
| 1 · Outcome | Customer lifetime value | Average order value × frequency × gross margin × expected lifespan | Whether retention work is producing money | Extremely sensitive to the lifespan assumption; state it explicitly |
| 2 · Diagnostic | Churn rate | Customers lost in the period divided by customers at the start | The inverse view; essential for subscriptions | For non-subscription businesses, "lost" is a judgement call you must define |
| 2 · Diagnostic | Time between purchases | Median gap between consecutive orders per customer | Defines your normal cycle — and therefore what "lapsed" means | Use the median, not the mean; outliers distort it badly |
| 2 · Diagnostic | Lapsed segment size | Count of customers past 1.5× the median cycle | The size of the problem you can still fix | Grows with total customers — track as a share, not a count |
| 2 · Diagnostic | Average order value | Revenue divided by orders | Whether retention is coming with margin attached | A discount-led programme can lift frequency while quietly lowering this |
| 2 · Diagnostic | Revenue per customer | Revenue divided by unique customers in the period | Combines frequency and order value in one number | Moves for acquisition reasons too — segment new versus returning |
| 3 · Programme | Loyalty enrolment rate | Enrolled customers divided by eligible customers | Whether the programme is reaching anyone | High enrolment with flat frequency means the incentive is not working |
| 3 · Programme | Reward redemption rate | Rewards redeemed divided by rewards earned | Whether the reward is worth claiming | Low redemption may mean the threshold is too high, not that customers do not care |
| 3 · Programme | Win-back rate | Lapsed customers who returned divided by lapsed customers targeted | Whether reactivation is worth running | Requires a holdout group, or you are counting people who would have returned anyway |
Cost per retained customer, and the honest version of ROI
The cleanest single measure of whether the software paid for itself:
Cost per retained customer = (software cost + implementation + staff time + incentive cost) ÷ additional customers retained versus a control.
The phrase doing the work is versus a control. Without a holdout group, you are measuring customers who would have come back anyway and attributing them to the platform — which is how retention programmes produce spectacular reported ROI and no change in the business. If your platform supports holdouts, use them. If it does not, the crude alternative is a staged rollout: launch by location or by cohort and compare.
Retention benchmarks are widely republished with no disclosed sample, period or methodology, and the figures in this category frequently trace back to vendor marketing rather than to research. A number that looks authoritative and is wrong is worse than no number, because it becomes the target. Measure your own baseline for one full purchase cycle before launching anything, and compare against yourself. Your own before-and-after, with a control, is the only benchmark that is true for your business.
Subscription: churn, renewal rate, save rate at cancellation, involuntary churn recovered. Ecommerce: repeat purchase rate, first-to-second conversion, time between purchases, CLV. Retail and hospitality: visit frequency, enrolment rate, lapsed share, revenue per customer. Services and appointments: rebooking rate, time to rebook, no-show rate. Reporting all twelve to everyone is a way of reporting nothing; pick the four that describe your actual model.
- Four outcome metrics judge the purchase; programme metrics only diagnose.
- Cost per retained customer is only meaningful against a control or holdout.
- Measure your own baseline for a full purchase cycle — published benchmarks in this category are unreliable.
14. Customer retention software pricing
Published pricing across the platforms in this guide runs from $0 to $45,000 per organisation per month, and three vendors publish nothing at all — so there is no useful "average cost of retention software." What matters more than the headline figure is the pricing model, because different models behave in opposite directions as you grow. Per-contact and per-profile pricing scales with your audience whether or not those people buy. Per-message pricing scales with success. Per-site pricing multiplies with locations. Consumption pricing is unknowable in advance. Model your real cost at three times your current size before signing anything annual.
The eight pricing models, and how each behaves as you grow
| Model | How it is charged | Behaviour as you grow | Published examples |
|---|---|---|---|
| Flat monthly subscription | A fixed fee per tier | Predictable until you cross a tier boundary | Loopy Loyalty $25 / $69 / $95; Boomerangme from $199 |
| Per contact or profile | Banded by audience size | Grows with your list, including people who never buy | Klaviyo email plans are priced on active profile count; PushNotice bands by wallet audience |
| Per user or seat | Charged per person with access | Grows with your team, not your customers | HubSpot Marketing and Service Hubs; Salesforce Service Cloud $25–$550 per user per month |
| Usage-based | Per tracked user, order, session, message or credit | Grows with activity — and with anonymous traffic in some models | Twilio Segment monthly tracked users; Yotpo per-order overage above 500 orders; Marsello SMS from US$0.028 per credit |
| Per site or location | Charged per physical location | Multiplies directly with expansion | Marsello NZ$100 / NZ$200 per site; Square Plus $49 per location |
| Transaction or volume-based | Per pass, per record, per event | Efficient at low volume; watch high-water-mark billing | PassKit platform fee from $39.50 plus per-pass volume; multi-use passes billed on the highest monthly live count |
| Revenue or churn-volume based | Banded by the money at stake | Aligns cost with value, but scales with your success | Churnkey Starter $250/mo billed yearly under $5k monthly churn volume |
| Enterprise / custom | Quoted, usually annually | Unknowable before a sales process | Braze (edition + MAU + credits); Insider One (MAU); Salesforce Data 360 (consumption); Salesforce Loyalty Management from $20,000 per org per month |
Free plans that are genuinely free
Several vendors publish permanent free tiers rather than trials, which materially changes the shape of a small-business decision. Verified as of August 2026: Smile.io free up to 200 monthly orders; Yotpo Loyalty free with basic points and referrals; LoyaltyLion free for stores processing 400 orders a month or fewer; Twilio Segment Connections free at 1,000 visitors a month; HubSpot free tiers on Marketing, Service and Data Hubs; Raaft free for 20 cancellation sessions a month; PushNotice free forever at 100 wallet customers and 4 campaigns a month, no card required. Trials rather than free plans: Braze 14 days, Marsello 14 days, Boomerangme 14 days, Loopy Loyalty 15 days, Square Plus and Premium 30 days with loyalty included in the trial, PassKit 45 days. Stamped publishes no free plan or trial on stamped.io, though it directs smaller brands to cheaper self-serve tiers on its Shopify App listing.
Total cost of ownership — the nine lines that are not the subscription
- Implementation — and note that HubSpot's onboarding fees are mandatory, not optional: $3,000 at Marketing Hub Professional, $7,000 at Enterprise, $1,500 and $3,500 on the equivalent Service Hub tiers
- Integrations — connecting commerce, POS, booking or support systems, and maintaining those connections
- Migration — moving existing members, balances and history, which is the real switching cost and the reason to choose carefully the first time
- Data — cleanup, deduplication, consent records, and any warehouse or CDP charges
- Messaging — per-message SMS costs, and separately metered contact volumes where the platform splits them out
- Design — pass artwork, email templates, in-store signage, QR materials
- Administration — staff time to run campaigns, enrol customers and answer questions; at small scale this is frequently the largest real cost
- Training — including counter staff, who determine enrolment rate more than any feature does
- Support — where priority support is a paid tier rather than a standard inclusion
Audience-based billing that counts non-buyers. Klaviyo's Advanced data tier is billed on total profiles including suppressed and non-subscribed; Segment's monthly tracked users include anonymous visitors. A high-traffic, low-conversion site pays for people who will never buy. High-water-mark pass billing. PassKit bills multi-use passes at the highest live count in the month, so a large dormant loyalty base keeps costing money whether or not those customers ever return. Separately priced wallet. LoyaltyLion's Loyalty Pass is a paid add-on priced by active pass installs, with the rate unpublished — so the cost of the feature you may have shortlisted the vendor for cannot be determined before a sales conversation.
- Published prices span $0 to $45,000 per month; three vendors publish nothing.
- The model matters more than the number — per-message scales with success, per-site with expansion, per-profile with your list.
- Nine cost lines sit outside the subscription; onboarding fees alone reach $7,000 at HubSpot Enterprise.
15. Common customer retention software mistakes
Thirteen mistakes account for most failed retention software purchases, and the first one causes several of the others. Choosing software before identifying the retention problem, buying too many tools, ignoring the customer experience, over-communicating, poor segmentation, weak data, no automation strategy, ignoring loyalty, ignoring win-back, measuring clicks instead of retention, choosing on price alone, buying enterprise software for a simple problem, and building an app that was never needed.
| Mistake | Why it matters | Better approach |
|---|---|---|
| Choosing software before identifying the problem | Selects a category at random; every later decision inherits the error | Write the one-sentence problem with a number in it, then pick the mechanism, then the category (Section 7, steps 1–3) |
| Buying too many tools | Each tool adds an integration, an admin surface and a bill; the data fragments further | Two tools well integrated beat four tools partially configured. Add the third only when a named gap blocks a named automation |
| Ignoring the customer experience | A programme that is confusing at the counter or the checkout will not be used, whatever the software does | Enrol yourself and redeem a reward as a customer before launch, on both an iPhone and an Android phone |
| Over-communicating | The failure mode is permanent: a deleted pass or a revoked permission has no re-permission path | Set a frequency cap across all campaigns, not within each one, and enforce it centrally |
| Poor segmentation | Sending everything to everyone trains customers to ignore you, then to leave | Ask who should not receive this. Relevance is mostly subtraction |
| Weak data | Every automation is capped by what the platform actually knows about the customer | Fix identification at the transaction before buying anything that depends on it |
| No automation strategy | Manual campaigns stop the week things get busy — which is exactly when retention matters | Build the four core automations from Section 12 first and let them run |
| Ignoring loyalty | Without a mechanic, every retention message has to carry the entire reason to return by itself | Give customers something that accumulates, so the reason to return exists between messages |
| Ignoring win-back | Lapsed customers are the cheapest audience you will ever address — they already bought once | Define your normal cycle from median time between purchases, then automate against it |
| Measuring clicks instead of retention | Activity metrics let a failing programme look successful indefinitely | Judge on the four Tier 1 outcome metrics in Section 13; use everything else to diagnose |
| Choosing on price alone | The cheapest tool that does not solve your problem is the most expensive purchase available | Shortlist on category fit first, then compare price within the category |
| Enterprise software for a simple problem | You buy a multi-quarter implementation instead of a retention programme | Buy for the constraint you have now (Section 8); treat the next stage as a future migration |
| Building an app unnecessarily | Build cost plus permanent maintenance, in exchange for a channel most customers will never install | Build an app when the app is the product. For notifications and loyalty alone, use wallet, web or email |
Treating retention as a software category rather than as a business outcome. Software can give a customer a reason to return, reach them at the right time, show you who is lapsing, or catch them at the exit. It cannot make a mediocre product worth returning to, fix a service problem, or manufacture a reason to buy something twice that people buy once. If your retention rate is poor because customers were disappointed, every platform in this guide will help you observe that more precisely and none will change it.
- Most failures start with buying before diagnosing.
- Two well-integrated tools beat four partially configured ones.
- Frequency capping across campaigns is what keeps a persistent channel alive.
16. How PushNotice fits into the customer retention stack
PushNotice is a wallet-based customer engagement layer: it issues Apple Wallet and Google Wallet passes — loyalty stamp cards, membership cards, VIP reward cards and coupons — and runs lock-screen campaigns against them, with no app for the business to build and none for the customer to install. Using the map from Section 3, it sits in category seven, touching the incentive and communication layers of the stack and nothing else. It is not a CRM, not a CDP, not an email or SMS platform, not a point of sale, and not a lifecycle journey builder. It complements those systems; for most businesses it does not replace any of them.
PushNotice publishes this guide and PushNotice is our product. Everything above this section is written to be useful whether or not you ever use it — which is why Section 5 lists our limitations in the same column as everyone else's, Section 6 names five use cases where a different platform is the better answer, and this section names six things PushNotice does not do. The capabilities below are taken from PushNotice's own published product and pricing pages as of 30 August 2026. Anything plan-dependent is marked to confirm rather than asserted.
Where it genuinely fits — and where it genuinely does not
The comparison in Section 5 makes the gap PushNotice addresses fairly clear, so it is worth stating it plainly rather than claiming a general advantage.
A business with a physical location and repeat customers, no app, no developer, and no Shopify or Square dependency has a narrow set of options. Smile.io, LoyaltyLion and Stamped require a supported ecommerce platform. Square Loyalty requires processing payments on Square. Marsello requires a supported point of sale or ecommerce platform and starts at a per-site fee. Boomerangme starts at $199 per month. PassKit publishes an excellent rate card but is developer-oriented, with no native segmentation or journey builder. Loopy Loyalty is a strong, simple stamp-card product whose documented filters do not include recency.
That is the position PushNotice occupies: a wallet-native loyalty and engagement layer for businesses that want a branded card and a lock-screen channel without a commerce platform, a point of sale, a developer or an app — with a free tier to start and published plans at $29 and $79 a month. It is a deliberately narrow product, and the narrowness is the point.
Where it is not the answer: an ecommerce brand that needs post-purchase and win-back email flows should buy Klaviyo before anything else. A retailer whose loyalty must read transaction data from a supported point of sale should look at Marsello. An enterprise needing identity resolution across markets needs a data platform. A subscription business losing people at the cancel screen needs a deflection tool. None of those problems is one a wallet pass solves.
| Area | What is published |
|---|---|
| Category | Wallet-based customer engagement — category 7 of the seven in Section 3 |
| App requirement | None — no app for the business to build, none for the customer to install |
| Wallet platforms | Apple Wallet and Google Wallet, issued together, built on the official Wallet APIs |
| Pass types | Loyalty stamp cards, membership cards, VIP reward cards, coupon passes |
| Enrolment | QR code or shareable link; no customer account required; no download |
| Campaigns | Lock-screen campaigns sent to all customers or filtered by tag and loyalty tier |
| Segmentation | Tagging and tier filtering (published on the Pro plan) [recency/inactivity filtering not published — confirm] |
| Automation | Manual and scheduled campaigns [no journey builder published — confirm] |
| Location | Smart Location for iPhone lock-screen surfacing when customers are nearby, and Google Wallet nearby notifications — published on Starter and above, not on the Free plan, and operating within the platform behaviour documented in Section 10 |
| Analytics | Real-time install tracking, visit tracking and campaign results; basic analytics on Free, detailed analytics from Starter |
| Agency use | Agency plan with white-label branding, a dedicated workspace per client and client self-service access |
| Plans | Free $0 forever (100 wallet customers, 4 campaigns/month, 1 pass design, 1 workspace, no card required) · Starter $29/month (2,500 customers, 100 campaigns/month, Smart Location, detailed analytics) · Pro $79/month (25,000 customers, 1,000 campaigns/month, 5 workspaces, tagging and segmentation, priority support) · Agency custom. Annual billing saves 10% [verify current plans] |
| Cost structure | Audience-size tiers with no per-message fee — sending more does not cost more |
| Integrations | No third-party integrations are published as of 30 August 2026 — confirm current status before assuming a connection to your POS, commerce platform or CRM |
| Not provided | Email sending · SMS sending · CRM · CDP · point-of-sale software · lifecycle journey orchestration |
For most businesses the realistic pattern is complementary, not competitive. A restaurant keeps its booking system and adds a wallet loyalty card. A Shopify brand keeps Klaviyo for email flows and adds a wallet VIP card for the customers who buy in person at pop-ups and markets. An agency keeps its clients' existing marketing stack and adds a wallet layer as a service line. The wallet card is doing something none of those tools does — sitting visibly on the phone between messages — and it is doing nothing that they do.
PushNotice does not exceed what Apple and Google document, because no wallet vendor can. Section 10 quotes the constraints exactly: on Apple, a pass update push carries an empty payload and the visible alert comes from a changed field's change message; on Google, developer-authored messages are real but capped at three notifying sends per 24 hours, and users can turn off notifications per pass. Anyone — including us — describing a wallet pass as equivalent to native app push is overstating it. Ask us, or any wallet vendor, which documentation page supports a claim before you build a campaign plan on it.
- PushNotice is a wallet-based engagement layer — the incentive and communication layers only.
- Its genuine advantage is businesses with no app, no developer and no commerce or POS dependency.
- It does not provide email, SMS, CRM, CDP, POS or journey orchestration, and publishes no third-party integrations.
17. The customer retention software decision tree
Seven questions plus a disqualifying question zero, asked in the order that eliminates the most options soonest. Cite or adapt with attribution.
Seven questions, asked in the order that eliminates the most options soonest. Do you need rewards and repeat-purchase incentives? Evaluate loyalty software. Complex lifecycle messaging? Lifecycle marketing. Unified customer data? A CDP. Relationship and account management? CRM. Automated recovery of lapsed customers? A lifecycle flow, or a deflection tool if you have subscriptions. A persistent app-free customer touchpoint? Wallet-based engagement. Several of these at once? An integrated stack — and budget for the integration, not just the licences.
Most businesses of any size answer yes to two or three questions, and that is the correct outcome rather than a failure of the framework. The useful discipline is sequencing: buy the one that unblocks the others first. If you cannot identify a returning customer, buy the tool that solves identification before the one that sends clever messages. If you have identification and no reason to return, buy the incentive before the data platform. And when you buy the second tool, budget the integration between them as a line item — Section 7, step 10 exists because that connection is where retention stacks most often quietly fail.
- Seven questions, asked in order, select the category — the largest part of the decision.
- Question zero disqualifies more purchases than the other six combined.
- Multiple yes answers mean sequencing and an integration budget, not a bigger single platform.
18. Customer retention software FAQ
Twenty questions, answered in the shortest accurate form. Where a vendor capability or price is involved, the answer says which vendor and reflects what that vendor publishes as of 30 August 2026.
The category
What is customer retention software?
Customer retention software is technology that helps a business increase repeat engagement, repeat purchases, renewals or customer relationships through capabilities such as loyalty, lifecycle communication, segmentation, automation, customer data and reactivation. It is an umbrella term, not a single product category: no vendor sells a product that does all of it, and seven recognisably different categories of software compete for the search term.
What does customer retention software do?
Depending on the category, it identifies and unifies customer records, segments customers by behaviour, automates communication across channels, rewards repeat behaviour, recovers inactive customers, administers a loyalty programme, personalises campaigns, and measures retention outcomes. Very few platforms do more than three or four of those well, which is why the buying question is which capability your retention problem actually needs.
What types of customer retention software exist?
Seven categories. Loyalty software for rewards and repeat-purchase incentives. Lifecycle marketing platforms for automated behavioural journeys. CRM platforms for relationship and account management. Customer data platforms for unifying and activating customer data. Customer engagement platforms for multi-channel orchestration at scale. Win-back and churn-deflection tooling, which splits into ecommerce reactivation flows and subscription cancellation deflection. And wallet-based engagement for persistent, app-free customer touchpoints.
What is the difference between customer retention software and loyalty software?
Loyalty software is one category inside the wider customer retention software landscape. Loyalty software runs the incentive mechanic — points, stamps, tiers, rewards, referrals — and holds the member data. Customer retention software is the umbrella covering that plus lifecycle marketing, CRM, customer data platforms, engagement platforms, win-back tooling and wallet-based engagement. Every loyalty platform is retention software; most retention software is not loyalty software, and most loyalty platforms cannot send a lifecycle campaign on their own.
What software helps retain customers?
Software helps retention in four distinct ways, and it is worth knowing which one you are buying. It can give customers a reason to come back — loyalty and rewards platforms. It can talk to them at the right moment — lifecycle and engagement platforms. It can tell you who is slipping away — customer data platforms, analytics and RFM segmentation. Or it can intercept the moment of leaving — cancellation deflection and win-back tooling. A retention problem that is really a product or service problem is not solved by any of them.
Choosing a platform
What is the best customer retention software?
There is no single best one, and a universal ranking would be misleading because the platforms are not substitutes for one another. The honest answer is by use case: Klaviyo or Braze for lifecycle automation, Smile.io or LoyaltyLion for ecommerce loyalty programmes, Salesforce Loyalty Management for enterprise loyalty, Marsello or Square Loyalty for brick-and-mortar retail, Twilio Segment for a unified data layer, Churnkey for subscription cancellation deflection, and a wallet platform such as PushNotice, Loopy Loyalty or PassKit for a persistent, app-free customer touchpoint.
What is the best retention software for small businesses?
It depends on whether the business is online or physical. A small ecommerce store on Shopify is well served by Smile.io, which has a genuine free plan and paid tiers from $15 per month. A small brick-and-mortar business running Square gets loyalty included in Square's $49 per location per month Plus plan. A small local business that wants a persistent customer touchpoint without an app or a point-of-sale dependency is better served by a wallet platform — Loopy Loyalty from $25 per month, PushNotice with a free tier and paid plans from $29 per month. Enterprise retention suites are not a small-business answer at any price.
What is the best retention software for ecommerce?
Ecommerce retention normally needs two tools, not one: a lifecycle platform to send the messages and a loyalty platform to run the incentive. Klaviyo is the default lifecycle layer for Shopify brands and has no native loyalty engine of its own; Smile.io, LoyaltyLion and Yotpo are the common loyalty layers and none of them can run a full lifecycle programme alone. Expect to integrate two vendors, and check that the loyalty data actually syncs into the messaging tool before you commit to either.
What is the best retention software for DTC brands?
For a direct-to-consumer brand at scale, the common stack is a lifecycle platform such as Klaviyo for behavioural messaging, a loyalty platform such as LoyaltyLion or Yotpo for the incentive and VIP tiers, and — where subscriptions are involved — a churn-deflection tool such as Churnkey at the cancellation moment. Stamped bundles reviews, loyalty and replenishment timing but still relies on Klaviyo, Attentive or Postscript to send. Verify what each tier actually includes: VIP tiers and segmentation are frequently gated behind unpublished pricing.
How do I choose customer retention software?
Define the retention problem before you look at any vendor. Name the customer behaviour you want to change, then the mechanism that would change it — an incentive, a message, a data insight or an intervention at the point of leaving. That single decision selects the category. Only then compare platforms within that category on data requirements, segmentation, automation, loyalty capability, channels, wallet support where relevant, integrations, analytics and total cost — and run a real test with real customers before signing an annual contract.
Do I need a CRM or a customer retention platform?
A CRM is the right answer when retention is relationship-driven and low-volume — named accounts, renewals, a salesperson or success manager per customer. A consumer retention platform is the right answer when retention is behaviour-driven and high-volume, where nobody will ever call the customer and the programme has to run on triggers. Businesses with both — a B2B sales motion and a consumer base — usually run both, with the CRM owning accounts and the retention platform owning the consumer programme.
Categories explained
Can loyalty software improve customer retention?
It can, when the underlying offer is worth returning for and the mechanic is visible to the customer. Loyalty software supplies a structured reason to return and a way to identify repeat customers you could not otherwise track — particularly valuable for cash and in-person businesses with no account system. What it cannot do is manufacture loyalty where the product, price or service does not merit it, and a discount programme aimed at customers who would have returned anyway simply lowers your margin.
What is lifecycle marketing software?
Lifecycle marketing software triggers automated customer journeys from behavioural events — a first purchase, an abandoned cart, a period of inactivity, a subscription renewal — and delivers messages across channels such as email, SMS, push and WhatsApp. Klaviyo and Braze are the archetypes. It owns the timing and the message; it does not normally own the incentive, which is why most lifecycle platforms integrate with a separate loyalty vendor rather than shipping points and tiers themselves.
What is win-back software?
For business-to-consumer retention, win-back is not a product category — it is a flow inside a lifecycle platform. Klaviyo, for example, documents a winback flow as a series of messages sent to customers who previously engaged but have not interacted for a defined period, and files it under lifecycle flows. For subscription businesses there is a genuine standalone category: cancellation-deflection and payment-recovery tools such as Churnkey, Churn Buster, Raaft and Paddle Retain, which intercept a clicked cancel button or a failed payment. The two are not substitutes.
What is a customer data platform?
A customer data platform collects customer data from your website, app, point of sale and back-office systems, resolves it into unified customer profiles, and activates audiences into the tools that act on them. Twilio Segment is the reference example. A CDP does not itself retain anyone: it makes retention possible in the tools downstream of it, which is why buying one before you have a working retention programme usually produces an expensive data project rather than more repeat customers.
Apps and wallets
Can customer retention software work without a mobile app?
Yes. Most retention software has never required an app: email, SMS, web and loyalty platforms all work without one. The only capability an app uniquely provides is native app push notifications and in-app experiences. The closest app-free equivalent to a persistent on-device presence is a wallet pass, which sits in Apple Wallet or Google Wallet, carries stamps, points or membership status, and can be updated after issue — with no download by the business or the customer.
Can customer retention software use Apple Wallet?
Some can, and far fewer than the marketing suggests. Apple documents a pass update web service: the device registers the pass with your server, your server sends a push notification when pass data changes, and the device fetches the updated pass. Critically, that push carries an empty JSON payload — visible alert text comes only from a changed field that declares a change message. Among platforms verified for this guide, Marsello, LoyaltyLion, Square Loyalty, PassKit, Loopy Loyalty, Boomerangme and PushNotice support Apple Wallet passes. Klaviyo, Braze, HubSpot, Smile.io, Stamped and Twilio Segment do not do it natively.
Can customer retention software use Google Wallet?
Yes, and the mechanism differs from Apple's in a way that matters. Google supports developer-authored messages on a pass: a message set to TEXT_AND_NOTIFY renders as text on the card and as an Android notification, and field updates can trigger notifications when notifyPreference is set. Google documents hard limits — a maximum of three notifying messages and three notifying updates per 24 hours, plus discretionary throttling — and the user must have notifications enabled for their passes. Verified Google Wallet support among the platforms in this guide includes Marsello, LoyaltyLion, Salesforce Loyalty Management, PassKit, Loopy Loyalty, Boomerangme and PushNotice.
Cost and measurement
How much does customer retention software cost?
The published range in this guide runs from $0 to $45,000 per month, which is why an average figure would be useless. Wallet and small-business loyalty tools publish rates from around $25 to $99 per month, with Boomerangme higher at $199. Ecommerce loyalty platforms cluster at $199 per month for their real entry tier. Lifecycle platforms price on contacts or profiles and scale with audience size. Enterprise engagement platforms publish nothing at all. Salesforce Loyalty Management starts at $20,000 per organisation per month billed annually. Budget for implementation, integration, migration, messaging fees, design and administration on top of any subscription.
What metrics should customer retention software track?
Four outcome metrics decide whether the software is working: customer retention rate, repeat purchase rate, purchase or visit frequency, and customer lifetime value. Three diagnostic metrics explain why: churn rate, time between purchases, and the size of your lapsed segment. Programme metrics — enrolment rate, reward redemption rate, campaign engagement, win-back rate — tell you whether the tool is being used, not whether retention improved. Judge software on the outcome metrics and use the programme metrics to debug.
19. Methodology, sources & disclosure
This guide is published by PushNotice, reviewed by its editorial team, and written to be useful whether or not you use our product. Every vendor capability and price was verified against that vendor's own documentation or pricing page in August 2026. No statistics, ROI benchmarks, retention improvement figures, market share numbers, ratings, reviews or customer results are asserted anywhere in this article. Where a capability could not be confirmed from an official source, it is marked "Not verified" rather than inferred.
How to read the different kinds of claim in this guide
Six categories of statement appear here and they are not equivalent. Vendor information — capabilities, plan contents, published limits — comes from the vendor's own product pages, help centres and developer documentation, dated to August 2026. Pricing information comes from official pricing pages only, quoted as published, with the model stated alongside the figure. Platform documentation — the Apple Wallet and Google Wallet behaviour in Section 10 — is quoted from Apple's and Google's own developer documentation. Independent research is not cited, because we found no source in this category with a disclosed sample and methodology worth relying on. PushNotice analysis covers the seven-category taxonomy, all eight frameworks, the use-case recommendations and every editorial judgement, and is labelled as such. Illustrative examples — the automation table in Section 12 — are templates to adapt, never presented as tested campaigns.
How vendors were selected and verified
Vendors were included on three tests: current self-positioning around retention, loyalty, lifecycle or churn; native ownership of at least one of the four retention jobs; and verifiability from published material. Third-party "best of" listicles, review aggregators and competitor comparison pages were deliberately not used as evidence for any factual claim — they appeared in research and were excluded. Where two official sources conflicted, both are noted rather than resolved in whichever direction suited the argument: Google's own FAQ still states that developer-authored push notifications are not supported, while Google's REST reference and six use-case guides document TEXT_AND_NOTIFY and notifyPreference. We treat the current guides and reference as authoritative and flag the FAQ as stale.
Known limitations of this comparison
- Klaviyo's core plan pricing could not be read from klaviyo.com/pricing, which renders client-side. Only its published add-on prices and the free-tier limits from its help centre are quoted here; no core plan figure is asserted.
- Braze, Insider One and Salesforce Data 360 publish no usable pricing. Any figure for them found elsewhere is unverifiable and is not reproduced.
- HubSpot's Starter pricing is promotional at the time of checking — $7 per seat per month is flagged on HubSpot's own page as new customers only for a limited time, against a standard $20. Treat the standard rate as the planning figure.
- Several wallet claims are one-sided. Square's Apple Wallet support is documented and its Google Wallet support was not found; Salesforce's Google Wallet integration is documented and no Apple Wallet equivalent for Loyalty Management was found. Both are reported as split rather than flattened.
- Absence of evidence is reported as such. "Not verified" throughout means the vendor does not publish it and we did not find it — not that the capability is impossible.
Why there are no benchmarks, ratings or ROI figures
Deliberate. Retention benchmarks are widely republished without a disclosed sample, period or methodology, and figures in this category frequently trace back to vendor marketing rather than to research. Ratings and review scores reflect who asked for reviews, not who solves your problem. A number that looks authoritative and is wrong is worse than no number, because it becomes someone's target. Section 13 gives a measurement framework instead, so you can generate the only benchmark that is true for your business — your own baseline, measured against a control.
Editorial policy and conflict of interest
PushNotice sells wallet-based customer engagement, which is one of seven categories described here and the right answer for some readers and not others. We manage that conflict by stating it before the comparison table rather than after it, by applying the same verification standard and the same limitations column to our own product, by naming five use cases in Section 6 where another platform fits better, and by listing six things PushNotice does not provide in Section 16. Nothing here is paid placement. No vendor reviewed this guide before publication, and no vendor was contacted for approval of how it is described.
Review and updates
Published 30 August 2026 and last reviewed 30 August 2026 by the PushNotice Editorial Team. Vendor capabilities, plan contents and prices in this category change frequently — Yotpo deprecated its own email and SMS products, Salesforce renamed two of the products named here, and Segment moved domains, all within roughly a year. Re-verify any figure before making a purchase decision on it. Corrections are welcome via the PushNotice contact page.
About the author
Sajid Ali — Founder & CEO, PushNotice. Sajid builds and sells retention software for a living. He works directly on wallet pass design, pass-update and notification logic, and the loyalty and retention programmes small businesses run on top of them, and he reads Apple's Wallet Passes and Google's Wallet API documentation as a working requirement rather than as research. That is the perspective behind this guide's central argument — that "customer retention software" describes seven non-substitutable categories, and that most bad purchases in this market are category errors rather than vendor errors. He is not an independent analyst: PushNotice competes in one of the seven categories described here, which is why Section 19 sets out exactly how that conflict is managed. Connect on LinkedIn.
Reviewed by the PushNotice Editorial Team. The team verified every vendor capability and price against the vendor's own published material, checked every Apple and Google platform claim against primary developer documentation, confirmed that no statistic, benchmark, rating, review or customer result is asserted anywhere in the article, and checked that every PushNotice claim in Section 16 corresponds to something PushNotice publishes.
Sources
All sources are the vendor's or platform owner's own material. Consulted 30 August 2026 unless otherwise noted.
Vendor product and pricing pages
- Klaviyo — homepage positioning, product pages and help centre, including published add-on pricing and free-tier limits. klaviyo.com · help.klaviyo.com — billing and add-ons · help.klaviyo.com — winback flow
- Braze — product, pricing and partner documentation, including the mobile wallet partner page naming PassKit. braze.com/pricing · braze.com — mobile wallet partners
- HubSpot — Marketing Hub and Service Hub pricing pages, including onboarding fees, and the SMS knowledge-base article. hubspot.com/pricing/marketing · hubspot.com/pricing/service · knowledge.hubspot.com — SMS
- Salesforce — Loyalty Management product and pricing pages, marketing pricing, and the Google Wallet integration documentation. salesforce.com — Loyalty Management pricing · salesforce.com — marketing pricing · help.salesforce.com — Google Wallet integration
- Twilio Segment — product and pricing pages, including Connections list pricing and monthly tracked user definitions. twilio.com/segment · twilio.com — Connections pricing
- Insider One — positioning, channel list and pricing-model statements. insiderone.com · insiderone.com/channels
- Smile.io — pricing page, supported platforms and email documentation. smile.io/pricing · help.smile.io — supported platforms · help.smile.io — segments require an email app
- Yotpo — Loyalty pricing page, loyalty product page, and the official email and SMS migration notice. yotpo.com — loyalty pricing · yotpo.com — email and SMS migration
- LoyaltyLion — pricing page and the Loyalty Pass wallet feature pages. loyaltylion.com/pricing · loyaltylion.com — Loyalty Pass
- Marsello — pricing page and the Apple Wallet, Google Wallet and proximity notification help articles. marsello.com/pricing · help.marsello.com — Apple Wallet · help.marsello.com — proximity notifications
- Square — Loyalty product page, unified pricing, and the April 2025 Apple Wallet digital loyalty pass announcement. squareup.com/loyalty · squareup.com/pricing
- Stamped — pricing page and the Loyalty and Lifecycle product pages. stamped.io/pricing · stamped.io — loyalty
- PassKit — pricing model, live rate card and integrations directory. passkit.com/pricing/rates · help.passkit.com — wallet push notifications
- Loopy Loyalty — pricing page and the push message and segment documentation. loopyloyalty.com/pricing · docs.loopyloyalty.com — segment filters
- Boomerangme — pricing page and the RFM analysis and geo-push documentation. boomerangme.com/pricing · docs.boomerangme.cards — RFM analysis
- Churnkey and Raaft — product and pricing pages for subscription churn deflection. churnkey.co/pricing · raaft.io/pricing
- PushNotice — published product and pricing pages, for the capabilities in Section 16. pushnotice.io
Platform documentation
- Apple Developer — Adding a Web Service to Update Passes. Source of the five-step pass update flow and the statement that the update push uses "an empty JSON dictionary for the payload." developer.apple.com
- Apple Developer — PassFieldContent (Wallet Passes). Source of the
changeMessagedefinition and the requirement to provide a value for the system to show a change notification. developer.apple.com - Apple Developer — Showing a Pass on the Lock Screen. Source of date and location relevance behaviour and the ten-location limit. developer.apple.com
- Apple Developer — Wallet Developer Guide (archived). Source of the statement that relevance information "doesn't present alerts or post notifications." developer.apple.com
- Google for Developers — Trigger push notifications (Google Wallet, loyalty cards). Source of the three-messages and three-updates per 24 hours limits, the throttling statement and the user notification requirement. developers.google.com
- Google for Developers — Message (Google Wallet API REST reference). Source of the
TEXTandTEXT_AND_NOTIFYdefinitions. developers.google.com - Google for Developers — Release notes (Google Wallet API). Source of the October 2025 nearby-passes geofence notification launch and the ten merchant locations per class and object limit. developers.google.com
Frameworks, matrices, checklists, the decision tree and the category taxonomy in this guide are original PushNotice analysis and are labelled as such. They are structures to test against your own business, not findings. Automation examples are illustrative templates and no performance results are claimed for them.
Related guides
This page owns one question: "I need software that can help my business retain more customers, and I want to understand which type of tool and which platform is right for me." It is deliberately not a retention strategy guide, not a loyalty software comparison and not a wallet marketing explainer. For the strategy that should precede the purchase, read customer retention strategies. For the loyalty category specifically, read best loyalty software for DTC brands and free loyalty software. For the wallet channel, read what is wallet marketing. For push specifically, read push notification marketing and push notification automation. For running retention in a physical location, read local business retention and in-store marketing.
Cite this guide
- APA: Ali, S. (2026). Customer Retention Software: Tools Compared (2026). PushNotice. https://pushnotice.io/blog/customer-retention-software
- MLA: Ali, Sajid. "Customer Retention Software: Tools Compared (2026)." PushNotice, 30 Aug. 2026, pushnotice.io/blog/customer-retention-software.