How we think about loyalty.

No customer app

The average user has sixty icons on their phone and opens ten. A loyalty app for a single café will not be in the ten. We have watched this play out in operator interviews: branded café apps that the operator paid to build are checked weekly by the operator, never opened by customers, and quietly retired after a year. We chose the wallet instead. Apple Wallet, Google Wallet, Samsung Wallet. The apps every modern phone opens daily. Customers install with one tap from a link or QR. No app store, no review process, no icon clutter, no abandoned install.

No phone number, no OTP

"What's your mobile number, sir?" is the interaction Indian loyalty programs trained cafés to perform. It is friction at the worst moment, when the customer is paying, the counter is busy, and a queue is forming behind them. It is also a privacy ask the premium customer rejects. We chose a one-tap wallet install with no number, no OTP, no signup wall. The counter interaction becomes "show me your pass." The customer holds up their phone, the barista scans the QR, the stamp lands. Faster, friendlier, exclusive instead of intrusive.

No WhatsApp, SMS, or email blast

WhatsApp is the app people use to talk to their family. Marketing messages there get muted, archived, resented. Per-send economics through Meta's WhatsApp Business API also mean the cost curve compounds the more customers you have, which is the opposite of how a loyalty program should scale. We chose the wallet OS's lock-screen channel instead. No template, no send button, no per-message fee, no spam fatigue. Stamps added, rewards earned, new tiers unlocked, all surface on the lock screen the next time the customer touches their phone. Pure presence, not broadcast.

No POS integration

This is the choice we get most often questioned and the most deliberate one. POS integration sounds like a convenience, and on the surface it is. Points credit automatically, no staff effort. But automatic loyalty is invisible loyalty, and invisible loyalty does not form habits.

The behavioral mechanic we want is the card-flashing ritual. Customer opens the wallet, barista nods, cashier scans the QR. Three seconds, one moment of mutual recognition, every visit. Skip the ritual and the customer forgets the loyalty program exists. The data shows up in the POS report; the relationship does not show up in the customer's mind.

POS coupling also makes the loyalty layer hostage to the POS vendor. Switch your POS next year and watch the loyalty program break, or worse, watch the new POS vendor force you onto their loyalty product. We built Brava to outlast your stack choices. Switch your POS, your delivery platform, your reservations tool, anything you like. The wallet pass keeps running.

No feature bloat

The default shape of restaurant CRMs in India is a dashboard kitchen sink: every metric, every chart, every campaign type, every channel. The operator drowns in it. The features that drive revenue blend into the features that look impressive in a sales demo, and the operator cannot tell which is which. We chose the actionable layer. Fewer charts, more answers.

Wallet-native delivery, three platforms

Apple Wallet, Google Wallet, Samsung Wallet. One operator dashboard, three customer ecosystems. The pass installs from a link or QR in one tap. No app review, no signup form, no friction. The pass surfaces on the lock screen the next time the customer touches their phone after an update fires. Stamp added, they see it. Reward unlocked, they see it. Tier changed, they see it. No campaign to design, no send to schedule, no template to write. The wallet OS handles delivery.

Geo-fenced re-engagement at ~100m

When the customer walks within roughly 100 meters of one of your locations, the wallet OS surfaces the pass on the lock screen. The "you exist" reminder fires at the exact moment the customer can act on it. Passive recall, automatic, zero per-message cost. We configure the geo radius and the message per-location in the dashboard; the wallet OS does the rest.

Sixteen behavioral segments across three analytical lenses

The standard restaurant CRM gives you "New", "Active", "Lapsed". Three buckets, no nuance, no action. Brava ships three lenses on top of the same underlying customer database, sixteen distinct categories across them, each with a recommended next step attached:

• A 7-segment RFM-flavored taxonomy (Dormant, New, Casual, Loyal, VIP, At Risk, Lost) that crosses redemption behavior with recency. A high-spend customer who never redeems is not a VIP, just a customer. A regular who has not shown up in 60 days is not Loyal anymore, they are At Risk. Recency wins because the action you should take is the same regardless of historical frequency.
• A 6-tier engagement classification (Power, Frequent, Regular, Casual, Trialer, Dormant) for the merchant who wants the visit-frequency lens, cross-cut by recency to surface where customers are in their lifecycle.
• A 13-segment customer journey sankey that shows lifecycle flow: how customers move from first visit to first redemption to repeat redeemer, and where the funnel leaks.

The VIP threshold adapts to your business. A 50-customer kirana and a 10,000-customer chain both see meaningful VIPs because the cutoff is the 90th percentile of YOUR revenue distribution, not a hardcoded number. Same names everywhere, calibrated to each operator's actual customer base.

Engagement funnels, not just charts

Charts tell you what happened. Engagement funnels tell you where customers are getting stuck and what to do next. The cleanest example is the leakage-rate metric: the percentage of your At Risk and Lost customers who never redeemed before lapsing. A high leakage rate (above 50%) means your reward threshold is too high or the program is not being explained at the counter. A low leakage rate means customers who try the program understand it; the lapses are normal lifecycle attrition. Either way, the number tells you what to fix. That is the difference between a chart and a funnel.

Actionable insights with playbooks attached

Every segment in the analytics centerpiece has a recommended action written into the dashboard. Not generic ("send a campaign"). Specific. Earn the second visit from your New customers with a "double stamps if you come back in 7 days" wallet push. Reward your Loyal customers with surprise perks and advocacy asks. Treat VIPs like family with hand-written notes, and default them out of generic promo blasts so you do not burn the relationship. Hit At Risk with a time-bounded win-back. Give Lost one last reactivation shot, then leave them alone, because re-pinging an opted-in but uninterested customer burns the opt-in.

These are not templates we invented in a planning meeting. They are the playbook that emerged from sitting with real operators and watching what actually moved repeat-visit rates. The dashboard surfaces them at the moment of decision.

The card-flashing ritual

Customer opens the wallet. Barista nods. Cashier scans the QR. Three seconds of interaction, one moment of mutual recognition, every visit. That ritual is the loyalty program. Everything else is infrastructure that makes the ritual easy.